As stated in the bug ticket linked above, this commit:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186&id=3879f4364139acb2bd3932e6a15994f109c49d6b
causes issues on hardware where the intel_lpss driver tries to load the intel
idma driver, becau
FIXED IT! It is indeed the intel_lpss driver, at least in my case.
This commit:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186&id=3879f4364139acb2bd3932e6a15994f109c49d6b
will not work right when a module that is asynchronously loaded tries t
This commit is suspected to cause issues for many users:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186&id=3879f4364139acb2bd3932e6a15994f109c49d6b
Please see this bug ticket:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167
--
Y
My "prime suspect" is this commit:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186&id=3879f4364139acb2bd3932e6a15994f109c49d6b
Also see Linus' comments when this patch was submitted to the mainline kernel:
https://www.spinics.net/lists/kernel/m
I have found a change between 176 and 177 that looks suspicious:
diff -upr --color 176/linux-source-4.15.0/kernel/module.c
177/linux-source-4.15.0/kernel/module.c
--- 176/linux-source-4.15.0/kernel/module.c 2022-03-29 19:39:48.0
+0200
+++ 177/linux-source-4.15.0/kernel/module.c 2
Trying to isolate the issue, I:
1. Booted my portable Ubuntu 18.04.6 installation on a different machine
(different CPU, chipset, but still Intel). On the other machine, kernel
4.15.0-177 booted without issues, so apparently it does not depend on
the installation, but rather on the hardware or BIO
Alas! I spoke to seen. The seeming "workaround" only lasted for one
boot, and after that, the ~180 seconds delay is back to stay, although
the Intel IOMMU is still disabled.
So this issue is "sporadic". Maybe even a race condition... :(
And maybe not even related to the intel-lpss driver: The lin
When the machine is booted, open a terminal and run "dmesg" to see on
what the kernel was stuck so long. In my case, it was the intel-lpss PCI
device initialization, and I fixed it by disabling the Intel IOMMU. If
you get similar results, this issue might be a duplicate of mine which I
reported her
After grepping dmesg for all lines about the "00:15" devices, I found
two lines starting with "DMAR:", which made me think of another machine
running debian which had issues with DMAR: devices that were related to
the Intel IOMMU.
So I tried the workaround I knew from there:
Edit /etc/default/gru
After finding someone reporting the same issue
(https://forums.linuxmint.com/viewtopic.php?t=373747&p=2175201) and
reading that the machine may come alive after a while, I found that
indeed after 3 minutes the machine works. dmesg that reveals that it
seemingly was the initialization of the intel_l
Public bug reported:
After updating to linux-image-4.15.0-177-generic, my machine completely
freezes on the Ubuntu Welcome screen, i.e. right after switching to GUI
mode. The mouse pointer is frozen, the keyboard does not even respond to
CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows no reactio
For the curious and technically savvy, I suppose this is the actual fix:
diff -Nru compiz-0.9.12.2+16.04.20160415/src/window.cpp
compiz-0.9.12.2+16.04.20160415/src/window.cpp
--- compiz-0.9.12.2+16.04.20160415/src/window.cpp 2016-04-15
05:30:40.0 +
+++ compiz-0.9.12.2+16.04.201
*** This bug is a duplicate of bug 1521302 ***
https://bugs.launchpad.net/bugs/1521302
Also a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1524665
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I have the same problem with the released Ubuntu 16.04 LTS:
compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
gnome-terminal 3.18.3-1ubuntu1
unity 7.4.0+16.04.20160415-0ubuntu1
--
You received this bu
My patch to fix this issue was pulled into Ubuntu 15.04 with the kernel
update 3.19.0-26.27:
https://launchpad.net/ubuntu/+source/linux/3.19.0-26.27
usb: core: Fix USB 3.0 devices lost in NOTATTACHED state after a hub
port reset
I can confirm that the updated kernel fixes the problem on my machi
Well, I developed the patch to fix my problem, so it would be rather
strange if it didn't ;-)
In short: Yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Title:
REGRESSION after upgrade fr
An enhanced version of the fix I outlined above has now been accepted
for inclusion in Linux kernel 4.2:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/usb/core/hub.c?id=fb6d1f7df5d25299fd7b3e84b72b8851d3634764
** Attachment removed: "AlsaInfo.txt"
https://bugs
I took a different route and tried to find out what is going wrong with
the current code. I loaded the linux-source package and built kernel
3.19.3 versions with added debug messages in drivers/usb/core/hub.c to
see that is happening. I found the following chain of calls:
1. hub_port_reset()
2. >
Here's what it says on the sticker:
SAMSUNG
NOTEBOOK
MODEL: NP-RF711
MODEL CODE: NP-RF711-S08DE
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Summary changed:
- USB3 boot device lost during system boot: "xhci_hcd :04:00.0: Error while
assigning device slot ID"
+ REGRESSION after upgrade from 14.10 to 15.04: USB3 boot device lost during
system boot: "xhci_hcd :04:00.0: Error while assigning device slot ID"
** Summary change
Further possibly related bugs:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408471
https://bugzilla.kernel.org/show_bug.cgi?id=90941
Seems unresolved :-(
** Bug watch added: Linux Kernel Bug Tracker #90941
http://bugzilla.kernel.org/show_bug.cgi?id=90941
--
You received this bug no
Seems others have been seeing similar regressions between kernels 3.17
and 3.18:
http://lkml.iu.edu/hypermail/linux/kernel/1501.2/01802.html
Is it possible that Ubuntu did not pick up that fix...?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Trying various kernels from http://kernel.ubuntu.com/~kernel-
ppa/mainline, I can pinpoint that this bug was introduced with linux
kernel 3.18.
These kernels did NOT exhibit the bug:
linux-image-3.16.7-031607-generic_3.16.7-031607.201410301735_amd64.deb
linux-image-3.17.2-031702-generic_3.17.2-03
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398311/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398309/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Title:
USB3 b
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398319/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Titl
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398318/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398317/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/145
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398323/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Ti
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398315/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398322/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398313/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Title:
USB3
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398314/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Title:
USB3
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398316/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398320/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Title:
US
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398321/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Title:
US
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398310/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1455376/+attachment/4398312/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14553
apport information
** Tags added: apport-collected vivid
** Description changed:
Booting Ubuntu 15.04 amd64 kernel "Linux version 3.19.0-16-generic
(buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) )
#16-Ubuntu SMP Thu Apr 30 16:09:58 UTC 2015" on a Samsung RF711-S08
laptop (
Forgot to mention: Ubuntu 14.10 (linux kernel 3.16) booted without this
problem off the same USB3 stick on the same USB3 port on the same
laptop. So this is a regression that was introduced in Ubuntu 15.04
(linux kernel 3.19).
--
You received this bug notification because you are a member of Ubun
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1455376
Title:
USB3 boot device lost during system boot: "xhci_hcd :04:00.0:
Error while assigning de
Public bug reported:
Booting Ubuntu 15.04 amd64 kernel "Linux version 3.19.0-16-generic
(buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) )
#16-Ubuntu SMP Thu Apr 30 16:09:58 UTC 2015" on a Samsung RF711-S08
laptop (Sandy Bridge) from a USB3 stick connected to the USB3 port on
the righ
42 matches
Mail list logo
