From: "Shaun Reitan" <mailinglists@unix-scripts.com>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel panic - not syncing: Fatal exception in interupt
Date: Sun, 17 Apr 2005 13:32:42 -0700 [thread overview]
Message-ID: <d3ugtr$gml$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.61.0504120612210.14171@montezuma.fsmlabs.com
OK, finally got a full dump from the serial console! Here is it!
----------------------------------------------------------------------------
---------------------------------------
Unable to handle kernel paging request at virtual address f8b6f02c
printing eip:
f88b0078
*pde = 031f6067
Oops: 0000 [#1]
SMP
Modules linked in: loop tun ebt_ip ebt_arp ebtable_filter ebtables autofs4
ipv6
bridge e1000 ohci1394 ieee1394 floppy sg parport_pc parport ext3 jbd 3w_9xxx
sd_
mod scsi_mod
CPU: 0
EIP: 0060:[<f88b0078>] Not tainted VLI
EFLAGS: 00010286 (2.6.11.5-hr1)
EIP is at ebt_do_table+0x78/0x6e0 [ebtables]
eax: f8b6f000 ebx: f88b7000 ecx: f88b7080 edx: f88b7080
esi: c03e8d20 edi: c0438f08 ebp: 80000000 esp: c03e8c7c
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, threadinfo=c03e8000 task=c0333b60)
Stack: c0438dd8 80000000 c0294362 f7728580 c02a9010 00000003 00000003
c85c6012
f8816610 f8b6f000 f8b6f000 f8b39000 00000000 f88b7080 f88b7080
0000000a
0000000a f6646800 c03e8d1c 00000001 f8816620 c03e8d20 c0438f08
80000000
Call Trace:
[<c0294362>] nf_iterate+0x72/0xb0
[<c02a9010>] dst_output+0x0/0x20
[<c0294362>] nf_iterate+0x72/0xb0
[<f889e6d0>] br_pass_frame_up_finish+0x0/0x10 [bridge]
[<c0294708>] nf_hook_slow+0x68/0xf0
[<f889e6d0>] br_pass_frame_up_finish+0x0/0x10 [bridge]
[<f889e73a>] br_pass_frame_up+0x5a/0x60 [bridge]
[<f889e6d0>] br_pass_frame_up_finish+0x0/0x10 [bridge]
[<f889e7b9>] br_handle_frame_finish+0x79/0x110 [bridge]
[<f889e740>] br_handle_frame_finish+0x0/0x110 [bridge]
[<c0294752>] nf_hook_slow+0xb2/0xf0
[<f889e740>] br_handle_frame_finish+0x0/0x110 [bridge]
[<f88a231c>] br_nf_pre_routing_finish+0xfc/0x290 [bridge]
[<f889e740>] br_handle_frame_finish+0x0/0x110 [bridge]
[<c0113d20>] try_to_wake_up+0x220/0x250
[<c012dbeb>] autoremove_wake_function+0x1b/0x50
[<c0115737>] __wake_up_common+0x37/0x60
[<c0122386>] __mod_timer+0xd6/0x120
[<c0294362>] nf_iterate+0x72/0xb0
[<f88a2220>] br_nf_pre_routing_finish+0x0/0x290 [bridge]
[<f88a2220>] br_nf_pre_routing_finish+0x0/0x290 [bridge]
[<c0294752>] nf_hook_slow+0xb2/0xf0
[<f88a2220>] br_nf_pre_routing_finish+0x0/0x290 [bridge]
[<f88a29f7>] br_nf_pre_routing+0x257/0x410 [bridge]
[<f88a2220>] br_nf_pre_routing_finish+0x0/0x290 [bridge]
[<c0294362>] nf_iterate+0x72/0xb0
[<f889e740>] br_handle_frame_finish+0x0/0x110 [bridge]
[<f889e740>] br_handle_frame_finish+0x0/0x110 [bridge]
[<c0294708>] nf_hook_slow+0x68/0xf0
[<f889e740>] br_handle_frame_finish+0x0/0x110 [bridge]
[<f889e94a>] br_handle_frame+0xfa/0x1e0 [bridge]
[<f889e740>] br_handle_frame_finish+0x0/0x110 [bridge]
[<c028aa3d>] netif_receive_skb+0x13d/0x2c0
[<f888b42e>] e1000_clean_rx_irq+0x15e/0x4a0 [e1000]
[<c02849d9>] __kfree_skb+0xa9/0x150
[<f888b06a>] e1000_clean+0xba/0xf0 [e1000]
[<c028ad4f>] net_rx_action+0x6f/0x100
[<c011e909>] __do_softirq+0xb9/0xd0
[<c0104a8a>] do_softirq+0x4a/0x60
=======================
[<c0104953>] do_IRQ+0x63/0xb0
[<c010e7d0>] smp_apic_timer_interrupt+0xd0/0xe0
[<c01030c2>] common_interrupt+0x1a/0x20
[<c0100812>] mwait_idle+0x52/0x80
[<c0100650>] default_idle+0x0/0x30
[<c010071b>] cpu_idle+0x5b/0x70
[<c03ad911>] start_kernel+0x161/0x1a0
[<c03ad350>] unknown_bootoption+0x0/0x1e0
Code: 00 89 54 24 34 8b 43 20 c7 44 24 2c 00 00 00 00 85 c0 74 07 8b 0c 88
89 4c
24 2c 8b 44 24 4c 8b 4c 24 34 8b 44 83 08 89 44 24 28 <8b> 50 2c 89 c5 83
c5 30
89 54 24 3c 8b 40 24 c1 e0 04 01 c8 89
<0>Kernel panic - not syncing: Fatal exception in interrupt
----------------------------------------------------------------------------
-----------------------------
--
Best Regards,
Shaun Reitan
"Zwane Mwaikambo" <zwane@arm.linux.org.uk> wrote in message
news:Pine.LNX.4.61.0504120612210.14171@montezuma.fsmlabs.com...
> On Tue, 12 Apr 2005, mailinglist@unix-scripts.com wrote:
>
> > The machine crashed again twice today. I have vga=791 so i caugh a bit
more
> > of the crash. i enabled serial redirection in the bios so i'm hoping to
> > catch the full dump next time.
>
> Cool, can you also try Cc'ing netdev@oss.sgi.com?
>
> Thanks,
> Zwane
>
next prev parent reply other threads:[~2005-04-17 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 6:04 kernel panic - not syncing: Fatal exception in interupt shaun
2005-04-06 8:10 ` Zwane Mwaikambo
2005-04-06 21:00 ` mailinglist@unix-scripts.com
2005-04-07 8:09 ` Zwane Mwaikambo
2005-04-07 19:57 ` mailinglist@unix-scripts.com
2005-04-12 8:43 ` mailinglist@unix-scripts.com
2005-04-12 12:19 ` Zwane Mwaikambo
2005-04-17 20:32 ` Shaun Reitan [this message]
2005-04-18 6:07 ` Herbert Xu
2005-04-18 6:25 ` Shaun Reitan
2005-04-22 7:40 ` Shaun Reitan
2005-05-12 4:26 ` [stable] " Greg KH
-- strict thread matches above, loose matches on Subject: below --
2005-04-12 19:27 Kernel Panic - not syncing: Fatal Exception " Shaun Reitan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='d3ugtr$gml$1@sea.gmane.org' \
--to=mailinglists@unix-scripts.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.