System is crashing if I am using more then one disk on scsi controler :(

System is crashing if I am using more then one disk on scsi controler :(

Post by Maciek Zobnio » Wed, 28 May 2003 18:59:22



System: Pentium3 600MHz, scsi PCI controler with chipset sym53c895, 400W
power supply. System was stable quite long time (320 days uptime) until
I decided to add an additional scsi disk. After I am adding disk system
is crashing after a few minutes. The system is recognizing all disks
properly, I can mount it and format...until crash :(. Below you can find
a kernel dump output:

May 26 19:48:06 prod-mta-1 kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000013
May 26 19:48:06 prod-mta-1 kernel:  printing eip:
May 26 19:48:06 prod-mta-1 kernel: c013f561
May 26 19:48:06 prod-mta-1 kernel: *pde = 00000000
May 26 19:48:06 prod-mta-1 kernel: Oops: 0000
May 26 19:48:06 prod-mta-1 kernel: CPU:    0
May 26 19:48:06 prod-mta-1 kernel: EIP:    0010:[<c013f561>]    Not tainted
May 26 19:48:06 prod-mta-1 kernel: EFLAGS: 00010286
May 26 19:48:06 prod-mta-1 kernel: eax: ffffffff   ebx: 00000000   ecx:
00000003   edx: d6a3e160
May 26 19:48:06 prod-mta-1 kernel: esi: d6a3e160   edi: 00000000   ebp:
00000145   esp: d5601f38
May 26 19:48:06 prod-mta-1 kernel: ds: 0018   es: 0018   ss: 0018
May 26 19:48:06 prod-mta-1 kernel: Process screen (pid: 2158,
stackpage=d5601000)
May 26 19:48:06 prod-mta-1 kernel: Stack: d5601f54 00000008 d5600000
7fffffff 00000003 00000000 00000007 00000000
May 26 19:48:06 prod-mta-1 kernel:        d3036000 00000020 bfffe540
d7cc1b00 00000400 c013f9f9 00000400 d5601f90
May 26 19:48:06 prod-mta-1 kernel:        d5601f8c c14296a0 d6a3e160
00000080 d7cc1800 7fffffff d7cc1800 d7cc1880
May 26 19:48:06 prod-mta-1 kernel: Call Trace:    [<c013f9f9>] [<c0106d93>]
May 26 19:48:06 prod-mta-1 kernel:
May 26 19:48:06 prod-mta-1 kernel: Code: 8b 40 14 85 c0 74 0c 8b 4c 24
14 51 56 ff d0 89 c5 58 5a 89
May 26 19:48:06 prod-mta-1 kernel:  <1>Unable to handle kernel NULL
pointer dereference at virtual address 00000007
May 26 19:48:06 prod-mta-1 kernel:  printing eip:
May 26 19:48:06 prod-mta-1 kernel: c0124938
May 26 19:48:06 prod-mta-1 kernel: *pde = 00000000
May 26 19:48:06 prod-mta-1 kernel: Oops: 0000
May 26 19:48:06 prod-mta-1 kernel: CPU:    0
May 26 19:48:06 prod-mta-1 kernel: EIP:    0010:[<c0124938>]    Not tainted
May 26 19:48:06 prod-mta-1 kernel: EFLAGS: 00010246
May 26 19:48:06 prod-mta-1 kernel: eax: ffffffff   ebx: d6ebace0   ecx:
00000013   edx: d6ebace0
May 26 19:48:06 prod-mta-1 kernel: esi: 0002b000   edi: d7eccaa0   ebp:
401e6000   esp: d5601dd4
May 26 19:48:06 prod-mta-1 kernel: ds: 0018   es: 0018   ss: 0018
May 26 19:48:06 prod-mta-1 kernel: Process screen (pid: 2158,
stackpage=d5601000)
May 26 19:48:06 prod-mta-1 kernel: Stack: d6c84540 d74b3f64 00000046
d5601e00 00000086 d7eccaa0 d5601f04 d5600000
May 26 19:48:06 prod-mta-1 kernel:        0000000b c011438a d7eccaa0
d7eccaa0 c01184c1 d7eccaa0 d5601f04 c0229163
May 26 19:48:06 prod-mta-1 kernel:        c011209e c023636a 00000000
c010735d 00000000 c02457bb c022332e c0229163
May 26 19:48:06 prod-mta-1 kernel: Call Trace:    [<c011438a>]
[<c01184c1>] [<c011209e>] [<c010735d>] [<c0112427>]
May 26 19:48:06 prod-mta-1 kernel:   [<c018c153>] [<c012c8d0>]
[<c0113184>] [<c01120b0>] [<c0106e84>] [<c013f561>]
May 26 19:48:06 prod-mta-1 kernel:   [<c013f9f9>] [<c0106d93>]
May 26 19:48:06 prod-mta-1 kernel:
May 26 19:48:06 prod-mta-1 kernel: Code: 8b 40 08 74 06 ff 80 04 01 00
00 8b 53 28 85 d2 74 09 8b 43
May 26 19:48:06 prod-mta-1 kernel:  <1>Unable to handle kernel NULL
pointer dereference at virtual address 00000023
May 26 19:48:06 prod-mta-1 kernel:  printing eip:
May 26 19:48:06 prod-mta-1 kernel: c0131d8a
May 26 19:48:06 prod-mta-1 kernel: *pde = 00000000
May 26 19:48:06 prod-mta-1 kernel: Oops: 0000
May 26 19:48:06 prod-mta-1 kernel: CPU:    0
May 26 19:48:06 prod-mta-1 kernel: EIP:    0010:[<c0131d8a>]    Not tainted
May 26 19:48:06 prod-mta-1 kernel: EFLAGS: 00010286
May 26 19:48:06 prod-mta-1 kernel: eax: ffffffff   ebx: d6a3e160   ecx:
00000000   edx: d6a3e160
May 26 19:48:06 prod-mta-1 kernel: esi: 00000000   edi: d572d8c0   ebp:
00000003   esp: d5601c78
May 26 19:48:06 prod-mta-1 kernel: ds: 0018   es: 0018   ss: 0018
May 26 19:48:06 prod-mta-1 kernel: Process screen (pid: 2158,
stackpage=d5601000)May 26 19:48:06 prod-mta-1 kernel: Stack: 0000000f
d572d8c0 00000001 c0117eec d6a3e160 d572d8c0 00000000 d5601da0
May 26 19:48:06 prod-mta-1 kernel:        d5600000 0000000b c01184df
d572d8c0 00000000 d74b2000 d74b3f64 d5601da0
May 26 19:48:06 prod-mta-1 kernel:        c0229163 00000007 c023636a
c0240018 c0220018 ffffffef c0107369 00000010
May 26 19:48:06 prod-mta-1 kernel: Call Trace:    [<c0117eec>]
[<c01184df>] [<c0107369>] [<c0112427>] [<c0187ce9>]
May 26 19:48:06 prod-mta-1 kernel:   [<c012b355>] [<c0121e65>]
[<c0122278>] [<c01120b0>] [<c0106e84>] [<c0124938>]
May 26 19:48:06 prod-mta-1 kernel:   [<c011438a>] [<c01184c1>]
[<c011209e>] [<c010735d>] [<c0112427>] [<c018c153>]
May 26 19:48:06 prod-mta-1 kernel:   [<c012c8d0>] [<c0113184>]
[<c01120b0>] [<c0106e84>] [<c013f561>] [<c013f9f9>]
May 26 19:48:06 prod-mta-1 kernel:   [<c0106d93>]
May 26 19:48:06 prod-mta-1 kernel:
May 26 19:48:06 prod-mta-1 kernel: Code: 8b 50 24 85 d2 74 07 53 ff 50
24 59 89 c6 57 53 e8 91 40 01

If you have an idea please answer me!
Thanks
Maciej Zobniow

 
 
 

System is crashing if I am using more then one disk on scsi controler :(

Post by Dr. J.C.Hil » Wed, 28 May 2003 21:02:12


Details of the disks would be helpful. I assume that the SCSI
termination has been set up correctly (ie. only on the devices
at either end of the chain - typically though not always the controller
and the final disk on the SCSI bus)?

Regards,
John Hill


> System: Pentium3 600MHz, scsi PCI controler with chipset sym53c895, 400W
> power supply. System was stable quite long time (320 days uptime) until
> I decided to add an additional scsi disk. After I am adding disk system
> is crashing after a few minutes. The system is recognizing all disks
> properly, I can mount it and format...until crash :(. Below you can find
> a kernel dump output:

> May 26 19:48:06 prod-mta-1 kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000013
> May 26 19:48:06 prod-mta-1 kernel:  printing eip:
> May 26 19:48:06 prod-mta-1 kernel: c013f561
> May 26 19:48:06 prod-mta-1 kernel: *pde = 00000000
> May 26 19:48:06 prod-mta-1 kernel: Oops: 0000
> May 26 19:48:06 prod-mta-1 kernel: CPU:    0
> May 26 19:48:06 prod-mta-1 kernel: EIP:    0010:[<c013f561>]    Not tainted
> May 26 19:48:06 prod-mta-1 kernel: EFLAGS: 00010286
> May 26 19:48:06 prod-mta-1 kernel: eax: ffffffff   ebx: 00000000   ecx:
> 00000003   edx: d6a3e160
> May 26 19:48:06 prod-mta-1 kernel: esi: d6a3e160   edi: 00000000   ebp:
> 00000145   esp: d5601f38
> May 26 19:48:06 prod-mta-1 kernel: ds: 0018   es: 0018   ss: 0018
> May 26 19:48:06 prod-mta-1 kernel: Process screen (pid: 2158,
> stackpage=d5601000)
> May 26 19:48:06 prod-mta-1 kernel: Stack: d5601f54 00000008 d5600000
> 7fffffff 00000003 00000000 00000007 00000000
> May 26 19:48:06 prod-mta-1 kernel:        d3036000 00000020 bfffe540
> d7cc1b00 00000400 c013f9f9 00000400 d5601f90
> May 26 19:48:06 prod-mta-1 kernel:        d5601f8c c14296a0 d6a3e160
> 00000080 d7cc1800 7fffffff d7cc1800 d7cc1880
> May 26 19:48:06 prod-mta-1 kernel: Call Trace:    [<c013f9f9>] [<c0106d93>]
> May 26 19:48:06 prod-mta-1 kernel:
> May 26 19:48:06 prod-mta-1 kernel: Code: 8b 40 14 85 c0 74 0c 8b 4c 24
> 14 51 56 ff d0 89 c5 58 5a 89
> May 26 19:48:06 prod-mta-1 kernel:  <1>Unable to handle kernel NULL
> pointer dereference at virtual address 00000007
> May 26 19:48:06 prod-mta-1 kernel:  printing eip:
> May 26 19:48:06 prod-mta-1 kernel: c0124938
> May 26 19:48:06 prod-mta-1 kernel: *pde = 00000000
> May 26 19:48:06 prod-mta-1 kernel: Oops: 0000
> May 26 19:48:06 prod-mta-1 kernel: CPU:    0
> May 26 19:48:06 prod-mta-1 kernel: EIP:    0010:[<c0124938>]    Not tainted
> May 26 19:48:06 prod-mta-1 kernel: EFLAGS: 00010246
> May 26 19:48:06 prod-mta-1 kernel: eax: ffffffff   ebx: d6ebace0   ecx:
> 00000013   edx: d6ebace0
> May 26 19:48:06 prod-mta-1 kernel: esi: 0002b000   edi: d7eccaa0   ebp:
> 401e6000   esp: d5601dd4
> May 26 19:48:06 prod-mta-1 kernel: ds: 0018   es: 0018   ss: 0018
> May 26 19:48:06 prod-mta-1 kernel: Process screen (pid: 2158,
> stackpage=d5601000)
> May 26 19:48:06 prod-mta-1 kernel: Stack: d6c84540 d74b3f64 00000046
> d5601e00 00000086 d7eccaa0 d5601f04 d5600000
> May 26 19:48:06 prod-mta-1 kernel:        0000000b c011438a d7eccaa0
> d7eccaa0 c01184c1 d7eccaa0 d5601f04 c0229163
> May 26 19:48:06 prod-mta-1 kernel:        c011209e c023636a 00000000
> c010735d 00000000 c02457bb c022332e c0229163
> May 26 19:48:06 prod-mta-1 kernel: Call Trace:    [<c011438a>]
> [<c01184c1>] [<c011209e>] [<c010735d>] [<c0112427>]
> May 26 19:48:06 prod-mta-1 kernel:   [<c018c153>] [<c012c8d0>]
> [<c0113184>] [<c01120b0>] [<c0106e84>] [<c013f561>]
> May 26 19:48:06 prod-mta-1 kernel:   [<c013f9f9>] [<c0106d93>]
> May 26 19:48:06 prod-mta-1 kernel:
> May 26 19:48:06 prod-mta-1 kernel: Code: 8b 40 08 74 06 ff 80 04 01 00
> 00 8b 53 28 85 d2 74 09 8b 43
> May 26 19:48:06 prod-mta-1 kernel:  <1>Unable to handle kernel NULL
> pointer dereference at virtual address 00000023
> May 26 19:48:06 prod-mta-1 kernel:  printing eip:
> May 26 19:48:06 prod-mta-1 kernel: c0131d8a
> May 26 19:48:06 prod-mta-1 kernel: *pde = 00000000
> May 26 19:48:06 prod-mta-1 kernel: Oops: 0000
> May 26 19:48:06 prod-mta-1 kernel: CPU:    0
> May 26 19:48:06 prod-mta-1 kernel: EIP:    0010:[<c0131d8a>]    Not tainted
> May 26 19:48:06 prod-mta-1 kernel: EFLAGS: 00010286
> May 26 19:48:06 prod-mta-1 kernel: eax: ffffffff   ebx: d6a3e160   ecx:
> 00000000   edx: d6a3e160
> May 26 19:48:06 prod-mta-1 kernel: esi: 00000000   edi: d572d8c0   ebp:
> 00000003   esp: d5601c78
> May 26 19:48:06 prod-mta-1 kernel: ds: 0018   es: 0018   ss: 0018
> May 26 19:48:06 prod-mta-1 kernel: Process screen (pid: 2158,
> stackpage=d5601000)May 26 19:48:06 prod-mta-1 kernel: Stack: 0000000f
> d572d8c0 00000001 c0117eec d6a3e160 d572d8c0 00000000 d5601da0
> May 26 19:48:06 prod-mta-1 kernel:        d5600000 0000000b c01184df
> d572d8c0 00000000 d74b2000 d74b3f64 d5601da0
> May 26 19:48:06 prod-mta-1 kernel:        c0229163 00000007 c023636a
> c0240018 c0220018 ffffffef c0107369 00000010
> May 26 19:48:06 prod-mta-1 kernel: Call Trace:    [<c0117eec>]
> [<c01184df>] [<c0107369>] [<c0112427>] [<c0187ce9>]
> May 26 19:48:06 prod-mta-1 kernel:   [<c012b355>] [<c0121e65>]
> [<c0122278>] [<c01120b0>] [<c0106e84>] [<c0124938>]
> May 26 19:48:06 prod-mta-1 kernel:   [<c011438a>] [<c01184c1>]
> [<c011209e>] [<c010735d>] [<c0112427>] [<c018c153>]
> May 26 19:48:06 prod-mta-1 kernel:   [<c012c8d0>] [<c0113184>]
> [<c01120b0>] [<c0106e84>] [<c013f561>] [<c013f9f9>]
> May 26 19:48:06 prod-mta-1 kernel:   [<c0106d93>]
> May 26 19:48:06 prod-mta-1 kernel:
> May 26 19:48:06 prod-mta-1 kernel: Code: 8b 50 24 85 d2 74 07 53 ff 50
> 24 59 89 c6 57 53 e8 91 40 01

> If you have an idea please answer me!
> Thanks
> Maciej Zobniow


 
 
 

System is crashing if I am using more then one disk on scsi controler :(

Post by Maciek Zobnio » Wed, 28 May 2003 22:15:48



> Details of the disks would be helpful. I assume that the SCSI
> termination has been set up correctly (ie. only on the devices
> at either end of the chain - typically though not always the controller
> and the final disk on the SCSI bus)?

Thanks for your answer.
Details of the disk:

  Vendor: IBM       Model: IC35L018UWD210-0  Rev: S5BS
   Type:   Direct-Access                      ANSI SCSI revision: 03

The second one is same (18GB, IBM).
Both disks are on same cable and last is terminated. Hardware
configurations seems to be properly. It could that maybe damaged cable
generating this problem?

Best Regards
Maciej Zobniow

 
 
 

System is crashing if I am using more then one disk on scsi controler :(

Post by Dr. J.C.Hil » Thu, 29 May 2003 18:07:15




>> Details of the disks would be helpful. I assume that the SCSI
>> termination has been set up correctly (ie. only on the devices
>> at either end of the chain - typically though not always the controller
>> and the final disk on the SCSI bus)?

> Thanks for your answer.
> Details of the disk:

>  Vendor: IBM       Model: IC35L018UWD210-0  Rev: S5BS
>   Type:   Direct-Access                      ANSI SCSI revision: 03

> The second one is same (18GB, IBM).
> Both disks are on same cable and last is terminated. Hardware
> configurations seems to be properly. It could that maybe damaged cable
> generating this problem?

Very possibly - certainly worth trying a replacement cable if you
have one. You might also try removing the old disk and putting the
new disk in its location - whether this works or fails should tell
you whether the new disk is to blame or not.

Regards,
John Hill

- Show quoted text -

Quote:

> Best Regards
> Maciej Zobniow

 
 
 

System is crashing if I am using more then one disk on scsi controler :(

Post by Michael Buchenriede » Thu, 29 May 2003 15:51:31


[...]

Quote:>  Vendor: IBM       Model: IC35L018UWD210-0  Rev: S5BS
>   Type:   Direct-Access                      ANSI SCSI revision: 03
>The second one is same (18GB, IBM).
>Both disks are on same cable and last is terminated.

[...]

That's wrong. You'll need _one_ device providing termination power,
and an active terminator on the last connector of the internal SCSI
cable. Assuming the SCSI adaptar card is the other end of the SCSI
chain, its termination setting must be enabled as well.

Michael
--

          Lumber Cartel Unit #456 (TINLC) & Official Netscum
    Note: If you want me to send you email, don't munge your address.

 
 
 

1. This clone thing...am I stupid, or am I right?


says...

I admire your passion, Chris..

The only issues which have kept myself from looking seriously at Linux
would be:

* It's Unix and the learning curve to start getting productive strikes me
as probably very steep

* It doesn't support plug-and-play.  If your hardware doesn't have Linux
drivers, it don't play..

* Not nearly the amount of developers out there doing stuff for Linux as
there are for Wintel.  Can I get MS Office for Linux?  Can I get
Photoshop for Linux?  Can I get QuarkXpress for Linux? etc.. a big turn
off for me.

--
Reuben King
Email: "reuben at texas dot net" (in plain english to foil spam-bots.
grrr!)

2. password change script

3. IDA mailer problem with MX recs

4. I am with the following error, when i am running lilo...

5. some dbm passwords don't work anymore

6. Am I touchy? Or am I right?

7. How to get dtcm to alert me if not running

8. Am I seeing IPv5, or am I hallucinating?

9. I am buying an Ultra 5 but am lost in part numbers ....

10. I am in text mode, what browser am I running....

11. I am si**y am I?

12. Boot disk problems: Am I a moron, or is my system not supported?