Deadlock problem apparently solved with a ICP GDT RAID controller on a ABit VP6 motherboard.

Deadlock problem apparently solved with a ICP GDT RAID controller on a ABit VP6 motherboard.

Post by T. A » Tue, 12 Feb 2002 12:00:12


    Just thought I'd mention it in case anyone else has encountered the same
problem I had been having with this combination.  I reported this a couple
of months ago.  After lots of trial and error I finally found that using the
pirq="" kernel option to specify the PCI irqs apparently fixes the deadlock
problem I was having.  Once I set this parameter the RAID is able to survive
a good number of stress tests.  Funny thing is that it doesn't matter much
how I configure the pirq option.  Setting this to pretty much anything and
in any order just makes the system work.  This is despite what the
documentation on pirq says in that you have to specify exactly what the
motherboard assigns to the pci slots, usually found with trial an error.
One weird thing though.  The USB irq and possibly others are consistently
remapped by the kernel on bootup anyway despite the pirq assignments and
this trick still seams to work.  I've attached the dmesg on this system in
case anyone wants to take a look into this weirdness.

11K Download

1. Consistant complete deadlock with kernel 2.4.16 on an Abit VP6 with dual 1 Gig CPUs and an ICP GDT RAID card

    Did the two debugging steps listed below.  Tried the nmi_watchdog=1 and
also the kdb debugger.  Unfortunately neither debugging feature gave me any
results.  When the machine locks up the result is total.  The nmi_watchdog
does not produce any output (after the lockup) and the kdb debugger fails to
load up when pressing the pause key (after the lockup).  I suppose this is
indicating a hardware issue.  However as I said before my burning test under
FreeBSD was successful.  No machine lockup.  And the last test (under
FreeBSD) burned in for two days.  I also tried removing a processor.  Just
as with the non-smp kernel, the lockup did not occur.  Tried single
processor mode with each processor, both were successful.  Also gave
2.2.17-rc2 a try, just in case.  Same result.  As it stands looks like I'm
still in the same boat.  8-(  Anything else I can do to debug this issue?

    By the way.  Are people:  Successfully using the Abit VP6 motherboard
under Linux?  Successfully using the ICP GDT7528RN raid controller under
Linux in an SMP system?  Successfully using an ICP GDT7528RN on a Abit VP6

2. PostgreSQL table access

3. Abit VP6 and Hotrod 100 IDE raid controller

4. Difference between MU4 and patch cluster ?

5. HP NetRaid Controller = ICP Vortex GDT ???

6. RedHat 6 and Pilot-Manager

7. NVidia Driver Issues on Abit vp6 motherboard...

8. scsi config

9. Solaris x86 on Abit's VP6 Motherboard?

10. motherboard Abit VP6 / Dual CPU PIII

11. raid support for abit VP6?

12. HPT370 Raid controler on a abit vp6 mainboard

13. smp and gdth (ICP vortex raid controller) -- kernel oops