[Kernel-packages] [Bug 1810239] Re: amd_iommu conflict with Marvell 88SE9230 SATA Controller
Hi,
I had similar Problems with my Marvell 88EE9230. I was able to improve the
situation quite a lot by updating the firmware of the controller itself. In
General all firmware versions beyond version 2.3.xxx improved the situation
quite a lot. The remaining problem is, that I get failures on ata6 which is the
only port which is not connected to any drive at all. Any drive connected to
the marvell controller itself is perfectly stable (24/7 for +400 days).
Source for Firmwares: https://www.station-
drivers.com/index.php?option=com_remository&Itemid=352&func=select&id=347&lang=en
May 05 03:16:10 doomsdaydevice kernel: ata6.00: exception Emask 0x0 SAct 0x6
SErr 0x0 action 0x6 frozen
May 05 03:16:11 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
May 05 03:16:11 doomsdaydevice kernel: ata6.00: cmd
61/10:08:18:6a:14/00:00:01:00:00/40 tag 1 ncq dma 8192 out
res
40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
May 05 03:16:11 doomsdaydevice kernel: ata6.00: status: { DRDY }
May 05 03:16:11 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
May 05 03:16:11 doomsdaydevice kernel: ata6.00: cmd
61/10:10:10:e8:5e/00:00:3a:00:00/40 tag 2 ncq dma 8192 out
res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 05 03:16:11 doomsdaydevice kernel: ata6.00: status: { DRDY }
May 05 03:16:11 doomsdaydevice kernel: ata6.00: supports DRM functions and may
not be fully accessible
May 05 03:16:11 doomsdaydevice kernel: ata6.00: supports DRM functions and may
not be fully accessible
May 05 06:01:33 doomsdaydevice kernel: ata6.00: exception Emask 0x0 SAct 0x60
SErr 0x0 action 0x6 frozen
May 05 06:01:33 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
May 05 06:01:33 doomsdaydevice kernel: ata6.00: cmd
61/08:28:90:da:14/00:00:23:00:00/40 tag 5 ncq dma 4096 out
res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 05 06:01:33 doomsdaydevice kernel: ata6.00: status: { DRDY }
May 05 06:01:33 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
May 05 06:01:33 doomsdaydevice kernel: ata6.00: cmd
61/08:30:a8:fd:20/00:00:05:00:00/40 tag 6 ncq dma 4096 out
res
40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 05 06:01:33 doomsdaydevice kernel: ata6.00: status: { DRDY }
May 05 06:01:33 doomsdaydevice kernel: ata6.00: supports DRM functions and may
not be fully accessible
May 05 06:01:33 doomsdaydevice kernel: ata6.00: supports DRM functions and may
not be fully accessible
May 05 06:37:03 doomsdaydevice kernel: ata6.00: exception Emask 0x0 SAct 0x30
SErr 0x0 action 0x6 frozen
May 05 06:37:03 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
May 05 06:37:03 doomsdaydevice kernel: ata6.00: cmd
61/08:20:48:08:10/00:00:00:00:00/40 tag 4 ncq dma 4096 out
res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 05 06:37:03 doomsdaydevice kernel: ata6.00: status: { DRDY }
May 05 06:37:03 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
May 05 06:37:03 doomsdaydevice kernel: ata6.00: cmd
61/08:28:00:08:10/00:00:00:00:00/40 tag 5 ncq dma 4096 out
res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 05 06:37:03 doomsdaydevice kernel: ata6.00: status: { DRDY }
May 05 06:37:03 doomsdaydevice kernel: ata6.00: supports DRM functions and may
not be fully accessible
May 05 06:37:03 doomsdaydevice kernel: ata6.00: supports DRM functions and may
not be fully accessible
--
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/1810239
Title:
amd_iommu conflict with Marvell 88SE9230 SATA Controller
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux package in Debian:
New
Status in linux package in Fedora:
Unknown
Bug description:
Booting with kernel 4.18.0-13.14~18.04.1-generic shows errors:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/153
WORKAROUND: Use kernel boot parameter:
amd_iommu=off
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mythfe 1170 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=/dev/mythnew/swap
InstallationDate: Installed on 2016-07-02 (913 days ago)
InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
IwConfig:
lono wireless extensions.
enp9s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. B450M S2H
Package: linux (not installed)
ProcFB: 0 am
[Kernel-packages] [Bug 1832383] [NEW] failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 88EE9230 sata controller
Public bug reported:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate the
behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware 1.x.xxx
which caused massive problems with all connected drives. It was common,
that the kernel rested links, which caused raid corruption, kernel
panics. Example from May/2018 (hostname changed, same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Attachment added: "ubuntu-bug linux"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270182/+files/apport.linux-image-4.18.0-21-generic.4fpndma9.apport
--
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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example fro
[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 88EE9230 sata controller
Output of lshw -C storage -C disk
Note: There is no drive attached to scsi@6.0.0.0
** Attachment added: "lshw -C storage -C disk"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+attachment/5270183/+files/lshw_storage_disk.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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 88EE9230 sata controller
apport information
** Tags added: apport-collected bionic
** Description changed:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware 1.x.xxx
which caused massive problems with all connected drives. It was common,
that the kernel rested links, which caused raid corruption, kernel
panics. Example from May/2018 (hostname changed, same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
+ ---
+ ProblemType: Bug
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Jun 11 01:17 seq
+ crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 18.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
+ InstallationDate: Installed on 2018-03-29 (438 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
+ IwConfig:
+ enp3s0no wireless extensions.
+
+ lono wireless extensions.
+
+ enp5s0no wireless extensions.
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: linux (not installed)
+ PciMultimedia:
+
+ ProcFB:
+
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic
root=UUID=c77001fd-6968-4606-9baa-a60439b1e173 ro
+ ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+ linux-restricted-modules-4.18.0-21-generic N/A
+
[Kernel-packages] [Bug 1832383] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270198/+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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270196/+files/CurrentDmesg.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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270199/+files/ProcCpuinfoMinimal.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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell 88EE9230 sata controller
I made a mistake!
ata6 is populated with an drive. It is an SAMSUNG MZ7TN512 which lshw locates
at scsi@5:0.0.0 which is ata6
Typical off by one on layer 8 :/
** Attachment added: "tree /sys/bus/scsi/drivers/sd/"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+attachment/5270205/+files/scisi_drives.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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270203/+files/UdevDb.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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270201/+files/ProcInterrupts.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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270204/+files/WifiSyslog.txt
** Description changed:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
+
+ CORRECTION: ata6 is populated! I made a mistake!
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware 1.x.xxx
which caused massive problems with all connected drives. It was common,
that the kernel rested links, which caused raid corruption, kernel
panics. Example from May/2018 (hostname changed, same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
- When the command that caused the error occurred, the device was active or
idle.
-
- After command completion occurred, registers were:
- ER ST SC SN CL CH DH
- -- -- -- -- -- -- --
- 84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
-
- Commands leading to the command that caused the error were:
- CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
- -- -- -- -- -- -- -- --
- 25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
- 25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
- 25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
- 25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
- 25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
- ---
- ProblemType: Bug
- AlsaDevices:
- total 0
- crw-rw 1 root audio 116, 1 Jun 11 01:17 seq
- crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
- AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
- ApportVersion: 2.20.9-0ubuntu7.6
- Architecture: amd64
- ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
- AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
- DistroRelease: Ubuntu 18.04
- EcryptfsInUse: Yes
- HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
- InstallationDate: Installed on 2018-03-29 (438 days ago)
- InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
- IwConfig:
- enp3s0no wireless extensions.
-
- lono wireless extensions.
-
- enp5s0no wireless extensions.
- MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
- Package: linux (not installed)
- PciMultimedia:
-
- ProcFB:
-
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic
root=UUID=c77001fd-6968-4606-9baa-a60439b1e173 ro
- ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
P
[Kernel-packages] [Bug 1832383] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270200/+files/ProcEnviron.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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270202/+files/ProcModules.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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1832383/+attachment/5270197/+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/1832383
Title:
failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller
** Summary changed:
- failed command: WRITE FPDMA QUEUED on unpopulated sata port of marvell
88EE9230 sata controller
+ failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller
--
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/1832383
Title:
failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata
controller
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is connected to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
My machines throws errors on ata6.00 like these:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated
ports don't trigger any failures after updating the firmware (2.3.xxx) of the
Sata controller.
The problem occurs every 2-3 weeks and I did not find a method to replicate
the behaviour. Anyhow, the system is stable.
##
The Marvell controller itself initially was used with firmware
1.x.xxx which caused massive problems with all connected drives. It
was common, that the kernel rested links, which caused raid
corruption, kernel panics. Example from May/2018 (hostname changed,
same machine)
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810239] Re: amd_iommu conflict with Marvell 88SE9230 SATA Controller
Christoper, I filed the bug. Anyway I made a mistake. I took the output from lshw where scsi@6 was not populated and I took for granted, that ata6 equals scsi@6 which isn't the case. Therefore I get the mentioned errors on my boot drive. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832383 -- 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/1810239 Title: amd_iommu conflict with Marvell 88SE9230 SATA Controller Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux package in Debian: New Status in linux package in Fedora: Unknown Bug description: Booting with kernel 4.18.0-13.14~18.04.1-generic shows errors: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/153 WORKAROUND: Use kernel boot parameter: amd_iommu=off --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mythfe 1170 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mythnew/swap InstallationDate: Installed on 2016-07-02 (913 days ago) InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp9s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B450M S2H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/mythnew-root ro verbose drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.173.2 RfKill: Tags: bionic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago) UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 12/04/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2c dmi.board.asset.tag: Default string dmi.board.name: B450M S2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879989] Re: "Failed to play sound: No such driver" ubuntu 20.04
*** This bug is a duplicate of bug 1879939 *** https://bugs.launchpad.net/bugs/1879939 Judging on the described behaviour this Bug also is present in Ubuntu 14.04 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879869 -- 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/1879989 Title: "Failed to play sound: No such driver" ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: my speakers- built in audio produces terrible sound I tested the speakers via settings/sound and there was no sound I checked gnome logs and found "Failed to play sound: No such driver" I checked online and it seams to be a problem that affects many users ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: regern70802 F pulseaudio /dev/snd/pcmC0D0c: regern70802 F...m pulseaudio /dev/snd/pcmC0D0p: regern70802 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 19:13:55 2020 InstallationDate: Installed on 2020-05-16 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 15-3552 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.sku: 06AC dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879989] Re: "Failed to play sound: No such driver" ubuntu 20.04
*** This bug is a duplicate of bug 1879939 *** https://bugs.launchpad.net/bugs/1879939 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879939/comments/3 Mentions, that Kernel 5.4.0-32 is going to fix the problem, which is not right. 5.4.0-33 still has the problem. ** This bug has been marked a duplicate of bug 1879939 Audio stopped working after 5.4.0-31 kernel update -- 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/1879989 Title: "Failed to play sound: No such driver" ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: my speakers- built in audio produces terrible sound I tested the speakers via settings/sound and there was no sound I checked gnome logs and found "Failed to play sound: No such driver" I checked online and it seams to be a problem that affects many users ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: regern70802 F pulseaudio /dev/snd/pcmC0D0c: regern70802 F...m pulseaudio /dev/snd/pcmC0D0p: regern70802 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 19:13:55 2020 InstallationDate: Installed on 2020-05-16 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 15-3552 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.sku: 06AC dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879989/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879939] Re: Audio stopped working after 5.4.0-31 kernel update
Hi Hui Wang, 5.4.0-33 is installed on my machines and nothing was fixed. Please keep an eye on this bug. -- 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/1879939 Title: Audio stopped working after 5.4.0-31 kernel update Status in linux package in Ubuntu: Confirmed Bug description: After rebooting following a system update where kernel 5.4.0-31 got installed, the main audio output stopped working. HDMI audio and USB headphones still work. Rebooting using the previous kernel (5.4.0-29) restores audio. Description:Ubuntu 20.04 LTS Release:20.04 log of the update that broke audio: Install: linux-image-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-extra-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31:amd64 (5.4.0-31.35) Upgrade: bind9-dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-headers-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), linux-libc-dev:amd64 (5.4.0-29.33, 5.4.0-31.35), linux-image-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-host:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-libs:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zeyelth1921 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu May 21 13:05:44 2020 HibernationDevice: RESUME=UUID=8ede6c97-084e-4c19-b235-2ba8b2c5565c InstallationDate: Installed on 2017-10-29 (934 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-08 (12 days ago) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd04/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879760] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1879939 *** https://bugs.launchpad.net/bugs/1879939 ** This bug has been marked a duplicate of bug 1879939 Audio stopped working after 5.4.0-31 kernel update -- 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/1879760 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Confirmed Bug description: after updating ubuntu kernel pc cant detect sound its show dummy output but when i select from boot previous kernel the sound working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 21:20:11 2020 InstallationDate: Installed on 2020-05-10 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/03/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879939] Re: Audio stopped working after 5.4.0-31 kernel update
Odd Behavior of this Bug: 1. The audio device is not detected (not by gnome and not by lshw -C multimedia) and won't play sounds unless it's the "bell" from the terminal. 2. If headphones are plugged in, there won't be an detected audio device but lightly distorted sound is played thru headphones. 2. /proc/asound/card1/codec#0 is present and readable Codec: Realtek ALC892 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0892 [...] -- 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/1879939 Title: Audio stopped working after 5.4.0-31 kernel update Status in linux package in Ubuntu: Confirmed Bug description: After rebooting following a system update where kernel 5.4.0-31 got installed, the main audio output stopped working. HDMI audio and USB headphones still work. Rebooting using the previous kernel (5.4.0-29) restores audio. Description:Ubuntu 20.04 LTS Release:20.04 log of the update that broke audio: Install: linux-image-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-extra-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31:amd64 (5.4.0-31.35) Upgrade: bind9-dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-headers-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), linux-libc-dev:amd64 (5.4.0-29.33, 5.4.0-31.35), linux-image-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-host:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-libs:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zeyelth1921 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu May 21 13:05:44 2020 HibernationDevice: RESUME=UUID=8ede6c97-084e-4c19-b235-2ba8b2c5565c InstallationDate: Installed on 2017-10-29 (934 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-08 (12 days ago) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd04/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1574125] Re: suspend not working after uprade
Same problem with my HP Pavilion G6 after fresh installation of Ubuntu 16.04. ** Summary changed: - suspend not working after uprade + suspend not working after upgrade -- 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/1574125 Title: suspend not working after upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, Upgraded from Ubuntu 15.10 where suspend workes flawlessly. After upgrade, putting machine in suspend turns the monitor black and everything seem to be off, though the fan still spins, the power light is on and the battery is trained. Nothing seem to wake it up (Meaning different key combinations - trying to get a shell by Ctrl+Alt+F1, for example; pressing power, any other key). Unsure how to try to get it working since I have to kill the power by pressing down the power button, then restarting it (it then does a drive scan for errors). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maria 2076 F pulseaudio /dev/snd/controlC1: maria 2076 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 24 00:07:49 2016 HibernationDevice: RESUME=UUID=cc1bb3f2-abd6-41ad-b36e-62190fc5faaa InstallationDate: Installed on 2016-01-31 (83 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20351 ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-21 (2 days ago) dmi.bios.date: 04/02/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN25WW:bd04/02/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1116525] Re: [Lenovo ThinkPad X230 Tablet] USB devices in docking station no longer working after resuming from standby
** Also affects: archlinux Importance: Undecided Status: New -- 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/1116525 Title: [Lenovo ThinkPad X230 Tablet] USB devices in docking station no longer working after resuming from standby Status in “linux” package in Ubuntu: Incomplete Status in Arch Linux: New Bug description: rehooking up doesn't help. It happens but now always. I notices this in dmesg: [22731.711155] xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 0 with no TDs queued? [22732.254116] xhci_hcd :00:14.0: wake-up capability enabled by ACPI [22732.270095] xhci_hcd :00:14.0: power state changed by ACPI to D3 [22733.293595] xhci_hcd :00:14.0: wake-up capability disabled by ACPI [22733.293604] xhci_hcd :00:14.0: power state changed by ACPI to D0 [22733.293607] xhci_hcd :00:14.0: power state changed by ACPI to D0 [22733.295064] xhci_hcd :00:14.0: power state changed by ACPI to D0 [22733.295068] xhci_hcd :00:14.0: power state changed by ACPI to D0 [22733.295081] xhci_hcd :00:14.0: setting latency timer to 64 [22733.541145] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880113d5b880 [22733.962236] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880113fb3f00 [22734.249780] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801138c9f80 [22734.249784] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801138c9580 [22734.249812] xhci_hcd :00:14.0: Not enough bandwidth on HS bus for newly activated TT. [22734.249813] xhci_hcd :00:14.0: Not enough bandwidth [22734.344723] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880113fb3580 [22734.344735] xhci_hcd :00:14.0: Not enough bandwidth on HS bus for newly activated TT. [22734.344738] xhci_hcd :00:14.0: Not enough bandwidth [22735.504432] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880113fb3580 [22735.508451] xhci_hcd :00:14.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? [22735.607469] xhci_hcd :00:14.0: Not enough bandwidth on HS bus for newly activated TT. [22735.607471] xhci_hcd :00:14.0: Not enough bandwidth [22745.115509] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801138c9f80 [22745.115516] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801138c9580 [22745.231357] xhci_hcd :00:14.0: Not enough bandwidth on HS bus for newly activated TT. [22745.231360] xhci_hcd :00:14.0: Not enough bandwidth where :00:14.0 is: 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-generic 3.5.0.23.29 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mastier3564 F pulseaudio /dev/snd/controlC0: mastier3564 F pulseaudio Date: Tue Feb 5 19:12:53 2013 HibernationDevice: RESUME=UUID=f6738183-910b-49b9-b769-898c55ff5967 InstallationDate: Installed on 2012-10-25 (103 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 34352NG MarkForUpload: True ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-23-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GCET61WW (2.01 ) dmi.board.asset.tag: Not Available dmi.board.name: 34352NG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET61WW(2.01):bd09/20/2012:svnLENOVO:pn34352NG:pvrThinkPadX230Tablet:rvnLENOVO:rn34352NG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34352NG dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1116525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.
[Kernel-packages] [Bug 1116525] Re: [Lenovo ThinkPad X230 Tablet] USB devices in docking station no longer working after resuming from standby
This bug also occurs on Arch Linux (Linux 3.14.4-1-ARCH #1 SMP PREEMPT x86_64 GNU/Linux; BIOS Version 2.54), additionaly I have to mention that system also looses the ability sometimes to use the battery if I undock the X230T from the Ultrabase after waking it up from S3. Usually undocking and then redocking allows again the use of the USB Ports. Actually not all USB devices are affected by this issue, sometimes it's the mouse, sometimes the keyboard or sometimes everything. Also a working USB Device fails to work after reattaching it to the same USB Port. Bus 001 Device 006: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse Bus 001 Device 005: ID 08bb:2902 Texas Instruments PCM2902 Audio Codec Bus 001 Device 003: ID 17ef:6047 Lenovo (LENOVO ThinkPad Compact USB Keyboard with TrackPoint) -- 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/1116525 Title: [Lenovo ThinkPad X230 Tablet] USB devices in docking station no longer working after resuming from standby Status in “linux” package in Ubuntu: Incomplete Status in Arch Linux: New Bug description: rehooking up doesn't help. It happens but now always. I notices this in dmesg: [22731.711155] xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 0 with no TDs queued? [22732.254116] xhci_hcd :00:14.0: wake-up capability enabled by ACPI [22732.270095] xhci_hcd :00:14.0: power state changed by ACPI to D3 [22733.293595] xhci_hcd :00:14.0: wake-up capability disabled by ACPI [22733.293604] xhci_hcd :00:14.0: power state changed by ACPI to D0 [22733.293607] xhci_hcd :00:14.0: power state changed by ACPI to D0 [22733.295064] xhci_hcd :00:14.0: power state changed by ACPI to D0 [22733.295068] xhci_hcd :00:14.0: power state changed by ACPI to D0 [22733.295081] xhci_hcd :00:14.0: setting latency timer to 64 [22733.541145] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880113d5b880 [22733.962236] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880113fb3f00 [22734.249780] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801138c9f80 [22734.249784] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801138c9580 [22734.249812] xhci_hcd :00:14.0: Not enough bandwidth on HS bus for newly activated TT. [22734.249813] xhci_hcd :00:14.0: Not enough bandwidth [22734.344723] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880113fb3580 [22734.344735] xhci_hcd :00:14.0: Not enough bandwidth on HS bus for newly activated TT. [22734.344738] xhci_hcd :00:14.0: Not enough bandwidth [22735.504432] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 880113fb3580 [22735.508451] xhci_hcd :00:14.0: WARN Event TRB for slot 2 ep 2 with no TDs queued? [22735.607469] xhci_hcd :00:14.0: Not enough bandwidth on HS bus for newly activated TT. [22735.607471] xhci_hcd :00:14.0: Not enough bandwidth [22745.115509] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801138c9f80 [22745.115516] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8801138c9580 [22745.231357] xhci_hcd :00:14.0: Not enough bandwidth on HS bus for newly activated TT. [22745.231360] xhci_hcd :00:14.0: Not enough bandwidth where :00:14.0 is: 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-generic 3.5.0.23.29 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mastier3564 F pulseaudio /dev/snd/controlC0: mastier3564 F pulseaudio Date: Tue Feb 5 19:12:53 2013 HibernationDevice: RESUME=UUID=f6738183-910b-49b9-b769-898c55ff5967 InstallationDate: Installed on 2012-10-25 (103 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 34352NG MarkForUpload: True ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-23-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-23-generic N/A linux-backports-modules-3.5.0-23-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2012 dmi.bios.vendor: LENOVO dmi.bios.version: GCET61WW (2.01 ) dmi.board.asset.t
[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported
I'm on an Acer Aspire VN7-591G and Ubuntu 15.04 (Vivid dev) with kernel 3.18.0-8 and while wifi doesn't work, bluetooth *does*. It pairs and can send files to my smartphone. -- 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/1383184 Title: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] not supported Status in linux package in Ubuntu: Confirmed Bug description: Card detail: Qualcomm Atheros Device [168c:003e] (rev 20) Subsystem: Bigfoot Networks, Inc. Device [1a56:1525] This is on a fully updated Ubuntu Server 14.04 installation, with the ubuntu-desktop environment installed. This happened in order to get the md raid drivers for raid0 on my system, as the desktop version doesn't support them. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: matanis2333 F pulseaudio /dev/snd/controlC0: matanis2333 F pulseaudio CRDA: Error: [Errno 2] No such file or directory CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6 InstallationDate: Installed on 2014-10-16 (3 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: Micro-Star International Co., Ltd. GT72 2QE NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RelatedPackageVersions: linux-restricted-modules-3.13.0-37-generic N/A linux-backports-modules-3.13.0-37-generic N/A linux-firmware 1.127.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10D dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1233576] [NEW] [LENOVO 7505] suspend/resume failure [non-free: wl]
Public bug reported: [LENOVO 7505] suspend/resume failure [non-free: wl] ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johannes 1500 F pulseaudio Date: Mon Sep 30 08:56:57 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-09-21 (9 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130919) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 7505 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=7d712dfb-ba09-4882-a6d3-60ef2ad1d96e ro nomodeset quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.114 SourcePackage: linux StagingDrivers: rts5139 Title: [LENOVO 7505] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/14/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN92WW(V8.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad N581 dmi.modalias: dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn7505:pvrLenovoIdeaPadN581:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadN581: dmi.product.name: 7505 dmi.product.version: Lenovo IdeaPad N581 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume saucy staging suspend -- 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/1233576 Title: [LENOVO 7505] suspend/resume failure [non-free: wl] Status in “linux” package in Ubuntu: New Bug description: [LENOVO 7505] suspend/resume failure [non-free: wl] ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-9-generic 3.11.0-9.16 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 NonfreeKernelModules: wl Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johannes 1500 F pulseaudio Date: Mon Sep 30 08:56:57 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2013-09-21 (9 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130919) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 7505 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=7d712dfb-ba09-4882-a6d3-60ef2ad1d96e ro nomodeset quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-9-generic N/A linux-backports-modules-3.11.0-9-generic N/A linux-firmware1.114 SourcePackage: linux StagingDrivers: rts5139 Title: [LENOVO 7505] suspend/resume failure [non-free: wl] UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/14/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN92WW(V8.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad N581 dmi.modalias: dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn7505:pvrLenovoIdeaPadN581:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadN581: dmi.product.name: 7505 dmi.product.version: Lenovo IdeaPad N581 dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1848831]
These all: 0x20100222 | ADVANCED_SYSASSERT 0x201000A3 | ADVANCED_SYSASSERT and possibly the SecBoot CPU1 Status: 0x5ae1, CPU2 Status: 0x3 as well all point to a similar issue with (firmware) timeouts during PCIe DMA transactions. I don't know if there's something with the link that makes it slower, or the timeouts are just really small, I guess we'll need to check. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1848831 Title: Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi Status in Gaming Edition: In Progress Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC uname -a Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux The card is detected OK as dmesg shows, however the card's firmware fails immediately after loading (see dmesg output below) and wifi doesn't work at all. Big disappointment since the AX200 chip was supposed to be supported on 19.10. Ubuntu includes two ax200 firmware versions, version 48 loads by default in my system (and fails). I tried version 46 (by renaming the version 48 file) and it failed in the exact same manner $ ls /lib/firmware/iwlwifi-cc-* /lib/firmware/iwlwifi-cc-a0-46.ucode /lib/firmware/iwlwifi-cc-a0-48.ucode The card's Bluetooth functionality is also detected and it works fine. It's just the wifi FW loading what seems broken in ubuntu's 5.3 kernel. $ rfkill list 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no ~$ dmesg | grep iwl [ 12.312443] iwlwifi :01:00.0: enabling device ( -> 0002) [ 12.321098] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [ 12.321101] iwlwifi :01:00.0: Found debug destination: EXTERNAL_DRAM [ 12.321102] iwlwifi :01:00.0: Found debug configuration: 0 [ 12.321309] iwlwifi :01:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [ 12.390389] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 12.400654] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM [ 12.400893] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware monitor. [ 13.414781] iwlwifi :01:00.0: Collecting data: trigger 15 fired. [ 13.414908] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 13.414910] iwlwifi :01:00.0: Status: 0x, count: 6 [ 13.414911] iwlwifi :01:00.0: Loaded firmware version: 48.4fa0041f.0 [ 13.414912] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 13.414913] iwlwifi :01:00.0: 0x002022F0 | trm_hw_status0 [ 13.414913] iwlwifi :01:00.0: 0x | trm_hw_status1 [ 13.414914] iwlwifi :01:00.0: 0x004F8E3C | branchlink2 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink1 [ 13.414915] iwlwifi :01:00.0: 0x004E4FF4 | interruptlink2 [ 13.414916] iwlwifi :01:00.0: 0x004F3DB0 | data1 [ 13.414917] iwlwifi :01:00.0: 0x1000 | data2 [ 13.414917] iwlwifi :01:00.0: 0xF000 | data3 [ 13.414918] iwlwifi :01:00.0: 0x | beacon time [ 13.414919] iwlwifi :01:00.0: 0x795F | tsf low [ 13.414919] iwlwifi :01:00.0: 0x | tsf hi [ 13.414920] iwlwifi :01:00.0: 0x | time gp1 [ 13.414921] iwlwifi :01:00.0: 0xDFD5 | time gp2 [ 13.414921] iwlwifi :01:00.0: 0x0001 | uCode revision type [ 13.414922] iwlwifi :01:00.0: 0x0030 | uCode version major [ 13.414923] iwlwifi :01:00.0: 0x4FA0041F | uCode version minor [ 13.414923] iwlwifi :01:00.0: 0x0340 | hw version [ 13.414924] iwlwifi :01:00.0: 0x18C89000 | board version [ 13.414925] iwlwifi :01:00.0: 0x8002FF03 | hcmd [ 13.414925] iwlwifi :01:00.0: 0x0002 | isr0 [ 13.414926] iwlwifi :01:00.0: 0x | isr1 [ 13.414926] iwlwifi :01:00.0: 0x08F2 | isr2 [ 13.414927] iwlwifi :01:00.0: 0x00CC | isr3 [ 13.414928] iwlwifi :01:00.0: 0x | isr4 [ 13.414928] iwlwifi :01:00.0: 0x | last cmd Id [ 13.414929] iwlwifi :01:00.0: 0x004F3DB0 | wait_event [ 13.414930] iwlwifi :01:00.0: 0x | l2p_control [ 13.414930] iwlwifi :01:00.0: 0x0020 | l2p_duration [ 13.414931] iwlwifi :01:00.0: 0x | l2p_mhvalid [ 13.414932] iwlwifi :01:00.0: 0x | l2p_addr_match [ 13.414932] iwlwifi :01:00.0: 0x0009 | lmpm_pmg_sel [ 13.414933] iwlwifi :01:00.0: 0x | timestamp [ 13.414934] iwlwifi :01:00.0: 0xF81C | flow_handler [ 13.414974] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 13.414975] iwlwifi :01:00.0: Status: 0x,
[Kernel-packages] [Bug 2033271] Re: Fujitsu keyboard not working after updates
I found a solution that worked for me with ubuntu, although the solution is described for fedora. https://discussion.fedoraproject.org/t/fujitsu-lifebook-e5510-keyboard- not-detected/70907/18 edit boot parameter in grub, usually after "quiet splash" "i8042.nomux=1 i8042.reset" result: "quiet splash i8042.nomux=1 i8042.reset" worked for me detailed doc for boot parameters: https://wiki.ubuntu.com/Kernel/KernelBootParameters as hint for urgend workaround: using standby and wake up again solved the problem for me too, as quick solution, if no external keyboard is available. -- 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/2033271 Title: Fujitsu keyboard not working after updates Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.3 LTS Fujitsu Lifebook E5410 Expected to happen is that the keyboard is working as previous before the updates. What instead happens is, that the keyboard is dead and does not work. Attaching an external USB-keyboard works. The keyboard works before boot in the BIOS context, so it is not hardware related. -- There is another user reporting the same issue for a E5510 on ask Ubuntu. https://askubuntu.com/questions/1483381/ubuntu-22-04-fujitsu- lifebook-e5510-keyboard-not-working-after-update-kernel ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 28 12:01:29 2023 InstallationDate: Installed on 2022-04-21 (493 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cysec 1698 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-21 (497 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5410 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.18 Tags: wayland-session jammy Uname: Linux 6.2.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 06/30/2023 dmi.bios.release: 2.30 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.30 dmi.board.name: FJNB2D6 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK E5410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.30:bd06/30/2023:br2.30:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5410:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D6:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5410:skuSK01: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK E5410 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062426] Re: simple-framebuffer: swiotlb buffer is full
The fix seems to have now come to 24.04.1 with NVIDIA 535 drivers (and works yeah!) Just in case there's others using CUDA with podman, you might need to update your configs now that the /dev/dri/card0 is missing: sudo nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml -- 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/2062426 Title: simple-framebuffer: swiotlb buffer is full Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-550 package in Ubuntu: Confirmed Bug description: [ 29.548909] [ cut here ] [ 29.548912] simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem) [ 29.548924] WARNING: CPU: 7 PID: 2700 at drivers/gpu/drm/drm_gem_shmem_helper.c:319 drm_gem_shmem_vmap+0x1a5/0x1e0 [ 29.548932] Modules linked in: nf_tables libcrc32c snd_seq_dummy snd_hrtimer ccm qrtr binfmt_misc nvidia_uvm(POE) nvidia_drm(POE) nvidia_modeset(POE) nls_iso8859_1 nvidia(POE) intel_rapl_msr intel_rapl_common snd_hda_codec_hdmi snd_hda_intel rtl8192ee snd_intel_dspcfg snd_intel_sdw_acpi btcoexist snd_hda_codec snd_usb_audio rtl_pci snd_hda_core snd_usbmidi_lib rtlwifi snd_hwdep snd_ump snd_seq_midi edac_mce_amd snd_seq_midi_event snd_rawmidi mac80211 mc kvm_amd snd_seq snd_pcm snd_seq_device kvm joydev snd_timer input_leds cfg80211 snd irqbypass soundcore libarc4 rapl video wmi_bmof ccp k10temp i2c_piix4 gpio_amdpt mac_hid msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic r8169 ghash_clmulni_intel sha256_ssse3 sha1_ssse3 ahci xhci_pci realtek libahci xhci_pci_renesas wmi aesni_intel crypto_simd cryptd [ 29.549044] CPU: 7 PID: 2700 Comm: Xorg Tainted: P OE 6.8.0-22-generic #22-Ubuntu [ 29.549047] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./A320M-DVS R4.0, BIOS P4.00 07/16/2020 [ 29.549049] RIP: 0010:drm_gem_shmem_vmap+0x1a5/0x1e0 [ 29.549054] Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 44 a6 ec ff 48 c7 c1 73 62 82 9f 4c 89 ea 48 c7 c7 b2 3d 82 9f 48 89 c6 e8 4b 3f 44 ff <0f> 0b 48 8b 83 f0 00 00 00 4c 89 e6 48 8b 38 e8 f7 48 f5 ff b8 fb [ 29.549056] RSP: 0018:b6da8304ba08 EFLAGS: 00010246 [ 29.549060] RAX: RBX: a0778c558a00 RCX: [ 29.549062] RDX: RSI: RDI: [ 29.549063] RBP: b6da8304ba28 R08: R09: [ 29.549065] R10: R11: R12: a0778cdaa6c8 [ 29.549067] R13: a07781d2efc0 R14: a0778cdaa6c8 R15: a0778cdaa6c8 [ 29.549069] FS: 7e8343530ac0() GS:a07a8e58() knlGS: [ 29.549071] CS: 0010 DS: ES: CR0: 80050033 [ 29.549073] CR2: 567a82464778 CR3: 00014044e000 CR4: 003506f0 [ 29.549075] Call Trace: [ 29.549078] [ 29.549082] ? show_regs+0x6d/0x80 [ 29.549087] ? __warn+0x89/0x160 [ 29.549092] ? drm_gem_shmem_vmap+0x1a5/0x1e0 [ 29.549096] ? report_bug+0x17e/0x1b0 [ 29.549103] ? handle_bug+0x51/0xa0 [ 29.549108] ? exc_invalid_op+0x18/0x80 [ 29.549112] ? asm_exc_invalid_op+0x1b/0x20 [ 29.549121] ? drm_gem_shmem_vmap+0x1a5/0x1e0 [ 29.549125] ? drm_gem_shmem_vmap+0x1a5/0x1e0 [ 29.549130] drm_gem_shmem_object_vmap+0x9/0x20 [ 29.549133] drm_gem_vmap+0x26/0x80 [ 29.549138] drm_gem_vmap_unlocked+0x2b/0x50 [ 29.549142] drm_gem_fb_vmap+0x40/0x150 [ 29.549147] drm_gem_begin_shadow_fb_access+0x25/0x40 [ 29.549150] drm_atomic_helper_prepare_planes.part.0+0x142/0x1e0 [ 29.549155] drm_atomic_helper_prepare_planes+0x5d/0x70 [ 29.549160] drm_atomic_helper_commit+0x84/0x160 [ 29.549164] drm_atomic_commit+0x99/0xd0 [ 29.549167] ? __pfx___drm_printfn_info+0x10/0x10 [ 29.549173] drm_atomic_helper_set_config+0x82/0xd0 [ 29.549176] drm_mode_setcrtc+0x535/0x8b0 [ 29.549187] ? __pfx_drm_mode_setcrtc+0x10/0x10 [ 29.549191] drm_ioctl_kernel+0xbc/0x120 [ 29.549194] ? srso_return_thunk+0x5/0x5f [ 29.549200] drm_ioctl+0x2d4/0x550 [ 29.549204] ? __pfx_drm_mode_setcrtc+0x10/0x10 [ 29.549214] __x64_sys_ioctl+0xa3/0xf0 [ 29.549220] do_syscall_64+0x85/0x180 [ 29.549223] ? srso_return_thunk+0x5/0x5f [ 29.549226] ? count_memcg_events.constprop.0+0x2a/0x50 [ 29.549231] ? srso_return_thunk+0x5/0x5f [ 29.549234] ? handle_mm_fault+0xad/0x380 [ 29.549238] ? srso_return_thunk+0x5/0x5f [ 29.549241] ? do_user_addr_fault+0x338/0x6b0 [ 29.549245] ? srso_return_thunk+0x5/0x5f [ 29.549248] ? irqentry_exit_to_user_mode+0x7b/0x260 [ 29.549252] ? srso_return_thunk+0x5/0x5f [ 29.549255] ? irqentry_exit+0x43/0x50 [
[Kernel-packages] [Bug 1837833] Re: EBS Volumes get stuck detaching from AWS instances
@mruffell we saw the same issue on our AWS machines, but a kernel version including https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=f0c83dd15ee1e89f73523cb82da9205d204cf440 (e.g. 4.19.61) fixed it for us. -- 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/1837833 Title: EBS Volumes get stuck detaching from AWS instances Status in linux package in Ubuntu: Incomplete Bug description: On AWS, it is possible to get a EBS volume stuck in the detaching state, where it is not present in lsblk or lspci, but the cloud console says the volume is detaching, and pci / nvme errors are output to dmesg every 180 seconds. To reproduce reliably: 1) Start a AWS instance. Can be any type, nitro or regular. I have successfully reproduced on m5.large and t3.small. Add an extra volume during creation, of any size. 2) Connect to the instance. lsblk and lspci show the nvme device there. Detach the volume from the web console. It will detach successfully. You can attach and then detach the volume again, and it will also work successfully. 3) With the volume detached, reboot the instance. I do "sudo reboot". 4) When the instance comes back up and you have logged in, attach the volume. dmesg will have (normal): kernel: [ 67] pci :00:1f.0: [1d0f:8061] type 00 class 0x010802 kernel: [ 67] pci :00:1f.0: reg 0x10: [mem 0x-0x3fff] kernel: [ 67] pci :00:1f.0: BAR 0: assigned [mem 0x8000-0x80003fff] kernel: [ 67] nvme nvme1: pci function :00:1f.0 kernel: [ 67] nvme :00:1f.0: enabling device ( -> 0002) kernel: [ 67] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 5) Detach the volume from the web console. If you keep refreshing the volume view, you will see the volume in the detaching state and the volume is still in use. The device will be missing from lsblk and lspci. dmesg will print these messages every 180 seconds: 4.4 -> 4.15 kernel: [ 603] pci :00:1f.0: [1d0f:8061] type 00 class 0x010802 kernel: [ 603] pci :00:1f.0: reg 0x10: [mem 0x8000-0x80003fff] kernel: [ 603] pci :00:1f.0: BAR 0: assigned [mem 0x8000-0x80003fff] kernel: [ 603] nvme nvme1: pci function :00:1f.0 kernel: [ 603] nvme nvme1: failed to mark controller live kernel: [ 603] nvme nvme1: Removing after probe failure status: 0 Latest mainline kernel: kernel: [ 243] pci :00:1f.0: [1d0f:8061] type 00 class 0x010802 kernel: [ 243] pci :00:1f.0: reg 0x10: [mem 0xc000-0xc0003fff] kernel: [ 243] pci :00:1f.0: BAR 0: assigned [mem 0xc000-0xc0003fff] kernel: [ 243] nvme nvme1: pci function :00:1f.0 kernel: [ 244] nvme nvme1: failed to mark controller CONNECTING kernel: [ 244] nvme nvme1: Removing after probe failure status: 0 The volume is now stuck detaching and the above will continue until you forcefully detach the volume. This seems to effect all distributions and all kernels. I have tested xenial, bionic, bionic + hwe, bionic + eoan, bionic + mainline 5.2.2, rhel8 and Amazon Linux 2. All are affected with the same symptoms. I tried to trace NVMe on 5.2, but with not much success on finding any problem: https://paste.ubuntu.com/p/c6rmDpvHJk/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833842] Re: Kernel 4.4.0-151 fails to boot
This might be the same as https://bugs.launchpad.net/ubuntu/+source /linux-signed/+bug/1829657 (-145 works, -148 doesn't (-146 boots, but might have other problems)) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1833842 Title: Kernel 4.4.0-151 fails to boot Status in linux-signed package in Ubuntu: New Bug description: On startup, choosing Linux image 4.4.0-151 on grub makes system freeze immediately. Same behaviour with Linux image 4.4.0-150. No problem with Linux image 4.4.0-141. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-151-generic 4.4.0-151.178 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jun 23 11:55:00 2019 InstallationDate: Installed on 2015-05-02 (1513 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcEnviron: LANGUAGE=fr_FR TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1833842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Sorry, how do I install these kernels? They are conflicting with default versions (bionic) and dpkg refuses to install them. ** Bug watch added: Linux Kernel Bug Tracker #199855 https://bugzilla.kernel.org/show_bug.cgi?id=199855 -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Btw, there is another hardware issue with the laptop I got here, which is caused by the ideapad_laptop module. I have also prepared a patch for that: https://bugzilla.kernel.org/show_bug.cgi?id=199855. Could that also be included before being in the official kernel sources? Should I open a new issue for that? -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Ok, got the kernel installed and the touchpad is working as expected. -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774636] [NEW] Lenovo V330 needs patch in ideapad_laptop module for rfkill
Public bug reported: The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. I have provided a patch to the kernel developers upstream: https://bugzilla.kernel.org/show_bug.cgi?id=199855 However, there is not much activity at the moment. Since this laptop is available now and the bug is a real blocker for unexperienced users, would it be possible to add the (quite simple) fix to the ubuntu kernel until it is accepted upstream? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1774636 Title: Lenovo V330 needs patch in ideapad_laptop module for rfkill Status in linux package in Ubuntu: Incomplete Bug description: The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. I have provided a patch to the kernel developers upstream: https://bugzilla.kernel.org/show_bug.cgi?id=199855 However, there is not much activity at the moment. Since this laptop is available now and the bug is a real blocker for unexperienced users, would it be possible to add the (quite simple) fix to the ubuntu kernel until it is accepted upstream? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
ok. done: https://bugs.launchpad.net/bugs/1774636 -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774636] Re: Lenovo V330 needs patch in ideapad_laptop module for rfkill
Sorry for the delay. Yes, this seems to work as well. -- 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/1774636 Title: Lenovo V330 needs patch in ideapad_laptop module for rfkill Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. I have provided a patch to the kernel developers upstream: https://bugzilla.kernel.org/show_bug.cgi?id=199855 However, there is not much activity at the moment. Since this laptop is available now and the bug is a real blocker for unexperienced users, would it be possible to add the (quite simple) fix to the ubuntu kernel until it is accepted upstream? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Thanks for accepting this. Any idea when this will be available in the packages? -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, this patch is being sent as a SAUCE patch until it lands upstream. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 == Fix == UBUNTU: SAUCE: Input: elan_i2c - add ELAN0612 to the ACPI table == Regression Potential == Low. One liner to add a device id. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Sorry, I don't understand the process, I think. I have reported this issue for bionic. How am I supposed to test this for artful? -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, this patch is being sent as a SAUCE patch until it lands upstream. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 == Fix == UBUNTU: SAUCE: Input: elan_i2c - add ELAN0612 to the ACPI table == Regression Potential == Low. One liner to add a device id. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] Re: ELANPAD ELAN0612 does not work, patch available
And I can't even add tags??? -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, this patch is being sent as a SAUCE patch until it lands upstream. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 == Fix == UBUNTU: SAUCE: Input: elan_i2c - add ELAN0612 to the ACPI table == Regression Potential == Low. One liner to add a device id. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773509] [NEW] ELANPAD ELAN0612 does not work, patch available
Public bug reported: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: New Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1770845] Re: Make vfio-pci built-in or xhci_hcd optional
Including VFIO in the kernel would be great! This would resolve all
kinds of pass-through crashes.
Currently, the only way to do this is to hope that the USB controller
behaves properly during reclamation by the kernel (most of them do not),
which varies wildly by vendor. In my case, it gets as bad as having the
whole system hang on shutdown due to a crash in the xhci_hcd driver. The
ideal solution would be the ability to pass the device through directly
to a VM guest, so that no cooperation by the controller is required.
--
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/1770845
Title:
Make vfio-pci built-in or xhci_hcd optional
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Cosmic:
Triaged
Bug description:
Because of
nazar-pc@nazar-pc ~> cat '/boot/config-4.15.0-21-generic' | grep
CONFIG_USB_XHCI_HCD
CONFIG_USB_XHCI_HCD=y
Following doesn't work:
nazar-pc@nazar-pc ~> cat /etc/modprobe.d/gpu-passthrough.conf
options vfio-pci ids=10de:1b06,10de:10ef,1b21:2142
softdep nouveau pre: vfio-pci
softdep xhci_hcd pre: vfio-pci
GPU is fine (first 2 IDs), but USB controller is always occupied by
xhci_hcd and I can't change that while xhci_hcd is built-in.
I'd like you to resolve this issue by either embedding vfio-pci module
too (prefered solution) or making xhci_hcd optional.
There are some discussions withot clean solution online like this:
https://www.reddit.com/r/VFIO/comments/4o6wla/cant_get_vfiopci_to_bind_to_usb_30_card_at_boot/
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.15.0-21-generic 4.15.0-21.22
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-21-generic.
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: S51 [SB Omni Surround 5.1], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0c: nazar-pc 2226 F...m pulseaudio
/dev/snd/pcmC1D0p: nazar-pc 2226 F...m pulseaudio
/dev/snd/controlC1: nazar-pc 2226 F pulseaudio
nazar-pc 2267 F volumeicon
Card1.Amixer.info:
Card hw:1 'S51'/'Creative Technology Ltd SB Omni Surround 5.1 at
usb-:00:14.0-9.2, full spee'
Mixer name : 'USB Mixer'
Components : 'USB041e:322c'
Controls : 12
Simple ctrls : 5
CurrentDesktop: Custom
Date: Sat May 12 16:44:11 2018
IwConfig: Error: [Errno 2] Немає такого файла або каталогу: 'iwconfig':
'iwconfig'
MachineType: Micro-Star International Co., Ltd. MS-7B45
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/root/boot/vmlinuz-4.15.0-21-generic
root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root
nosplash intel_pstate=disable scsi_mod.use_blk_mq=1 intel_iommu=on
RelatedPackageVersions:
linux-restricted-modules-4.15.0-21-generic N/A
linux-backports-modules-4.15.0-21-generic N/A
linux-firmware 1.173
RfKill: Error: [Errno 2] Немає такого файла або каталогу: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.51
dmi.board.asset.tag: Default string
dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrA.51:bd03/29/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: Default string
dmi.product.name: MS-7B45
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770845/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection
I'm getting this on Ubuntu desktop 18.10 at work. It seems to be happening more and more often. Today it's up to 5 times within 2-3 hours. Currently I fix it by disconnecting and reconnecting the ethernet cable after af few seconds. This is becomming rather painful. -- 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/1785171 Title: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I've turned up many, many new server and workstation systems over the years on both Linux and Windows. Never seen anything like this behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply lose Internet connectivity while using a browser. Ethernet interfaces usually either work or they don't work. I've configured the Intel I219-V Ethernet interface (wired Ethernet connection, there is no wifi on this system) using the e1000e driver for Ubuntu. The Ethernet connection is configured to use NetworkManager via Netplan on Ubuntu 18.04 LTS Server version. ASRock Z370m Pro4 motherboard. The Ethernet interface will drop the Internet connectivity when I'm using either the Firefox or Chrome browser. It usually happens when I'm using the search features of the browser. I can't figure out what would cause this type of behaviour. When the Internet connection drops, the only way to get back Internet connectivity is to disconnect the wired connection using the Ubuntu features and then re-connect (this restarts the NetworkManager service I notice). In the NetworkManager logs I do notice an "auth" error about a file or directory not found. I've never seen that before. Note: The auth error does not coincide with the loss of Internet connectivity, but it does proceed it. Often there can be many hours between the auth error and the actual loss of Internet connectivity. After I reconnect the connection (via re-starting the NetworkManager service) all will be fine for up to a day or so, but then I stress test it with a bunch of searches using the browser and usually I can get the Internet connectivity to drop again. Repeat the disconnect and reconnect process again (aka re-start NetworkManager) and the Internet connectivity will be fine again. The longest I've seen it go without an "Internet connectivity drop" issue is about 36 hours. I notice that the e1000e driver does not list the I219-V as a supported Ethernet interface in the Intel documentation for the Linux version of the driver. I'm not sure why that is. The I219-V is supposed to used another driver, but it's not clear there's a Linux version for of the driver for the I219-V. I'm really disappointed that I've run into this issue with Ubuntu Server LTS 18.04 on this motherboard. I had CentOS Server 7.4 (my standard server OS, a great Linux distro) on this same motherboard for a week with no issues, so I know the motherboard and the I219-V Ethernet interface are 100% good hardware wise and can work properly. CentOS 7.4 uses NetworkManager as the default for managing the Ethernet interface. The only reason I'm using Ubuntu Server 18.04 on this motherboard is because of a specific package that Ubuntu has a newer packaged version than CentOS. CentOS is extremely stable when it comes to basic server functionality. Hopefully, this bug with the I219-V Ethernet interface using the e1000e drive for Linux can be verified and a fix rolled out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907432] [NEW] Raspberry Pi 400 Kernel Panic
Public bug reported: When I power the Pi 400 down (with the key-combination on the pi 400 or with the navigation from the top right), a line like this is on screen: [59095.049506] reboot: Power down or that: [25784.810857] reboot: Power down Under this line, the cursor is frozen. After a while, suddenly, the text scrolls and stops after a while. I can read something about "Kernel Panic" on screen. I cannot power the device off. I have to pull the power plug to shut it down, or to re-plug it to reset it. The power-button (2sec) does not work, 10 seconds reset signal, neither. Here you can find my initial question to this phenomenon: https://answers.launchpad.net/ubuntu/+question/694349 This I should include: Linux version 5.8.0-1008-raspi (buildd@bos02-arm64-062) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #11-Ubuntu SMP PREEMPT Thu Nov 12 15:49:32 UTC 2020 I hope this report includes enough information. If not, please do not hesitate to contact me! Thanks so much for this project and thx for being a part of it! <3 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-1008-raspi 5.8.0-1008.11 ProcVersionSignature: Ubuntu 5.8.0-1008.11-raspi 5.8.17 Uname: Linux 5.8.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 9 10:40:08 2020 ImageMediaBuild: 20201022 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1907432 Title: Raspberry Pi 400 Kernel Panic Status in linux-raspi package in Ubuntu: New Bug description: When I power the Pi 400 down (with the key-combination on the pi 400 or with the navigation from the top right), a line like this is on screen: [59095.049506] reboot: Power down or that: [25784.810857] reboot: Power down Under this line, the cursor is frozen. After a while, suddenly, the text scrolls and stops after a while. I can read something about "Kernel Panic" on screen. I cannot power the device off. I have to pull the power plug to shut it down, or to re-plug it to reset it. The power-button (2sec) does not work, 10 seconds reset signal, neither. Here you can find my initial question to this phenomenon: https://answers.launchpad.net/ubuntu/+question/694349 This I should include: Linux version 5.8.0-1008-raspi (buildd@bos02-arm64-062) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #11-Ubuntu SMP PREEMPT Thu Nov 12 15:49:32 UTC 2020 I hope this report includes enough information. If not, please do not hesitate to contact me! Thanks so much for this project and thx for being a part of it! <3 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-1008-raspi 5.8.0-1008.11 ProcVersionSignature: Ubuntu 5.8.0-1008.11-raspi 5.8.17 Uname: Linux 5.8.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 9 10:40:08 2020 ImageMediaBuild: 20201022 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1907432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889669] Re: Focal update: v5.4.54 upstream stable release
Isn't this due to be released today (31 August), according to
https://kernel.ubuntu.com/?
--
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/1889669
Title:
Focal update: v5.4.54 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.54 upstream stable release
from git://git.kernel.org/
soc: qcom: rpmh: Dirt can only make you dirtier, not cleaner
gpio: arizona: handle pm_runtime_get_sync failure case
gpio: arizona: put pm_runtime in case of failure
pinctrl: amd: fix npins for uart0 in kerncz_groups
mac80211: allow rx of mesh eapol frames with default rx key
scsi: scsi_transport_spi: Fix function pointer check
xtensa: fix __sync_fetch_and_{and,or}_4 declarations
xtensa: update *pos in cpuinfo_op.next
scsi: mpt3sas: Fix unlock imbalance
drivers/net/wan/lapbether: Fixed the value of hard_header_len
ALSA: hda/hdmi: fix failures at PCM open on Intel ICL and later
net: sky2: initialize return of gm_phy_read
drm/nouveau/i2c/g94-: increase NV_PMGR_DP_AUXCTL_TRANSACTREQ timeout
scsi: mpt3sas: Fix error returns in BRM_status_show
scsi: dh: Add Fujitsu device to devinfo and dh lists
dm: use bio_uninit instead of bio_disassociate_blkg
drivers/firmware/psci: Fix memory leakage in alloc_init_cpu_groups()
fuse: fix weird page warning
irqdomain/treewide: Keep firmware node unconditionally allocated
ARM: dts: imx6qdl-gw551x: Do not use 'simple-audio-card,dai-link'
ARM: dts: imx6qdl-gw551x: fix audio SSI
dmabuf: use spinlock to access dmabuf->name
drm/amd/display: Check DMCU Exists Before Loading
SUNRPC reverting d03727b248d0 ("NFSv4 fix CLOSE not waiting for direct IO
compeletion")
btrfs: reloc: fix reloc root leak and NULL pointer dereference
btrfs: reloc: clear DEAD_RELOC_TREE bit for orphan roots to prevent runaway
balance
uprobes: Change handle_swbp() to send SIGTRAP with si_code=SI_KERNEL, to fix
GDB regression
ALSA: hda/realtek: Fixed ALC298 sound bug by adding quirk for Samsung
Notebook Pen S
ALSA: info: Drop WARN_ON() from buffer NULL sanity check
ASoC: rt5670: Correct RT5670_LDO_SEL_MASK
btrfs: fix double free on ulist after backref resolution failure
btrfs: fix mount failure caused by race with umount
btrfs: fix page leaks after failure to lock page for delalloc
bnxt_en: Fix race when modifying pause settings.
bnxt_en: Fix completion ring sizing with TPA enabled.
fpga: dfl: pci: reduce the scope of variable 'ret'
fpga: dfl: fix bug in port reset handshake
hippi: Fix a size used in a 'pci_free_consistent()' in an error handling path
vsock/virtio: annotate 'the_virtio_vsock' RCU pointer
ax88172a: fix ax88172a_unbind() failures
RDMA/mlx5: Use xa_lock_irq when access to SRQ table
ASoC: Intel: bytcht_es8316: Add missed put_device()
net: dp83640: fix SIOCSHWTSTAMP to update the struct with actual configuration
ieee802154: fix one possible memleak in adf7242_probe
drm: sun4i: hdmi: Fix inverted HPD result
net: smc91x: Fix possible memory leak in smc_drv_probe()
bonding: check error value of register_netdevice() immediately
mlxsw: destroy workqueue when trap_register in mlxsw_emad_init
ionic: use offset for ethtool regs data
ionic: fix up filter locks and debug msgs
net: ag71xx: add missed clk_disable_unprepare in error path of probe
net: hns3: fix error handling for desc filling
net: dsa: microchip: call phy_remove_link_mode during probe
netdevsim: fix unbalaced locking in nsim_create()
qed: suppress "don't support RoCE & iWARP" flooding on HW init
qed: suppress false-positives interrupt error messages on HW init
ipvs: fix the connection sync failed in some cases
net: ethernet: ave: Fix error returns in ave_init
Revert "PCI/PM: Assume ports without DLL Link Active train links in 100 ms"
nfsd4: fix NULL dereference in nfsd/clients display code
enetc: Remove the mdio bus on PF probe bailout
i2c: rcar: always clear ICSAR to avoid side effects
i2c: i2c-qcom-geni: Fix DMA transfer race
bonding: check return value of register_netdevice() in bond_newlink()
geneve: fix an uninitialized value in geneve_changelink()
serial: exar: Fix GPIO configuration for Sealevel cards based on XR17V35X
scripts/decode_stacktrace: strip basepath from all paths
scripts/gdb: fix lx-symbols 'gdb.error' while loading modules
HID: i2c-hi
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
today's kernel update seems to have fixed it, as expected. -- 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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of course, this is a crutch, and when you can't run balance, then the fs is bound to run out of space at some point
[Kernel-packages] [Bug 1890951] [NEW] btrfs not writable when mounted without "skip_balance"
Public bug reported: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of course, this is a crutch, and when you can't run balance, then the fs is bound to run out of space at some point. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: New Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
Unfortunately, producing the logs apart from the backtrace above isn't really possible. As soon as I reproduce the bug, the FS becomes unwritable, so that no logs can be obtained. That's a catch22 ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: New Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only tem
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
apport information ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Tags added: apport-collected focal ** Description changed: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 - So this is obviously a btrfs bug that got introduced by the newer btrfs - code in the newer kernel, although, booting an older kernel didn't fix - it. Apparently something about the fs is messed up now and no balance - can be run. The only temporary remedy I found was to add the - skip_balance mount option to /etc/fstab, but of course, this is a - crutch, and when you can't run balance, then the fs is bound to run out - of space at some point. + So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed
[Kernel-packages] [Bug 1890951] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400184/+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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of course, this
[Kernel-packages] [Bug 1890951] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400185/+files/Lspci-vt.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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of cours
[Kernel-packages] [Bug 1890951] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400189/+files/ProcModules.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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of
[Kernel-packages] [Bug 1890951] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400188/+files/ProcInterrupts.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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab,
[Kernel-packages] [Bug 1890951] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400191/+files/WifiSyslog.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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of c
[Kernel-packages] [Bug 1890951] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400186/+files/ProcCpuinfo.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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of
[Kernel-packages] [Bug 1890951] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400190/+files/UdevDb.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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of course, th
[Kernel-packages] [Bug 1890951] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400183/+files/CurrentDmesg.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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but
[Kernel-packages] [Bug 1890951] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1890951/+attachment/5400187/+files/ProcCpuinfoMinimal.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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
** Bug watch added: Linux Kernel Bug Tracker #203405 https://bugzilla.kernel.org/show_bug.cgi?id=203405 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=203405 Importance: Unknown Status: Unknown -- 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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
Apparently this is (probably) fixed in kernels from 5.4.54 https://lore.kernel.org/linux-btrfs/8a3370fd-7cda- 78d2-b036-8350c5a3e...@gmx.com/T/#r52f03985dd7982c8f92c8a65089583f01c62020b so I hope it becomes available in Ubuntu soon. -- 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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
apparently fixed in kernel 5.4.56 https://lore.kernel.org/linux-btrfs/8a3370fd-7cda-78d2-b036-8350c5a3e...@gmx.com/T/#r52f03985dd7982c8f92c8a65089583f01c62020b Will it become available for Ubuntu? -- 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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount op
[Kernel-packages] [Bug 1890951] Re: btrfs not writable when mounted without "skip_balance"
** No longer affects: linux -- 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/1890951 Title: btrfs not writable when mounted without "skip_balance" Status in linux package in Ubuntu: Confirmed Bug description: Yesterday, I upgraded to Ubuntu 20.04, since when there is a problem with the btrfs volume it is installed on. The system hung when launching a btrfs balance and on next boot, it hung indefinitely, when trying to created the volatile files and dirs. Booting from a Debian buster rescue system, I noticed that I was unable to create or delete any files and I noticed the following in dmesg: [Sun Aug 9 12:21:35 2020] [ cut here ] [Sun Aug 9 12:21:35 2020] kernel BUG at fs/btrfs/relocation.c:2626! [Sun Aug 9 12:21:35 2020] invalid opcode: [#1] SMP PTI [Sun Aug 9 12:21:35 2020] CPU: 1 PID: 4537 Comm: btrfs-balance Tainted: G O 5.4.47 #1 [Sun Aug 9 12:21:35 2020] Hardware name: FUJITSU D3401-H1/D3401-H1, BIOS V5.0.0.11 R1.14.0 for D3401-H1x06/09/2016 [Sun Aug 9 12:21:35 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:35 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 [Sun Aug 9 12:21:35 2020] RSP: 0018:8887e0b0bb20 EFLAGS: 00010246 [Sun Aug 9 12:21:35 2020] RAX: 8887dfab5280 RBX: RCX: [Sun Aug 9 12:21:35 2020] RDX: 8887e0b0bb24 RSI: 8887e0b0bc10 RDI: 8887dfab52c0 [Sun Aug 9 12:21:35 2020] RBP: 8887dfab5280 R08: 8887dfab52c0 R09: a0491e7e [Sun Aug 9 12:21:35 2020] R10: 8887f4ba7e70 R11: 090ed158 R12: 8887dfab5280 [Sun Aug 9 12:21:35 2020] R13: 8887fd330800 R14: 8887e0b0bc10 R15: 8887e7fa66e8 [Sun Aug 9 12:21:35 2020] FS: () GS:0e24() knlGS: [Sun Aug 9 12:21:35 2020] CS: 0010 DS: ES: CR0: 80050033 [Sun Aug 9 12:21:35 2020] CR2: 55b4d5b7cfe0 CR3: 0200a004 CR4: 003606e0 [Sun Aug 9 12:21:35 2020] DR0: DR1: DR2: [Sun Aug 9 12:21:35 2020] DR3: DR6: fffe0ff0 DR7: 0400 [Sun Aug 9 12:21:35 2020] Call Trace: [Sun Aug 9 12:21:35 2020] do_relocation+0xb6/0x4c2 [btrfs] [Sun Aug 9 12:21:35 2020] ? calcu_metadata_size.isra.36.constprop.42+0x9e/0xc4 [btrfs] [Sun Aug 9 12:21:35 2020] ? do_raw_spin_lock+0x2f/0x5a [Sun Aug 9 12:21:35 2020] ? btrfs_block_rsv_refill+0x4b/0x8b [btrfs] [Sun Aug 9 12:21:35 2020] relocate_tree_blocks+0x301/0x427 [btrfs] [Sun Aug 9 12:21:35 2020] ? tree_insert+0x49/0x4e [btrfs] [Sun Aug 9 12:21:35 2020] ? add_tree_block.isra.38+0x11e/0x144 [btrfs] [Sun Aug 9 12:21:35 2020] relocate_block_group+0x279/0x49e [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_block_group+0x15e/0x23d [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_relocate_chunk+0x25/0x8c [btrfs] [Sun Aug 9 12:21:35 2020] btrfs_balance+0xaf0/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] ? btrfs_balance+0xd45/0xd45 [btrfs] [Sun Aug 9 12:21:35 2020] balance_kthread+0x32/0x46 [btrfs] [Sun Aug 9 12:21:35 2020] kthread+0xf5/0xfa [Sun Aug 9 12:21:35 2020] ? kthread_associate_blkcg+0x86/0x86 [Sun Aug 9 12:21:35 2020] ret_from_fork+0x3a/0x50 [Sun Aug 9 12:21:35 2020] Modules linked in: btrfs xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate raid6_pq libcrc32c sd_mod ipmi_devintf ipmi_msghandler sg x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crc32_pclmul crc32c_intel iTCO_wdt ghash_clmulni_intel aesni_intel crypto_simd psmouse ahci cryptd libahci i2c_i801 serio_raw glue_helper intel_pch_thermal evdev video thermal acpi_pad button fan jc42 ftsteutates nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 e1000e [Sun Aug 9 12:21:36 2020] ---[ end trace 442b443de6cecc6e ]--- [Sun Aug 9 12:21:36 2020] RIP: 0010:select_reloc_root+0x5b/0x19f [btrfs] [Sun Aug 9 12:21:36 2020] Code: c0 c7 44 24 04 00 00 00 00 e8 8b 9d 17 e1 48 89 df 4c 89 f6 48 8d 54 24 04 e8 9c e6 ff ff 48 8b 58 60 48 89 c5 48 85 db 75 02 <0f> 0b 48 8b 43 20 a8 02 75 02 0f 0b 48 83 bb df 01 00 00 f8 75 45 So this is obviously a btrfs bug that got introduced by the newer btrfs code in the newer kernel, although, booting an older kernel didn't fix it. Apparently something about the fs is messed up now and no balance can be run. The only temporary remedy I found was to add the skip_balance mount option to /etc/fstab, but of course, this is a crutch, and when you can't run balance, then the fs is bound to run out of space at some point. --- ProblemType: Bug A
[Kernel-packages] [Bug 1889669] Re: Focal update: v5.4.54 upstream stable release
So when is the package going to be available? Asking because with the
current kernel, btrfs balance fails and the updated one has the fix, see
https://lore.kernel.org/linux-btrfs/feffe90f-de6b-0f53-c54d-
0df135c49...@gmail.com/T/#t
--
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/1889669
Title:
Focal update: v5.4.54 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.54 upstream stable release
from git://git.kernel.org/
soc: qcom: rpmh: Dirt can only make you dirtier, not cleaner
gpio: arizona: handle pm_runtime_get_sync failure case
gpio: arizona: put pm_runtime in case of failure
pinctrl: amd: fix npins for uart0 in kerncz_groups
mac80211: allow rx of mesh eapol frames with default rx key
scsi: scsi_transport_spi: Fix function pointer check
xtensa: fix __sync_fetch_and_{and,or}_4 declarations
xtensa: update *pos in cpuinfo_op.next
scsi: mpt3sas: Fix unlock imbalance
drivers/net/wan/lapbether: Fixed the value of hard_header_len
ALSA: hda/hdmi: fix failures at PCM open on Intel ICL and later
net: sky2: initialize return of gm_phy_read
drm/nouveau/i2c/g94-: increase NV_PMGR_DP_AUXCTL_TRANSACTREQ timeout
scsi: mpt3sas: Fix error returns in BRM_status_show
scsi: dh: Add Fujitsu device to devinfo and dh lists
dm: use bio_uninit instead of bio_disassociate_blkg
drivers/firmware/psci: Fix memory leakage in alloc_init_cpu_groups()
fuse: fix weird page warning
irqdomain/treewide: Keep firmware node unconditionally allocated
ARM: dts: imx6qdl-gw551x: Do not use 'simple-audio-card,dai-link'
ARM: dts: imx6qdl-gw551x: fix audio SSI
dmabuf: use spinlock to access dmabuf->name
drm/amd/display: Check DMCU Exists Before Loading
SUNRPC reverting d03727b248d0 ("NFSv4 fix CLOSE not waiting for direct IO
compeletion")
btrfs: reloc: fix reloc root leak and NULL pointer dereference
btrfs: reloc: clear DEAD_RELOC_TREE bit for orphan roots to prevent runaway
balance
uprobes: Change handle_swbp() to send SIGTRAP with si_code=SI_KERNEL, to fix
GDB regression
ALSA: hda/realtek: Fixed ALC298 sound bug by adding quirk for Samsung
Notebook Pen S
ALSA: info: Drop WARN_ON() from buffer NULL sanity check
ASoC: rt5670: Correct RT5670_LDO_SEL_MASK
btrfs: fix double free on ulist after backref resolution failure
btrfs: fix mount failure caused by race with umount
btrfs: fix page leaks after failure to lock page for delalloc
bnxt_en: Fix race when modifying pause settings.
bnxt_en: Fix completion ring sizing with TPA enabled.
fpga: dfl: pci: reduce the scope of variable 'ret'
fpga: dfl: fix bug in port reset handshake
hippi: Fix a size used in a 'pci_free_consistent()' in an error handling path
vsock/virtio: annotate 'the_virtio_vsock' RCU pointer
ax88172a: fix ax88172a_unbind() failures
RDMA/mlx5: Use xa_lock_irq when access to SRQ table
ASoC: Intel: bytcht_es8316: Add missed put_device()
net: dp83640: fix SIOCSHWTSTAMP to update the struct with actual configuration
ieee802154: fix one possible memleak in adf7242_probe
drm: sun4i: hdmi: Fix inverted HPD result
net: smc91x: Fix possible memory leak in smc_drv_probe()
bonding: check error value of register_netdevice() immediately
mlxsw: destroy workqueue when trap_register in mlxsw_emad_init
ionic: use offset for ethtool regs data
ionic: fix up filter locks and debug msgs
net: ag71xx: add missed clk_disable_unprepare in error path of probe
net: hns3: fix error handling for desc filling
net: dsa: microchip: call phy_remove_link_mode during probe
netdevsim: fix unbalaced locking in nsim_create()
qed: suppress "don't support RoCE & iWARP" flooding on HW init
qed: suppress false-positives interrupt error messages on HW init
ipvs: fix the connection sync failed in some cases
net: ethernet: ave: Fix error returns in ave_init
Revert "PCI/PM: Assume ports without DLL Link Active train links in 100 ms"
nfsd4: fix NULL dereference in nfsd/clients display code
enetc: Remove the mdio bus on PF probe bailout
i2c: rcar: always clear ICSAR to avoid side effects
i2c: i2c-qcom-geni: Fix DMA transfer race
bonding: check return value of register_netdevice() in bond_newlink()
geneve: fix an uninitialized value in geneve_changelink()
serial: exar: Fix GPIO configuration for Sealevel cards based on XR1
[Kernel-packages] [Bug 1903483] Re: "Caps Lock is also a Ctrl" setting stops working when connecting an external keyboard
Can confirm. I also tried to manually invoke the setting: $ gsettings set org.gnome.desktop.input-sources xkb-options "['ctrl:nocaps']" Doesn't work, too. My current workaround is using setxkbmap directly: $ setxkbmap -option ctrl:nocaps -- 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/1903483 Title: "Caps Lock is also a Ctrl" setting stops working when connecting an external keyboard Status in linux package in Ubuntu: Confirmed Bug description: In Tweaks, I've set the "Caps Lock is also a Ctrl" setting. However, when I connect my external keyboard via USB, the setting stops taking effect. If I go to Tweaks, the setting still appears to be enabled, but I have to disable it and re-enable it to make it take effect again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mgummelt 2175 F pulseaudio /dev/snd/pcmC1D7p: mgummelt 2175 F...m pulseaudio /dev/snd/controlC0: mgummelt 2175 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 21:15:48 2020 HibernationDevice: RESUME=UUID=b92322bb-a24e-4286-8452-f6e2272a4fb3 InstallationDate: Installed on 2018-03-26 (959 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20ENCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=ab4a36d6-e419-424e-9f0d-3635cd2543b5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-07-09 (122 days ago) WifiSyslog: dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET86W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20ENCTO1WW dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752350] [NEW] Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen
Public bug reported: The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when booted as a dom0 under Xen. A similar bug was reported by someone else for archlinux (https://bugs.archlinux.org/task/57500). A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it fixes the problem for me. (https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7). Xen output: (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) (gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n Fri Oct 13 15:58:41 UTC 2017 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9 (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ec00 (usable) (XEN) 000f - 0010 (reserved) (XEN) 0010 - cb6cfc00 (usable) (XEN) cb6cfc00 - cb723c00 (ACPI NVS) (XEN) cb723c00 - cb725c00 (ACPI data) (XEN) cb725c00 - cc00 (reserved) (XEN) f800 - fc00 (reserved) (XEN) fec0 - fed00400 (reserved) (XEN) fed2 - feda (reserved) (XEN) fee0 - fef0 (reserved) (XEN) ffb0 - 0001 (reserved) (XEN) 0001 - 00013000 (usable) (XEN) New Xen image base address: 0xcb00 (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL ) (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K 15 ASL61) (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K 15 ASL61) (XEN) ACPI: DSDT FFDC89E4, 47BC (r1 DELLdt_ex 1000 INTL 20050624) (XEN) ACPI: FACS CB6CFC00, 0040 (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1 DELLst_ex 1000 INTL 20050624) (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K 15 ASL61) (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K 15 ASL61) (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K 15 ASL61) (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K 15 ASL61) (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K 15 ASL61) (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K 15 ASL61) (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K 15 ASL61) (XEN) System RAM: 4022MB (4118964kB) (XEN) Domain heap initialised (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2926.007 MHz processor. (XEN) Initing memory sharing. (XEN) Intel VT-d iommu 0 supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping not enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) :04:00.0: unknown type 4 (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Allocated console ring of 16 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB (XEN) Brought up 4 CPUs (XEN) Dom0 has maximum 600 PIRQs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00012000->00012400 (952940 pages to be allocated) (XEN) Init. ramdisk: 00012d251000->00012575 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 8100->82b69000 (XEN) Init. ramdisk: -> (XEN) Phys-Mach map: 0080->00800077c0d8 (XEN) Start info:82b69000->82b694b4 (XEN) Page tables: 82b6a000->82b85000 (XEN) Boot stack:82b85000->82b86000 (XEN) TOTAL: 8000->8300 (XEN) ENTRY ADDRESS: 826a3180 (XEN) Dom0 has maximum 4 VCPUs (XEN) setup :04:00.0 for d0 failed (-22) (XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs (XEN) ..done. (XEN) Initial low memory virq threshold set at 0x
[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen
I can not run apport-collect on the affected system, since the kernel crashes immediately. ** 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. https://bugs.launchpad.net/bugs/1752350 Title: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen Status in linux package in Ubuntu: Confirmed Bug description: The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when booted as a dom0 under Xen. A similar bug was reported by someone else for archlinux (https://bugs.archlinux.org/task/57500). A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it fixes the problem for me. (https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7). Xen output: (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) (gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n Fri Oct 13 15:58:41 UTC 2017 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9 (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ec00 (usable) (XEN) 000f - 0010 (reserved) (XEN) 0010 - cb6cfc00 (usable) (XEN) cb6cfc00 - cb723c00 (ACPI NVS) (XEN) cb723c00 - cb725c00 (ACPI data) (XEN) cb725c00 - cc00 (reserved) (XEN) f800 - fc00 (reserved) (XEN) fec0 - fed00400 (reserved) (XEN) fed2 - feda (reserved) (XEN) fee0 - fef0 (reserved) (XEN) ffb0 - 0001 (reserved) (XEN) 0001 - 00013000 (usable) (XEN) New Xen image base address: 0xcb00 (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL ) (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K 15 ASL61) (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K 15 ASL61) (XEN) ACPI: DSDT FFDC89E4, 47BC (r1 DELLdt_ex 1000 INTL 20050624) (XEN) ACPI: FACS CB6CFC00, 0040 (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1 DELLst_ex 1000 INTL 20050624) (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K 15 ASL61) (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K 15 ASL61) (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K 15 ASL61) (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K 15 ASL61) (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K 15 ASL61) (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K 15 ASL61) (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K 15 ASL61) (XEN) System RAM: 4022MB (4118964kB) (XEN) Domain heap initialised (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2926.007 MHz processor. (XEN) Initing memory sharing. (XEN) Intel VT-d iommu 0 supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping not enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) :04:00.0: unknown type 4 (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Allocated console ring of 16 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB (XEN) Brought up 4 CPUs (XEN) Dom0 has maximum 600 PIRQs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00012000->00012400 (952940 pages to be allocated) (XEN) Init. ramdisk: 00012d251000->00012575 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel:
[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen
I think I will find some time later today to try it out. -- 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/1752350 Title: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when booted as a dom0 under Xen. A similar bug was reported by someone else for archlinux (https://bugs.archlinux.org/task/57500). A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it fixes the problem for me. (https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7). Xen output: (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) (gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n Fri Oct 13 15:58:41 UTC 2017 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9 (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ec00 (usable) (XEN) 000f - 0010 (reserved) (XEN) 0010 - cb6cfc00 (usable) (XEN) cb6cfc00 - cb723c00 (ACPI NVS) (XEN) cb723c00 - cb725c00 (ACPI data) (XEN) cb725c00 - cc00 (reserved) (XEN) f800 - fc00 (reserved) (XEN) fec0 - fed00400 (reserved) (XEN) fed2 - feda (reserved) (XEN) fee0 - fef0 (reserved) (XEN) ffb0 - 0001 (reserved) (XEN) 0001 - 00013000 (usable) (XEN) New Xen image base address: 0xcb00 (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL ) (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K 15 ASL61) (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K 15 ASL61) (XEN) ACPI: DSDT FFDC89E4, 47BC (r1 DELLdt_ex 1000 INTL 20050624) (XEN) ACPI: FACS CB6CFC00, 0040 (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1 DELLst_ex 1000 INTL 20050624) (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K 15 ASL61) (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K 15 ASL61) (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K 15 ASL61) (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K 15 ASL61) (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K 15 ASL61) (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K 15 ASL61) (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K 15 ASL61) (XEN) System RAM: 4022MB (4118964kB) (XEN) Domain heap initialised (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2926.007 MHz processor. (XEN) Initing memory sharing. (XEN) Intel VT-d iommu 0 supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping not enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) :04:00.0: unknown type 4 (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Allocated console ring of 16 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - Extended Page Tables (EPT) (XEN) - Virtual-Processor Identifiers (VPID) (XEN) - Virtual NMI (XEN) - MSR direct-access bitmap (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB (XEN) Brought up 4 CPUs (XEN) Dom0 has maximum 600 PIRQs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x100 -> 0x2b69000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 00012000->00012400 (952940 pages to be allocated) (XEN) Init. ramdisk: 00012d251000->00012575 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: 8100->82b69000 (XEN) In
[Kernel-packages] [Bug 1752350] Re: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen
@jsalibury, the Kernel you provided does successfully boot on Xen. ... (XEN) Initial low memory virq threshold set at 0x4000 pages. (XEN) Std. Loglevel: Errors and warnings (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen) (XEN) Freed 460kB init memory mapping kernel into physical memory about to get started... [0.00] Linux version 4.15.0-10-generic (root@kathleen) (gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)) #11~lp1752350 SMP Mon Mar 5 08:26:15 UTC 2018 (Ubuntu 4.15.0-10.11~lp1752350-generic 4.15.3) [0.00] Command line: placeholder root=/dev/mapper/vg-xen--nfo--dom0 ro rootflags=data=journal console=hvc0 console=tty0 kgdboc=hvc0 early_printk=xen ignore_loglevel ... -- 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/1752350 Title: Bionic x86_64 Linux Kernel 4.15 fails to boot on Xen Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: The Linux Kernel 4.15 from bionic on x86_64 immediately crashes when booted as a dom0 under Xen. A similar bug was reported by someone else for archlinux (https://bugs.archlinux.org/task/57500). A patch exists for 4.16. I tried this patch on 4.15.0-10-generic, it fixes the problem for me. (https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git/patch/?id=4f277295e54c5b7340e48efea3fc5cc21a2872b7). Xen output: (XEN) Xen version 4.9.0 (Ubuntu 4.9.0-0ubuntu3) (stefan.ba...@canonical.com) (gcc (Ubuntu 7.2.0-8ubuntu2) 7.2.0) debug=n Fri Oct 13 15:58:41 UTC 2017 (XEN) Bootloader: GRUB 2.02~beta2-36ubuntu3.9 (XEN) Command line: placeholder com1=115200,8N1 console=com1,vga (XEN) Xen image load base address: 0 (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds (XEN) EDID info not retrieved because no DDC retrieval method detected (XEN) Disc information: (XEN) Found 1 MBR signatures (XEN) Found 1 EDD information structures (XEN) Xen-e820 RAM map: (XEN) - 0009ec00 (usable) (XEN) 000f - 0010 (reserved) (XEN) 0010 - cb6cfc00 (usable) (XEN) cb6cfc00 - cb723c00 (ACPI NVS) (XEN) cb723c00 - cb725c00 (ACPI data) (XEN) cb725c00 - cc00 (reserved) (XEN) f800 - fc00 (reserved) (XEN) fec0 - fed00400 (reserved) (XEN) fed2 - feda (reserved) (XEN) fee0 - fef0 (reserved) (XEN) ffb0 - 0001 (reserved) (XEN) 0001 - 00013000 (usable) (XEN) New Xen image base address: 0xcb00 (XEN) ACPI: RSDP 000FEC00, 0024 (r2 DELL ) (XEN) ACPI: XSDT 000FC7E7, 006C (r1 DELLB11K 15 ASL61) (XEN) ACPI: FACP 000FC8D7, 00F4 (r3 DELLB11K 15 ASL61) (XEN) ACPI: DSDT FFDC89E4, 47BC (r1 DELLdt_ex 1000 INTL 20050624) (XEN) ACPI: FACS CB6CFC00, 0040 (XEN) ACPI: SSDT FFDCD2C1, 00AC (r1 DELLst_ex 1000 INTL 20050624) (XEN) ACPI: APIC 000FC9CB, 0092 (r1 DELLB11K 15 ASL61) (XEN) ACPI: BOOT 000FCA5D, 0028 (r1 DELLB11K 15 ASL61) (XEN) ACPI: ASF! 000FCA85, 0096 (r32 DELLB11K 15 ASL61) (XEN) ACPI: MCFG 000FCB1B, 003E (r1 DELLB11K 15 ASL61) (XEN) ACPI: HPET 000FCB59, 0038 (r1 DELLB11K 15 ASL61) (XEN) ACPI: TCPA 000FCDB5, 0032 (r1 DELLB11K 15 ASL61) (XEN) ACPI: DMAR 000FCDE7, 0068 (r1 DELLB11K 15 ASL61) (XEN) System RAM: 4022MB (4118964kB) (XEN) Domain heap initialised (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec0, GSI 0-23 (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Platform timer is 14.318MHz HPET (XEN) Detected 2926.007 MHz processor. (XEN) Initing memory sharing. (XEN) Intel VT-d iommu 0 supported page sizes: 4kB. (XEN) Intel VT-d Snoop Control enabled. (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. (XEN) Intel VT-d Queued Invalidation enabled. (XEN) Intel VT-d Interrupt Remapping not enabled. (XEN) Intel VT-d Posted Interrupt not enabled. (XEN) Intel VT-d Shared EPT tables not enabled. (XEN) :04:00.0: unknown type 4 (XEN) I/O virtualisation enabled (XEN) - Dom0 mode: Relaxed (XEN) Interrupt remapping disabled (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) Allocated console ring of 16 KiB. (XEN) VMX: Supported advanced features: (XEN) - APIC MMIO access virtualisation (XEN) - APIC TPR shadow (XEN) - E
[Kernel-packages] [Bug 1742318] Re: USB-Storage Quirk for 174c:1356
Hi, I am facing a related bug. I am using an SSD enclosure utilizing the ASM1352R controller as well. This controller supports RAID-0, RAID-1 and other configurations with up to two SSDs, and I'm currently using it with only one SSD; the product advertises as ASM1352R-Safe in this configuration, which is also what it advertises as when in RAID-1. I am running Debian buster. The advertised product IDs and serial, etc. are all different for me. Nevertheless, the bug still remains, and the fix proposed by OP works. OP mentioned "With/without UAS the issue persisted". I suspect that OP might be confused and does not realize that the fix he proposes is responsible for the message "UAS is blacklisted for this device, using usb-storage instead"; the quirk he used disables UAS support from the kernel side. Nevertheless, fix OP proposes is not a universal fix. ASMedia, reputable hardware manufacturer that it is, manufactures multiple chips with different architectures and capabilities under the same vendorId:productId identifier. Blacklisting this identifier will blacklist all its controllers, which may not exactly be a bad thing as multiple other models have issues with UAS under Linux as well. Inspection of latest upstream source seems that it is not handled upstream, though I have not tried running it. I'd be happy to contribute however I can but I have my hands tied if you need more info: I'm running Debian buster, and I'm running the controller with only one SSD. Nevertheless, it seems to me that this is an upstream bug and not Ubuntu-kernel specific. -- 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/1742318 Title: USB-Storage Quirk for 174c:1356 Status in linux package in Ubuntu: Incomplete Bug description: A usb-storage quirk is needed for the Mediasonic ProRaid 2 Bay 2.5' SATA HDD / SSD Enclosure - USB 3.1 Gen-II Type-C (HUR6-SU31) for reliable use in Ubuntu/Kubuntu 14-17.10. Using quirk 'u' appears to have fixed disconnect issues during install and use. Linux Version: Ubuntu 4.13.0-16.19-generic 4.13.4 Device ID:174c:1356 ASMedia Technology Inc. usb 9-1: new SuperSpeed USB device number 2 using xhci_hcd usb 9-1: New USB device found, idVendor=174c, idProduct=1356 usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 usb 9-1: Product: ASM1352R-Fast usb 9-1: Manufacturer: ASMT usb 9-1: SerialNumber: 0001 usb 9-1: UAS is blacklisted for this device, using usb-storage instead Note: With/without UAS the issue persisted. I disabled UAS to prevent devices sleeping to eliminate that as a possibility. Symptoms: Before using the quirk, the enclosure would completely stop responding during an install attempt, and the usb host would eventually be disabled. The device's LEDs would continue to blink as if being accessed. Fix: I specified the quirk by appending "usb- storage.quirks=174c:1356:u" to the linux line in Grub. Hopefully others can verify this (if I'm not insane) and include a patch for this upstream in the Kernel. Note: For those who install to a device such as this, you may need to modify your installation before booting it, by creating a file "/etc/modprobe.d/asm1352r-usb-quirk.conf" with contents "options usb- storage quirks=0x174c:0x1356:u". I have seen others (through Google) issuing the same "u" quirk for several ASMedia devices...Perhaps their chipsets need this? This is my first bug report. If any more information is needed, please inform me. I'd like to thank a TJ- in Ubuntu's IRC for helping nail this down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time
I just ran into this with a cleanly installed 17.04. Figured it out myself, added "copy_exec /usr/sbin/cache_check" to /usr/share/initramfs- tools/hooks/lvm2 in order to fix it. Can we PLEASE get this bug -- which renders systems UNBOOTABLE after attaching a cache -- fixed, especially since there are good and reasonable patches available already (#12)? -- 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/1423796 Title: Unable to mount lvmcache root device at boot time Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: Confirmed Bug description: I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1575038] [NEW] Connecting docking station reboots computer
Public bug reported: When connecting a awake and running laptop to Dells docking station the desktop crashes and shows the disk encryption password login prompt: https://goo.gl/photos/9QEkQDkNPbT71wDD6 After entering the password all screens goes black and nothing happens. Trying to undock and then dock again after the above problem the console displays the follwing: https://goo.gl/photos/KLrtdCuTKa7sps298 Also posted a question with more details before the upgrade to 16.04 here https://answers.launchpad.net/ubuntu/+question/291536 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johannes 2499 F pulseaudio /dev/snd/controlC0: johannes 2499 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 10:14:15 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-13 (378 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Latitude E7450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=!Windows 2012 crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (3 days ago) dmi.bios.date: 03/29/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 06HN6G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/29/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Attachment added: "Screen after second docking when screen went black after encryption password" https://bugs.launchpad.net/bugs/1575038/+attachment/4647501/+files/20160426_101242.jpg -- 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/1575038 Title: Connecting docking station reboots computer Status in linux package in Ubuntu: Confirmed Bug description: When connecting a awake and running laptop to Dells docking station the desktop crashes and shows the disk encryption password login prompt: https://goo.gl/photos/9QEkQDkNPbT71wDD6 After entering the password all screens goes black and nothing happens. Trying to undock and then dock again after the above problem the console displays the follwing: https://goo.gl/photos/KLrtdCuTKa7sps298 Also posted a question with more details before the upgrade to 16.04 here https://answers.launchpad.net/ubuntu/+question/291536 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johannes 2499 F pulseaudio /dev/snd/controlC0: johannes 2499 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 10:14:15 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-13 (378 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Latitude E7450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=!Windows 2012 crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (3 days ago) dmi.bios.date: 03/29/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 06HN6G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/29/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1575038] Re: Connecting docking station reboots computer
** Tags added: kernel-fixed-upstream ** 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. https://bugs.launchpad.net/bugs/1575038 Title: Connecting docking station reboots computer Status in linux package in Ubuntu: Confirmed Bug description: When connecting a awake and running laptop to Dells docking station the desktop crashes and shows the disk encryption password login prompt: https://goo.gl/photos/9QEkQDkNPbT71wDD6 After entering the password all screens goes black and nothing happens. Trying to undock and then dock again after the above problem the console displays the follwing: https://goo.gl/photos/KLrtdCuTKa7sps298 Also posted a question with more details before the upgrade to 16.04 here https://answers.launchpad.net/ubuntu/+question/291536 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johannes 2499 F pulseaudio /dev/snd/controlC0: johannes 2499 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 10:14:15 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-13 (378 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Latitude E7450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=!Windows 2012 crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (3 days ago) dmi.bios.date: 03/29/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 06HN6G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/29/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1098985] Re: On adding modules kernel version is not checked
I have the same issue on a debian "jessie/sid" system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1098985 Title: On adding modules kernel version is not checked Status in “dkms” package in Ubuntu: New Bug description: I'm using Ubuntu 13.04 dev with dkms 2.2.0.3-1.1ubuntu2. If a module is added but it already exists with the same name and version but another kernel version dkms doesn't add the module. Here is an example output: root@ubuntu:~# dkms status nvidia-current-updates, 304.64, 3.7.0-7-generic, x86_64: installed virtualbox, 4.1.22, 3.7.0-7-generic, x86_64: installed virtualbox, 4.1.22, 3.8.0-0-generic, x86_64: installed root@ubuntu:~# dkms add -k 3.8.0-0-generic -m nvidia-current-updates -v 304.64 Error! DKMS tree already contains: nvidia-current-updates-304.64 You cannot add the same module/version combo more than once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1098985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 871983] Re: 1002:9593 [HP EliteBook 8730w] Radeon Mobility HD 3670 gets very hot, battery usage consequently low (45 minutes)
I have the same problem with elitebook 8470p also on Oneiric. Battery lasts at maximum 1 hour and temperature is inconveniently high. -- 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/871983 Title: 1002:9593 [HP EliteBook 8730w] Radeon Mobility HD 3670 gets very hot, battery usage consequently low (45 minutes) Status in “linux” package in Ubuntu: Incomplete Bug description: The laptop HP EliteBook 8730w gets very hot. The battery life is very short (45-50 minutes on Oneiric, 3-4 hours on Windows). $ sensors acpitz-virtual-0 Adapter: Virtual device temp1:+30.0°C (crit = +115.0°C) temp2:+53.0°C (crit = +105.0°C) temp3:+49.2°C (crit = +110.0°C) temp4:+60.0°C (crit = +110.0°C) temp5:+48.0°C (crit = +85.0°C) temp6:+16.0°C (crit = +105.0°C) coretemp-isa- Adapter: ISA adapter Core 0: +52.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +52.0°C (high = +105.0°C, crit = +105.0°C) radeon-pci-0100 Adapter: PCI adapter temp1:+70.0°C The temperature doesn't drop even when the laptop is completely idle. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xserver-xorg-video-radeon 1:6.14.99~git20110811.g93fc084-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,move,snap,compiztoolbox,place,gnomecompat,vpswitch,resize,ring,session,mousepoll,imgpng,unitymtgrabhandles,grid,regex,animation,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz Date: Mon Oct 10 21:56:52 2011 DistUpgraded: Log time: 2011-10-07 09:50:42.700723 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: vboxhost, 4.1.4, 2.6.38-11-generic, x86_64: installed vboxhost, 4.1.4, 3.0.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: ATI Technologies Inc Radeon Mobility HD 3670 [1002:9593] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30ec] MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlIdent: Socket 0: product info: "RICOH", "Bay8Controller", "", "" manfid: 0x, 0x function: 254 (unknown) PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-12-generic root=UUID=59ad8fb2-a45b-4f83-8bd1-b12499301514 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to oneiric on 2011-10-07 (3 days ago) dmi.bios.date: 01/26/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.11 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.23 dmi.chassis.asset.tag: CNU94039H1 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.11:bd01/26/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.11:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.11 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.ia32-libs: ia32-libs 20090808ubuntu25 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/871983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1337196] Re: 3.2.0-64 kernel version breaks usb3.0 port in asus k53sv
I have a similar problem. It first occurred with the kernel upgrade to 3.2.0-64 (I guess) and a Seagate USB 3.0 external HD. Now I bought a WD Passport ultra harddrive. Same issue: The WD Passport Ultra harddrive works without problems on a USB 2.0 port, yet when connected to an USB 3.0 port, dmesg shows the following error: [ 887.802679] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd [ 887.819755] scsi10 : usb-storage 4-1:1.0 [ 888.815996] scsi 10:0:0:0: Direct-Access WD My Passport 0820 1007 PQ: 0 ANSI: 6 [ 888.816292] scsi 10:0:0:1: Enclosure WD SES Device 1007 PQ: 0 ANSI: 6 [ 888.817656] sd 10:0:0:0: Attached scsi generic sg2 type 0 [ 888.817888] ses 10:0:0:1: Attached Enclosure device [ 888.817994] ses 10:0:0:1: Attached scsi generic sg3 type 13 [ 919.523155] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 919.536526] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e00 [ 919.536531] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e40 uname -a Linux jb-desktop 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lsusb -vvv [...] Bus 004 Device 002: ID 1058:0820 Western Digital Technologies, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x1058 Western Digital Technologies, Inc. idProduct 0x0820 bcdDevice 10.07 iManufacturer 1 iProduct2 iSerial 5 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 224mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 6 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 [...] Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice3.02 iManufacturer 3 iProduct2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 31 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0 ** Changed in: linux (Ubuntu) Status: I
[Kernel-packages] [Bug 1337196] Re: 3.2.0-64 kernel version breaks usb3.0 port in asus k53sv
Additional information: I experienced the problem on an Asus P8H67-M mainboard. -- 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/1337196 Title: 3.2.0-64 kernel version breaks usb3.0 port in asus k53sv Status in “linux” package in Ubuntu: Confirmed Bug description: release: Ubuntu 12.04.4 LTS Few weeks ago my system was updated to the new kernel version 3.2.0-64 and inmediately my 3.0usb port of my asus k53sv laptop breaks. I'm so sure that it is a bug of the kernel because if I restart my computer with the older kernel version(3.2.0-63) the port work's perfectly well. Anyway my system recognizes that the port exists and if I connect something to the port the command lususb recognizes it, but still not working. Recently I update my system to the 3.2.0-65 kernel version but the problem still there. This is my 3.0 usb controller: 04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller Thank you for your support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1351242] [NEW] Problems with USB 3.0 since 3.2.0-64 (at least) with Asus mainboard
Public bug reported: The problem first occurred with the kernel upgrade to 3.2.0-64 (I guess) and a Seagate USB 3.0 external HD. Before the kernel update, everything worked fine. I guess it is this bug: https://lists.debian.org/debian- kernel/2014/03/msg00153.html Mainboard is Asus P8H67-M. Now I bought a WD Passport ultra harddrive. Same issue: The WD Passport Ultra harddrive works without problems on a USB 2.0 port, yet when connected to an USB 3.0 port, dmesg shows the following error: [ 887.802679] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd [ 887.819755] scsi10 : usb-storage 4-1:1.0 [ 888.815996] scsi 10:0:0:0: Direct-Access WD My Passport 0820 1007 PQ: 0 ANSI: 6 [ 888.816292] scsi 10:0:0:1: Enclosure WD SES Device 1007 PQ: 0 ANSI: 6 [ 888.817656] sd 10:0:0:0: Attached scsi generic sg2 type 0 [ 888.817888] ses 10:0:0:1: Attached Enclosure device [ 888.817994] ses 10:0:0:1: Attached scsi generic sg3 type 13 [ 919.523155] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 919.536526] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e00 [ 919.536531] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e40 uname -a Linux jb-desktop 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lsusb -vvv [...] Bus 004 Device 002: ID 1058:0820 Western Digital Technologies, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x1058 Western Digital Technologies, Inc. idProduct 0x0820 bcdDevice 10.07 iManufacturer 1 iProduct 2 iSerial 5 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 224mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 6 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 [...] Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 3.02 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 31 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-67-generic 3.2.0-67.101 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbecker2921 F xfce4-volumed jbecker2988 F pulseaudio /dev/snd/controlC0: jbecker2921 f xfce4-volumed jbecker2988 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfb40 irq 22' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,10438436,00100302' Cont
[Kernel-packages] [Bug 1351242] Re: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64
Dear Christopher, thank you for your advice. I did as you suggested -- behaviour did not change at all (exactly the same symptoms). sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 3703 05/03/2013 Best regards, Johannes -- 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/1351242 Title: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64 Status in “linux” package in Ubuntu: Confirmed Bug description: The problem first occurred with the kernel upgrade to 3.2.0-64 (I guess) and a Seagate USB 3.0 external HD. Before the kernel update, everything worked fine. I guess it is this bug: https://lists.debian.org/debian- kernel/2014/03/msg00153.html Mainboard is Asus P8H67-M. Now I bought a WD Passport ultra harddrive. Same issue: The WD Passport Ultra harddrive works without problems on a USB 2.0 port, yet when connected to an USB 3.0 port, dmesg shows the following error: [ 887.802679] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd [ 887.819755] scsi10 : usb-storage 4-1:1.0 [ 888.815996] scsi 10:0:0:0: Direct-Access WD My Passport 0820 1007 PQ: 0 ANSI: 6 [ 888.816292] scsi 10:0:0:1: Enclosure WD SES Device 1007 PQ: 0 ANSI: 6 [ 888.817656] sd 10:0:0:0: Attached scsi generic sg2 type 0 [ 888.817888] ses 10:0:0:1: Attached Enclosure device [ 888.817994] ses 10:0:0:1: Attached scsi generic sg3 type 13 [ 919.523155] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 919.536526] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e00 [ 919.536531] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e40 uname -a Linux jb-desktop 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lsusb -vvv [...] Bus 004 Device 002: ID 1058:0820 Western Digital Technologies, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x1058 Western Digital Technologies, Inc. idProduct 0x0820 bcdDevice 10.07 iManufacturer 1 iProduct 2 iSerial 5 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 224mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 6 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 [...] Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 3.02 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 31 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package:
[Kernel-packages] [Bug 1351242] Re: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64
** 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. https://bugs.launchpad.net/bugs/1351242 Title: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64 Status in “linux” package in Ubuntu: Incomplete Bug description: The problem first occurred with the kernel upgrade to 3.2.0-64 (I guess) and a Seagate USB 3.0 external HD. Before the kernel update, everything worked fine. I guess it is this bug: https://lists.debian.org/debian- kernel/2014/03/msg00153.html Mainboard is Asus P8H67-M. Now I bought a WD Passport ultra harddrive. Same issue: The WD Passport Ultra harddrive works without problems on a USB 2.0 port, yet when connected to an USB 3.0 port, dmesg shows the following error: [ 887.802679] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd [ 887.819755] scsi10 : usb-storage 4-1:1.0 [ 888.815996] scsi 10:0:0:0: Direct-Access WD My Passport 0820 1007 PQ: 0 ANSI: 6 [ 888.816292] scsi 10:0:0:1: Enclosure WD SES Device 1007 PQ: 0 ANSI: 6 [ 888.817656] sd 10:0:0:0: Attached scsi generic sg2 type 0 [ 888.817888] ses 10:0:0:1: Attached Enclosure device [ 888.817994] ses 10:0:0:1: Attached scsi generic sg3 type 13 [ 919.523155] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 919.536526] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e00 [ 919.536531] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e40 uname -a Linux jb-desktop 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lsusb -vvv [...] Bus 004 Device 002: ID 1058:0820 Western Digital Technologies, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x1058 Western Digital Technologies, Inc. idProduct 0x0820 bcdDevice 10.07 iManufacturer 1 iProduct 2 iSerial 5 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 224mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 6 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 [...] Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 3.02 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 31 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-67-generic 3.2.0-67.101 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced
[Kernel-packages] [Bug 1351242] Re: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64
Seems to be fixed with uname -a Linux jb-desktop 3.16.0-031600rc7-generic #201407271635 SMP Sun Jul 27 20:36:48 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.16-rc7 ** 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. https://bugs.launchpad.net/bugs/1351242 Title: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64 Status in “linux” package in Ubuntu: Confirmed Bug description: The problem first occurred with the kernel upgrade to 3.2.0-64 (I guess) and a Seagate USB 3.0 external HD. Before the kernel update, everything worked fine. I guess it is this bug: https://lists.debian.org/debian- kernel/2014/03/msg00153.html Mainboard is Asus P8H67-M. Now I bought a WD Passport ultra harddrive. Same issue: The WD Passport Ultra harddrive works without problems on a USB 2.0 port, yet when connected to an USB 3.0 port, dmesg shows the following error: [ 887.802679] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd [ 887.819755] scsi10 : usb-storage 4-1:1.0 [ 888.815996] scsi 10:0:0:0: Direct-Access WD My Passport 0820 1007 PQ: 0 ANSI: 6 [ 888.816292] scsi 10:0:0:1: Enclosure WD SES Device 1007 PQ: 0 ANSI: 6 [ 888.817656] sd 10:0:0:0: Attached scsi generic sg2 type 0 [ 888.817888] ses 10:0:0:1: Attached Enclosure device [ 888.817994] ses 10:0:0:1: Attached scsi generic sg3 type 13 [ 919.523155] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 919.536526] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e00 [ 919.536531] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e40 uname -a Linux jb-desktop 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lsusb -vvv [...] Bus 004 Device 002: ID 1058:0820 Western Digital Technologies, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x1058 Western Digital Technologies, Inc. idProduct 0x0820 bcdDevice 10.07 iManufacturer 1 iProduct 2 iSerial 5 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 224mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 6 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 [...] Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 3.02 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 31 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0 ProblemType: Bug DistroRele
[Kernel-packages] [Bug 1351242] Re: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64
No problems with the Live CD: uname -a Linux ubuntu 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 01:59:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux cat /proc/version Linux version 3.16.0-6-generic (buildd@toyol) (gcc version 4.8.3 (Ubuntu 4.8.3-5ubuntu2) ) #11-Ubuntu SMP Mon Jul 28 01:59:56 UTC 2014 ** 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. https://bugs.launchpad.net/bugs/1351242 Title: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64 Status in “linux” package in Ubuntu: Confirmed Bug description: The problem first occurred with the kernel upgrade to 3.2.0-64 (I guess) and a Seagate USB 3.0 external HD. Before the kernel update, everything worked fine. I guess it is this bug: https://lists.debian.org/debian- kernel/2014/03/msg00153.html Mainboard is Asus P8H67-M. Now I bought a WD Passport ultra harddrive. Same issue: The WD Passport Ultra harddrive works without problems on a USB 2.0 port, yet when connected to an USB 3.0 port, dmesg shows the following error: [ 887.802679] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd [ 887.819755] scsi10 : usb-storage 4-1:1.0 [ 888.815996] scsi 10:0:0:0: Direct-Access WD My Passport 0820 1007 PQ: 0 ANSI: 6 [ 888.816292] scsi 10:0:0:1: Enclosure WD SES Device 1007 PQ: 0 ANSI: 6 [ 888.817656] sd 10:0:0:0: Attached scsi generic sg2 type 0 [ 888.817888] ses 10:0:0:1: Attached Enclosure device [ 888.817994] ses 10:0:0:1: Attached scsi generic sg3 type 13 [ 919.523155] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 919.536526] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e00 [ 919.536531] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e40 uname -a Linux jb-desktop 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lsusb -vvv [...] Bus 004 Device 002: ID 1058:0820 Western Digital Technologies, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x1058 Western Digital Technologies, Inc. idProduct 0x0820 bcdDevice 10.07 iManufacturer 1 iProduct 2 iSerial 5 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 224mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 6 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 [...] Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 3.02 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 31 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes
[Kernel-packages] [Bug 1351242] Re: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64
As far as I see it, there is currently no LTS version with working USB 3.0 for me (and several other people, I suppose). If the bug was introduced by a backport, I think it makes sense to backport the fix as well. ** 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. https://bugs.launchpad.net/bugs/1351242 Title: [Asus P8H67-M EVO] USB 3.0 problem since at least 3.2.0-64 Status in “linux” package in Ubuntu: Confirmed Bug description: The problem first occurred with the kernel upgrade to 3.2.0-64 (I guess) and a Seagate USB 3.0 external HD. Before the kernel update, everything worked fine. I guess it is this bug: https://lists.debian.org/debian- kernel/2014/03/msg00153.html Mainboard is Asus P8H67-M. Now I bought a WD Passport ultra harddrive. Same issue: The WD Passport Ultra harddrive works without problems on a USB 2.0 port, yet when connected to an USB 3.0 port, dmesg shows the following error: [ 887.802679] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd [ 887.819755] scsi10 : usb-storage 4-1:1.0 [ 888.815996] scsi 10:0:0:0: Direct-Access WD My Passport 0820 1007 PQ: 0 ANSI: 6 [ 888.816292] scsi 10:0:0:1: Enclosure WD SES Device 1007 PQ: 0 ANSI: 6 [ 888.817656] sd 10:0:0:0: Attached scsi generic sg2 type 0 [ 888.817888] ses 10:0:0:1: Attached Enclosure device [ 888.817994] ses 10:0:0:1: Attached scsi generic sg3 type 13 [ 919.523155] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 919.536526] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e00 [ 919.536531] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with disabled ep 880306f35e40 uname -a Linux jb-desktop 3.2.0-67-generic #101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lsusb -vvv [...] Bus 004 Device 002: ID 1058:0820 Western Digital Technologies, Inc. Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x1058 Western Digital Technologies, Inc. idProduct 0x0820 bcdDevice 10.07 iManufacturer 1 iProduct 2 iSerial 5 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 224mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 6 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 [...] Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 3.02 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 31 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0 ProblemType: Bug DistroRelease: Ubu
[Kernel-packages] [Bug 1575038] Re: Connecting docking station reboots computer
I have been working out of the office for some weeks now without access to the dock. Been back for a while now and some update since then have fixed the issue. Have been daily for a few days now connecting and disconnecting from dock and it has worked without any flaws. I can no longer reproduce the bug. -- 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/1575038 Title: Connecting docking station reboots computer Status in linux package in Ubuntu: Incomplete Bug description: When connecting a awake and running laptop to Dells docking station the desktop crashes and shows the disk encryption password login prompt: https://goo.gl/photos/9QEkQDkNPbT71wDD6 After entering the password all screens goes black and nothing happens. Trying to undock and then dock again after the above problem the console displays the follwing: https://goo.gl/photos/KLrtdCuTKa7sps298 Also posted a question with more details before the upgrade to 16.04 here https://answers.launchpad.net/ubuntu/+question/291536 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johannes 2499 F pulseaudio /dev/snd/controlC0: johannes 2499 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 10:14:15 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-13 (378 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Latitude E7450 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=!Windows 2012 crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-04-22 (3 days ago) dmi.bios.date: 03/29/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 06HN6G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/29/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
setting acpi_osi='' to grub worked for me. sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date UX32LN.202 02/24/2014 and uname -a Linux toretto 4.5.2-040502-generic #201604200335 SMP Wed Apr 20 07:37:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- 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/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1348890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
*setting in grub not to -- 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/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1348890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 578506] Re: [Acer Aspire 5930] ACPI: EC: input buffer is not empty, aborting transaction
Gabriele Bianchi, at least for me the bug is still persistant on Debian. $ uname -a Linux debian 3.11-2-amd64 #1 SMP Debian 3.11.10-1 (2013-1 2-04) x86_64 GNU/Linux -- 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/578506 Title: [Acer Aspire 5930] ACPI: EC: input buffer is not empty, aborting transaction Status in “linux” package in Ubuntu: Incomplete Bug description: On my notebook acer aspire 5930G on upgrade to 10.04 version, after few minutes of use apci stops working (don't recognize ac/dc or battery, don't change lcd blacklight, etc.) and start to flood dmes with this messages: [ 767.208058] ACPI: EC: input buffer is not empty, aborting transaction [ 767.208072] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20090903/evregion-424) [ 767.208106] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.GBST] (Node f7017030), AE_TIME [ 767.208197] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node f7017120), AE_TIME [ 767.208277] ACPI Exception: AE_TIME, Evaluating _BST (20090903/battery-393) Trying to reboot (or to shutdown and restart) my pc don't want to boot! WORKAROUND: Get out the battery and replace. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-headers-2.6.32-21-generic 2.6.32-21.32 Regression: Yes Reproducible: No ProcVersionSignature: Ubuntu 2.6.31-19.56-generic Uname: Linux 2.6.31-19-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.20. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 5325 F pulseaudio /dev/snd/pcmC0D0p: luca 5325 F...m pulseaudio CRDA: Error: [Errno 2] Nessun file o directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf650 irq 21' Mixer name : 'Nvidia MCP78 HDMI' Components : 'HDA:10ec0888,1025013f,00100202 HDA:11c11040,11c10001,00100200 HDA:10de0003,10de0101,0010' Controls : 39 Simple ctrls : 21 Date: Mon May 10 23:25:40 2010 Frequency: Once a day. HibernationDevice: RESUME=UUID=96cdf22d-d1a9-4285-818c-c7751f7b8bd4 MachineType: Acer Aspire 5930 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-19-generic root=UUID=eb29c17b-d483-46a9-853c-0236d0829819 ro quiet splash ProcEnviron: LANGUAGE=it_IT:it:en_GB:en LANG=it_IT.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34 SourcePackage: linux WpaSupplicantLog: dmi.bios.date: 08/01/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.19 dmi.board.name: Eiger dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/01/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5930 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/578506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Hi, I am experiencing this exact same bug on Manjaro with Kernels 6.0.x and 6.1.x. @Kai-Heng Feng, could you please provide the patch you used for `lp1988346-5` so I could test if this fixes in those kernels as well? Thanks for your work! -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]:
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Hi, also sorry, now for my delayed response. My `/sys/power/mem_sleep` says: s2idle [deep] So, if I read this correctly, this means s3 is selected, right? (Currently checking from a session in Kernel 5.15, as I was testing other things not being smooth with 6.1 for me. But I presume this would be the same for all installed Kernels, right?) -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target:
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Hi, sorry for this incredibly delayed response. I have been running on 6.2.x versions (on Manjaro still) since early February and with one minor version it was all working fine again with suspend and hibernate. Not sure if it is the same fix, but thanks a ton to look into this! -- 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. A
[Kernel-packages] [Bug 2047683] Re: Kernel build fails on debian/build/tools-perarch/tools/bpf/bpftool/vmlinux
Building 6.8.0-7 was possible. Building 6.8.0-9 fails - but I changed a few things: added LLVM=1 and removed it later on (then debain/rules clean 'ed), installed lib*-dev based on "Auto-detecting system features" output, KBUILD_BUILD_TIMESTAMP='2024-02-13' CC='ccache cc' -- 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/2047683 Title: Kernel build fails on debian/build/tools- perarch/tools/bpf/bpftool/vmlinux Status in linux package in Ubuntu: Confirmed Bug description: I've been attempting to build both the hwe-edge and lowlatency-hwe- next kernels from source. Both fail on bpftool not being present, though `debian/build/tools-perarch/tools/bpf/bpftool/vmlinux.h` is there. ``` make[1]: Leaving directory '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/perf' mv /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/vmlinux mv: cannot stat '/home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/build/tools-perarch/tools/bpf/bpftool/vmlinux': No such file or directory make: *** [debian/rules.d/2-binary-arch.mk:713: /home/ubuntu/build-linux/linux-hwe-6.5-6.5.0/debian/stamps/stamp-build-perarch] Error 1 ``` I've installed the related version of libbpf1 and libbpf-devel, but still seeing this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926032] Re: [i915] Screen "disconnects" when updating screen buffer
** Changed in: linux (Ubuntu) Status: Expired => New -- 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/1926032 Title: [i915] Screen "disconnects" when updating screen buffer Status in linux package in Ubuntu: New Bug description: I have a problem in which the screen will behave as if I pulled the HDMI or turned the computer off (no source) for a few seconds until the screen comes back on again. This happens a lot when I open a new window, moves the mouse after it has been still for a while or I open a new window or move the current window. I can watch a whole movie without this problem but as soon as I pause or touch the controls of VLC or move the mouse the problem reocurr. It seems to be after a certain idle period most of the time, but not always. Sometimes it happens many times in a row. The setup is my home built media PC with intel integrated graphics (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV receiver. I have tried probably every possible resolution and screen update frequency and the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 21:57:54 2021 DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) [1849:3e98] InstallationDate: Installed on 2020-12-01 (144 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago) dmi.bios.date: 05/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.10 dmi.board.name: H310CM-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926032] Re: [i915] Screen "disconnects" when updating screen buffer
This problem is persisting and today I noticed something I think might help pinpoint the problem. I was playing a slide show in shotwell when the screen went black again and when it came back on after a few seconds, the last picture displayed was stuck and the new pictures were displaying in a corner in a much smaller frame as if the system just tried to reset the resolution to something much smaller and then changed its mind and reverted (but shotwell didn't get the message and kept rendering to the small resolution rather than the wide one). Hope this helps to pinpoint the issue. ** Attachment added: "IMG_2026_111933.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926032/+attachment/5541181/+files/IMG_2026_111933.jpg -- 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/1926032 Title: [i915] Screen "disconnects" when updating screen buffer Status in linux package in Ubuntu: Confirmed Bug description: I have a problem in which the screen will behave as if I pulled the HDMI or turned the computer off (no source) for a few seconds until the screen comes back on again. This happens a lot when I open a new window, moves the mouse after it has been still for a while or I open a new window or move the current window. I can watch a whole movie without this problem but as soon as I pause or touch the controls of VLC or move the mouse the problem reocurr. It seems to be after a certain idle period most of the time, but not always. Sometimes it happens many times in a row. The setup is my home built media PC with intel integrated graphics (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV receiver. I have tried probably every possible resolution and screen update frequency and the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 21:57:54 2021 DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) [1849:3e98] InstallationDate: Installed on 2020-12-01 (144 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago) dmi.bios.date: 05/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.10 dmi.board.name: H310CM-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1970869] Re: [i915] random flashing, blinking screen
Likely similar to: https://bugs.launchpad.net/ubuntu/+bug/1970426 https://gitlab.freedesktop.org/drm/intel/-/issues/5569 https://gitlab.freedesktop.org/drm/intel/-/issues/5238 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #5569 https://gitlab.freedesktop.org/drm/intel/-/issues/5569 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #5238 https://gitlab.freedesktop.org/drm/intel/-/issues/5238 -- 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/1970869 Title: [i915] random flashing, blinking screen Status in linux package in Ubuntu: Incomplete Bug description: hello, after installing ubuntu 22.04 my screen flickers or flashes randomly under wayland or xorg. Under ubuntu 21.10 - no problem. thank you to consider. The proof in video : https://photos.app.goo.gl/ZqsKqyoZvCjXfTda8 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 07:57:06 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970426] Re: [i915] screen suddenly starts flickering after update
I did the following changes and am now flicker-free for two days: In file /etc/default/grub I added to parameter GRUB_CMDLINE_LINUX_DEFAULT: i915.enable_dc=0 intel_idle.max_cstate=2 then: sudo update-grub reboot My laptop is now usable but it cant be a permanent solution to disable energy saving features on a low-energy laptop. I will report in a week if this indeed fixes the flickering or if it just happens less often. -- 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/1970426 Title: [i915] screen suddenly starts flickering after update Status in linux package in Ubuntu: Confirmed Bug description: After I updated to 22.04 sometimes (about 3 ~ 4 times a day) the screen starts glitching and flickering like in the attached video and it doesn't stop until I move the cursor. Description: Ubuntu 22.04 LTS Release: 22.04 wayland processor: Intel® Core™ i5-8265U CPU @ 1.60GHz × 8 graphics: Mesa Intel® UHD Graphics 620 (WHL GT2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926032] Re: [i915] Screen "disconnects" when updating screen buffer
Most certainly not a problem with hdmi connection. I have had windows installed on the same machine without issues. The behavior is such that it is very clear that as soon as you move the mouse after a period of idle, the problem occurs. Also if the computer receives a notification after a period of idle it occurs. There is a definite link to activity which renders new information on the screen buffer. It can play a movie without a problem on vlc but when I pause, it disconnects the screen (presumably because the "pause" bars appear on the screen). If I right click to add subtitles or change something else in the video it also appears at the exact same time I click. This problem is very repeatable. I can do a phone quality video if that would be of interest. If it was a problem with hdmi it would be more random in behavior and it would be a problem on windows as well. -- 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/1926032 Title: [i915] Screen "disconnects" when updating screen buffer Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a problem in which the screen will behave as if I pulled the HDMI or turned the computer off (no source) for a few seconds until the screen comes back on again. This happens a lot when I open a new window, moves the mouse after it has been still for a while or I open a new window or move the current window. I can watch a whole movie without this problem but as soon as I pause or touch the controls of VLC or move the mouse the problem reocurr. It seems to be after a certain idle period most of the time, but not always. Sometimes it happens many times in a row. The setup is my home built media PC with intel integrated graphics (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV receiver. I have tried probably every possible resolution and screen update frequency and the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 21:57:54 2021 DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) [1849:3e98] InstallationDate: Installed on 2020-12-01 (144 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago) dmi.bios.date: 05/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.10 dmi.board.name: H310CM-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.l
[Kernel-packages] [Bug 2028999] Re: Slow download speed kubuntu 23.04 starting from kernel 6.2.0-25
installing r8168-dkms seems to better the result, but not completely solve it. Suggested here: https://askubuntu.com/q/1488178 Afterwards download is 920 mbit and upload 400 mbit, should be 980/980 mbit. -- 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/2028999 Title: Slow download speed kubuntu 23.04 starting from kernel 6.2.0-25 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading kernel to linux-image-6.2.0-25-generic (or -26), I experience slow download speed (20-30Mbps instead of the expected 500Mbps-1Gbps). This happens with firefox, chrome, chromium and wget. Upload speeds are ok. Downloads in LAN seems not to be affected. Only from the Internet (i.e.: speedtest.net with firefox/chrome/chromium or some big ISO files downloads). When booting with older kernel, i.e. 6.2.0-24, the problem disappear. My network card is a Realtek, see attached lspci output, and is using r8169 module. PC is a Dell Optiplex 3080 /proc/version_signature: Ubuntu 6.2.0-26.26-generic 6.2.13 lspci output is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031240] Re: Ethernet gradually disconnects/crashes after update to Kernel 6.2.0-26
Confirm that problem still persist with kernel 6.2.0-31-generic (Linux Mint) -- 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/2031240 Title: Ethernet gradually disconnects/crashes after update to Kernel 6.2.0-26 Status in linux package in Ubuntu: Confirmed Bug description: I received an Ubuntu update which included a new Kernel 6.2.0-26, after rebooting everything seemed ok, I launched qBittorrent as I normally have this application running on my laptop, and thought no more of it, about 15 minutes later I notice qBittorrent was no longer uploading, this seemed a bit strange so I opened Firefox to run a Google speed test, thereby checking my internet connection as well, but I had nothing no internet. I rebooted my Acer Aspire A515-55 laptop and followed the same procedure as before, and once again after some minutes I had no internet/network connection again. With my laptop using a wired connection I unplugged the ethernet cable and my internet was stable and worked fine using WiFi, I managed to carry out some Google searches and eventually discovered I'd received a new Kernel and this was likely to be the cause of this problem, so with some further research I was able to use Grub Customizer to revert back to the previous Kernel 5.19.0-50-generic, after doing so and plugging in the ethernet cable again launching qBittorrent everything worked as it should without dropping the network/internet. This is a consistently repeatable problem, which I responded to a thread on ubuntuforums.org to someone else having a similar problem after the Kernel update, and was asked to make a bug report. https://ubuntuforums.org/showthread.php?t=2489612 Without launching qBittorrent v4.5.4 (64 bit) my network/internet has remained connected, however if I resume my uploads then the internet/network does dropout again, only by reverting back to the previous Kernel can I carry on with a stable connection. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.17 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 664:1000:124:0:2023-08-12 12:39:59.254174367 +0100:2023-08-12 12:39:59.254174367 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_opera_opera.1000.upload 640:1000:124:69271379:2023-08-12 12:39:58.254174470 +0100:2023-08-12 12:39:59.254174470 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_opera_opera.1000.crash 600:117:124:37:2023-08-12 12:40:00.586204161 +0100:2023-08-12 12:40:00.586204161 +0100:/var/crash/_usr_lib_x86_64-linux-gnu_opera_opera.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Aug 13 14:08:19 2023 InstallationDate: Installed on 2023-05-26 (79 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22
Google Compute Engine seems to be affected as well for Ubuntu 20.04. Using kernel 5.13.0-1030-gcp #36~20.04.1-Ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1977919 Title: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22 Status in linux-aws package in Ubuntu: Confirmed Bug description: Running the attached script on the latest AWS AMI for Ubuntu 20.04, I get a kernel panic and hard reset of the node. [ 12.314552] VFS: Close: file count is 0 [ 12.351090] [ cut here ] [ 12.351093] kernel BUG at include/linux/fs.h:3104! [ 12.355272] invalid opcode: [#1] SMP PTI [ 12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws #31~20.04.1-Ubuntu [ 12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017 [ 12.371130] RIP: 0010:__fput+0x247/0x250 [ 12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.393425] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.398679] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.419533] FS: () GS:9153ea90() knlGS: [ 12.426937] CS: 0010 DS: ES: CR0: 80050033 [ 12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 007706e0 [ 12.436716] DR0: DR1: DR2: [ 12.441941] DR3: DR6: fffe0ff0 DR7: 0400 [ 12.447170] PKRU: 5554 [ 12.450355] Call Trace: [ 12.453408] [ 12.456296] fput+0xe/0x10 [ 12.459633] task_work_run+0x70/0xb0 [ 12.463157] do_exit+0x37b/0xaf0 [ 12.466570] do_group_exit+0x43/0xb0 [ 12.470142] __x64_sys_exit_group+0x18/0x20 [ 12.473989] do_syscall_64+0x61/0xb0 [ 12.477565] ? exit_to_user_mode_prepare+0x9b/0x1c0 [ 12.481734] ? do_user_addr_fault+0x1d0/0x650 [ 12.485665] ? irqentry_exit_to_user_mode+0x9/0x20 [ 12.489790] ? irqentry_exit+0x19/0x30 [ 12.493443] ? exc_page_fault+0x8f/0x170 [ 12.497199] ? asm_exc_page_fault+0x8/0x30 [ 12.501013] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 12.505289] RIP: 0033:0x7f80d42a1bd6 [ 12.508868] Code: Unable to access opcode bytes at RIP 0x7f80d42a1bac. [ 12.513783] RSP: 002b:7ffe924f9ed8 EFLAGS: 0246 ORIG_RAX: 00e7 [ 12.520897] RAX: ffda RBX: 7f80d45a4740 RCX: 7f80d42a1bd6 [ 12.526115] RDX: RSI: 003c RDI: [ 12.531328] RBP: R08: 00e7 R09: fe98 [ 12.536484] R10: 7f80d3d422a0 R11: 0246 R12: 7f80d45a4740 [ 12.541687] R13: 0002 R14: 7f80d45ad708 R15: [ 12.546916] [ 12.549829] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua crct10dif_pclmul ppdev crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd psmouse cryptd parport_pc input_leds parport ena serio_raw sch_fq_codel ipmi_devintf ipmi_msghandler msr drm ip_tables x_tables autofs4 [ 12.583913] ---[ end trace 77367fed4d782aa4 ]--- [ 12.587963] RIP: 0010:__fput+0x247/0x250 [ 12.591729] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48 [ 12.605796] RSP: 0018:b50280d9fd88 EFLAGS: 00010246 [ 12.610166] RAX: RBX: 000a801d RCX: 9152e0716000 [ 12.615417] RDX: 9152cf075280 RSI: 0001 RDI: [ 12.620635] RBP: b50280d9fdb0 R08: 0001 R09: 9152dfcba2c8 [ 12.625878] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 9152d04e9d00 [ 12.631121] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 9152dfc2e180 [ 12.636358] FS: () GS:9153ea90() knlGS: [ 12.643770] CS: 0010 DS: ES: CR0: 80050033 [ 12.648355] CR2: 556cf30250a8 CR3: 000
[Kernel-packages] [Bug 1680544] [NEW] Glitched grahpics around windows when waking from suspension
Public bug reported: The issue is not present when starting from a power-down. The graphical glitch can be reproduced on this machine by simple waking it from suspension. [version.log] Ubuntu 4.4.0-72.93-generic 4.4.49 [Release] Description:Ubuntu 16.04.2 LTS Release:16.04 [lspci-vnvn.log] 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ivb_uncore Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:84ca] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 4191 Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt+ SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet+ LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+ Addr: fed19000 Capabilities: [d94 v1] #19 Kernel driver in use: pcieport Kernel modules: shpchp 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] Control: I/O- Mem+ BusMaster+ SpecCycle
[Kernel-packages] [Bug 757074] Re: UVC video camera no longer works
I'm getting this same error now years later ...
* on my old Sony Vaio
* after upgrading from 16.04 to 17.04
dmesg shows:
[ 1181.128100] uvcvideo: Found UVC 1.00 device USB2.0 Camera (5986:02d3)
[ 1181.129834] uvcvideo: Failed to set UVC probe control : -32 (exp. 26).
[ 1181.130748] uvcvideo 1-1.3:1.0: Entity type for entity Extension 3 was not
initialized!
[ 1181.130752] uvcvideo 1-1.3:1.0: Entity type for entity Processing 2 was not
initialized!
[ 1181.130755] uvcvideo 1-1.3:1.0: Entity type for entity Camera 1 was not
initialized!
[ 1181.133085] input: USB2.0 Camera as
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input13
[ 1181.133281] usbcore: registered new interface driver uvcvideo
[ 1181.133282] USB Video Class driver (1.1.1)
after rmmodding and modprobing uvcvideo ...
no chance to get a v4l device in cheese, kamerka, ...
when trying to manually install the driver that fits most likely to my
sony vaio integrated webcam, it fails
sudo /usr/share/r5u87x/r5u87x-download-firmware.sh #(the final command
that installs the firmware - from the official ubuntu tutorial on
webcams for most sony vaio)
it fails saying
Error: Failed to find any supported webcams
ls -lisa /dev/video0
66245 0 crw-rw-rw-+ 1 root video 81, 0 Jun 15 21:04 /dev/video0
I'm part of the video group
Any ideas?
--
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/757074
Title:
UVC video camera no longer works
Status in linux package in Ubuntu:
Invalid
Bug description:
In Maverick, my webcam (Logitech QuickCam Deluxe for Notebooks) worked
flawlessly. Now, when I boot up Natty Beta, I get nothing in Cheese.
In gstreamer-properties, I get
gstreamer-properties-Message: Error running pipeline 'Video for Linux 2
(v4l2)': Device '/dev/video0' cannot capture at 8192x8192
[gstv4l2object.c(2093): gst_v4l2_object_set_format ():
/GstPipeline:pipeline0/GstV4l2Src:v4l2src1:
Call to S_FMT failed for YUYV @ 8192x8192: Input/output error]
Most importantly, dmesg gives this:
jeremy@Megatron-test:~$ dmesg | grep uvc
[ 18.169128] uvcvideo: Found UVC 1.00 device (046d:09c1)
[ 18.210483] usbcore: registered new interface driver uvcvideo
[ 42.076106] uvcvideo: Failed to query (131) UVC probe control : -32 (exp.
26).
[ 91.714758] uvcvideo: Failed to set UVC probe control : -32 (exp. 26).
[ 96.710109] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
[ 101.710123] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
[ 106.710123] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
[ 111.710124] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
[ 116.710134] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
[ 121.710133] uvcvideo: Failed to set UVC probe control : -110 (exp. 26).
Hope to see this fixed quickly. Thanks!
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.41
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: NVidia [HDA NVidia], device 0: ALC883 Analog [ALC883 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jeremy 1532 F pulseaudio
/dev/snd/controlC1: jeremy 1532 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfe028000 irq 20'
Mixer name : 'Realtek ALC883'
Components : 'HDA:10ec0883,147b1c2a,0012'
Controls : 28
Simple ctrls : 17
Card1.Amixer.info:
Card hw:1 'U0x46d0x9c1'/'USB Device 0x46d:0x9c1 at usb-:00:02.1-3.1,
high speed'
Mixer name : 'USB Mixer'
Components : 'USB046d:09c1'
Controls : 2
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
Capture channels: Mono
Limits: Capture 0 - 3072
Mono: Capture 0 [0%] [18.00dB] [on]
Date: Sun Apr 10 22:32:32 2011
HibernationDevice: RESUME=UUID=b65e9a95-d889-45f8-ae50-ba7c23be95f0
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110321)
IwConfig:
lono wireless extensions.
eth1 no wireless extensions.
MachineType: System Manufacturer System Product Name
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic
root=UUID=fc04b7d9-0c22-4a9c-b257-9de400a18f64 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-8-generic N/A
