Skip to contentSkip to conversation

Adaptect 2940u2 w/ 2.4.20 or 2.5.59

DISCUSSION Anthony R. Mattke 2 participants 4 messages Mar 27, 2003 – Apr 3, 2003

lore
Share & tools
lore

Anthony R. Mattke

author
#0 lore raw

I have a current linux desktop curring 2.4.19 that has been running fine for ever. Altho, when I atempted to do an update to 2.4.20, I was rather surprised to see that my machine kernel panics on boot, just as it would normally init the scsi bus.

The machine in question is an x86 SMP system (p3) with an adaptect 2940u2 card.. it also has another scsi controller on the mobo that is disabled in bios. it is a 2940uw.

Is there any reason why the newer kernel has a problem with this card ? I have tried both adaptect drivers for this card.. the new one that started shipping in .20 and the olderone..

Has anyone else seen this problem? Its a current show stopper, I need to reinstall my desktop, but the newer version of slackware ships with 2.4.20.

Any help would be appreciated..

Thanks..

Signature · 1 line
Anthony R. Mattke <[email protected]>
#1 lore raw
Quoted 4 lines

I have a current linux desktop curring 2.4.19 that has been running fine for ever. Altho, when I atempted to do an update to 2.4.20, I was rather surprised to see that my machine kernel panics on boot, just as it would normally init the scsi bus.

What is the panic?

--
Justin

author
#2 lore raw

Ok, this is the kernel message (i dont know of a good way to log these, so i hand typed it from a laptop)

This is from booting the slackware9.0 install cd, i get the same panic when booting 2.4.20 on my machine (the device not available because of resource colissions is normal, i see that in 2.4.19 and everything seems to work ok..)

Detecting Adaptec I20 RAID controllers...
PCI: Device 00:0b.1 not available because of resource collisions
PCI: Device 00:0b.0 not available because of resource collisions

Unable to handle kernel NULL pointer reference at virtual address

00000000
printing eip:
c024e0db
*pde = 00000000

Oops: 0002

CPU: 0
EIP: 0010:[<c024e0db>] Not tainted
EFLAGS: 00010246
eax: 00000000 ebx: cfda0c00 ecx: c033e974 edx: 00000000
esi: c033eae0 edi: cfdaf50 ebp: c0340718 esp: cfda7ec8
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 1, stackpage=cfda7000)

Stack: cfda0c00 cfd82a00 c02345d6 c033eae0 cfda0c00 cfd82a00 c022d562
cfd82a00
       5f636861 3a696370 31313a30 c000303a c12c5188 00000046 00000003
00000020
       c12c555c c12c5554 00000002 00000021 c012f276 c12c5554 00000002
00000244
Call Trace:    [<c02345d6>] [<c022d562>] [<c012f276>] [<c0214599>]

[<c024e031>]
[<c024e0c7>] [<c022d5fb>] [<c0228ebb>] [<c0105000>] [<c0213651>]
[<c0105000>]
[<c010503b>] [<c0104000>] [<c0107416>] [<c0105030>]

Code: 89 02 c7 06 00 00 00 00 8b 1d e8 0c 34 c0 81 fb e8 0c 34 c0
 <0>Kernel Panic: Attempted to kill init!

let me know if you need anything else.. I really appreciate the help.. and yeah.. sorry about the typos.. It was late when I wrote the first email and Adaptec seemed to be a hard word to type at the time.

Thanks for the help !

Quoted 15 lines · Justin T. Gibbs
Quoted 4 lines

I have a current linux desktop curring 2.4.19 that has been running fine for ever. Altho, when I atempted to do an update to 2.4.20, I was rather surprised to see that my machine kernel panics on boot, just as it would normally init the scsi bus.

What is the panic?

--
Justin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 1 line
Anthony R. Mattke <[email protected]>
author
#3 lore raw

Re: Adaptec 2940u2 w/ 2.4.20 or 2.5.59

Anyone have a clue as to why i'm getting this panic after uprading from 2.4.19 to 2.4.20.. I have been unable to boot a development version or 2.4.20.

This machine is a intel SMP all scsi system

I can supply more info as needed.. thanks

Quoted 63 lines · Anthony R. Mattke

Ok, this is the kernel message (i dont know of a good way to log these, so i hand typed it from a laptop)

This is from booting the slackware9.0 install cd, i get the same panic when booting 2.4.20 on my machine (the device not available because of resource colissions is normal, i see that in 2.4.19 and everything seems to work ok..)

Detecting Adaptec I20 RAID controllers...
PCI: Device 00:0b.1 not available because of resource collisions
PCI: Device 00:0b.0 not available because of resource collisions

Unable to handle kernel NULL pointer reference at virtual address

00000000
printing eip:
c024e0db
*pde = 00000000

Oops: 0002

CPU: 0
EIP: 0010:[<c024e0db>] Not tainted
EFLAGS: 00010246
eax: 00000000 ebx: cfda0c00 ecx: c033e974 edx: 00000000
esi: c033eae0 edi: cfdaf50 ebp: c0340718 esp: cfda7ec8
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 1, stackpage=cfda7000)

Stack: cfda0c00 cfd82a00 c02345d6 c033eae0 cfda0c00 cfd82a00 c022d562
cfd82a00
       5f636861 3a696370 31313a30 c000303a c12c5188 00000046 00000003
00000020
       c12c555c c12c5554 00000002 00000021 c012f276 c12c5554 00000002
00000244
Call Trace:    [<c02345d6>] [<c022d562>] [<c012f276>] [<c0214599>]

[<c024e031>]
[<c024e0c7>] [<c022d5fb>] [<c0228ebb>] [<c0105000>] [<c0213651>]
[<c0105000>]
[<c010503b>] [<c0104000>] [<c0107416>] [<c0105030>]

Code: 89 02 c7 06 00 00 00 00 8b 1d e8 0c 34 c0 81 fb e8 0c 34 c0
 <0>Kernel Panic: Attempted to kill init!

let me know if you need anything else.. I really appreciate the help.. and yeah.. sorry about the typos.. It was late when I wrote the first email and Adaptec seemed to be a hard word to type at the time.

Thanks for the help !

Quoted 15 lines · Justin T. Gibbs
Quoted 4 lines

I have a current linux desktop curring 2.4.19 that has been running fine for ever. Altho, when I atempted to do an update to 2.4.20, I was rather surprised to see that my machine kernel panics on boot, just as it would normally init the scsi bus.

What is the panic?

--
Justin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 1 line
Anthony R. Mattke <[email protected]>