On Sat, 11 Nov 2000, Andrew Morton wrote:
> Oh no. Another one. Could you please try this attached
> patch (against test11-pre2) and see if the diagnostics
> come out?
There's an oops in the attachment. I haven't try your latest patch yet.
But I'm applying it at the moment.
pkot
--
mailto:[E
Jasper Spaans wrote:
>
> On Sun, Nov 12, 2000 at 01:27:13PM +1100, Keith Owens wrote:
>
> > >That's a pretty wierd trace. You seem to have addresses related
> > >to the `apm' kernel thread on mysqld's stack.
> >
> > Normal unfortunately. Firstly the ix86 oops code just scans the stack
> > and
Keith Owens wrote:
>
> On Mon, 13 Nov 2000 09:58:17 +0100,
> Jasper Spaans <[EMAIL PROTECTED]> wrote:
> >All right, here's another one, this time using the oops directly from the
> >console -- this seems to give better symbols.. The 'console shuts up ...'
> >works, the oops from the other CPU did
On Mon, 13 Nov 2000 09:58:17 +0100,
Jasper Spaans <[EMAIL PROTECTED]> wrote:
>All right, here's another one, this time using the oops directly from the
>console -- this seems to give better symbols.. The 'console shuts up ...'
>works, the oops from the other CPU didn't get put out.
O, damn!
On Sun, Nov 12, 2000 at 01:27:13PM +1100, Keith Owens wrote:
> >That's a pretty wierd trace. You seem to have addresses related
> >to the `apm' kernel thread on mysqld's stack.
>
> Normal unfortunately. Firstly the ix86 oops code just scans the stack
> and prints anything that looks like it mi
On Sun, 12 Nov 2000 12:32:55 +1100,
Andrew Morton <[EMAIL PROTECTED]> wrote:
>> > > NMI Watchdog detected LOCKUP on CPU3, registers:
>That's a pretty wierd trace. You seem to have addresses related
>to the `apm' kernel thread on mysqld's stack.
Normal unfortunately. Firstly the ix86 oops code
Jasper Spaans wrote:
>
> On Sat, Nov 11, 2000 at 11:25:00AM +1100, Andrew Morton wrote:
>
> > > NMI Watchdog detected LOCKUP on CPU3, registers:
>
> > Oh no. Another one. Could you please try this attached
> > patch (against test11-pre2) and see if the diagnostics
> > come out?
>
> And yet a
On Sat, Nov 11, 2000 at 11:25:00AM +1100, Andrew Morton wrote:
> > NMI Watchdog detected LOCKUP on CPU3, registers:
> Oh no. Another one. Could you please try this attached
> patch (against test11-pre2) and see if the diagnostics
> come out?
And yet another one... I applied your patch, and ra
"Pawe³ Kot" wrote:
>
> Hello,
>
> I've following error with 2.4.0-test{9|10|pre11pre1-ac1|pre11pre2-ac1}:
>
> NMI Watchdog detected LOCKUP on CPU3, registers:
>
> And then the machine hangs. No response at all.
> Always CPU3 is mentioned.
> The machine is:
> The latest Intel motherboard for 4x
> On Fri, 10 Nov 2000, [iso-8859-2] Paweł Kot wrote:
>
> > NMI Watchdog detected LOCKUP on CPU3, registers:
>
> > What can be wrong?
>
> You forgot to read the REPORTING-BUGS file.
>
> You told us everything except the really
> important information ... the backtrace from
> the info printed by th
On Fri, 10 Nov 2000, [iso-8859-2] Pawe³ Kot wrote:
> NMI Watchdog detected LOCKUP on CPU3, registers:
> What can be wrong?
You forgot to read the REPORTING-BUGS file.
You told us everything except the really
important information ... the backtrace from
the info printed by the NMI Oopser...
re
11 matches
Mail list logo
