Skip to contentSkip to conversation

Errors on 2th ide channel of promise ultra100 tx2

DISCUSSION Erik van Engelen 7 participants 17 messages Feb 27, 2004 – Mar 3, 2004

lore
Share & tools
lore
#0 lore raw

Hi,

I've got a Proliant 2500 running a 2.4.25 kernel. It has 2 pentium pro CPUs and a smart-2/E disk array on EISA bus from which it boots.

I added a promise ultra100 tx2 ide cart and put on 3 disks. During boot i get a couple of errors but everything seems to work ok. When read/write to a disk on the first ide-channel everything is ok. When i read/write to a disk on the second ide-channel everything is ok. But when i try to read/write to both disks at once i get these errors:

hdh: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdh: status error: status=0x58 { DriveReady SeekComplete DataRequest }

I read somewhere it helps to add a line in the lilo.conf. I also tried that but it doesn't make any diffents. This is the lilo.conf line:
append="mem=128M smart2=0x4000 ide2=serialize ide3=serialize"

The next thing i tried is to boot from a 2.6.3 kernel but that one ends up in a big kernel panic. When i leave out the smart2 (cpqarray) driver it boot up to the point where it needs a disk to boot from which isn't there naturally.

Can anyone help me with this problem? I like to stay on the 2.4 kernel because i want to run debian stable but if thats impossible i want to work on the 2.6. If you need any informatie or if i have to run some tests on the machine just ask. It is here opend up on the floor and i've got my screwdriver ready.

THX...
Erik van Engelen.

This is a part of my 2.4.25 boot messages.
PDC20268: IDE controller at PCI slot 01:0a.0
PDC20268: chipset revision 2
PDC20268: not 100% native mode: will probe irqs later

    ide2: BM-DMA at 0x6410-0x6417, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0x6418-0x641f, BIOS settings: hdg:pio, hdh:pio

hda: CD-ROM CDU571-Q, ATAPI CD/DVD-ROM drive
hde: Conner Peripherals 1275MB - CFS1275A, ATA DISK drive
hdg: WDC AC2850F, ATA DISK drive
hdh: QUANTUM FIREBALL1080A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0x6420-0x6427,0x6432 on irq 9
ide3 at 0x6428-0x642f,0x643a on irq 9
hde: attached ide-disk driver.
hde: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hde: task_no_data_intr: error=0x04 { DriveStatusError }
hde: 2496876 sectors (1278 MB) w/64KiB Cache, CHS=2477/16/63
hdg: attached ide-disk driver.
hdg: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: task_no_data_intr: error=0x04 { DriveStatusError }
hdg: 1667232 sectors (854 MB) w/64KiB Cache, CHS=1654/16/63
hdh: attached ide-disk driver.
hdh: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: task_no_data_intr: error=0x04 { DriveStatusError }
hdh: 2128896 sectors (1090 MB) w/83KiB Cache, CHS=2112/16/63

#1 lore raw

I'm clueless about this, anyway...

Quoted 5 lines · Erik van Engelen

Hi,

I've got a Proliant 2500 running a 2.4.25 kernel. It has 2 pentium pro CPUs and a smart-2/E disk array on EISA bus from which it boots.

Quoted 8 lines

I added a promise ultra100 tx2 ide cart and put on 3 disks. During boot i get a couple of errors but everything seems to work ok. When read/write to a disk on the first ide-channel everything is ok. When i read/write to a disk on the second ide-channel everything is ok. But when i try to read/write to both disks at once i get these errors:

hdh: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdh: status error: status=0x58 { DriveReady SeekComplete DataRequest }

Are you using DMA?

I'm not sure about what these mean. A lot of similar reports (error status=0x58) can be found on the list for a variety of different controllers. On 2.6 too.

What is the meaning of this error? By reading the archives, it seems it can be caused by several different problems (bad cables for example). Is that right?

What do they mean?

Quoted 9 lines

I read somewhere it helps to add a line in the lilo.conf. I also tried that but it doesn't make any diffents. This is the lilo.conf line:
append="mem=128M smart2=0x4000 ide2=serialize ide3=serialize"

