Heather wrote:
> Is there any type of hot key sequence that can be used to create a system
> dump even after the system has frozen?
In the "kernel hacking" section of the kernel configure select
"Magic SysRq key" before rebuilding you kernel.
Then after a SCSI sub-system meltdown try:
Alt-SysRq S [emergency sync]
Alt-SysRq U [remount read-only]
Alt-SysRq S [emergency sync]
[see linux/Documentation/sysrq.txt for other options]
......
Alt-SysRq B [reboot system!]
> I'm running 2.2.5 on a Compaq AP200 with an AHA-2940UW (for the boot drive)
> and a QLA2100F for connectivity to an external storage device. I have the
> Qlogic card as a module and insmod'd it. When I do a dd (like #dd
> if=/dev/sdb of=/dev/null bs=16384 count=500) or try to send I/O to the
> external storage via an app called Iorate, I get the message below and the
> system freezes.
> I can't figure out what the fault address is referring to either. I did a
> #ksyms -m | sort and there's nothing that refers to the fault address of
> 00000000.
> Any suggestions are greatly appreciated. Thanks!
Build the Qlogic driver into the kernel (don't use it as
a module].
The SCSI mid-level always tries to allocate memory
below the 16 MB level irrespective of whether you
have any ISA adpaters (for backward compatibility
with the distant past). The oops is probably caused
because it cannot find that memory below 16MB returning
a NULL pointer causing ...
The Qlogic module may look like it loads ok but may
have 0 command blocks allocated causing an oops as
soon as you try and use it.
BTW It makes _no_ difference if your machine has 256MB
of RAM (it just makes it worse)!!
If the driver is built into the kernel then it tries
to get that memory at boot time when it is a lot more
likely to get find it.
Contact me if you need more help.
Doug Gilbert
