Thanks for the update. I have applied the patch on 6.4.3 but no effect.
I see the following error in the kernel log -
```
Jul 16 12:51:26 andrew-laptop kernel: mt7921e :03:00.0: enabling device
( -> 0002)
Jul 16 12:51:26 andrew-laptop kernel: mt7921e :03:00.0: driver own failed
Jul
Reproduced on ASUS G14 Laptop (model number GA402NV).
Ubuntu 23.04
6.2.0-23-generic
`dmesg | grep mt7` gives the following -
```
[ 14.665322] mt7921e :03:00.0: ASIC revision: 79220010
[ 17.955295] mt7921e :03:00.0: Message 0010 (seq 1) timeout
[ 17.955309] mt7921e
Independent confirmation from me, with the same symptoms:
updated from kernel 5.13 to 5.15 today. After rebooting the system hangs
at "Loading ramdisk". I reverted to 5.13 and it started properly.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Independent confirmation from me, with the same symptoms:
updated from kernel 5.13 to 5.15 today. After rebooting the system hangs
at "Loading ramdisk". I reverted to 5.13 and it started properly.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hi, apologies if bluez is not the appropriate package. I have followed
the above instructions in an case.
1. No crash files present.
2. The following problems were reported on errors.ubuntu.com
https://errors.ubuntu.com/oops/feac943a-8847-11eb-9538-fa163ee63de6
Public bug reported:
Crash on resume from suspend. The following messages appear and the
computer stops responding:
```
[ 26.227264] Bluetooth: hci0: Reading supported features failed (-16)
[ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask
failed (-95)
```
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461007/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461002/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461005/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461004/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461001/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461008/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461003/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461006/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461000/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460997/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460998/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5461009/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460999/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460996/+files/Lsusb.txt
--
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/1914881
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460992/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460995/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460994/+files/Lspci.txt
--
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/1914881
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460991/+files/CRDA.txt
--
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/1914881
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1914881/+attachment/5460993/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
There is no sound output from the laptop internal speakers when running
Ubuntu 20.10.
This is a dual-boot system;
- Booting Windows first and then rebooting to Ubuntu -> sound works fine
- Booting Ubuntu
Following instructions at:
https://wiki.ubuntu.com/DebuggingSoundProblems
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
** Tags added: kernel-sound
** Description changed:
There is no sound output from the laptop internal speakers when running
Ubuntu 20.10.
This is a
Upgrading bluez to 5.50 as mentioned in link below fixed the problem
with bluetooth headphones not connecting after resume on Ubuntu 18.04.
https://askubuntu.com/questions/1036195/bluetooth-doesnt-work-after-
resuming-from-sleep-ubuntu-18-04-lts
--
You received this bug notification because you
Got it fixed, thanks. Now I'm having other issues but I don't think they
are related.
--
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/1571416
Title:
System freezes shortly after reaching
I put quotes around both, that must be what broke it. Then I tried to
fix it using live CD to re-edit but I couldn't make it stick as the live
CD couldn't update the bin. Mint always warns me of syntax errors so if
this did as well I missed it.
I'll try it again. I might just switch back to Tiger
I tried that and got a syntax error on reboot that I couldn't recover
from. I'll look at it again.
--
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/1571416
Title:
System freezes shortly
How do I add the boot options and have them stick? I tried modifying the
yaboot but I ended up breaking my install.
I can get it installed with the live radeon.agpmode=-1
then I was able to boot it by typing at the first boot Linux radeon.agpmode=-1
that's where it breaks down, I don't know how
Public bug reported:
While debugging something, I ran the kvm-ok script on a VM running on
openstack, and got an interesting error:
ubuntu@juju-bradm-lcy02-machine-0:~$ sudo kvm-ok
INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm_intel
INFO: Your CPU supports KVM extensions
Haven't seen it in a few days. I'll reboot and see if I can reproduce
it. It usually happens after rebooting the host, when launching new
containers or existing ones would autostart.
Info you requested. I think the /usr/share/lxc/... might have been a red
herring. I'm exclusively using LXD on
@stforshee I'll uncomment the debugfs mount in my
/usr/share/lxc/config/ubuntu.common.conf (putting it back the way it
was), reboot, and see if I can reproduce it again.
My juju-lxd profile shows:
name: juju-lxd
config:
boot.autostart: "true"
security.nesting: "true"
description: ""
devices:
Interesting. I removed the /sys/kernel/debug mount and containers seem
to start up just fine:
c@mawhrin-skel:~$ grep kernel/debug /usr/share/lxc/config/ubuntu.common.conf
# lxc.mount.entry = /sys/kernel/debug sys/kernel/debug none bind,optional 0 0
c@mawhrin-skel:~$ lxc launch ubuntu-trusty t2
This is the config from the container that had the issue this morning:
c@mawhrin-skel:~/omnibus-layers$ lxc config show
juju-145a3177-d1c0-4974-89f6-feaebb3ca87d-machine-0
name: juju-145a3177-d1c0-4974-89f6-feaebb3ca87d-machine-0
profiles:
- default
- juju-lxd
config:
user.juju-model-uuid:
FWIW I've observed the bug outside of Juju. Launching a trusty
container, sshd did not start until I remounted debug on the host. The
main reason it's been observed with juju is, Juju tries to SSH into the
instance right after cloud-init, but upstart in the container isn't
starting sshd so
I also confirmed that the mountall error message was duplicated every
time I restarted the machine-0 container -- until remounting on the
host.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I'm using lxd with zfs block storage on xenial, and having issues with
trusty containers. I've witnessed this problem when trying to bootstrap
as well as after rebooting the host and a container failed to start.
In the latter case, the container that failed to start was the
Public bug reported:
Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
servers lock up with a similar looking cpu lockup bug. All 3 of these
servers are nova-compute nodes in an OpenStack cluster, with a
reasonable amount of load on them. The symptoms are the load shoots up
2nd of the lockups.
** Attachment added: "CPU Lockup 2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478313/+files/cpu-lockup-2.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The first of the lockups. These all required us to hard reset the
servers via the ilo.
** Attachment added: "CPU Lockup 1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478312/+files/cpu-lockup-1.log
--
You received this bug notification because you are a
3rd of the lockups
** Attachment added: "CPU Lockup 3"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478314/+files/cpu-lockup-3.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected trusty uec-images
** Description changed:
Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9
servers lock up with a similar looking cpu lockup bug. All 3 of these
servers are nova-compute nodes in an OpenStack cluster,
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479440/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479438/+files/Lspci.txt
--
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/1500739
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479445/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479436/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479442/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479443/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479439/+files/Lsusb.txt
--
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/1500739
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479444/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479441/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1500739/+attachment/4479437/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Unfortunately we're unable to test the latest upstream kernel in this
situation. These servers are running a production system, and as they
use bcache we need a kernel that supports it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hi,
Brad Marshall, could you please test the latest mainline kernel
(3.18-rc5) and advise to the results?
Done, roughly the same results - still timeouts, still having to reset
the bluetooth service to get things going again sometimes.
Also, did this issue not occur in a release prior
Hi,
Brad Marshall, which previous release(s) specifically did it occur in?
As well, could you please quantify how much less frequently?
I did my initial install on Raring, and I've upgraded across every
release since then. I do remember it happening occasionally on the
earlier ones - maybe
If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?
Done, and it doesn't seem to change anything.
If it doesn't, could you please both specify what happened
Er, how can I specify what happened when its not changed? :) I'm still
seeing
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Yes, it occured in previous versions, just not as frequently I think.
Would it be possible for you to test the latest upstream kernel? Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds .
Please test the
Public bug reported:
I'm using a Razor Orochi 2013 mouse with my Dell XPS13 laptop via
bluetooth on Ubuntu 14.10, and have noticed a seeming increase in the
frequency of the timeouts I'm seeing.
The symptoms are when I don't use my mouse for a while, it seems to go
to sleep, and reasonably
Nope, still burnin. A fresh boot it doesn't seem too bad, but this just
happened, coming off of standby (that seems to worsen it):
Wed Aug 6 18:28:53 CEST 2014
193 Load_Cycle_Count0x0012 089 089 000Old_age Always
- 113151
Wed Aug 6 18:29:54 CEST 2014
193
The rate certainly seems slower than before with latest 3.16 kernel
(Linux cloudsong 3.16.0-031600-generic #201408031935 SMP Sun Aug 3
23:36:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux).
Is this looking more like a normal cycle pattern, or still more load
cycles than there should be?
Installed the BIOS update:
root@cloudsong:~# dmidecode -s bios-version sudo dmidecode -s
bios-release-date
G2ETA1WW (2.61 )
04/22/2014
Still burning load cycles on battery power:
root@cloudsong:~# while true;
do
date
smartctl -a /dev/sda | grep Load_Cycle
sleep 60
done
Fri Aug 1
Public bug reported:
When running my Thinkpad x230 on battery, the Load_Cycle_Count increases
at a high rate: about 10-15 load cycles per minute. I discovered this
issue in a quiet room, where I could hear the clicks (or death rattle,
as I've come to think of them).
The following commands will
** 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/1316284
Title:
[HP Probook 4540s] Load/Unload Cycle Count
Status in
I am reopening this because:
1. My harddrive has already been cooked by this bug and I'll probably
have to buy a new one. I set up an upstart script to run the hdparm
command, but it seems to need it run more often than at just startup.
Check it out:
193 Load_Cycle_Count0x0012 090
I'm also seeing a ridiculous load cycle count increase on my thinkpad
x230 running xubuntu 14.04. I got suspicious when I could hear the faint
click in a quiet room, and it reminded me of the issue from several
years back.
193 Load_Cycle_Count0x0012 094 094 000Old_age Always
-
This stopped the runaway load cycles as a workaround:
sudo hdparm -B 254 /dev/sda
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
69 matches
Mail list logo
