On 10/21/05, Emmett Lazich <[email protected]> wrote:
> Posting to you after reading Documentation/oops-tracing.txt
> I am still looking into how to report this fault to SUSE.
Call your SuSE representative I'd say would be a pretty good first step.
SuSE/Novell have plenty of support options listed on their website,
shouldn't be hard to find the right contact info.
> After this oops, the machine kept running (phew!), however these
Don't put too much trust in the machine after the kernel has Oopsed.
It may appear to run, but most likely something is badly wrong in
kernel land at this point, so anything could happen - I'd say reboot
that machine as soon as you are able to.
> processes hang: ps, top, w. However vmstat, iostat and uptime still
> work ok. uptime says machine has a load average of around 20, but vmstat
> and iostat say machine is near idle. We will reboot it with nosmp until
> this fault is better understood.
>
> dmesg output:
> general protection fault: 0000 [1] SMP
> CPU 3
> Pid: 26432, comm: ps Not tainted (2.6.5-7.191-smp
2.6.5 is a pretty darn old kernel by now. First thing I would
personally do would be to go to kernel.org, grab a 2.6.13.4 kernel
source, build that, then try to reproduce the problem. An enourmous
amount of fixes have happened since 2.6.5.
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
