On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
> > panic_on_oops has no effect, a bunch of stuff flies past and the last
> > thing I see is "gam_server: scheduling while atomic" then a stack trace
> > of the core dump path then "Aiee, killing interrupt handler".
> >
> > I am starting to
On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
> > panic_on_oops has no effect, a bunch of stuff flies past and the last
> > thing I see is "gam_server: scheduling while atomic" then a stack trace
> > of the core dump path then "Aiee, killing interrupt handler".
> >
> > I am starting to
> panic_on_oops has no effect, a bunch of stuff flies past and the last
> thing I see is "gam_server: scheduling while atomic" then a stack trace
> of the core dump path then "Aiee, killing interrupt handler".
>
> I am starting to suspect the hard drive, does that sound plausible?
> It's as if it
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
> On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
>
> > I have a machine here that oopses reliably when I start X, but the
> > interesting stuff scrolls away too fast, and a bunch more Oopses get
> > printed ending with "Aieee,
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
> On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
>
> > I have a machine here that oopses reliably when I start X, but the
> > interesting stuff scrolls away too fast, and a bunch more Oopses get
> > printed ending with "Aieee,
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
> I have a machine here that oopses reliably when I start X, but the
> interesting stuff scrolls away too fast, and a bunch more Oopses get
> printed ending with "Aieee, killing interrupt handler".
>
> How do I get the output to stop
On Sat, 2005-07-30 at 19:48 -0400, Lee Revell wrote:
> I have a machine here that oopses reliably when I start X, but the
> interesting stuff scrolls away too fast, and a bunch more Oopses get
> printed ending with "Aieee, killing interrupt handler".
>
> How do I get the output to stop after the
On Sat, 2005-07-30 at 19:48 -0400, Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing interrupt handler.
How do I get the output to stop after the first
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing interrupt handler.
How do I get the output to stop after the
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing
On Sun, 2005-07-31 at 02:11 +0200, Alexander Nyberg wrote:
On Sat, Jul 30, 2005 at 07:48:11PM -0400 Lee Revell wrote:
I have a machine here that oopses reliably when I start X, but the
interesting stuff scrolls away too fast, and a bunch more Oopses get
printed ending with Aieee, killing
panic_on_oops has no effect, a bunch of stuff flies past and the last
thing I see is gam_server: scheduling while atomic then a stack trace
of the core dump path then Aiee, killing interrupt handler.
I am starting to suspect the hard drive, does that sound plausible?
It's as if it locks up
On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
panic_on_oops has no effect, a bunch of stuff flies past and the last
thing I see is gam_server: scheduling while atomic then a stack trace
of the core dump path then Aiee, killing interrupt handler.
I am starting to suspect the hard
On Sun, 2005-07-31 at 10:40 +1000, Dave Airlie wrote:
panic_on_oops has no effect, a bunch of stuff flies past and the last
thing I see is gam_server: scheduling while atomic then a stack trace
of the core dump path then Aiee, killing interrupt handler.
I am starting to suspect the hard
14 matches
Mail list logo
