I just upgraded to Ubuntu 24.04, kernel 6.8.0-48. Still won't boot
without intremap=off
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without no
I just upgraded to Ubuntu 22.04 and I'm still affected by this bug. I
tried with the latest kernel (5.15.0-47) and it won't boot without
intremap=off
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Description changed:
+ (For anyone coming to this bug for the first time, the current
+ workaround is to add this to the kernel boot parameters: intremap=off)
+
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10
This workaround works for me until this is properly fixed:
wget
http://mirrors.kernel.org/ubuntu/pool/restricted/b/bcmwl/bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu8_amd64.deb
sudo dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu8_amd64.deb
--
You received this bug notification because
9fefca7 does not boot (without intremap=off)
333830a (the parent) boots fine
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workar
I built the two parents of commit 900db15: 8685217 and e9bdf7e
They both booted fine. I built 900db15 again just in case, and it does
not boot. So it does indeed seem to be the first bad commit, unless I'm
doing something wrong on my end.
Any suggestions?
Thanks!
--
You received this bug notif
I don't understand; doesn't the commit say it changed files?
> 6 files changed, 42 insertions(+), 18 deletions(-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad
This is what I got with a bisect between tags v5.7-rc2 and v5.7. It
looks like a merge commit. Assuming that looks right I'll see if I can
figure out how to do a bisect on the individual commits of the merge.
$ git bisect bad
900db15047044ef50b32e23630880f4780ec5b9e is the first bad commit
commit
I've done some more testing and built tags v5.7 and v5.7-rc2 from
source.
v5.7-rc2 seems to consistently boot without any special kernel flags
v5.7 gives me rather odd behaviour:
- When I'm first powering on the machine, v5.7 does not boot without any
special kernel flags
- If I set intremap=of
Can someone with administrative permissions mark that this bug also
affects Focal? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without
** Tags added: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
Status in linux package in Ubuntu:
Confirmed
Sta
I just installed a few kernels to see if I could narrow down the latest
regression, and this is what I found:
- 5.7.0-050700 boots fine
- 5.7.5-050705 exhibits the problematic behaviour (does not boot)
- The latest kernel (5.13.7-051307) also does not boot
I doubt this is helpful, but these are t
5.8.0-36-generic was just installed as part of the 20.04 HWE and it does
not boot without intremap=off.
What does that mean? Was this fixed in 5.7 and broken again in 5.8? Do I
need to do another rebase?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Oh cool. Is there a page I can check to see when that happens so I can
test it? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without no
I installed 5.7.0-5 from that link but it looks like the bcmwl module
still fails to compile:
Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.7.0-5-generic -C /lib/modules/5.7.0-5-generic/build
M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build(bad exit status: 2)
ERROR (dkms app
I tried booting another half dozen times or so with 5.7 on Ubuntu 20.04
and I didn't have any issues. So maybe it's fixed with that combination?
Unfortunately since the wifi doesn't work I can't continue to use the
5.7 kernel.
--
You received this bug notification because you are a member of Kern
I just upgraded to 20.04 and I can confirm that this bug affects the
default 5.4 kernel that it ships with.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u w
> Maybe the bcmwl-kernel-source package just isn't compatible with 5.7
yet?
I see now in the logs that's the case:
Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.7.0-050700rc2-generic -C
/lib/modules/5.7.0-050700rc2-generic/build
M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build.
Very odd... 5.7 boots (without noapic or intremap=off), but not
consistently.
It boots a number of times just fine (in my tests, anywhere from 3-5
successful boots) and then after that it will hang at boot. Most of the
time after powering off/powering back on it boots fine again, without
needing t
Due to the aforementioned issue, I believe I was getting a lot of false
negatives and my previous bisects were faulty as a result.
I redid the bisect from the beginning, and this is what I got:
# first bad commit: [c4e1be9ec1130fff4d691cdc0e0f9d666009f9ae] mm,
sparsemem: break out of loops early
I'm hopeful that doing the bisect over again will find a more relevant
commit. While bisecting this time I ran into a weird scenario the I
believe may have affected the previous attempts to do a bisect.
The short version of this is that when the computer has failed to boot a
kernel (without noapic
The article I linked was for an AMD CPU so it only helped me up to a
certain point.
I'm thinking I must've messed up the second bisect (the one for the
merge point) so I'm going to try to do the bisect again.
--
You received this bug notification because you are a member of Kernel
Packages, whic
I'm still tinkering...
I removed noapic and I tried instead with this, and it booted!:
intremap=off
Is this related by any chance to the link I posted in the original bug
report?: https://evilazrael.de/node/401
It's a different model ThinkPad but the symptoms are very similar.
--
You received
After that I tried booting 5.3.0-7642-generic, removing noapic and
adding dis_ucode_ldr. And it booted just fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T
Oops, please disregard that last message. I'm multitasking :P
I booted 5.3.0-7642-generic, removing noapic and adding dis_ucode_ldr,
and it wouldn't boot (it froze at ACPI: EC: interrupt blocked)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
I booted 4.13.0-rc1, removing noapic and adding dis_ucode_ldr.
Unfortunately it still doesn't boot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boo
I'm still seeing this same behaviour for the 5.3 kernel.
I'm just now getting back to this, and I think I'm going to need some
hand holding...
> Try changing IRQ configs (CONFIG_GENERIC_IRQ_MIGRATION=y to =n) and
i2c-designware's (CONFIG_I2C_DESIGNWARE_CORE=y to =m).
I copied the 4.13.0 configur
> - First, try latest mainline kernel (v5.0) again, hopefully there's a fix
> already.
No, it looks like it still won't boot (without noapic).
> - Does the issue happen 100% of the time? Otherwise the bisection can be
> inconclusive.
Yes, it happens 100% of the time.
> - Or, take a look kernel
This is what I'm getting:
63db7c815bc0997c29e484d2409684fdd9fcd93b is the first bad commit
But that feels wrong; it looks like it's a fix for XFS?:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=63db7c815bc0997c29e484d2409684fdd9fcd93b
... and I'm not using XFS:
This is the correct commit, right?:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7bf1e44f865523aa16e0eb340a82d643da9215b5
It looks to me like there are a lot more than just ARM changes there,
but I don't know anything about kernel development so I might not be .
I
I followed your instructions exactly as written. How can I use the
mainline release?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapi
I finally got around to doing the bisect, and here's the result:
7bf1e44f865523aa16e0eb340a82d643da9215b5 is the first bad commit
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/18
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1751584
Title:
Ubuntu doesn't boot with 4.13.0 kernels
Status in linux p
Here's the kernel log from v4.12.14 (with apic=debug)
$ uname -a
Linux bryan-ThinkPad-T430u 4.12.14-041214-generic #201709200843 SMP Wed Sep 20
12:46:23 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Attachment added: "kernel log from v4.12.14"
https://bugs.launchpad.net/ubuntu/+source/linux/+bu
I tested a few kernels, and v4.12.14 is the last kernel that works
without noapic. Starting with v4.13-rc1 my computer will hang on boot
unless I use noapic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Here's the kernel log from v4.12.14
$ uname -a
Linux bryan-ThinkPad-T430u 4.12.14-041214-generic #201709200843 SMP Wed Sep 20
12:46:23 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Attachment added: "kernel log from v4.12.14"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachm
I haven't reformatted my machine in years and was running into some
other issues, so I just did a reinstall of 18.04. With both the install
media and the latest 18.04 kernel (4.15.something), I needed noapic.
So I installed kernel v4.20.4-042004, and it would not boot without
noapic either. Howeve
I'm assuming I should add apic=debug to a kernel that has the bug (and
not one that boots fine), correct?
Should I used apic=debug with or without noapic?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
I tried to boot with an older kernel (4.15.0-43), and it wouldn't boot
without noapic. But v4.20-rc7 seems to boot fine. I guess it must've
been a fluke that it didn't boot for me the first time.
Should I still try to figure out which RC kernel the problem started?
--
You received this bug notif
I'm still using v4.20-rc7, and I wanted to try some more kernel
parameters to narrow down the problem. Since the last kernel messages I
got using earlyprintk
(https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot7.png)
I'm not sure if this helps, but I removed noapic and added
earlyprintk=efi,keep in an attempt to show some logs. I took a video and
extracted the frames. I've gone through them briefly but I don't see any
errors or warnings:
https://gist.githubusercont
I just tried kernel v4.20-rc7 and without noapic my computer hangs at a
blank screen. With noapic it boots fine.
Thanks!
** Description changed:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10 HWE and
continui
** Description changed:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10 HWE and
continuing into 18.04 kernels my computer would no longer boot, hanging
at various screens:
- A blank screen with a flashing
** Description changed:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10 HWE and
continuing into 18.04 kernels my computer would no longer boot, hanging
at various screens:
- A blank screen with a flashing
** Attachment added: "IMG_20181028_141659821.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachment/5222108/+files/IMG_20181028_141659821.jpg
** Description changed:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 ker
** Attachment added: "IMG_20180225_083323505.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachment/5222107/+files/IMG_20180225_083323505.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
I went ahead and filed this new bug that's more specific to my hardware:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1751584
Public bug reported:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10 HWE and
continuing into 18.04 kernels my computer would no longer boot, hanging
at various screens:
- A blank screen with a flashing cursor
- A scr
...on second thought, I'm not sure updating it would be the best idea
since the end problem appears to be specific to my hardware. I think
it's probably better to mark this bug as invalid and create a new one.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this
After upgrading my BIOS the problem came back again with the 4.15
kernels. I was able to solve the issue by adding noapic to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"
Once I did that, the kernels worked fine as did intel-microcode.
I'
I hesitatingly upgraded to 18.04, and the 4.15 kernel that it comes with
booted just fine, so it seems like this issue is limited to the 4.13
kernels that come with 17.10/16.04 HWE.
This is what I have now:
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ uname -a
Linux
Since this bug was marked as fixed I'm not sure what the best way to
proceed is. I went ahead and filed a new bug:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1769335
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This is *not* fixed for Xenial. I had originally applied the workaround
in the bug description to get my computer to boot again. After seeing a
"fixed" status for this bug, I updated intel-microcode. After I
rebooted, my computer would not boot to the kernel which had the
microcode applied (4.4.0-1
Okay, I filed one:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1751584
I wonder if it's related to this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Kristoffer, did you file your bug report yet? I think I'm experiencing
the exact same issue. After Grub, my system hangs with the 4.13.0-36
kernel. I just see a flashing cursor. 4.13.0-32 boots fine.
I'm using Ubuntu 16.04.3 on a Thinkpad T430u with an Intel i5-3317U.
--
You received this bug no
Confirmed with latest 12.04 kernel (linux-image-3.2.0-54-generic) and
latest BIOS:
$ sudo dmidecode --type 0 | head -n 8
# dmidecode 2.11
SMBIOS 2.7 present.
Handle 0x000E, DMI type 0, 24 bytes
BIOS Information
Vendor: LENOVO
Version: H6ET90WW (2.08 )
Release Date: 01/11/2013
** Changed in: l
I have no idea how, but the problem is back. I've tried several kernels,
and it's doing the same thing it used to. Apparently my testing wasn't
very thorough. I'm using the latest BIOS:
$ sudo dmidecode --type 0 | head -n 8
# dmidecode 2.11
SMBIOS 2.7 present.
Handle 0x000E, DMI type 0, 24 bytes
Christopher, do you think there's any chance the upgraded BIOS from bug
1157909 would affect this issue? If so, I can use the default 12.04
kernel instead of the latest and test it out.
My thought is that if the 12.04 kernel triggers this bug, it'd be best
to fix it, especially since 12.04 is an L
Ha, I can't believe I didn't even think to update my BIOS. At any rate,
that worked! I tried it on these kernels:
3.11.1-031101-generic
3.2.0-53-generic
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
Christopher,
I tried the version of Ubuntu you mentioned for a few hours and didn't
see the bug. I was running it from a USB drive, however, because I
didn't want to put a development release of Ubuntu on my computer. So
I'm not sure if that makes a difference in triggering the bug.
** Changed in
** Summary changed:
- Thinkpad T430u randomly locks up/freezes
+ Thinkpad randomly locks up/freezes
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1197869
Title:
Thinkpad randomly locks
** Summary changed:
- Thinkpad T430u reboots twice after suspend then shutdown
+ Thinkpad reboots twice after suspend then shutdown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1157909
Christopher,
There hasn't been any activity because nothing's changed. The bug's
still there.
I tried the version of Ubuntu you mentioned and didn't see the bug. I
was running it from a USB drive, however, because I didn't want to put a
development release of Ubuntu on my computer. So I'm not sur
Jacob,
Since updating to the latest kernel, I haven't had one single lockup, so
it seems like that did the trick.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1197869
Title:
Thinkpad
Excellent! I guess I don't need to file a bug about the wireless
drivers. And now I can thoroughly test the new kernel. I'll go ahead and
mark this as fixed in the latest upstream kernel. Thanks, Duncan!
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete
Duncan, could you go near the top left of this page and mark that it
affects you too? That might help bring more attention to it. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1197
Joseph,
I've tested it using the latest kernel, and it hasn't locked up yet.
However...
1. I haven't used it much with the latest kernel, because my wireless doesn't
work with the latest kernel. Should I file a separate bug for this?
2. I'm still not sure if the bug is fixed in the latest kernel
67 matches
Mail list logo
