I am having the same EXACT crash on a Lenovo box. I also see that the
crash is always associated with fwupd running, so I've disabled it to
see if that helps.
I'm running the kernel as a snap on a full-disk-encrypted with TPM-
sealed key, in case that matters.
--
You received this bug notificati
Verified with 5.13.0-1007.
** Tags added: cqa-verified
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1938298
Title:
[EHL][Graphic]Removing force probe protection from EHL pl
Verified fixed with 5.13.0-1007.
** Tags added: cqa-verified
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1938413
Title:
[ehl] Shutdown hangs on board
Status in intel:
Fix Co
TGL-Aaeon:
20.04LTS Desktop: Detects both interfaces and allows them to get an IP#
when you plug in a cable.
IOTG Desktop (Oct. 13 build): Detects both interfaces and allows them to
get an IP# when you plug in a cable. (Desktop Manual network tests
pass.)
IOTG Core (Oct. 14 build): If you perfor
I see this same behavior on the TGL-Aaeon running Core.
I even tried to manually edit /etc/netplan/00-snapd-config.yaml but I
could not make it bring the interface up.
When the cable is plugged in the link lights are on but the system
doesn't seem to acknowledge the connection.
The other port wo
** Tags added: lookout-canyon
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1936903
Title:
CDTS Network (Ethernet) failures
Status in intel:
New
Status in Ubuntu:
Incomplete
** Tags added: lookout-canyon
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1936899
Title:
[IoTG] [TGL-H] TPM tests fail
Status in intel:
Invalid
Status in linux-intel package
Public bug reported:
Laptop: Dell XPS-15-9500
OS: Ubuntu Desktop 20.04.3
I plugged in the headphones while watching a video in Firefox.
I expected Ubuntu to detect the headphones and use them for audio
output.
Instead the laptop's built-in speakers continued to be used.
Audio settings did not
Actually I made a mistake. I filed these with iotg-focal-
desktop-20210706.img
This is the only image I've used on the EHL board. I got confused with
the TGL-H board which I've used both Desktop and Core.
So, What is the old kernel you want me to use?
--
You received this bug notification beca
Which is the Old Kernel you want me to try?
All these bugs were filed using
iotg-focal-core-20210722.img (5.11.0-1011-intel)
I then used the patch you gave me on this kernel and retested.
I have managed to have the system hang on booting after a shutdown
twice, but after another 10 shutdowns, it
I spoke too soon.
If you continually shutdown/boot the system, it will hang, about 20% of
the time, at the splash screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1938413
Titl
System shuts down properly after this workaround. Fan stops, board LEDs
remain on (system has no LED power indicator.) System boots properly
upon unplugging/plugging back in.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in
Applied the patch as instructed in
https://bugs.launchpad.net/bugs/1938413:
Hi @Doug,
Please use this test kernel to verify this issue.
version: 5.11.0-1011-intel #12+lp1938408~lp1938413
[Installation steps]
1. tar -zxvf revert.tgz
2. cd revert
3. sudo dpkg -i *.deb
After the patch was appli
solution of hui wang works for me!
thx
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1862831
Title:
hciattach on rpi4 times out on first attempt
Status in linux-raspi package in
I installed version 5.55-0ubuntu2
did not make a difference.
in journalctl is this :
bluetoothd[40120]: src/main.c:parse_controller_config() Key file does not have
group “Controller”
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez i
Hello Kai-Heng,
I see how the fix I provided is included in the 4.4.0, however I don't
see it (yet) in 4.15.0. Is there something I need to do to get this fix
into 4.15.0, or will it eventually percolate through by itself?
Thanks!
--
You received this bug notification because you are a member o
Yes, confirmed. On my Lenovo x240, kernel 4.18.0-15-generic, I removed
i2c_i801 from the blacklist and no longer can reproduce the hang.
--
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/1802
Okay, after the latest update (from the 0-13 kernel) it now seems to be
booting normally. I hope that means the problem has been corrected and
this bug can be closed. Perhaps some kind of regression bug?
If anyone over there wants me to collect any additional information
about what was going on, p
I am unable to run that command under the afflicted kernel because the
machine cannot boot under that kernel.
--
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/1815258
Title:
4.18.0-14-gene
The robotic message tells me to change the status to confirmed after
adding the previous comment, but the instructions there say that the
confirmed status is supposed to be done by someone else.
By the way, my current theory (based on weak understanding) is that
there might be some logs of the boo
** Description changed:
After the update for the 4.18.0-14-generic kernel the machine freezes on
booting. Machine still books under the 0-13 kernel. Booting in Recovery
Mode seems go normally to the Recovery Menu. At that point it reports
- "Starting Avahi mDNS-SD Stack" and gets and OK. Tha
Public bug reported:
After the update for the 4.18.0-14-generic kernel the machine freezes on
booting. Machine still books under the 0-13 kernel. Booting in Recovery
Mode seems go normally to the Recovery Menu. At that point it reports
"Starting Avahi mDNS-SD Stack" and gets and OK. That is repeat
The patch was picked up in the stable kernel
(https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/), and
added to 4.19.5, 4.14.84, 4.9.141, 4.4.165, and 4.20-rc4.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
My kernel patch was accepted this morning (very quick!!). Per the
notification received:
"The patch will show up in the next release of the linux-next tree
(usually sometime within the next 24 hours during the week.)
The patch will hopefully also be merged in Linus's tree for the
next -rc kernel
Hello Joseph,
To keep things in sync here (and to make sure the bug doesn't expire due
to inactivity):
1. I worked my way through the process for submitting a kernel patch. (Not for
the faint hearted I might add ;))
2. The patch has been submitted - now I have to wait and see if there's anybody
The change I applied to cdc-acm.c is as follows:
--- cdc-acm.orig.c 2018-11-11 11:31:18.754382981 -0500
+++ cdc-acm.c 2018-11-10 17:32:29.802278377 -0500
@@ -1713,6 +1713,9 @@
{ USB_DEVICE(0x0572, 0x1324), /* Conexant USB MODEM RD02-D400 */
.driver_info = NO_UNION_NORMAL, /*
Public bug reported:
I procured a USB modem manufactured by Hiro (model number H50228). This
is in fact a Conexant modem, and while some conexant models are
supported in cdc_adm, this particular type is not.
Hence, when I connect the modem to my system, cdc_adm does not
initialize the modem prope
The Linux changelog people seem a bit comfused...
I just received Linux 4.8.0-31.33,
and ITS changlog says:
" * Yakkety update to v4.8.11 stable release (LP: #1645421)
...
- Linux 4.8.11
* Yakkety update to 4.8.7 stable release (LP: #1642606)
...
- usb: increase ohci watchdog delay to
>4.8.0-30 does not have the 4.8.11 update. It's still at 4.8.6
Is "Michael Bock (michi-bock)" referring to a different problem?
I installed the previous version (4.8.0-29.31), which said:
"* Yakkety update to v4.8.11 stable release (LP: #1645421)"
and it fixed a timer problem ("usb: increase ohc
I just (yesterday?) installed Linux 4.8.0-29.31
"Release Tracking Bug
- LP: #1646194
* Yakkety update to v4.8.11 stable release (LP: #1645421)"
and for the first time since I installed Lubuntu 16.10, I can print, and have
the whole
page get printed!
This seems to have fixed the problem.
"And it looks like those updates are in Ubuntu-4.8.0-28:"
I think not.
I do not find mention of this bug in the changelog for 4.8.0-28-generic (I
searched for IO_WATCHDOG_DELAY, and USB and ohci - nothing for the latest
version)
and an attempted print failed exactly the same way, with a dead-in
Soon, I hope...
It will be nice to be able to print something, and not have it hang
somewhere in the middle of the page...
--
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/1630063
Title:
"The fix is in the current 4.8 stable rc."
How will I know what exact kernel version (when it pops up in Update Manager)
is the first to include this fix?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
[By the way - until a fix reaches everybody, here is a script that I found
online and modified to fit my system...
The commented-out for statement is as the script was found.]
#!/bin/bash
if [[ $EUID != 0 ]] ; then
echo This must be run as root!
exit 1
fi
#for xhci in /sys/bus/pci/drivers/
I also have this bug, which I filed for cups (since it first manifested with
several aborted print jobs, which I assumed somehow caused my USB mouse to stop
working)
See:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1637037
for details.
Summary:
scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
I have this problem, and for me to resolve was the power ACPI,
unfortunately you need programming knowledges; here is the problem, your
ACPI descriptor (DSDT) table is defective/wrong, and need re-
programming, is from 2006
Diagnostic:
ACPI: DSDT 0xDAFF1000 0092DA (v02 SECCSD IVB-CPT
36 matches
Mail list logo