The next thing i tried is to boot from a 2.6.3 kernel but that one ends up in a big kernel panic. When i leave out the smart2 (cpqarray) driver it boot up to the point where it needs a disk to boot from which isn't there naturally.

Quoted 5 lines

Can anyone help me with this problem? I like to stay on the 2.4 kernel because i want to run debian stable but if thats impossible i want to work on the 2.6. If you need any informatie or if i have to run some tests on the machine just ask. It is here opend up on the floor and i've got my screwdriver ready.

Can you please save and post the 2.6.3 panic?

Quoted 17 lines

This is a part of my 2.4.25 boot messages.
PDC20268: IDE controller at PCI slot 01:0a.0
PDC20268: chipset revision 2
PDC20268: not 100% native mode: will probe irqs later

     ide2: BM-DMA at 0x6410-0x6417, BIOS settings: hde:pio, hdf:pio
     ide3: BM-DMA at 0x6418-0x641f, BIOS settings: hdg:pio, hdh:pio

hda: CD-ROM CDU571-Q, ATAPI CD/DVD-ROM drive
hde: Conner Peripherals 1275MB - CFS1275A, ATA DISK drive
hdg: WDC AC2850F, ATA DISK drive
hdh: QUANTUM FIREBALL1080A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0x6420-0x6427,0x6432 on irq 9
ide3 at 0x6428-0x642f,0x643a on irq 9
hde: attached ide-disk driver.
hde: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hde: task_no_data_intr: error=0x04 { DriveStatusError }
hde: 2496876 sectors (1278 MB) w/64KiB Cache, CHS=2477/16/63

Quoted 8 lines

hdg: attached ide-disk driver.
hdg: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdg: task_no_data_intr: error=0x04 { DriveStatusError }
hdg: 1667232 sectors (854 MB) w/64KiB Cache, CHS=1654/16/63
hdh: attached ide-disk driver.
hdh: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: task_no_data_intr: error=0x04 { DriveStatusError }
hdh: 2128896 sectors (1090 MB) w/83KiB Cache, CHS=2112/16/63

Haven't got a clue about these "status=0x51" and "error=0x04". Anyone?

#2 lore raw
Quoted 5 lines
Quoted 3 lines

hdh: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: task_no_data_intr: error=0x04 { DriveStatusError }
hdh: 2128896 sectors (1090 MB) w/83KiB Cache, CHS=2112/16/63

Haven't got a clue about these "status=0x51" and "error=0x04". Anyone?

Basically, the errors mean what they say - the drive is in an error state, (received an unrecognised command), but is ready for further operation.

John.

#3 lore raw
Quoted 9 lines · John Bradford
Quoted 5 lines
Quoted 3 lines

hdh: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: task_no_data_intr: error=0x04 { DriveStatusError }
hdh: 2128896 sectors (1090 MB) w/83KiB Cache, CHS=2112/16/63

Haven't got a clue about these "status=0x51" and "error=0x04". Anyone?

Basically, the errors mean what they say - the drive is in an error state, (received an unrecognised command), but is ready for further operation.

Received an unrecognised command from the kernel? What can cause that?

Thanks!

#4 lore raw
Quoted 7 lines · Marcelo Tosatti
Quoted 5 lines
Quoted 1 line

Haven't got a clue about these "status=0x51" and "error=0x04". Anyone?

Basically, the errors mean what they say - the drive is in an error state, (received an unrecognised command), but is ready for further operation.

Received an unrecognised command from the kernel? What can cause that?

Our early setup/probing code in 2.4.x at least may send stuff that very very old disks don't understand. Its arguably a bug in the ident parsing but it shouldnt ever be harmful

#14 lore raw
In reply to Marcelo Tosatti
Quoted 3 lines · Marcelo Tosatti
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

hdh: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdh: task_no_data_intr: error=0x04 { DriveStatusError }
hdh: 2128896 sectors (1090 MB) w/83KiB Cache, CHS=2112/16/63

[ ... ]

Quoted 1 line

Received an unrecognised command from the kernel? What can cause that?

Still this one, it would appear:

http://www.ussg.iu.edu/hypermail/linux/kernel/0402.0/1421.html

Everyone running 2.4 (> .19 or so, the new IDE stuff) with an older drive is seeing this.

