[lkml]   [2000]   [Feb]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: wq bug, forcing oops.
On Sun, 20 Feb 2000, Q wrote:

> On Sun, Feb 20, 2000 at 06:52:49AM +0100, Mike Galbraith wrote:
> > On Sat, 19 Feb 2000, Q wrote:
> >
> > > When I stopped a program, my screen got filled with:
> > > wq bug, forcing oops.
> >
> > If the EIP: XXXX:[<address>] bit stays on screen long enough, write
> > down the address and look up the next lower address in your
> No it didn't, it just scrolled those of my screen before I can see it.
> Looks like he was in some loop trying to force an oops or something, or
> had it 100 times a second?
> > > After a few second, it rebooted. I can't find anything in the logs.
> >
> > Make sure that you aren't using 'panic=n(secs)' on the command line.
> I'm not. Normally it does not reboot after an Oops.

If you have another machine there, you can set up a serial console
(Documentation/serial-console.txt), or if not but you do have a line
printer, enable lp-console and boot with console=lp console=tty.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:56    [W:0.037 / U:0.116 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site