Your message dated Mon, 29 Dec 2008 21:16:44 +0100
with message-id <20081229201644.ga4...@galadriel.inutil.org>
and subject line Re: Ooops on Xen reboot
has caused the Debian Bug report #390724,
regarding Ooops on Xen reboot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
390724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.18-1-xen-amd64
Version: 2.6.18-2
Hi,
on rebooting my Xen dom0, I got this error message.
Cheers,
Andi
Kernel BUG at drivers/xen/netfront/netfront.c:717
invalid opcode: 0000 [1] SMP
CPU 0
Modules linked in: ipv6 dm_snapshot dm_mirror dm_mod evdev pcspkr ext3 jbd
mbcache raid1 md_mod
Pid: 8, comm: xenwatch Not tainted 2.6.18-1-xen-amd64 #1
RIP: e030:[<ffffffff8036f61b>] [<ffffffff8036f61b>]
network_alloc_rx_buffers+0x1de/0x460
RSP: e02b:ffff8800070d7de0 EFLAGS: 00010086
RAX: 0000000000000000 RBX: ffff8800083ebd80 RCX: 0000000000000040
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000001048
RBP: ffff8800013d8500 R08: ffffffff80455b88 R09: 0000000000000001
R10: 0000000000000001 R11: ffff88000156d460 R12: 0000000005605000
R13: ffff880007344838 R14: 0000000000000209 R15: ffff8800013ddae0
FS: 00002ae1cded4100(0000) GS:ffffffff804c3000(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
Process xenwatch (pid: 8, threadinfo ffff8800070d6000, task ffff8800070bc100)
Stack: ffff8800070d7e40 ffff8800013d8000 ffff88000145c000 000000000000000f
000000d100000100 ffff8800013f6d68 00000000000000d1 0000002f04ed2e70
0000000000000009 0000000000000001
Call Trace:
[<ffffffff80367a7b>] backend_changed+0x1c8/0x232
[<ffffffff80366920>] xenwatch_thread+0x0/0x145
[<ffffffff80290032>] keventd_create_kthread+0x0/0x61
[<ffffffff80365d2e>] xenwatch_handle_callback+0x15/0x48
[<ffffffff80366a4d>] xenwatch_thread+0x12d/0x145
[<ffffffff802901f5>] autoremove_wake_function+0x0/0x2e
[<ffffffff80290032>] keventd_create_kthread+0x0/0x61
[<ffffffff80366920>] xenwatch_thread+0x0/0x145
[<ffffffff802334f8>] kthread+0xd4/0x107
[<ffffffff8025d06c>] child_rip+0xa/0x12
[<ffffffff80290032>] keventd_create_kthread+0x0/0x61
[<ffffffff8024982d>] worker_thread+0x0/0x122
[<ffffffff8024982d>] worker_thread+0x0/0x122
[<ffffffff80233424>] kthread+0x0/0x107
[<ffffffff8025d062>] child_rip+0x0/0x12
Code: 0f 0b 68 ec ee 41 80 c2 cd 02 4c 63 e2 48 8d bd 80 15 00 00
RIP [<ffffffff8036f61b>] network_alloc_rx_buffers+0x1de/0x460
RSP <ffff8800070d7de0>
--
http://home.arcor.de/andreas-barth/
--- End Message ---
--- Begin Message ---
On Mon, Dec 29, 2008 at 08:54:31PM +0100, Andreas Barth wrote:
> * Moritz Muehlenhoff (j...@inutil.org) [081229 20:42]:
> > On Mon, Dec 29, 2008 at 08:32:42PM +0100, Andreas Barth wrote:
> > > * Moritz Muehlenhoff (j...@inutil.org) [081229 16:12]:
> > > > On Mon, Oct 02, 2006 at 08:07:34PM +0200, Andreas Barth wrote:
> > > > > Package: linux-image-2.6.18-1-xen-amd64
> > > > > Version: 2.6.18-2
> > > > >
> > > > > Hi,
> > > > >
> > > > > on rebooting my Xen dom0, I got this error message.
> > > >
> > > > Does this error occur reproducibly with current Etch Xen kernels?
> > >
> > > I had all strange kinds of errors and oops with xen, but none is
> > > reproducible. Sorry.
> >
> > So this is something that happened once and never again or does
> > it happen occasionally, but only not reproducibly?
>
> I cannot remember of having seen this oops again - and the bug report
> is now more than 2 years old, so sorry if details disappeared.
Thanks, closing the bug then.
Cheers,
Moritz
--- End Message ---
