From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH] qemui386-buster: Switch to linux-image intended for older PCs
Date: Mon, 1 Apr 2019 16:56:12 +0200 [thread overview]
Message-ID: <20190401145612.31564-1-mosipov@ilbers.de> (raw)
linux-image with suffix 686-pae frequently experiences
problems during boot:
[ 30.458173] ------------[ cut here ]------------
[ 30.458649] kernel BUG at arch/x86/kernel/alternative.c:726!
[ 30.459483] invalid opcode: 0000 [#1] SMP PTI
[ 30.459960] CPU: 0 PID: 176 Comm: systemd-udevd Tainted: G OE 4.19.0-4-686-pae #1 Debian 4.19.28-2
[ 30.460749] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014
[ 30.461571] EIP: text_poke+0x1bc/0x250
[ 30.461932] Code: 0f b6 07 38 01 75 23 8b 55 e8 8d 47 01 8d 34 1f 83 c2 01 8d 76 00 39 f0 74 14 0f b6 18 0f b6 0a 83 c0 01 83 c2 01 38 cb 74 ec <0f> 0b 66 90 8b 45 dc 50 9d 8d 74 26 00 8d 65 f4 89 f8 5b 5e 5f 5d
[ 30.463339] EAX: 000000f0 EBX: 00000001 ECX: f642be1b EDX: ffd30000
[ 30.463828] ESI: d0060b90 EDI: f7c00350 EBP: f642be00 ESP: f642bddc
[ 30.464328] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00200007
[ 30.464864] CR0: 80050033 CR2: f9a00000 CR3: 3642c000 CR4: 000006b0
[ 30.465453] Call Trace:
[ 30.466264] alternatives_smp_module_add+0x141/0x150
[ 30.466768] module_finalize+0x137/0x160
[ 30.467134] load_module+0x1a47/0x1e90
[ 30.467472] ? kernel_read_file+0x1e7/0x220
[ 30.467844] sys_finit_module+0x89/0xe0
[ 30.468217] do_fast_syscall_32+0x81/0x184
[ 30.468573] entry_SYSENTER_32+0x6b/0xbe
[ 30.478343] EIP: 0xb7ef0d71
[ 30.487659] Code: f6 ff ff 55 89 e5 8b 55 08 8b 80 5c cd ff ff 85 d2 74 02 89 02 5d c3 8b 04 24 c3 8b 1c 24 c3 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76
[ 30.507802] EAX: ffffffda EBX: 0000000f ECX: b7d00bdd EDX: 00000000
[ 30.517900] ESI: 00fba390 EDI: 00fba140 EBP: 00000000 ESP: bfbf781c
[ 30.527949] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00200292
[ 30.538212] Modules linked in: bochs_drm ttm drm_kms_helper evdev drm pcspkr serio_raw sg parport_pc parport qemu_fw_cfg button example_module(OE) ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb crypto_simd cryptd aes_i586 sr_mod cdrom sd_mod ata_generic ata_piix libata psmouse scsi_mod e1000 i2c_piix4 floppy
[ 30.571056] ---[ end trace c162d77644e01483 ]---
Switch to other linux-image flavor (intended for older PCs),
which behaves stable.
Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
---
meta-isar/conf/multiconfig/qemui386-buster.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-isar/conf/multiconfig/qemui386-buster.conf b/meta-isar/conf/multiconfig/qemui386-buster.conf
index 4216d85..6b5a18e 100644
--- a/meta-isar/conf/multiconfig/qemui386-buster.conf
+++ b/meta-isar/conf/multiconfig/qemui386-buster.conf
@@ -5,7 +5,7 @@ MACHINE ?= "qemui386"
DISTRO ?= "debian-buster"
DISTRO_ARCH ?= "i386"
-KERNEL_NAME ?= "686-pae"
+KERNEL_NAME ?= "686"
IMAGE_TYPE ?= "wic-img"
WKS_FILE ?= "directdisk-isar"
--
2.11.0
next reply other threads:[~2019-04-01 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 14:56 Maxim Yu. Osipov [this message]
2019-04-02 14:54 ` Maxim Yu. Osipov
2019-04-12 17:14 ` Henning Schild
2019-04-13 5:51 ` Maxim Yu. Osipov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190401145612.31564-1-mosipov@ilbers.de \
--to=mosipov@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox