On Thu, 16 Nov 2000, Andrew Morton wrote:
> OK, so the options are now:
>
> nmi_watchdog=0
> nmi_watchdog=1
> nmi_watchdog=1,verbose
looks good for me!
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Ingo Molnar wrote:
>
> > So... In this updated patch the console_silent() call remains
> > as you designed it, but the nmi_watchdog kernel boot parameter has
> > been overloaded so that
> >
> > nmi_watchdog=2
> >
> > will now cause _all_ NMI oops messages to be displayed on the console.
>
"Pawe³ Kot" wrote:
>
> In attachment. But don't beat me. I think I found the oops reason.
> /dev/shm was not mounted. After mounting it I couldn't get an oops yet.
> Could this be a reason?
No.
>>EIP; c010b5ee <__read_lock_failed+6/18> <=
Trace; c02026f7
Trace; c0120404
On Wed, 15 Nov 2000, Andrew Morton wrote:
> "Paweł Kot" wrote:
> >
> > Hi,
> >
> > The whole oops produced by the 2.4.0-test11pre4 with this patch is in the
> > attachment. Other system info is tehere as well.
> >
> > Oops is produced when runnning big-tables test from mysql sql-bench.
> > It's r
"Pawe³ Kot" wrote:
>
> Hi,
>
> The whole oops produced by the 2.4.0-test11pre4 with this patch is in the
> attachment. Other system info is tehere as well.
>
> Oops is produced when runnning big-tables test from mysql sql-bench.
> It's reproducable. The machine is running only mysqld.
Thank yo
On Wed, 15 Nov 2000, Andrew Morton wrote:
> [...] Problem is, we're getting some reported lockups in which we need
> to know what the other CPUs are doing (the other 1%). If a critical
> spinlock is stuck on, we don't get to type `dmesg'.
i know - but we cannot please everyone, so i went for th
Ingo Molnar wrote:
>
> On Tue, 14 Nov 2000, Andrew Morton wrote:
>
> > It also changes the x86 NMI oopser so that it no longer shuts the
> > console up after the first NMI oops. Instead, each CPU is allowed
> > to print out NMI diagnostics a single time per reboot.
>
> this is not how the NMI
On Tue, 14 Nov 2000, Andrew Morton wrote:
> It also changes the x86 NMI oopser so that it no longer shuts the
> console up after the first NMI oops. Instead, each CPU is allowed
> to print out NMI diagnostics a single time per reboot.
this is not how the NMI oopser works. It does *not* shut do
Hi,
The whole oops produced by the 2.4.0-test11pre4 with this patch is in the
attachment. Other system info is tehere as well.
Oops is produced when runnning big-tables test from mysql sql-bench.
It's reproducable. The machine is running only mysqld.
regards
pkot
--
mailto:[EMAIL PROTECTED]
h
9 matches
Mail list logo
