linux-next: 0907 fails to boot on thinkpad x60 (32bit machine)
Hi!
I do have some oopses, but they seem to be different on each boot. IIRC message was "scheduling?...on offline CPU?".
Any ideas? Does it work for you?
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Quoted 6 lines · Pavel Machek
Hi!
I do have some oopses, but they seem to be different on each boot. IIRC message was "scheduling?...on offline CPU?".
Any ideas? Does it work for you?
Seems that error is different on each try.
Now it is:
FS: Cannot open root device "sda4" or unknown-block(8,4): error -2 (followed by panic, but it listed sda4 as avialbe partition)
Next try:
sched: Unexpected reschedule of offline CPU#0!
WARNING: CPU: 1 PID: 1 at ...smp.c:128 native_smp_send_reschedule
(Aha, that's what I seen before)
Next try:
sched: Unexpected reschedule of offline CPU#0!
Next try: I added "nosmp" on command line, and got
FS: Cannot open root device "sda4" or unknown-block(8,4): error -2 (followed by panic, but it listed sda4 as avialbe partition)
Next try: with "l1tf=off nospectre_v2 nospec_store_bypass_disable"
FS: Cannot open root device "sda4" or unknown-block(8,4): error -2 (followed by panic, but it listed sda4 as avialbe partition)
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next-20180910: boots on thinkpad x60 (32bit machine) but has problems during suspend
Hi!
Quoted 24 lines
Quoted 4 lines
I do have some oopses, but they seem to be different on each boot. IIRC message was "scheduling?...on offline CPU?".
Any ideas? Does it work for you?
Seems that error is different on each try.
Now it is:
FS: Cannot open root device "sda4" or unknown-block(8,4): error -2 (followed by panic, but it listed sda4 as avialbe partition)
Next try:
sched: Unexpected reschedule of offline CPU#0!
WARNING: CPU: 1 PID: 1 at ...smp.c:128 native_smp_send_reschedule(Aha, that's what I seen before)
Next try:
sched: Unexpected reschedule of offline CPU#0!
Next try: I added "nosmp" on command line, and got
Quoted 7 lines
FS: Cannot open root device "sda4" or unknown-block(8,4): error -2 (followed by panic, but it listed sda4 as avialbe partition)
Next try: with "l1tf=off
nospectre_v2nospec_store_bypass_disable"FS: Cannot open root device "sda4" or unknown-block(8,4): error -2 (followed by panic, but it listed sda4 as avialbe partition)
Next -0910 seems to boot ok... but when I hit the power button to suspend the machine... Full dmesg is in the attachment.
Pavel
[ 22.372485] netlink: 16 bytes leftover after parsing attributes in process `ip'. [ 22.372680] netlink: 16 bytes leftover after parsing attributes in process `ip'. [ 233.629560] wlan0: deauthenticating from 00:00:00:00:00:01 by local choice (Reason: 3=DEAUTH_LEAVING) [ 233.827466] PM: suspend entry (deep) [ 233.827478] PM: Syncing filesystems ... [ 233.853369] netlink: 16 bytes leftover after parsing attributes in process `ip'. [ 233.853638] netlink: 16 bytes leftover after parsing attributes in process `ip'. [ 243.146818] INFO: task kworker/u4:6:1174 blocked for more than 120 seconds. [ 243.146836] Not tainted 4.19.0-rc2-next-20180910 #157 [ 243.146844] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 243.146854] kworker/u4:6 D 0 1174 2 0x80000000 [ 243.146889] Workqueue: writeback wb_workfn (flush-8:0) [ 243.146903] Call Trace: [ 243.146917] __schedule+0x390/0x7f0 [ 243.146926] schedule+0x29/0x70 [ 243.146935] io_schedule+0x10/0x40 [ 243.146946] __lock_page+0xd3/0x100 [ 243.146955] ? page_cache_tree_insert+0xb0/0xb0 [ 243.146966] mpage_prepare_extent_to_map+0x217/0x260 [ 243.146976] ? kmem_cache_alloc+0xd2/0xe0 [ 243.146986] ? ext4_init_io_end+0x13/0x30 [ 243.146995] ext4_writepages+0x2cf/0x6c0 [ 243.147005] ? writeback_sb_inodes+0x111/0x360 [ 243.147015] do_writepages+0x1d/0x70 [ 243.147024] __writeback_single_inode+0x2a/0x180 [ 243.147033] writeback_sb_inodes+0x1ea/0x360 [ 243.147042] __writeback_inodes_wb+0x7c/0xb0 [ 243.147051] wb_writeback+0x189/0x1a0 [ 243.147060] wb_workfn+0x14f/0x2d0 [ 243.147069] ? __lock_acquire.isra.25+0x4d3/0x8c0 [ 243.147079] process_one_work+0x17e/0x360 [ 243.147087] ? process_one_work+0x123/0x360 [ 243.147096] worker_thread+0x39/0x3b0 [ 243.147105] kthread+0xe7/0x120 [ 243.147113] ? process_one_work+0x360/0x360 [ 243.147122] ? kthread_park+0xa0/0xa0 [ 243.147131] ret_from_fork+0x2e/0x38 [ 243.147177] INFO: task zeitgeist-daemo:3648 blocked for more than 120 seconds. [ 243.147185] Not tainted 4.19.0-rc2-next-20180910 #157 [ 243.147191] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 243.147198] zeitgeist-daemo D 0 3648 1 0x00000004 [ 243.147210] Call Trace: [ 243.147219] __schedule+0x390/0x7f0 [ 243.147228] schedule+0x29/0x70
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Re: next-20180910: boots on thinkpad x60 (32bit machine) but has problems during suspend
Quoted 3 lines · Pavel Machek
Next -0910 seems to boot ok... but when I hit the power button to suspend the machine... Full dmesg is in the attachment.
Is this a next only issue or is this happening on Linus tree as well?
Thanks,
tglx
Re: next-20180910: boots on thinkpad x60 (32bit machine) but has problems during suspend
Hi!
Quoted 4 lines
Quoted 2 lines
Next -0910 seems to boot ok... but when I hit the power button to suspend the machine... Full dmesg is in the attachment.
Is this a next only issue or is this happening on Linus tree as well?
I believe this only happens in next. I'm pretty sure v4.19-rc1 was ok. Let me check v4.19-rc3... that one is ok.
Best regards,
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Re: next-20180910: boots on thinkpad x60 (32bit machine) but has problems during suspend
Hi!
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
Next -0910 seems to boot ok... but when I hit the power button to suspend the machine... Full dmesg is in the attachment.
Is this a next only issue or is this happening on Linus tree as well?
I believe this only happens in next. I'm pretty sure v4.19-rc1 was ok. Let me check v4.19-rc3... that one is ok.
I tested next-0913, and that seems to have no obvious problems.
Best regards,
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html