On Wed, Oct 10, 2007 at 08:42:52PM +0200, Jan Evert van Grootheest wrote: > 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) > (da...@debian.org) (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.
Did you upgrade to Lenny in the mean time? If so, does the error persist? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org