** 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
9fefca7 does not boot (without intremap=off)
333830a (the parent) boots fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
To mana
Can you please specifically check commit
9fefca775c8ddbbbcd97f2860218188b8641819d and its parent commit?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot withou
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't b
But that commit didn't modify any file...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
To manage notifications about this bug go
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic worka
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
To manage notifications about this bug go to:
https://bugs.laun
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
Same thing with 5.8.0-63-generic, on 20.04.2.
Need a lot of rebooting to load the kernel.
Adding kernel options:
nolapic => loads the kernel, but disables multicore, making use
impracticable
intremap=off => loads the kernel, does not seem to have noticeable side
effects
--
You received this b
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 Ubuntu
Bugs, which is subs
$ rmadison linux
When groovy jumps to 5.7, it's time to change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
To manage notificat
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workarou
We are gonna have 5.7 lands to 20.10 soon, so the DKMS build fail will
also be fixed there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic work
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
One possible choice is to use the 5.7 kernel here:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u
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 Ubun
Is there any log when the hang happens on v5.7?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
To manage notifications about this b
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot wit
> 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
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc2/
Looks like there are fixes on this topic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
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 Ubuntu
Bugs, which is
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't bo
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 Ubuntu
Bugs, which is subscribed t
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noa
Hmm, please try kernel parameter "dis_ucode_ldr" to disable microcode
loading.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
To ma
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
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
T
I can confirm the same behaviour:
$ sudo dmidecode -t bios
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
Handle 0x000E, DMI type 0, 24 bytes
BIOS Information
Vendor: LENOVO
Version: H6ETA0WW (2.18 )
Release Date: 06/01/2018
Address: 0xE
Try changing IRQ configs (CONFIG_GENERIC_IRQ_MIGRATION=y to =n) and i2c-
designware's (CONFIG_I2C_DESIGNWARE_CORE=y to =m).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430
** Attachment added: "config-4.12.0-041200-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachment/5245341/+files/config-4.12.0-041200-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Attachment added: "config-4.13.0-041300rc1-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachment/5245342/+files/config-4.13.0-041300rc1-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
> - 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
- First, try latest mainline kernel (v5.0) again, hopefully there's a fix
already.
- Does the issue happen 100% of the time? Otherwise the bisection can be
inconclusive.
- Or, take a look kernel config on v4.12 and v4.13-rc1 - maybe some new option
breaks your system.
--
You received this bug
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:
Oh it's a merge point so there are still some commits:
$ git diff e5770b7bdbfe..32c1431eea48
So probably a good idea to bisect between e5770b7bdbfe and 32c1431eea48.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
You are right.
Apparently something's wrong with my git,
$ git show 7bf1e44f865523aa16e0eb340a82d643da9215b5
commit 7bf1e44f865523aa16e0eb340a82d643da9215b5
Merge: e5770b7bdbfe 32c1431eea48
Author: Greg Kroah-Hartman
Date: Mon Jun 12 08:20:47 2017 +0200
Merge 4.12-rc5 into staging-next
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
This is really weird. I don't think you system has "ccree" device which
only presents on ARM devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without n
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
The commit is not correct. When doing a bisection, please skip stable
release, (e.g. 4.12.1), and use mainline release (e.g. 4.12).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Think
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
So I guess v4.12 also works? Let's do a kernel bisection:
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good v4.12
$ git bisect bad v4.13-rc1
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install
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 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
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 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Maybe you can try adding 'apic=debug' and remove 'quiet splash'
parameters when you boot and see if kernel shows more messages that can
point to the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
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)
were rel
The next step is to find the last working -rc kernel and first non-
working -rc kernel.
>From your description, both of them should be <= v4.13.
The kernels can be found in [1].
[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/
--
You received this bug notification because you are a member o
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.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8
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
Please try latest mainline kernel [1] without "noapic" parameter.
[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc7/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
65 matches
Mail list logo
