You are not logged in.
I first noticed this issue with linux-ck 4.13.11-1 and reported it in the relevant thread,
where I've been asked if it also happens with linux 4.13.11-1.
Turns out it does.
Thinkpad x230 runs boot process until Starting TLP system startup/shutdown... step and it just hangs there.
Pushing the power button does start the shutdown process so the computer is not fully unresponsive.
Offline
What's in the journal? Have you tried disabling tlp? What are you starting (GDM is my bet)?
Moving to NC...
Offline
Not sure which journal I should look into as I have made a number of tries with different kernels. IIRC journal had "Starting TLP system startup/shutdown..." then things related to shutting down.
I have not tried to disable TLP, I needed my computer working ASAP and so after a few tries I booted to 4.9 kernel and downgraded the problematic kernels.
My DM is SDDM, my desktop is KDE.
Offline
.
Last edited by masolit (2019-12-03 16:05:55)
Offline
Just wanted to confirm that i had the same problem.
Please do not do that Code_of_conduct#No_power-posting.2Fempty_posts
Edit:
What have you done to diagnose / resolve the issue?
Find the last release of the linux package that does not suffer from the issue. ( Download packages not cached locally from the ALA. )
What is in the journal from a failed boot? Is every other package up to date?
Last edited by loqs (2017-11-05 20:12:04)
Offline
Hi,
---------------
After writing the below message, I remembered that I had bfq as elevator. When I deleted that parameter from grub, it did boot. It was working normally before the full system update.
On grub menu, highlight the kernel you'd like to boot, press e, remove elevator=bfq, then press F10. And just change grub config to make it permanent.
---------------
I have the same problem. I will try to give brief info as I don't know how to get the dmesg from that unbootable system
model: 20FHCT01WW
kernels: 4.13.11-1 AND 4.13.11-1-ck-skylake
boot stops after 2nd panic code and before asking for disc encryption password.
all packages were updated
BUG: unable to handle kernel NULL pointer dereference at 0000000000000014
IP: blk_mp_init_sched+0x37/0x150
Oops: 0000 [#1] PREEMPT SMP
kworker/u8:0 Tainted G U
RIP: blk_mp_init_sched+0x37/0x150
Oops: 0000 [#2] PREEMPT SMP
kworker/u8:0 Tainted G UD
RIP: blk_mp_init_sched+0x37/0x150
call traces in both mention libata -> scsi_mod -> blk_init_allocated_queue -> elevator_init (ends with this)
Last edited by tr (2017-11-08 03:31:19)
Offline
Not sure which journal I should look into as I have made a number of tries with different kernels. IIRC journal had "Starting TLP system startup/shutdown..." then things related to shutting down.
I have not tried to disable TLP, I needed my computer working ASAP and so after a few tries I booted to 4.9 kernel and downgraded the problematic kernels.
My DM is SDDM, my desktop is KDE.
Does disabling SDDM help?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
I have not had the opportunity to run more test or even reboot the computer yet.
I'll do it at the first occasion.
Offline
What I did was to boot 4.9 kernel line to downgrade 4.13 to the last working version.
I just reinstalled 4.13.11-1 and upgraded linux-ck to the latest 4.13.12-2.
I first tried booting linux-ck 4.13.12-2 and it worked, then I tried linux 4.13.11-1 and it worked too.
I tried a few more reboots and cold boots but I am now unable to replicate the issue I had.
This is weird as I reinstalled from pacman local cache the same kernel I had the issue with and issue occurred every time.
Sorry I can't provide additional details about this.
Offline