Rene.

#5 lore raw
In reply to Alan Cox
Quoted 8 lines · Alan Cox
Quoted 7 lines · Marcelo Tosatti
Quoted 6 lines
Quoted 2 lines

Haven't got a clue about these "status=0x51" and "error=0x04". Anyone?

Basically, the errors mean what they say - the drive is in an error state, (received an unrecognised command), but is ready for further operation.

Quoted 5 lines
Quoted 1 line

Received an unrecognised command from the kernel? What can cause that?

Our early setup/probing code in 2.4.x at least may send stuff that very very old disks don't understand. Its arguably a bug in the ident parsing but it shouldnt ever be harmful

ide-disk.c sends WIN_READ_NATIVE_MAX_{EXT} without checking if HPA feature set is supported, this is fixed in 2.6.x for a long time.

We need 2.4<->2.6 IDE sync monkey... a really smart one...

Cheers,
Bartlomiej

#6 lore raw
Quoted 11 lines · Bartlomiej Zolnierkiewicz
Quoted 10 lines · Alan Cox
Quoted 8 lines · Marcelo Tosatti
Quoted 6 lines
Quoted 2 lines

Haven't got a clue about these "status=0x51" and "error=0x04". Anyone?

Basically, the errors mean what they say - the drive is in an error state, (received an unrecognised command), but is ready for further operation.

Received an unrecognised command from the kernel? What can cause that?

Quoted 8 lines
Quoted 3 lines

Our early setup/probing code in 2.4.x at least may send stuff that very very old disks don't understand. Its arguably a bug in the ident parsing but it shouldnt ever be harmful

ide-disk.c sends WIN_READ_NATIVE_MAX_{EXT} without checking if HPA feature set is supported, this is fixed in 2.6.x for a long time.

We need 2.4<->2.6 IDE sync monkey... a really smart one...

OK and what about the status=0x58 errors? What are those about?

#13 lore raw
In reply to Alan Cox
Quoted 7 lines · Alan Cox
Quoted 6 lines · Marcelo Tosatti
Quoted 5 lines
Quoted 1 line

Haven't got a clue about these "status=0x51" and "error=0x04". Anyone?

Basically, the errors mean what they say - the drive is in an error state, (received an unrecognised command), but is ready for further operation.

Quoted 5 lines
Quoted 1 line

Received an unrecognised command from the kernel? What can cause that?

Our early setup/probing code in 2.4.x at least may send stuff that very very old disks don't understand. Its arguably a bug in the ident parsing but it shouldnt ever be harmful

Yes it is potentially harmful. Old drives that can't grok HPA are asked if they have an HPA, which i.e. will cause my old Samsung 400 MB drive to become very unhappy. I sent in a patch fixing it quite a while back. It was accepted into 2.6.x but the 2.4.x version never made it in...

-Erik

--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

#8 lore raw
In reply to Bartlomiej Zolnierkiewicz
Quoted 4 lines · Bartlomiej Zolnierkiewicz

ide-disk.c sends WIN_READ_NATIVE_MAX_{EXT} without checking if HPA feature set is supported, this is fixed in 2.6.x for a long time.

We need 2.4<->2.6 IDE sync monkey... a really smart one...

Dunno if I qualify as sufficiently 'really smart' enough but the last time I put in the considerable effort needed to re-sync the 2.4 and 2.6 IDE layers, and merge in the useful -ac bits that never made it into mainstream, nothing whatsoever came of my efforts...

My 2.4.x patches are in daily use by a large group of people and they work fine, for what it is worth. My IDE merging patches are the following:

    http://codepoet.org/kernel/

    020_ide_layer_2.4.22-ac4.bz2
    021_ide_geom_hpa_capacity64.bz2
    022-extra-ide-drives.bz2
    023-2.4.25-libata1.patch.bz2
    024_libata-spurious2.diff.bz2
    025-cenatek.patch.bz2
    026-medley-softraid.patch.bz2

The 021_ide_geom_hpa_capacity64.bz2 is my original work, the others are the result of skimming patches from the list and merging/updating them as needed to sync with the other patches and keep them current.

-Erik

--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

