Skip to contentSkip to conversation

2.5.31 boot failure on pdc20267

DISCUSSION Petr Vandrovec 2 participants 2 messages Aug 15, 2002

lore
Share & tools
lore
#0 lore raw
Quoted 4 lines · Mikael Pettersson

Booting 2.5.31 (non-bk) on hde5, a UDMA(66) Quantum Fireball on a PDC20267 add-on card, resulted in a complete hang as init came to its "mount -n -o remount,rw /" point. No visible messages or anything in the log.

Known bug. Apply IDE113 (Aug 06, 11:02 CEST, from Martin), or just open drivers/ide/pcidma.c in your favorite text editor, look for (first) #ifdef CONFIG_BLK_DEV_TRM290, and replace whole ifdef block with '*--table |= cpu_to_le32(0x80000000);'

Test in the ifdef is exactly opposite, and #ifdef is also wrong.
Petr Vandrovec [email protected]

#1 lore raw
Quoted 10 lines · Petr Vandrovec
Quoted 4 lines · Mikael Pettersson

Booting 2.5.31 (non-bk) on hde5, a UDMA(66) Quantum Fireball on a PDC20267 add-on card, resulted in a complete hang as init came to its "mount -n -o remount,rw /" point. No visible messages or anything in the log.

Known bug. Apply IDE113 (Aug 06, 11:02 CEST, from Martin), or just open drivers/ide/pcidma.c in your favorite text editor, look for (first) #ifdef CONFIG_BLK_DEV_TRM290, and replace whole ifdef block with '*--table |= cpu_to_le32(0x80000000);'

Tested. First time 2.5.31 + the patch booted it seemed to work, but hung later on while compiling a 2.4.19 kernel. No messages of any kind. The hang _seemed_ to coincide with the console screen blanker kicking in. Second boot went ok and I made sure the screen blanker wouldn't kick in while doing the compile, and it didn't hang.

This box is the only one so far I've seen this problem on, my other Intel chipset boxes actually seem to work fairly well with 2.5.31.

/Mikael