[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#392449: marked as done (linux-image-2.6.18-1-xen-amd64: 2.6.18-xen-amd64 domU: bug on console)

Your message dated Wed, 30 Jan 2008 18:43:45 +0100
with message-id <20080130174345.GC12407@stro.at>
and subject line linux-image-2.6.18-1-xen-amd64: 2.6.18-xen-amd64 domU: bug on console
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-image-2.6.18-1-xen-amd64
Version: 2.6.18-2
Severity: important

After I started a domU yesterday (of the mentioned linux-image package), I found a BUG on
its console today when I returned to it.
>From kern.log I snipped this copy.

Oct 10 23:15:01 janus kernel: Call Trace:
Oct 10 23:15:01 janus kernel:  <IRQ> [<ffffffff802a029d>] softlockup_tick+0xdb/0
xed
Oct 10 23:15:01 janus kernel:  [<ffffffff8026859a>] timer_interrupt+0x38d/0x3db
Oct 10 23:15:01 janus kernel:  [<ffffffff80211151>] handle_IRQ_event+0x2d/0x60
Oct 10 23:15:01 janus kernel:  [<ffffffff802a05dc>] __do_IRQ+0xa4/0x105
Oct 10 23:15:01 janus kernel:  [<ffffffff80283dc0>] _local_bh_enable+0x59/0xb3
Oct 10 23:15:01 janus kernel:  [<ffffffff80266d96>] do_IRQ+0x65/0x73
Oct 10 23:15:01 janus kernel:  [<ffffffff803610a4>] evtchn_do_upcall+0x86/0xe0
Oct 10 23:15:01 janus kernel:  [<ffffffff8025ce06>] do_hypervisor_callback+0x1e/
0x2c
Oct 10 23:15:01 janus kernel:  <EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0
x1000
Oct 10 23:15:01 janus kernel:  [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000
Oct 10 23:15:01 janus kernel:  [<ffffffff80267b16>] raw_safe_halt+0x84/0xa8
Oct 10 23:15:01 janus kernel:  [<ffffffff80264d99>] xen_idle+0x38/0x4a
Oct 10 23:15:01 janus kernel:  [<ffffffff80248b21>] cpu_idle+0x97/0xba
Oct 10 23:15:01 janus kernel:  [<ffffffff804e3776>] start_kernel+0x215/0x21a
Oct 10 23:15:01 janus kernel:  [<ffffffff804e320d>] _sinittext+0x20d/0x213



In case it is important, dom0 is running the same kernel.
Xen (hypervisor, tools etc) is from
ii  xen-hypervisor-3.0-unstable-1-amd64 3.0-unstable+hg11561-1 The Xen Hypervisor on AMD64
ii  xen-tools                           2.6-1                  Tools to manage debian XEN virtual servers
ii  xen-utils-3.0-unstable-1            3.0-unstable+hg11561-1 XEN administrative tools
ii  xen-utils-common                    3.0+hg11624-1          XEN administrative tools - common files

I'm running the -unstable- version because the normal one doesn't even finish booting (hangs at some XEN
message about the display; don't remember exact text).

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-xen-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-1-xen-amd64 depends on:
ii  e2fsprogs                     1.39-1     ext2 file system utilities and lib
ii  initramfs-tools               0.82       tools for generating an initramfs
ii  linux-modules-2.6.18-1-xen-am 2.6.18-2   Linux 2.6.18 modules on AMD64

linux-image-2.6.18-1-xen-amd64 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.6.18-3

afair fixed by disabling serial or such,

--- End Message ---
Reply to: