*** This bug has been split off bug 149018 ***

------- Original comment by Jure PeÄar on 2005.02.17 17:45 -------

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; rv:1.7.3) Gecko/20041014 Firefox/0.10.1

Description of problem:
I have all my servers' serial consoles connected to one machine with many serial
ports, where I can access them via minicom. I also have watchdog modules
configured on servers to autoreboot them in case of problems.

Every now and then some server goes down with an oops. My idea for this serial
console setup was simplified oops capturing, but there's a problem: when
watchdog reboots the server, bios actually redraws the whole screen, deleting
all the oops info. So I was thinking ... Could it be possible to add a simple
loop to the oops printing function that would print a number of newlines after
the oops info, where number would be taken as a kernel boot line parameter? So
that bios would redraw over already blank screen and I could just scroll minicom
buffer up to get the oops.

Version-Release number of selected component (if applicable):
any kernel

How reproducible:
Always

Steps to Reproduce:
1. set up a server with console on serial port and watchdog timer to reboot it
2. make someting to oops it
3. watch the console in minicom and observe bios overwriting oops data
  

Additional info:

I don't know if this can be acomplished with some minicom setting or possibly
with using something else than minicom for serial terminal. If it is, I'd like
to know how to do it. Afterall, I'd like to see where my machines are oopsing
and figure out why.