#7 lore raw
In reply to Marcelo Tosatti
Quoted 17 lines · Marcelo Tosatti
Quoted 16 lines · Bartlomiej Zolnierkiewicz
Quoted 14 lines · Alan Cox
Quoted 9 lines · Marcelo Tosatti
Quoted 6 lines
Quoted 2 lines

Haven't got a clue about these "status=0x51" and "error=0x04". Anyone?

Basically, the errors mean what they say - the drive is in an error state, (received an unrecognised command), but is ready for further operation.

Received an unrecognised command from the kernel? What can cause that?

Our early setup/probing code in 2.4.x at least may send stuff that very very old disks don't understand. Its arguably a bug in the ident parsing but it shouldnt ever be harmful

Quoted 6 lines
Quoted 4 lines

ide-disk.c sends WIN_READ_NATIVE_MAX_{EXT} without checking if HPA feature set is supported, this is fixed in 2.6.x for a long time.

We need 2.4<->2.6 IDE sync monkey... a really smart one...

OK and what about the status=0x58 errors? What are those about?

These are from ide_wait_stat(). It looks like we are expecting drive to be idle but drive is ready to receive data. There should be another error message in logs (unless error comes from ide-cd.c) telling more what was the source of an error.

Bartlomiej

#9 lore raw
In reply to Erik Andersen
Quoted 11 lines · you
Quoted 4 lines · Bartlomiej Zolnierkiewicz

ide-disk.c sends WIN_READ_NATIVE_MAX_{EXT} without checking if HPA feature set is supported, this is fixed in 2.6.x for a long time.

We need 2.4<->2.6 IDE sync monkey... a really smart one...

Dunno if I qualify as sufficiently 'really smart' enough but the last time I put in the considerable effort needed to re-sync the 2.4 and 2.6 IDE layers, and merge in the useful -ac bits that never made it into mainstream, nothing whatsoever came of my efforts...

Did you actually split and send out your patches? :)

Quoted 7 lines

My 2.4.x patches are in daily use by a large group of people and they work fine, for what it is worth. My IDE merging patches are the following:

    http://codepoet.org/kernel/

    020_ide_layer_2.4.22-ac4.bz2

Needs splitting and most of this stuff needs new re-sync with 2.6. :-(

Quoted 1 line
    021_ide_geom_hpa_capacity64.bz2

Now I remember why this wasn't applied.
It breaks braindamaged HDIO_GETGEO_BIG_RAW ioctl (because changes way drive->cyls is calculated). We workaround-ed it in 2.6 by removing this ioctl. :) I think we really should do the same for 2.4.

Quoted 1 line
    022-extra-ide-drives.bz2

This hack to allow > 10 interfaces
is useless without additional major numbers.

Quoted 1 line
    025-cenatek.patch.bz2

IDE controller for solid state disks? Cool.

Bartlomiej

#10 lore raw
Quoted 7 lines · Bartlomiej Zolnierkiewicz
Quoted 5 lines

Dunno if I qualify as sufficiently 'really smart' enough but the last time I put in the considerable effort needed to re-sync the 2.4 and 2.6 IDE layers, and merge in the useful -ac bits that never made it into mainstream, nothing whatsoever came of my efforts...

Did you actually split and send out your patches? :)

Yes....
http://www.ussg.iu.edu/hypermail/linux/kernel/0308.2/0175.html

Quoted 9 lines
Quoted 7 lines

My 2.4.x patches are in daily use by a large group of people and they work fine, for what it is worth. My IDE merging patches are the following:

    http://codepoet.org/kernel/

    020_ide_layer_2.4.22-ac4.bz2

Needs splitting and most of this stuff needs new re-sync with 2.6. :-(

Yup. After splitting and submitting to no effect it was less effort to maintain the lot as one big patch...

Quoted 7 lines
Quoted 1 line
    021_ide_geom_hpa_capacity64.bz2

Now I remember why this wasn't applied.
It breaks braindamaged HDIO_GETGEO_BIG_RAW ioctl (because changes way drive->cyls is calculated). We workaround-ed it in 2.6 by removing this ioctl. :) I think we really should do the same for 2.4.

I did just that but it was rejected by Alan Cox...
http://www.ussg.iu.edu/hypermail/linux/kernel/0308.2/0193.html

-Erik

--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

#15 lore raw
In reply to Marcelo Tosatti

Hi,

Thanks for the fast reaction.

Quoted 16 lines · Marcelo Tosatti

I'm clueless about this, anyway...

Quoted 11 lines · Erik van Engelen

Hi,

I've got a Proliant 2500 running a 2.4.25 kernel. It has 2 pentium pro CPUs and a smart-2/E disk array on EISA bus from which it boots.

I added a promise ultra100 tx2 ide cart and put on 3 disks. During boot i get a couple of errors but everything seems to work ok. When read/write to a disk on the first ide-channel everything is ok. When i read/write to a disk on the second ide-channel everything is ok. But when i try to read/write to both disks at once i get these errors:

Quoted 6 lines
Quoted 2 lines

hdh: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdh: status error: status=0x58 { DriveReady SeekComplete DataRequest }

Are you using DMA?

I've tried it with and without DMA. But in both cases i got errors although the were different. I made some changes so i can't post the error with the DMA turned on. I can reverse the changes on Monday and post the errors for you.

Quoted 4 lines

Can you please save and post the 2.6.3 panic?

I'm trying to get a serial line connection working to log the bootlogs. I can make them as well on Monday.

I tried to boot with the cpqarray removed from the 2.6.3 kernel. In that case i don't get the errors from the ide devices during the kernel boot so i guess the solution made in the 2.6 according the ide problem is working. Again on Monday i want to try the patch from Erik B. Andersen on the 2.4 kernel. If i understood it all right. I'm not really into kernel hacking etc.

THX for the help so far..
Erik van Engelen

#11 lore raw
In reply to Erik Andersen
Quoted 8 lines · Erik Andersen
Quoted 5 lines

Now I remember why this wasn't applied.
It breaks braindamaged HDIO_GETGEO_BIG_RAW ioctl (because changes way drive->cyls is calculated). We workaround-ed it in 2.6 by removing this ioctl. :) I think we really should do the same for 2.4.

I did just that but it was rejected by Alan Cox...
http://www.ussg.iu.edu/hypermail/linux/kernel/0308.2/0193.html

You can't go around randomly removing bad ideas during a stable tree. Sucks but true.

Alan

#12 lore raw

Quote from Alan Cox <[email protected]>:

Quoted 7 lines · Erik Andersen
Quoted 6 lines
Quoted 5 lines

Now I remember why this wasn't applied.
It breaks braindamaged HDIO_GETGEO_BIG_RAW ioctl (because changes way drive->cyls is calculated). We workaround-ed it in 2.6 by removing this ioctl. :) I think we really should do the same for 2.4.

Quoted 5 lines
Quoted 2 lines

I did just that but it was rejected by Alan Cox...
http://www.ussg.iu.edu/hypermail/linux/kernel/0308.2/0193.html

You can't go around randomly removing bad ideas during a stable tree.

Ironically, you can add as many bad ideas as you like, but not remove them :-)

John.

#16 lore raw
In reply to Marcelo Tosatti
Quoted 7 lines
Quoted 7 lines

The next thing i tried is to boot from a 2.6.3 kernel but that one ends up in a big kernel panic. When i leave out the smart2 (cpqarray) driver it boot up to the point where it needs a disk to boot from which isn't there naturally.

Quoted 9 lines
Quoted 5 lines

Can anyone help me with this problem? I like to stay on the 2.4 kernel because i want to run debian stable but if thats impossible i want to work on the 2.6. If you need any informatie or if i have to run some tests on the machine just ask. It is here opend up on the floor and i've got my screwdriver ready.

Can you please save and post the 2.6.3 panic?

----------
KERNEL LOG

