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

Bug#1029270: marked as done (linux-image-6.1.0-2-686-pae fails to boot in qemu)

Your message dated Wed, 1 Feb 2023 14:59:06 +0100
with message-id <Y9pwKoox0TXVU0ph@eldamar.lan>
and subject line Re: Bug#1029270: linux-image-6.1.0-2-686-pae fails to boot in qemu
has caused the Debian Bug report #1029270,
regarding linux-image-6.1.0-2-686-pae fails to boot in qemu
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 owner@bugs.debian.org
immediately.)


-- 
1029270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029270
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-6.1.0-2-686-pae
Version: 6.1.7-1
Severity: important
Control: affects -1 + debvm

A CI job of debvm started failing. debvm creates a minimalistic virtual
machine based on Debian unstable i386 and tries to run it in qemu. With
the previous kernel package that worked. Once updating to 6.1.7-1, it
fails to boot:

https://salsa.debian.org/helmutg/debvm/-/jobs/3824112
| [    1.158184] traps: PANIC: double fault, error_code: 0x0
| [    1.158184] double fault: 0000 [#1] PREEMPT SMP PTI
| [    1.158184] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.1.0-2-686-pae #1  Debian 6.1.7-1
| [    1.158184] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-debian-1.16.0-5 04/01/2014
| [    1.158184] EIP: __kmem_cache_alloc_node+0xc4/0x350
| [    1.158184] Code: 85 c9 0f 84 6e 02 00 00 8b 75 f0 8b 47 1c 01 f0 89 c1 8b 00 33 47 78 0f c9 31 c8 8d 4a 20 89 c3 89 f0 8b 37 64 0f c7 0e 75 ba <8b> 75 e8 8b 47 1c 8d 74 26 00 3e 8d 74 26 00 3e 8d 74 26 00 8b 47
| [    1.158184] EAX: c11ed0c0 EBX: c11ed300 ECX: 00000301 EDX: 000002e1
| [    1.158184] ESI: d6e1e978 EDI: c10013c0 EBP: c1145e4c ESP: c1145e30
| [    1.158184] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: c11ed2c2
| [    1.158184] CR0: 80050033 CR2: 00000000 CR3: 16e2c000 CR4: 000006b0
| [    1.158184] Call Trace:
| [    1.158184]  __kmalloc+0x42/0x140
| [    1.158184]  ? cache_random_seq_create+0x81/0x130
| [    1.158184]  ? cache_random_seq_create+0x81/0x130
| [    1.158184]  cache_random_seq_create+0x81/0x130
| [    1.158184]  init_cache_random_seq+0x39/0x80
| [    1.158184]  __kmem_cache_create+0x10f/0x470
| [    1.158184]  kmem_cache_create_usercopy+0x158/0x2a0
| [    1.158184]  kmem_cache_create+0x17/0x20
| [    1.158184]  proto_register+0x183/0x240
| [    1.158184]  ? ipv4_offload_init+0x6e/0x6e
| [    1.158184]  inet_init+0x37/0x261
| [    1.158184]  do_one_initcall+0x4b/0x1e0
| [    1.158184]  kernel_init_freeable+0x1a5/0x1e5
| [    1.158184]  ? rest_init+0xb0/0xb0
| [    1.158184]  kernel_init+0x17/0x100
| [    1.158184]  ret_from_fork+0x1c/0x28
| [    1.158184] Modules linked in:
| [    1.158184] ---[ end trace 0000000000000000 ]---
| [    1.158184] EIP: __kmem_cache_alloc_node+0xc4/0x350
| [    1.158184] Code: 85 c9 0f 84 6e 02 00 00 8b 75 f0 8b 47 1c 01 f0 89 c1 8b 00 33 47 78 0f c9 31 c8 8d 4a 20 89 c3 89 f0 8b 37 64 0f c7 0e 75 ba <8b> 75 e8 8b 47 1c 8d 74 26 00 3e 8d 74 26 00 3e 8d 74 26 00 8b 47
| [    1.158184] EAX: c11ed0c0 EBX: c11ed300 ECX: 00000301 EDX: 000002e1
| [    1.158184] ESI: d6e1e978 EDI: c10013c0 EBP: c1145e4c ESP: c1145e30
| [    1.158184] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: c11ed2c2
| [    1.158184] CR0: 80050033 CR2: 00000000 CR3: 16e2c000 CR4: 000006b0
| [    1.158184] Kernel panic - not syncing: Fatal exception in interrupt

You can easily reproduce this by installing debvm, running `debvm-create
-a i386` (which will create a rootfs.ext4) and then `debvm-run`.

The only other packages changed since the last successful run are:
 * openssl
 * glib2.0
 * mmdebstrap

We can rule out mmdebstrap as a cause by adding `-r bookworm` to the
invocation and seeing that things boot. The other packages shouldn't be
able to cause a kernel panic.

Let me know if you need anything else.

Helmut

--- End Message ---
--- Begin Message --- 
Source: linux
Source-Version: 6.1.8-1

Hi

On Tue, Jan 31, 2023 at 05:05:53PM +0100, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Fri, Jan 20, 2023 at 04:42:27PM +0100, Helmut Grohne wrote:
> > Control: severity -1 normal
> > 
> > On Fri, Jan 20, 2023 at 03:55:53PM +0100, Helmut Grohne wrote:
> > > A CI job of debvm started failing. debvm creates a minimalistic virtual
> > > machine based on Debian unstable i386 and tries to run it in qemu. With
> > > the previous kernel package that worked. Once updating to 6.1.7-1, it
> > > fails to boot:
> > 
> > I have one more data point. If you pass -enable-kvm to qemu, it actually
> > boots. It only fails to boot when disabling kvm. That shouldn't affect
> > that many users. It's still unclear what causes the issue.
> > 
> > I'm also pulling qemu maintainer mjt into the discussion for possible
> > input.
> 
> I cannot now confirm the issue anymore with 6.1.8-1 as uploaded to
> unstable. So think we can close the bug accordingly with 6.1.8-1
> though it would be good to know/pin point the issue.

Doing for now. Still think would be nice to know the root cause.

Regards,
Salvatore

--- End Message ---
Reply to: