how to capture long oops w/o having second machine

What's the best way to capture (manually or otherwise) a rather long oops that scrolls off my console without having a second machine?

I'm gonna try to compile in a framebuffer and use a high resolution and see if that'll hold it all when I get back later today.

Quoted 5 lines

What's the best way to capture (manually or otherwise) a rather long oops that scrolls off my console without having a second machine?

I'm gonna try to compile in a framebuffer and use a high resolution and see if that'll hold it all when I get back later today.

shift+pageup ?

shift+pageup ?

What's the best way to capture (manually or otherwise) a rather long oops that scrolls off my console without having a second machine?

What's the best way to capture (manually or otherwise) a rather long oops that scrolls off my console without having a second machine?

I'm gonna try to compile in a framebuffer and use a high resolution and see if that'll hold it all when I get back later today.

Someone gave me a really awesome idea about possibly using a palm pilot to capture the oops. Anyone know if it will be a problem using /dev/ttyUSB0 as the serial port?

Baiscally if I want to duplicate the environment in which I'm getting the oops, I need to be dialed out. That takes out COM1. I never gt my COM2 to work (can't figure out what's wrong. doesn't work under windows either). So that's out. I have a Keyspan USB PDA adapter that I use for my Palm Vx which shows up as /dev/ttyUSB0.

I guess if usb serial can't be used I'll try duplicating the oops w/o being dialed out.

Someone gave me a really awesome idea about possibly using a palm pilot to capture the oops. Anyone know if it will be a problem using /dev/ttyUSB0 as the serial port?

I don't know if /dev/ttyUSBX would work, but I think it would. People have successfully run consoles through the usb-serial drivers, but I'm not sure if the oops main console requires something different (like registering itself actually as a console?)

And then there's the nice problem of the fact that if the oops comes from the USB code, you will not see it come out the usb-serial driver :)

Let me know if you try this, and have any success (or find that it doesn't work.)

Nope, this didn't fly. Would have been neat if it did work. Maybe it can be made to work for future use?

Quoted 10 lines · Greg KH

I don't know if /dev/ttyUSBX would work, but I think it would. People have successfully run consoles through the usb-serial drivers, but I'm not sure if the oops main console requires something different (like registering itself actually as a console?)

And then there's the nice problem of the fact that if the oops comes from the USB code, you will not see it come out the usb-serial driver :)

Let me know if you try this, and have any success (or find that it doesn't work.)

Quoted 3 lines · Mohammad A. Haque

Someone gave me a really awesome idea about possibly using a palm pilot to capture the oops. Anyone know if it will be a problem using /dev/ttyUSB0 as the serial port?

The driver itself has to provide support for serial console. If the USB serial driver doesn't (I don't know) it won't work. Check the config options for USB serial, if it doesn't offer an option for console on USB serial port then you're out of luck.

Unless the USB serial driver in some strange way hooks into the standard serial driver, but then someone more knowledgeable should answer that question.

Try reading:

http://www.linuxhq.com/kernel/v2.3/doc/oops-tracing.txt.html

It mentions:

Patch the kernel with one of the crash dump patches. These save data to a floppy disk or video rom or a swap partition. None of these are standard kernel patches so you have to find and apply them yourself. Search kernel archives for kmsgdump, lkcd and oops+smram.

I don't know if the "dump to floppy" patch is maintained for the 2.4.0 series.

Miles

Quoted 14 lines · Mohammad A. Haque

Nope, this didn't fly. Would have been neat if it did work. Maybe it can be made to work for future use?

Quoted 8 lines · Greg KH

I don't know if /dev/ttyUSBX would work, but I think it would. People have successfully run consoles through the usb-serial drivers, but I'm not sure if the oops main console requires something different (like registering itself actually as a console?)

And then there's the nice problem of the fact that if the oops comes from the USB code, you will not see it come out the usb-serial driver :)

Quoted 2 lines

Quoted 2 lines

Let me know if you try this, and have any success (or find that it doesn't work.)

-
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/

i've always been curious why none of the crash dump patches are default. an oops dumper alone would seem to be most useful. (i know anything more would be unacceptable 'cause linus isn't into debuggers ;)

-dean

Quoted 10 lines

Someone gave me a really awesome idea about possibly using a palm pilot to capture the oops. Anyone know if it will be a problem using /dev/ttyUSB0 as the serial port?

Baiscally if I want to duplicate the environment in which I'm getting the oops, I need to be dialed out. That takes out COM1. I never gt my COM2 to work (can't figure out what's wrong. doesn't work under windows either). So that's out. I have a Keyspan USB PDA adapter that I use for my Palm Vx which shows up as /dev/ttyUSB0.

Quoted 2 lines

I guess if usb serial can't be used I'll try duplicating the oops w/o being dialed out.

I don't know if /dev/ttyUSBX would work, but I think it would. People have successfully run consoles through the usb-serial drivers, but I'm not sure if the oops main console requires something different (like registering itself actually as a console?)

Quoted 9 lines

Quoted 3 lines

Someone gave me a really awesome idea about possibly using a palm pilot to capture the oops. Anyone know if it will be a problem using /dev/ttyUSB0 as the serial port?

The driver itself has to provide support for serial console. If the USB serial driver doesn't (I don't know) it won't work. Check the config options for USB serial, if it doesn't offer an option for console on USB serial port then you're out of luck.

Quoted 3 lines

Unless the USB serial driver in some strange way hooks into the standard serial driver, but then someone more knowledgeable should answer that question.

Nope, it doesn't specifically support the CONFIG_SERIAL_CONSOLE with all of the register_console code, etc., so this will not work, sorry.

But it's something that I would gladly take a patch for :)