LILO 22.2 boot: Linux-2.6.3
Loading Linux-2.6.3.......................
Linux version 2.6.3 (root@smurver) (gcc version 2.95.4 20011002 (Debian prerele4 BIOS-provided physical RAM map:
BIOS-88: 0000000000000000 - 000000000009f000 (usable)
BIOS-88: 0000000000100000 - 0000000001000000 (usable)
user-defined physical RAM map:
user: 0000000000000000 - 000000000009f000 (usable)
user: 0000000000100000 - 0000000001000000 (usable)
16MB LOWMEM available.
found SMP MP-table at 000f4ff0
hm, page 000f4000 reserved twice.
hm, page 000f5000 reserved twice.
hm, page 000f2000 reserved twice.
hm, page 000f3000 reserved twice.
On node 0 totalpages: 4096
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 0 pages, LIFO batch:1
HighMem zone: 0 pages, LIFO batch:1
DMI not present.
ACPI: Unable to locate RSDP
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: COMPAQ Product ID: PROLIANT APIC at: 0xFEE00000
Processor #1 6:1 APIC version 16
Processor #0 6:1 APIC version 16
I/O APIC #2 Version 17 at 0xFEC00000.
Enabling APIC mode: Flat. Using 1 I/O APICs
Processors: 2
Built 1 zonelists
Kernel command line: BOOT_IMAGE=Linux-2.6.3 ro root=4802 mem=128M smart2=0x40008 Initializing CPU#0
PID hash table entries: 128 (order 7: 1024 bytes)
Detected 199.609 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 12780k/16384k available (1638k kernel code, 3192k reserved, 638k data, ) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 388.09 BogoMIPS
Dentry cache hash table entries: 2048 (order: 1, 8192 bytes) Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: L1 I cache: 8K, L1 D cache: 8K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
CPU0: Intel Pentium Pro stepping 09
per-CPU timeslice cutoff: 730.16 usecs.
task migration cache decay timeout: 1 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Booting processor 1/0 eip 2000
Initializing CPU#1
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 397.31 BogoMIPS
CPU: L1 I cache: 8K, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel Pentium Pro stepping 09
Total of 2 processors activated (785.40 BogoMIPS).
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
..TIMER: vector=0x31 pin1=2 pin2=0
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
..... (found pin 0) ...works.
testing the IO APIC....................... .................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 199.0422 MHz.
..... host bus clock speed is 66.0474 MHz.
checking TSC synchronization across 2 CPUs: passed.
Starting migration thread for cpu 0
Starting migration thread for cpu 1
Brought up 1 CPUs
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xf0068, last bus=1
PCI: Using configuration type 1
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Device 00:00 not found by BIOS
PCI: Device 00:a0 not found by BIOS
Starting balanced_irq
devfs: v1.22 (20021013) Richard Gooch ([email protected])
devfs: boot_options: 0x1
Installing knfsd (copyright (C) 1996 [email protected]).
Limiting direct PCI/PCI transfers.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
pty: 256 Unix98 ptys configured
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
Compaq SMART2 Driver (v 2.4.5)
Found 1 controller(s)
cpqarray: Finding drives on ida0 (SMART-2/E)
cpqarray ida/c0d0: blksz=512 nr_blks=16755795

Unable to handle kernel NULL pointer dereference at virtual address 00000038
 printing eip:
c0350d85
*pde = 00000000
Oops: 0000 [#1]
CPU:    1
EIP:    0060:[<c0350d85>]    Not tainted
EFLAGS: 00010282

EIP is at cpqarray_init+0x29d/0x538
eax: 00000000 ebx: c0f48e00 ecx: 00008124 edx: 00000000
esi: c03a5920 edi: c03edf10 ebp: 00000010 esp: c0fe7f94
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=c0fe6000 task=c0fe1900)

Stack: 00000000 00000000 00000000 c0386c2c 00000001 00000000 00000000 00000048
       00000000 c0308120 00000048 00000000 00000000 00000001 00000000 
c033c7d2
       c0fe6000 00000000 c033c841 c01050ef 00000008 c0105094 00000000 
c0106ef1
Call Trace:
 [<c033c7d2>] do_initcalls+0x36/0x8c
 [<c033c841>] do_basic_setup+0x19/0x28
 [<c01050ef>] init+0x5b/0x15c
 [<c0105094>] init+0x0/0x15c
 [<c0106ef1>] kernel_thread_helper+0x5/0xc

Code: 8b 50 38 8b 48 3c 51 52 53 e8 e5 5c ea ff 6a 1f 53 e8 39 5e
 <0>Kernel panic: Attempted to kill init!