Linux 2.4.2-ac21
Oops...
Linux 2.4.2-ac21 does not like my box, or the other way around:
loading the agpgart module (MGA G400 AGP) -> system hangs loading the SCSI module (53c875) -> system hangs
In both cases, the magic SysRq sequence does not work, but it is still possible to ping the box from the outside. Connecting to it (ssh) does not work, however. I backed out both the SCSI driver patches as well as the agpgart patches, but this did not fix the symptoms. Looks more like a module-loading related issue, but I have not found it yet.
All this on an SMP (Abit BP6) box by the way...
The changes which introduced these symptoms have occured somewhere between -ac7 and -ac21, since -ac7 DID run on the same hardware.
Cheers//Frank
Signature · 9 lines
WWWWW _______________________
## o o\ / Frank de Lange \
}# \| / \
##---# _/ <Hacker for Hire> \
#### \ +31-320-252965 /
\ [email protected] /
-------------------------
[ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est." ]Quoted 5 lines · Frank de Lange
Linux 2.4.2-ac21 does not like my box, or the other way around:
loading the agpgart module (MGA G400 AGP) -> system hangs loading the SCSI module (53c875) -> system hangs
Quoted 7 lines
In both cases, the magic SysRq sequence does not work, but it is still possible to ping the box from the outside. Connecting to it (ssh) does not work, however. I backed out both the SCSI driver patches as well as the agpgart patches, but this did not fix the symptoms. Looks more like a module-loading related issue, but I have not found it yet.
All this on an SMP (Abit BP6) box by the way...
Activate the nmi watchdog with nmi_watchdog=1 in the boot parameters[*]. That will trip after 5 seconds and point to where it is hanging. If the nmi watchdog alone does not give enough data, add the kdb patch (with nmi watchdog on) and start debugging.
http://oss.sgi.com/projects/kdb/download/ix86/, the -ac20 patch should fit -ac21 as well.
Am I the only person who is annoyed that nmi watchdog is now off by default and the only way to activate it is by a boot parameter? You cannot even patch the kernel to build a version that has nmi watchdog on because the startup code runs out of the __setup routine, no boot parameter, no watchdog.
Quoted 6 lines · Keith Owens
Am I the only person who is annoyed that nmi watchdog is now off by default and the only way to activate it is by a boot parameter? You cannot even patch the kernel to build a version that has nmi watchdog on because the startup code runs out of the
__setuproutine, no boot parameter, no watchdog.
It was causing SMP boxes to crash mysteriously after several hours or days. Quite a lot of them. Nobody was able to explain why, so it was turned off.
Quoted 11 lines · Andrew Morton
Quoted 6 lines · Keith Owens
Am I the only person who is annoyed that nmi watchdog is now off by default and the only way to activate it is by a boot parameter? You cannot even patch the kernel to build a version that has nmi watchdog on because the startup code runs out of the
__setuproutine, no boot parameter, no watchdog.It was causing SMP boxes to crash mysteriously after several hours or days. Quite a lot of them. Nobody was able to explain why, so it was turned off.
I know why it was turned off by default. The annoying this is that now the *only* way to activate the watchdog is via a boot command. It is not possible to compile a standard debugging kernel with this option turned on, you have to rely on every user setting the boot options for every kernel. If it is going to be off by default there should be a way to patch the kernel to make it on by default.
Quoted 5 lines
Quoted 4 lines
It was causing SMP boxes to crash mysteriously after several hours or days. Quite a lot of them. Nobody was able to explain why, so it was turned off.
Quoted 7 lines
I know why it was turned off by default. The annoying this is that now the *only* way to activate the watchdog is via a boot command. It is not possible to compile a standard debugging kernel with this option turned on, you have to rely on every user setting the boot options for every kernel. If it is going to be off by default there should be a way to patch the kernel to make it on by default.
i'm troubled by that fact that something the would be used to debug the kernel, is something that actually causes crashes. doesn't that kind of defeat the purpose..and introduce just another unstable element to the problem/crash at hand?
-Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
[email protected] Intergrafix Internet Services
"Dream as if you'll live forever, live as if you'll die today"
http://www.asteroid-b612.org http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Quoted 12 lines · Admin Mailing Lists
Quoted 11 lines
Quoted 3 lines
It was causing SMP boxes to crash mysteriously after several hours or days. Quite a lot of them. Nobody was able to explain why, so it was turned off.
I know why it was turned off by default. The annoying this is that now the *only* way to activate the watchdog is via a boot command. It is not possible to compile a standard debugging kernel with this option turned on, you have to rely on every user setting the boot options for every kernel. If it is going to be off by default there should be a way to patch the kernel to make it on by default.
Quoted 4 lines
i'm troubled by that fact that something the would be used to debug the kernel, is something that actually causes crashes. doesn't that kind of defeat the purpose..and introduce just another unstable element to the problem/crash at hand?
I had some unreproducable system crashes with NO watchdog and NO SMP enabled that do no longer occure since I compile my kernels without CONFIG_DEBUG_KERNEL. I don't know if it this is related, but there seems to be a problem in one of the "Kernel hacking" options that isn't related to watchdog or SMP.
Quoted 1 line
-Tony
cu
Adrian
Signature · 2 lines
Nicht weil die Dinge schwierig sind wagen wir sie nicht, sondern weil wir sie nicht wagen sind sie schwierig.