RE: Fedora Core V2 Upgrade Woes

Mark Sansome <[email protected]>
Newsgroups gmane.linux.drivers.at76c503a.user
Message-ID <[email protected]>
On Tue, 2004-06-08 at 21:51, Joerg Albert wrote:
> Hi Kevin and Mark,
>
>  Mark could you please try this out, maybe as
> 
> 	sleep 5; iwconfig ...
> 
> and switch to the console during the 5 seconds sleep to watch the kernel
> panic. We need more info, i.e. the crash dump incl. the call back,
> to analyze anything (sometimes a digital camera comes handy here...).


Hi Jörg,

1) I don't know if this helps, but the attached file is a transcript of
my boot-up error.

With the Belkin plugged in, I booted into Linux (dual boot system). On
"probing for new hardware" the system freezes completely - no
possibility of an elegant escape, just have to hold down the power-off
button until the system stops - Then I re-booted, still with the Belkin
plugged in, and the system starts spewing out thousands of lines of
errors until eventually it stops with the attached output being the only
visible remainder of the errors (please note that I had to take down the
details with pencil & paper and then transcribe them into a file for you
so there are plenty of possibilities for transcription errors - but I
think I have most of it right).

2) I there any way of piping console output to a file?

If I boot (successfully) with the Belkin unplugged, and then run my
little script (which has all the modprobe/iwconfig... commands) in a
console, instead of a terminal window in Gnome, I get some interesting
output - but a little too much to write down and transcribe accurately.
(Also if I unplug and replug the Belkin). Unfortunately I don't know of
any way of capturing the output - does CTRL+SHIFT+C work? (I don't have
a [usable] digital camera I'm afraid).

Look forward to hearing from you.

Many thanks and best regards

Mark
boot fail (text/plain, 878 B)
[<02118726>] __call_consoledrivers+0x36/0x42
[<02114408>] do_page_fault+0x0/0x446
[<0210606e>] show_trace+0x3e/0x97
[<02106142>] show_stack+00x76/0x81
[<02106234>] show_registers+0xd9/0x172
[<02106386>] die+0x59/0xaf
[<021146ff>] do_page_fault+0x2f7/0x446
[<0210606e>] show_trace+0x3e/0x97
[<021c54a2>] scrup+068/0x10f
[<021c5af9>] complement_pos+0xf/0x128
[<021c5fab>] set_cursor+0x62/0x6e
[<021c8de7>] vt_console_print+0x271/0x28f
[<021c8b76>] vt_console_print+0x0/0x28f
[<02118726>] __call_consoledrivers+0x36/0x42
[<02114408>] do_page_fault+0x0/0x446
[<0210606e>] show_trace+0x3e/0x97
[<02106142>] show_stack+00x76/0x81
[<02106234>] show_registers+0xd9/0x172
[<02106386>] die+0x59/0xaf
[<021146ff>] do_page_fault+0x2f7/0x446

Code : ff b0 88 00 00 00 51 68 5f d0 28 02 e8 b1 26 01 00 83 c4 14
 <0>Kernel panic:Fatal exception in interrupt
In interrupt handler - not syncing
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.