lkml.org 
[lkml]   [2003]   [Nov]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.4.23 crash on Intel SDS2
Hi,

On Sat, Nov 15, 2003 at 12:58:28PM -0800, Shane Wegner wrote:

> I did and unfortunately, it was of little help. If
> anything though, it made the lockup more consistent. The
> three times I tried to boot with nmi_watchdog=1, it locked
> up when starting SpamAssassin. Nothing special about that
> process but just above that it started the hotplug
> subsystem which I use to automatically insert various usb
> drivers as needed. Could that have anything to do with it?

Would it be possible to print a "starting XXX" and
"XXX started" before and after every service ? And please
also try to disable automatic modprobe, or change it to
something which logs what is loaded. Eg:

echo /root/mymodprobe >/proc/sys/kernel/modprobe

with mymodprobe basically looking like :

#!/bin/bash
{date;echo "starting $@"} >> /tmp/modprobe.log
sync
exec modprobe $@

> Btw, to clarify, when the lockup occurs with nmi_watchdog,
> no oops gets printed.

You may try nmi_watchdog=2. I once was adviced to try =1,
but it never worked for me, while =2 worked as expected.
Don't ask me why, all I know is that there are a few other
people out there happily using it this way too.

Regards,
Willy

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

\
 
 \ /
  Last update: 2005-03-22 13:58    [W:0.051 / U:0.864 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site