Your message dated Mon, 15 Feb 2010 20:18:14 +0100
with message-id <[email protected]>
and subject line Re: Xen || vserver troubles
has caused the Debian Bug report #446148,
regarding linux-image-2.6.18-5-xen-amd64: domU panic with swiotlb=force
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 [email protected]
immediately.)
--
446148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446148
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6.18-5-xen-amd64
Version: 2.6.18.dfsg.1-13etch4
Severity: normal
Using swiotlb=force panics the kernel reaaaaaly quick:
Bootdata ok (command line is root=/dev/sda1 ro swiotlb=force)
Linux version 2.6.18-5-xen-amd64 (Debian 2.6.18.dfsg.1-13etch4)
([email protected]) (gcc version 4.1.2 20061115 (prerelease) (Debian
4.1.1-21)) #1 SMP Tue Oct 2 21:48:12 UTC 2007
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000035a00000 (usable)
No mptable found.
Built 1 zonelists. Total pages: 219648
Kernel command line: root=/dev/sda1 ro swiotlb=force
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Xen reported: 1800.061 MHz processor.
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at lib/../arch/i386/kernel/swiotlb.c:162
invalid opcode: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.18-5-xen-amd64 #1
RIP: e030:[<ffffffff8030c7f8>] [<ffffffff8030c7f8>]
swiotlb_init_with_default_size+0xa0/0x19e
RSP: e02b:ffffffff804dbf40 EFLAGS: 00010282
RAX: 00000000fffffff4 RBX: 0000000000000000 RCX: 0000000000000006
RDX: ffffffffff578000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000004000000 R08: 0000000000001000 R09: ffffffff80522040
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffffffff804c4000(0000)
knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff804da000, task
ffffffff8044bce0)
Stack: 0000000000000000 0000000000000800 0000000000000000
ffffffff8026e280
0000000000000000 ffffffff804ecf2a 0000000000000000 0000000000000800
0000000000000000 0000000000000000
Call Trace:
[<ffffffff8026e280>] pci_swiotlb_init+0x9/0x2d
[<ffffffff804ecf2a>] mem_init+0x5e/0x233
[<ffffffff804e36ea>] start_kernel+0x189/0x21a
[<ffffffff804e320d>] _sinittext+0x20d/0x213
Code: 0f 0b 68 e1 36 41 80 c2 a2 00 48 83 eb 80 48 8b 05 bb 20 24
RIP [<ffffffff8030c7f8>]
swiotlb_init_with_default_size+0xa0/0x19e
RSP <ffffffff804dbf40>
<0>Kernel panic - not syncing: Attempted to kill the idle task!
I was hoping this would fix the problem that usblp cannot allocate write
buffers for an USB connected printer.
But alas, this doesn't even produce a working domU.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (990, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-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-5-xen-amd64 depends on:
ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib
ii initramf 0.85h tools for generating an initramfs
ii linux-mo 2.6.18.dfsg.1-13etch4 Linux 2.6.18 modules on AMD64
linux-image-2.6.18-5-xen-amd64 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
the 2.6.18 linux images from Etch are no longer supported, thus closing
this bug report. As both Xen or vserver stayed out of tree it is very
unlikely that they improved a lot since.
With modern hardware kvm or lxc (linux containers) are recommended.
if you still haven't upgraded to Lenny please notice that Etch has
no security support any more as of today:
http://www.debian.org/News/2010/20100121
if you can reproduce said bugs with 2.6.32 linux images from
unstable please shout on said box and bug can be reopened:
reportbug -N <bugnr>
thank you for your report.
--- End Message ---
