2.2.13pre15+Unified IDE+SMP exploded

thx@rivalnet.de
Tue, 5 Oct 1999 15:36:47 +0200


Last night I had a stress test running on:

kernel 2.2.13pre15 with:
- Unified IDE 2.2.13pre14-19991003
- raid 2.2.11
(large disk patch was not required)

After 6 hours the kernel unfortunately exploded.

Probably the same kernel NULL pointer dereference as with 2.2.13pre14 + U-IDE-990925.
However, could also be the unlink() problem (see previous message).
Maybe I should do a specific unlink() stress test, too.

A minor issue with Unified IDE and 37GB drives: they need kernel parameters ("hdx=4560,255,63"), otherwise they are detected as 1027,255,63 (just as with the experimental large disk patch).

Side note: I also tested 2.2.13pre14 compiled as non-SMP (same machine, this time without unified-ide). All went well for 15 hours under heavy stress (then I stopped testing). The NULL pointer dereferences seem seem to be an SMP problem.

Configuration for the (6-hours-until-) NULL pointer dereference stress-test (2.2.13pre15+Unified IDE+SMP):

hardware:
- 2 x promise UDMA66
- 37GB drives at hde, hdf, hdi, hdj
- 25GB drive at hda

the log:

unrelated, maybe raid:
Oct 5 04:14:48 s_all@grs1 kernel: nr_blocks changed to 192 (blocksize 4096, j 19776, max_blocks 27163824)

some UDMA66 CRC errors:
Oct 5 04:26:59 s_all@grs1 kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 5 04:26:59 s_all@grs1 kernel: hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
Oct 5 04:56:11 s_all@grs1 kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 5 04:56:11 s_all@grs1 kernel: hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
Oct 5 06:02:50 s_all@grs1 kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 5 06:02:50 s_all@grs1 kernel: hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
Oct 5 07:06:58 s_all@grs1 kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 5 07:06:58 s_all@grs1 kernel: hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
Oct 5 07:56:58 s_all@grs1 kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 5 07:56:58 s_all@grs1 kernel: hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
Oct 5 08:01:39 s_all@grs1 kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 5 08:01:39 s_all@grs1 kernel: hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
Oct 5 09:26:10 s_all@grs1 kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Oct 5 09:26:10 s_all@grs1 kernel: hde: dma_intr: error=0x84 { DriveStatusError BadCRC }
Oct 5 09:46:36 s_all@grs1 kernel: hde: dma_intr: status=0x53 { DriveReady SeekComplete Index Error }
Oct 5 09:46:37 s_all@grs1 kernel: hde: dma_intr: error=0x84 { DriveStatusError BadCRC }

the oops (more wasn´t in the log):
Oct 5 10:32:19 s_all@grs1 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000004
Oct 5 10:54:29 s_all@grs1 kernel: current->tss.cr3 = 2d8db000, %cr3 = 2d8db000
Oct 5 10:54:29 s_all@grs1 kernel: *pde = 00000000
Oct 5 10:54:29 s_all@grs1 kernel: Oops: 0000
Oct 5 10:54:29 s_all@grs1 kernel: CPU: 0

--
the online community service for gamers & friends -  http://www.rivalnet.com
* unterstützt über 50 PC-Spiele im Multiplayer-Modus
* Dateien senden & empfangen bis 500 MB am Stück
* Newsgroups, Mail, Chat & mehr

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/