On Fri, 8 Sep 2000, Andrew Burgess wrote: > > > >Oops from 2.2.17 (some more before this, but it went offscreen): > ... > > You need to capture and decode the first oops. Compile a kernel with a > > serial console and capture the oops log on a second machine. > > Or set your console for more than 80x25 using SVGATextMode. I use > /usr/sbin/SVGATextMode -rx 80x50x8 Or just fix the blinkin' oops code so that if it gets an exception when trying to print the offending code, it doesn't actually oops again. -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Keith Owens
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Rasmus Andersen
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Marcelo Tosatti
- Re: Oops on boot with both 2.2.17 and 2.4.0t8... Rasmus Andersen
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Rasmus Andersen
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Mike Galbraith
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Rasmus Andersen
- Re: Oops on boot with both 2.2.17 and 2.4.0t8... Mike Galbraith
- Re: Oops on boot with both 2.2.17 and 2.4... Rasmus Andersen
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Andrew Burgess
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 David Woodhouse
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Rasmus Andersen
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Marcelo Tosatti
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Rasmus Andersen
- Re: Oops on boot with both 2.2.17 and 2.4.0t8... Marcelo Tosatti
- Re: Oops on boot with both 2.2.17 and 2.4.0t8p6 Mike Galbraith