Hello,

On Sat, 21 Apr 2007 15:41:41 -0500
"John Pierce" <[EMAIL PROTECTED]> wrote:

> > Consider, too, the "folk wisdom" that some hardware which exhibits no
> > problems when running Windows sometimes displays unreliability when
> > running Linux.
> >
> >
> Well, I will continue to look.  This machine has never had windows on
> it (save for the OEM Install of VISTA, which I deleted before it ever
> ran in userspace.), I partitioned the machine from the first boot when
> I got it home with suse 10.2.
> 
> Thanks though, like I said I will keep looking.

If you want to track the problem, then there is a netconsole.
(A serial port is very usable, but the HP DV9208nr note hasn't a serial port)
And an another machine is necessary to use a netconsole.

The way to use a netconsole is written in 
/usr/src/linux/Documentation/networking/netconsole.txt.
If the kernel-source package has not been installed yet, you need to install it.

As you read the document,


E.g.

Suppose set up like the following two Linux boxes.

  [target] -> 192.168.1.2 udp 6665(default)
  [remote] -> 192.168.1.3 udp 6666(default)  12:34:56:78:9a:bc


target:~ # insmod /lib/modules/`uname -r`/kernel/drivers/net/netconsole.ko \
 [EMAIL PROTECTED]/eth0,@192.168.1.3/12:34:56:78:9a:bc

remote:~ # netcat -u -l -p 6666

And you would like to check whether it goes well certainly.

target:~ # echo 1 > /proc/sys/kernel/sysrq
target:~ # echo m > /proc/sysrq-trigger

After this is performed, the log should be displayed in the remote linux box.
If nothing is displayed, then I suspect that an UDP packet on the remote box
or the target box (or both) is dropped by firewall.
Check /var/log/firewall and pass a udp packet for logging agent.

As for the setting, that's all.
And you would have to reproduce the random lockup on the target box. :)


hope this helps

Thanks,
eshsf

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to