From: Hans-Christian Armingeon <johnny@wh-netz.de>
To: xen-devel@lists.xensource.com
Cc: xen-users@lists.xensource.com
Subject: xen2 system crashing: Badness in br_fdb_cleanup at net/bridge/br_fdb.c:140
Date: Mon, 3 Apr 2006 11:16:12 +0200 [thread overview]
Message-ID: <200604031116.13274.johnny@wh-netz.de> (raw)
Hi There,
I am having serious troubles with one of my servers.
I installed ubuntu 5.10 on a second partition.
And after that, I booted the old system.
Now I am having these errors. They appear 3 minutes after reboot.
Has anyone a similar behaviour?
Many thanks in advance,
Johnny
Badness in br_fdb_cleanup at net/bridge/br_fdb.c:140
[<c8a5d49e>] br_fdb_cleanup+0xfe/0x130 [bridge]
[<c0123b61>] run_timer_softirq+0xf1/0x220
[<c0138470>] handle_IRQ_event+0x40/0x90
[<c8a5d3a0>] br_fdb_cleanup+0x0/0x130 [bridge]
[<c011f595>] __do_softirq+0x95/0xb0
[<c011f5f5>] do_softirq+0x45/0x50
[<c011f6c5>] irq_exit+0x35/0x40
[<c010ec3e>] do_IRQ+0x1e/0x30
[<c0105e7d>] evtchn_do_upcall+0x6d/0x90
[<c0109423>] hypervisor_callback+0x37/0x40
[<c0106f59>] xen_idle+0x29/0x50
[<c0106fba>] cpu_idle+0x3a/0x50
[<c0542740>] start_kernel+0x180/0x1d0
[<c0542300>] unknown_bootoption+0x0/0x1b0
Badness in br_fdb_cleanup at net/bridge/br_fdb.c:140
[<c8a5d49e>] br_fdb_cleanup+0xfe/0x130 [bridge]
[<c0123b61>] run_timer_softirq+0xf1/0x220
[<c0138470>] handle_IRQ_event+0x40/0x90
[<c8a5d3a0>] br_fdb_cleanup+0x0/0x130 [bridge]
[<c011f595>] __do_softirq+0x95/0xb0
[<c011f5f5>] do_softirq+0x45/0x50
[<c011f6c5>] irq_exit+0x35/0x40
[<c010ec3e>] do_IRQ+0x1e/0x30
[<c0105e7d>] evtchn_do_upcall+0x6d/0x90
[<c0109423>] hypervisor_callback+0x37/0x40
[<c0106f59>] xen_idle+0x29/0x50
[<c0106fba>] cpu_idle+0x3a/0x50
[<c0542740>] start_kernel+0x180/0x1d0
[<c0542300>] unknown_bootoption+0x0/0x1b0
Unable to handle kernel paging request at virtual address 00200200
printing eip:
c8a5d415
*pde = ma 00000000 pa 55555000
[<c0123b61>] run_timer_softirq+0xf1/0x220
[<c0138470>] handle_IRQ_event+0x40/0x90
[<c8a5d3a0>] br_fdb_cleanup+0x0/0x130 [bridge]
[<c011f595>] __do_softirq+0x95/0xb0
[<c011f5f5>] do_softirq+0x45/0x50
[<c011f6c5>] irq_exit+0x35/0x40
[<c010ec3e>] do_IRQ+0x1e/0x30
[<c0105e7d>] evtchn_do_upcall+0x6d/0x90
[<c0109423>] hypervisor_callback+0x37/0x40
[<c0106f59>] xen_idle+0x29/0x50
[<c0106fba>] cpu_idle+0x3a/0x50
[<c0542740>] start_kernel+0x180/0x1d0
[<c0542300>] unknown_bootoption+0x0/0x1b0
Oops: 0002 [#1]
PREEMPT
Modules linked in: bridge atm fcdslusb2 capi capifs ipv6 tsdev evdev fcpci kernelcapi i2c_amd756 i2c_amd8111 pci_hotplug ohci_hcd usbcore aic79xx sata_sil libata w83781d i2c_sensor i2c_isa i2c_core e100 mii tg3
CPU: 0
EIP: 0061:[<c8a5d415>] Tainted: P VLI
EFLAGS: 00211246 (2.6.11.12-xen0)
EIP is at br_fdb_cleanup+0x75/0x130 [bridge]
eax: 00000000 ebx: c3a5144c ecx: c04b04d8 edx: 00200200
esi: c3a51440 edi: c6227b04 ebp: c3ac7e88 esp: c0541f00
ds: 007b es: 007b ss: 0069
Process swapper (pid: 0, threadinfo=c0540000 task=c04aaea0)
Stack: c8a63f11 c8a63e09 c8a63efd 0000008c 00007530 c764f000 c0540000 00000101
c3ac7a20 c0540000 c0123b61 c3ac7a20 c0138470 00000082 00000000 c8a5d3a0
c8b443b8 c6e9d0ac c0540000 00000001 c058ab28 0000000a fbffc000 c011f595
Call Trace:
[<c0123b61>] run_timer_softirq+0xf1/0x220
[<c0138470>] handle_IRQ_event+0x40/0x90
[<c8a5d3a0>] br_fdb_cleanup+0x0/0x130 [bridge]
[<c011f595>] __do_softirq+0x95/0xb0
[<c011f5f5>] do_softirq+0x45/0x50
[<c011f6c5>] irq_exit+0x35/0x40
[<c010ec3e>] do_IRQ+0x1e/0x30
[<c0105e7d>] evtchn_do_upcall+0x6d/0x90
[<c0109423>] hypervisor_callback+0x37/0x40
[<c0106f59>] xen_idle+0x29/0x50
[<c0106fba>] cpu_idle+0x3a/0x50
[<c0542740>] start_kernel+0x180/0x1d0
[<c0542300>] unknown_bootoption+0x0/0x1b0
Code: 65 90 8d 74 26 00 8d 73 f4 8b 54 24 10 a1 60 e0 4a c0 03 56 18 39 d0 0f 88 9c 00 00 00 80 7e 23 00 75 68 8b 43 f4 8b 56 04 85 c0 <89> 02 74 03 89 50 04 80 7e 23 00 c7 46 04 00 02 20 00 75 17 8b
<0>Kernel panic - not syncing: Fatal exception in interrupt
(XEN) Domain 0 shutdown: rebooting machine.
(XEN) Reboot disabled on cmdline: require manual reset
--
jabber:johnny@wh-netz.de
icq:236971856
next reply other threads:[~2006-04-03 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 9:16 Hans-Christian Armingeon [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-02 14:33 xen2 system crashing: Badness in br_fdb_cleanup at net/bridge/br_fdb.c:140 Hans-Christian Armingeon
2006-04-02 14:11 Hans-Christian Armingeon
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=200604031116.13274.johnny@wh-netz.de \
--to=johnny@wh-netz.de \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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.