[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

[Bogdan]

Hello.
Ubuntu just updated pulseaudio from official channels and now I have sound.
Just a thought for newbies Even though after update computer doe not 
require reboot, in order to have you sound initialized please reboot.
That's what i did and now works.
Thank you guys.

-- 
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/1875252

Title:
  Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 20.04 LTS, the only way of hearing audio is
  through headphones. The sound settings tab doesn't even show any other
  output option other than "Dummy output" . I have already checked other
  versions and everything works perfectly when I downgrade to Ubuntu
  19.10, so I think this is a version related bug. Just to reiterate my
  laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer
  window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have
  looked up solutions online for 2 days and none has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  george 1499 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 19:04:06 2020
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 3420
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 04XGDT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3420
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+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 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

[Bogdan]

@Rajasekharan N (rajasekharan)

The link you've posted to another bug 
https://bugs.launchpad.net/oem-priority/+bug/1869819 actually did the trick and 
helped me bring back my sound card.
It was the patch that @hugh chao released on his channel as seen in this link 
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819.

-- 
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/1875252

Title:
  Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 20.04 LTS, the only way of hearing audio is
  through headphones. The sound settings tab doesn't even show any other
  output option other than "Dummy output" . I have already checked other
  versions and everything works perfectly when I downgrade to Ubuntu
  19.10, so I think this is a version related bug. Just to reiterate my
  laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer
  window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have
  looked up solutions online for 2 days and none has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  george 1499 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 19:04:06 2020
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 3420
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 04XGDT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3420
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+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 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

[Bogdan]

@Rajasekharan N (rajasekharan)

Well to late.
My laptop already updated. 
Never got the chance to see what was the update about.
Just requested to restart.
I'll follow the bug you reported.

-- 
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/1875252

Title:
  Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 20.04 LTS, the only way of hearing audio is
  through headphones. The sound settings tab doesn't even show any other
  output option other than "Dummy output" . I have already checked other
  versions and everything works perfectly when I downgrade to Ubuntu
  19.10, so I think this is a version related bug. Just to reiterate my
  laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer
  window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have
  looked up solutions online for 2 days and none has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  george 1499 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 19:04:06 2020
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 3420
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 04XGDT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3420
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+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 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

[Bogdan]

@Rajasekharan N (rajasekharan) 
Don't worry. It's a good thing that each problem risen from linux will teach me 
more about it as I am a newbie :)
Thank you though for the heads up regarding the fix.
I'll be waiting for the official release.

-- 
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/1875252

Title:
  Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 20.04 LTS, the only way of hearing audio is
  through headphones. The sound settings tab doesn't even show any other
  output option other than "Dummy output" . I have already checked other
  versions and everything works perfectly when I downgrade to Ubuntu
  19.10, so I think this is a version related bug. Just to reiterate my
  laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer
  window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have
  looked up solutions online for 2 days and none has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  george 1499 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 19:04:06 2020
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 3420
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 04XGDT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3420
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+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 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

[Bogdan]

Hello!
As posted before on this tracking bug (probably the wrong place) 
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1864871, I have the 
same issue with an old Toshiba Satellite L450 laptop.
I ran the live Ubuntu 20.04 image and the sound was recognized and played well.
In Settings I could see the output Internal speakers.
Then I installed from within the live image Ubuntu and still have sound.
Back then the kernel was 5.4.0-28.32-generic 5.4.30.
I've updated Ubuntu last night and surprise. Now I only have Dummy output (no 
sound).
I've researched and tested a lot of tricks to make it play but with no luck.
Attached is the pulse audio log file as instructed by @Hui Wang (hui.wang) in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/comments/5.

The pacmd command result is:

Memory blocks currently allocated: 3, size: 67,6 KiB.
Memory blocks allocated during the whole lifetime: 34834, size: 203,7 KiB.
Memory blocks imported from other processes: 0, size: 0 B.
Memory blocks exported to other processes: 0, size: 0 B.
Total sample cache size: 0 B.
Default sample spec: s16le 2ch 44100Hz
Default channel map: front-left,front-right
Default sink name: auto_null
Default source name: auto_null.monitor
Memory blocks of type POOL: 3 allocated/34834 accumulated.
Memory blocks of type POOL_EXTERNAL: 0 allocated/0 accumulated.
Memory blocks of type APPENDED: 0 allocated/0 accumulated.
Memory blocks of type USER: 0 allocated/0 accumulated.
Memory blocks of type FIXED: 0 allocated/0 accumulated.
Memory blocks of type IMPORTED: 0 allocated/0 accumulated.
28 module(s) loaded.
index: 0
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the volume/mute 
state of devices"
module.version = "13.99.1"
index: 1
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore the 
volume/mute/device state of streams"
module.version = "13.99.1"
index: 2
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "Lennart Poettering"
module.description = "Automatically restore profile of cards"
module.version = "13.99.1"
index: 3
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "Lennart Poettering"
module.description = "Augment the property sets of streams with 
additional static information"
module.version = "13.99.1"
index: 4
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "David Henningsson"
module.description = "Switches ports and profiles when devices 
are plugged/unplugged"
module.version = "13.99.1"
index: 5
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "Michael Terry"
module.description = "When a sink/source is added, switch to it 
or conditionally switch to it"
module.version = "13.99.1"
index: 6
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "Lennart Poettering"
module.description = "Detect available audio hardware and load 
matching drivers"
module.version = "13.99.1"
index: 7
name: 
argument: 
used: 0
load once: no
properties:
module.author = "Lennart Poettering"
module.description = "ALSA Card"
module.version = "13.99.1"
index: 8
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "Frédéric Dalleau, Pali Rohár"
module.description = "Policy module to make using bluetooth 
devices out-of-the-box easier"
module.version = "13.99.1"
index: 9
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "João Paulo Rechi Vita"
module.description = "Detect available Bluetooth daemon and 
load the corresponding discovery module"
module.version = "13.99.1"
index: 10
name: 
argument: <>
used: -1
load once: yes
properties:
module.author = "João Paulo Rechi Vita"
module.description = "Detect available BlueZ 5 Bluetooth audio 
devices and load BlueZ 5 Bluetooth audio drivers"
module.version = "13.99.1"
index: 11
   

[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

[Bogdan]

@Hui Wang

...and my Alsa info

** Attachment added: "alsainfo"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+attachment/5365734/+files/alsainfo

-- 
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/1875252

Title:
  Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 20.04 LTS, the only way of hearing audio is
  through headphones. The sound settings tab doesn't even show any other
  output option other than "Dummy output" . I have already checked other
  versions and everything works perfectly when I downgrade to Ubuntu
  19.10, so I think this is a version related bug. Just to reiterate my
  laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer
  window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have
  looked up solutions online for 2 days and none has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  george 1499 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 19:04:06 2020
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 3420
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 04XGDT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3420
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+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 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

[Bogdan]

@Hui Wang

Here it is my pacmd list as well.

** Attachment added: "pacmd"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+attachment/5365733/+files/pacmd

-- 
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/1875252

Title:
  Ubuntu 20.04 LTS update causing no sound coming from built-in speakers

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 20.04 LTS, the only way of hearing audio is
  through headphones. The sound settings tab doesn't even show any other
  output option other than "Dummy output" . I have already checked other
  versions and everything works perfectly when I downgrade to Ubuntu
  19.10, so I think this is a version related bug. Just to reiterate my
  laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer
  window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have
  looked up solutions online for 2 days and none has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  george 1499 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 19:04:06 2020
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 3420
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 04XGDT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3420
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+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 1864871] Re: Failed to init Intel sound card in 20.04

[Bogdan]

@ Jeremie Tamburini (jeremie2)

Thks mate. It works perfectly.
Did exactly as you said and now my sound card is back on.

-- 
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/1864871

Title:
  Failed to init Intel sound card in 20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing current 20.04 release on ThinkBook 13s IML with Intel
  audio card there is no sound available because sound card not detected
  (only dummy output available in sound settings):

  $ alsamixer 
  cannot open mixer: No such file or directory

  $ lspci -nnk |grep -A2 audio
  lspci: Unable to load libkmod resources: error -12
  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:02c8]
Subsystem: Lenovo Device [17aa:3816]
Kernel driver in use: sof-audio-pci
  00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:02a3]
Subsystem: Lenovo Device [17aa:3819]

  $ pacmd list-cards 
  0 card(s) available.

  $ dmesg |grep sof
  [0.755398] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [0.755400] software IO TLB: mapped [mem 0x7d91d000-0x8191d000] (64MB)
  [2.142149] systemd[1]: Mounting Mount unit for software-boutique, 
revision 54...
  [2.333772] systemd[1]: Mounted Mount unit for software-boutique, revision 
54.
  [2.770307] sof-audio-pci :00:1f.3: warning: No matching ASoC machine 
driver found
  [2.770316] sof-audio-pci :00:1f.3: DSP detected with PCI 
class/subclass/prog-if 0x040100
  [2.770473] sof-audio-pci :00:1f.3: use msi interrupt mode
  [2.770696] sof-audio-pci :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [2.779359] sof-audio-pci :00:1f.3: hda codecs found, mask 5
  [2.779360] sof-audio-pci :00:1f.3: using HDA machine driver 
skl_hda_dsp_generic now
  [2.817051] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-cnl.ri failed with error -2
  [2.817054] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-cnl.ri failed err: -2
  [2.817057] sof-audio-pci :00:1f.3: error: failed to load DSP firmware 
-2
  [2.817058] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: 
-2

  I've found similar bug reported here:
  https://bugs.archlinux.org/task/64720

  As a workaround I've added `snd_hda_intel.dmic_detect=0` to boot
  options and after that sound card successfully detected and started
  working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Wed Feb 26 19:22:05 2020
  InstallationDate: Installed on 2020-02-25 (1 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200221)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:0c02 Elan Microelectronics Corp. ELAN:Fingerprint
   Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20RR
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=94f1e507-a44a-46a8-9163-548d27303afb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  SourcePackage: linux-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CQCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 13s-IML
  dmi.modalias: 
dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML:
  dmi.product.family: ThinkBook 13s-IML
  dmi.product.name: 20RR
  dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML
  dmi.product.version: Lenovo ThinkBook 13s-IML
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+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

[Kernel-packages] [Bug 1888135] [NEW] Ubuntu 20.04 server randomly crash on rpi 4

[BogDan]

Public bug reported:

I'm experience the same problem as these
https://askubuntu.com/questions/1231755/random-system-halt-crash-with-
ubuntu-20-04-on-raspberry-pi-4  https://askubuntu.com/questions/1235113
/hang-with-ubuntu-20-04-64-bit-on-raspberry-pi people describe.

When the system crashes it doesn't respond to ssh nor to ping.

The only thing I saw in logs is this:


Jul 19 13:40:02 kernel: [16676.063926] INFO: task journal-offline:885 blocked 
for more than 120 seconds.
Jul 19 13:40:02 kernel: [16676.071182]   Tainted: G C  E 
5.4.0-1013-raspi #13-Ubuntu
Jul 19 13:40:02 kernel: [16676.078082] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 19 13:40:02 kernel: [16676.086032] journal-offline D0   885  1 
0x0800
Jul 19 13:40:02 kernel: [16676.086038] Call trace:
Jul 19 13:40:02 kernel: [16676.086050]  __switch_to+0x104/0x170
Jul 19 13:40:02 kernel: [16676.086057]  __schedule+0x30c/0x7c0
Jul 19 13:40:02 kernel: [16676.086062]  schedule+0x3c/0xb8
Jul 19 13:40:02 kernel: [16676.086067]  jbd2_log_wait_commit+0xe4/0x188
Jul 19 13:40:02 kernel: [16676.086071]  jbd2_complete_transaction+0x94/0xe8
Jul 19 13:40:02 kernel: [16676.086076]  ext4_sync_file+0x35c/0x410
Jul 19 13:40:02 kernel: [16676.086081]  vfs_fsync_range+0x4c/0x88
Jul 19 13:40:02 kernel: [16676.086085]  do_fsync+0x48/0x88
Jul 19 13:40:02 kernel: [16676.086090]  __arm64_sys_fsync+0x24/0x38
Jul 19 13:40:02 kernel: [16676.086094]  el0_svc_common.constprop.0+0xe0/0x1e8
Jul 19 13:40:02 kernel: [16676.086098]  el0_svc_handler+0x34/0xa0
Jul 19 13:40:02 kernel: [16676.086102]  el0_svc+0x10/0x14
Jul 19 13:40:02 kernel: [16676.086117] INFO: task kworker/3:2:884 blocked for 
more than 120 seconds.
Jul 19 13:40:02 kernel: [16676.093009]   Tainted: G C  E 
5.4.0-1013-raspi #13-Ubuntu
Jul 19 13:40:02 kernel: [16676.099900] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 19 13:40:02 kernel: [16676.107849] kworker/3:2 D0   884  2 
0x0028
Jul 19 13:40:02 kernel: [16676.107871] Workqueue: events_freezable mmc_rescan
Jul 19 13:40:02 kernel: [16676.107875] Call trace:
Jul 19 13:40:02 kernel: [16676.107880]  __switch_to+0x104/0x170
Jul 19 13:40:02 kernel: [16676.107885]  __schedule+0x30c/0x7c0
Jul 19 13:40:02 kernel: [16676.107897]  schedule+0x3c/0xb8
Jul 19 13:40:02 kernel: [16676.107903]  __mmc_claim_host+0xe4/0x2f0
Jul 19 13:40:02 kernel: [16676.107907]  mmc_get_card+0x38/0x48
Jul 19 13:40:02 kernel: [16676.107911]  mmc_sd_detect+0x24/0x90
Jul 19 13:40:02 kernel: [16676.107916]  mmc_rescan+0x37c/0x3f0
Jul 19 13:40:02 kernel: [16676.107921]  process_one_work+0x1d0/0x430
Jul 19 13:40:02 kernel: [16676.107924]  worker_thread+0x54/0x4a0
Jul 19 13:40:02 kernel: [16676.107929]  kthread+0xfc/0x128
Jul 19 13:40:02 kernel: [16676.107934]  ret_from_fork+0x10/0x1c
Jul 19 13:42:03 kernel: [16796.897856] INFO: task kworker/3:2:884 blocked for 
more than 241 seconds.
Jul 19 13:42:03 kernel: [16796.904757]   Tainted: G C  E 
5.4.0-1013-raspi #13-Ubuntu
Jul 19 13:42:03 kernel: [16796.911655] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 19 13:42:03 kernel: [16796.919606] kworker/3:2 D0   884  2 
0x0028
Jul 19 13:42:03 kernel: [16796.919631] Workqueue: events_freezable mmc_rescan
Jul 19 13:42:03 kernel: [16796.919636] Call trace:
Jul 19 13:42:03 kernel: [16796.919642]  __switch_to+0x104/0x170
Jul 19 13:42:03 kernel: [16796.919649]  __schedule+0x30c/0x7c0
Jul 19 13:42:03 kernel: [16796.919653]  schedule+0x3c/0xb8
Jul 19 13:42:03 kernel: [16796.919658]  __mmc_claim_host+0xe4/0x2f0
Jul 19 13:42:03 kernel: [16796.919662]  mmc_get_card+0x38/0x48
Jul 19 13:42:03 kernel: [16796.919667]  mmc_sd_detect+0x24/0x90
Jul 19 13:42:03 kernel: [16796.919671]  mmc_rescan+0x37c/0x3f0
Jul 19 13:42:03 kernel: [16796.919676]  process_one_work+0x1d0/0x430
Jul 19 13:42:03 kernel: [16796.919679]  worker_thread+0x54/0x4a0
Jul 19 13:42:03 kernel: [16796.919684]  kthread+0xfc/0x128
Jul 19 13:42:03 kernel: [16796.919689]  ret_from_fork+0x10/0x1c
Jul 19 13:01:47 kernel: [0.00] Booting Linux on physical CPU 
0x00 [0x410fd083]
Jul 19 13:01:47 kernel: [0.00] Linux version 5.4.0-1013-raspi 
(buildd@bos02-arm64-078) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) 
#13-Ubuntu SMP Mon Jun 15 03:17:37 UTC 2020 (Ubuntu 5.4.0-1013.13-raspi 5.4.44)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-1013-raspi 5.4.0-1013.13
ProcVersionSignature: Ubuntu 5.4.0-1013.13-raspi 5.4.44
Uname: Linux 5.4.0-1013-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: arm64
CasperMD5CheckResult: skip
Date: Sun Jul 19 18:40:08 2020
ImageMediaBuild: 20200423.1
ProcEnviron:
 SHELL=/bin/bash
 LANG=C.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: linux-raspi
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-raspi (Ubuntu)
 Importance:

[Kernel-packages] [Bug 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

[Bogdan]

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1593621

Title:
  Kernel panic after migration between XenServer 6.5 hosts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Problem: after live migration from one XenServer 6.5 server to another
  XenServer 6.5 the Ubuntu VM crashes (see attached screenshot).

  Affected verions (at least):
  1. Ubuntu 14.04 (3.19.0-61-generic)
  2. Ubuntu 16.04 (4.4.0-24-generic)

  Not affected versions:
  1.Ubuntu 14.04 (3.19.0-49-generic)

  The issue is not dependent on installed XenServer updates.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 16 11:23 seq
   crw-rw 1 root audio 116, 33 Jun 16 11:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   69.046113] nf_conntrack version 0.5.0 (7868 buckets, 31472 
max)
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=250f9548-2a14-41c1-bc6e-63199d6e9236
  InstallationDate: Installed on 2016-02-02 (136 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=5a4cba3d-3be6-4a07-9c55-d5ea7b52585e ro ipv6.disable=1 net.ifnames=0 
biosdevname=0
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/11/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.4.1-xs125381
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.4.1-xs125381:bd05/11/2016:svnXen:pnHVMdomU:pvr4.4.1-xs125381:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.4.1-xs125381
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593621/+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 1593621] Re: Kernel panic after migration between XenServer 6.5 hosts

[Bogdan]

Hello all,

I have probably same issue (freeze on Xenserver 6.5 with timekeeper.c in
backtrace) when unsuspending 14.04 VMs with 3.19 kernels.

To determine latest stable kernel version I've tested following versions
of kernel package:


linux-image-3.19.0-56-generic - Unsuspend works, XenMotion - not tested
linux-image-3.19.0-58-generic - Unsuspend works, XenMotion - works
linux-image-3.19.0-59-generic - Unsuspend causes kernel panic with 
timekeeper.c, Xenmotion - kernel panic 
linux-image-3.19.0-61-generic - Unsuspend causes kernel panic with 
timekeeper.c, Xenmotion - kernel panic 

We have some Ubuntu systems in production with 3.19.0-61 and can't
maintain our hypervisors well because it is not possible neither move
Ubuntu VM out of server nor suspend for maintenance time.

Tested on two pairs of Xenserver systems:

pair#1 - updates up to XS65ESP1023
pair#2 - updates up to XS65ESP1026 and XS65ESP1028


Please, let me know if I can give more information of test some fix.

-- 
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/1593621

Title:
  Kernel panic after migration between XenServer 6.5 hosts

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Problem: after live migration from one XenServer 6.5 server to another
  XenServer 6.5 the Ubuntu VM crashes (see attached screenshot).

  Affected verions (at least):
  1. Ubuntu 14.04 (3.19.0-61-generic)
  2. Ubuntu 16.04 (4.4.0-24-generic)

  Not affected versions:
  1.Ubuntu 14.04 (3.19.0-49-generic)

  The issue is not dependent on installed XenServer updates.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 16 11:23 seq
   crw-rw 1 root audio 116, 33 Jun 16 11:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   69.046113] nf_conntrack version 0.5.0 (7868 buckets, 31472 
max)
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=250f9548-2a14-41c1-bc6e-63199d6e9236
  InstallationDate: Installed on 2016-02-02 (136 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Xen HVM domU
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=5a4cba3d-3be6-4a07-9c55-d5ea7b52585e ro ipv6.disable=1 net.ifnames=0 
biosdevname=0
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 05/11/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.4.1-xs125381
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.4.1-xs125381:bd05/11/2016:svnXen:pnHVMdomU:pvr4.4.1-xs125381:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.4.1-xs125381
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1593621/+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 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Bogdan Harjoc]

5.3.0-24 crashed after 2 regular work days.

-- 
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/1861294

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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

Re: [Kernel-packages] [Bug 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Bogdan Harjoc]

The optiplex-7060 I was testing on is in the office, I'm working from
home and can't test at the moment unfortunately.

On Tue, Mar 31, 2020 at 9:25 AM Kai-Heng Feng
 wrote:
>
> Can you please test 5.3.0-45.37?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1861294
>
> Title:
>   Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
>   intel gpu
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
>   Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
>   (Coffeelake 3x8 GT2).
>
>   I had chrome, slack and vmware-player running in Gnome. While doing
>   some git clone, screen+mouse+keyboard froze for 2 minutes after which
>   xorg and everything else recovered. I saw this in dmesg:
>
>   kernel: show_signal_msg: 2 callbacks suppressed
>   kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
> 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
>   kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 
> a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 
> 00 00 00 00 37 13 00 00 c6 05 c1 6d
>   kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
>   kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
>   kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
>   kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
>   kernel: nvme nvme0: 12/0/0 default/read/poll queues
>
>   While writing this bug report, the system froze again, and this time
>   it didn't recover. After a cold reset I didn't see any other
>   GpuWatchdog messages in journalctl.
>
>   Ubuntu applied a BIOS firmware update before the first freeze, so my
>   BIOS was updated as part of the cold reset I did. Not sure if this is
>   relevant to reproducing the freeze.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+subscriptions

-- 
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/1861294

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Bogdan Harjoc]

Issue still reproduces on 5.3.0-40. Currently trying
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.6/

-- 
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/1861294

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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 1861294] [NEW] Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Bogdan Harjoc]

Public bug reported:

Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630 (Coffeelake
3x8 GT2).

I had chrome, slack and vmware-player running in Gnome. While doing some
git clone, screen+mouse+keyboard froze for 2 minutes after which xorg
and everything else recovered. I saw this in dmesg:

kernel: show_signal_msg: 2 callbacks suppressed
kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 
9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 00 
00 37 13 00 00 c6 05 c1 6d 
kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
kernel: nvme nvme0: Abort status: 0x0
kernel: nvme nvme0: Abort status: 0x0
kernel: nvme nvme0: Abort status: 0x0
kernel: nvme nvme0: Abort status: 0x0
kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
kernel: nvme nvme0: 12/0/0 default/read/poll queues

While writing this bug report, the system froze again, and this time it
didn't recover. After a cold reset I didn't see any other GpuWatchdog
messages in journalctl.

Ubuntu applied a BIOS firmware update before the first freeze, so my
BIOS was updated as part of the cold reset I did. Not sure if this is
relevant to reproducing the freeze.

** Affects: intel-gpu-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1861294

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in intel-gpu-tools package in Ubuntu:
  New

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1861294/+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 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Bogdan Harjoc]

Issue occurred again after BIOS update, during make -j12. I also had
chrome and vmplayer running. Dmesg errors from journalctl:

kernel: pcieport :00:1b.0: AER: Multiple Corrected error received: 
:01:00.0
kernel: pcieport :00:1b.0: AER: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Transmitter ID)
kernel: pcieport :00:1b.0: AER:   device [8086:a340] error 
status/mask=1000/2000
kernel: pcieport :00:1b.0: AER:[12] Timeout   
kernel: nvme :01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data 
Link Layer, (Receiver ID)
kernel: nvme :01:00.0: AER:   device [1344:5410] error 
status/mask=0040/2000
kernel: nvme :01:00.0: AER:[ 6] BadTLP
kernel: nvme :01:00.0: AER:   Error of this Agent is reported first

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1861294

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in intel-gpu-tools package in Ubuntu:
  New

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1861294/+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 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Bogdan Harjoc]

Similar issue on Red Hat Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1616364

I added the boot cmdline options mentioned there, so far so good.

On Thu, Jan 30, 2020 at 2:10 PM Timo Aaltonen  wrote:
>
> I'd say your hardware is falling apart
>
> ** Package changed: intel-gpu-tools (Ubuntu) => ubuntu
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1861294
>
> Title:
>   Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
>   intel gpu
>
> Status in Ubuntu:
>   New
>
> Bug description:
>   Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
>   Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
>   (Coffeelake 3x8 GT2).
>
>   I had chrome, slack and vmware-player running in Gnome. While doing
>   some git clone, screen+mouse+keyboard froze for 2 minutes after which
>   xorg and everything else recovered. I saw this in dmesg:
>
>   kernel: show_signal_msg: 2 callbacks suppressed
>   kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
> 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
>   kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 
> a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 
> 00 00 00 00 37 13 00 00 c6 05 c1 6d
>   kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
>   kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
>   kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
>   kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
>   kernel: nvme nvme0: 12/0/0 default/read/poll queues
>
>   While writing this bug report, the system froze again, and this time
>   it didn't recover. After a cold reset I didn't see any other
>   GpuWatchdog messages in journalctl.
>
>   Ubuntu applied a BIOS firmware update before the first freeze, so my
>   BIOS was updated as part of the cold reset I did. Not sure if this is
>   relevant to reproducing the freeze.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1861294/+subscriptions


** Bug watch added: Red Hat Bugzilla #1616364
   https://bugzilla.redhat.com/show_bug.cgi?id=1616364

-- 
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/1861294

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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

Re: [Kernel-packages] [Bug 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Bogdan Harjoc]

I have intel graphics as described in the initial report. The machine
just crashed again while doing apt install, no nvme or any other
relevant errors in journalctl this time. I downgraded to
linux-image-5.0.0-23-generic and if it's stable I will update to
5.3.0-24 and report back.

On Thu, Jan 30, 2020 at 6:50 PM Timo Aaltonen  wrote:
>
> so you have radeon graphics?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1861294
>
> Title:
>   Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
>   intel gpu
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
>   Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
>   (Coffeelake 3x8 GT2).
>
>   I had chrome, slack and vmware-player running in Gnome. While doing
>   some git clone, screen+mouse+keyboard froze for 2 minutes after which
>   xorg and everything else recovered. I saw this in dmesg:
>
>   kernel: show_signal_msg: 2 callbacks suppressed
>   kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
> 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
>   kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 
> a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 
> 00 00 00 00 37 13 00 00 c6 05 c1 6d
>   kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
>   kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
>   kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
>   kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: Abort status: 0x0
>   kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
>   kernel: nvme nvme0: 12/0/0 default/read/poll queues
>
>   While writing this bug report, the system froze again, and this time
>   it didn't recover. After a cold reset I didn't see any other
>   GpuWatchdog messages in journalctl.
>
>   Ubuntu applied a BIOS firmware update before the first freeze, so my
>   BIOS was updated as part of the cold reset I did. Not sure if this is
>   relevant to reproducing the freeze.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+subscriptions

-- 
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/1861294

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Bogdan Harjoc]

No crashes in the last 4 days using 5.0.0-23-generic, will try with
5.3.0-24.

-- 
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/1861294

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[Bogdan Arabadzhi]

Another Teclast F7 user here.
Touchpad is not working for me at all on 18.04 daily.

Works fine on Windows 10 though. =\

-- 
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/1728244

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Bogdan Micu]

Dear Christian,
Can you please detail a little how/where you added the rootdelay parameter.
I am facing the same problem with a 4 drive raid1 on a HP MicroServer Gen8, on 
update from Ubuntu server 16.04 to 18.04 (kernel 4.4 to kernel 4.15).
I tried to add the parameter to /etc/default/grub in both 
GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX= with no success, and then 
update-grub, grub-install /dev/sda.
sda is 3tb hdd gpt
I tried to increase rootdelay up to 90 still no boot.
On boot i can confirm that the rootdelay is added to commandline if i try to 
edit the entry.
For now i am booting with old 4.4 kernel, but i dont't think this is ok in the 
long run.
Thanks in advance.

-- 
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/1752961

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Bogdan Micu]

68cc38ff33f38424d0456f9a1ecfec4683226a7e has 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/1752961

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1752961] Re: With kernel 4.13 btrfs scans for devices before all devices have been discovered

[Bogdan Micu]

Dear Christian,
Thank you for your reply.
I took another route which worked.
First i booted with kernel 4.4 normally.
I edited /usr/share/initramfs-tools/scripts/local-premount/btrfs by adding 
sleep=5 before "/bin/btrfs device scan" line, then i ran the following commands:
update-initramfs -u
update-grub
grub-install /dev/sda
and then rebooted and it works :)

I also removed the rootdelay=5 which i inserted previously and it still
works.

-- 
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/1752961

Title:
  With kernel 4.13 btrfs scans for devices before all devices have been
  discovered

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  See attached dmesg outputs for booting kernels 4.11.x (working) and
  4.13.x (not working).

  dmesg-4.11.0-14-good.txt shows the dmesg output when booting kernel 4.11.x.
  btrfs scans for devices after all 4 (sda, sdb, sdc, sdd) of the devices have 
been discovered by the kernel.  The btrfs RAID1 filesystem mounts, and 
everything is good.

  dmesg-4.13.0-36-fail.txt shows the dmesg output when booting kernel 4.13.x.
  btrfs scans for devices after only 2 (sda, sdb) of the devices have been 
discovered by the kernel.  The btrfs RAID1 filesystem fails to mount ("failed 
to read the system array: -5").  The remaining 2 devices (sdc, sdd) are 
discovered by the kernel immediately afterward.  At the end of the log, I run 
`btrfs device scan` and mount the filesystem manually.

  Hardware:
HP ProLiant MicroServer Gen8
4x WDC WD20EFRX
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: aplay: device_list:270: no soundcards found...
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  ArecordDevices: arecord: device_list:270: no soundcards found...
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-10-15 (933 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: HP ProLiant MicroServer Gen8
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d976ab07-8377-46dd-ac6c-f5f7312a8305 ro rootflags=subvol=@ 
rootdelay=10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Tags:  bionic apport-hook-error
  Uname: Linux 4.15.0-20-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: HP
  dmi.bios.version: J06
  dmi.chassis.type: 7
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrJ06:bd07/16/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant MicroServer Gen8
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752961/+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 1891773] Re: kcompactd0 and btrfs-transaction keep deadlocking with each other

[Bogdan Mart]

attch dmesg

** Attachment added: "dmesg.202010251058"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891773/+attachment/5426902/+files/dmesg.202010251058

-- 
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/1891773

Title:
  kcompactd0 and btrfs-transaction keep deadlocking with each other

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Example 1:
  [346911.187920] INFO: task kcompactd0:53 blocked for more than 120 seconds.
  [346911.187938]   Not tainted 4.15.0-112-generic #113-Ubuntu
  [346911.187951] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [346911.187968] kcompactd0  D053  2 0x8000
  [346911.187969] Call Trace:
  [346911.187973]  __schedule+0x24e/0x880
  [346911.187986]  ? btree_releasepage+0x42/0x50 [btrfs]
  [346911.187987]  schedule+0x2c/0x80
  [346911.187988]  io_schedule+0x16/0x40
  [346911.187989]  __lock_page+0xff/0x140
  [346911.187990]  ? page_cache_tree_insert+0xe0/0xe0
  [346911.187992]  migrate_pages+0x91f/0xb80
  [346911.187993]  ? __ClearPageMovable+0x10/0x10
  [346911.187994]  ? isolate_freepages_block+0x3b0/0x3b0
  [346911.187995]  compact_zone+0x681/0x950
  [346911.187995]  kcompactd_do_work+0xfe/0x2a0
  [346911.187996]  ? __switch_to_asm+0x35/0x70
  [346911.187997]  ? __switch_to_asm+0x41/0x70
  [346911.187998]  kcompactd+0x86/0x1c0
  [346911.187999]  ? kcompactd+0x86/0x1c0
  [346911.188001]  ? wait_woken+0x80/0x80
  [346911.188002]  kthread+0x121/0x140
  [346911.188003]  ? kcompactd_do_work+0x2a0/0x2a0
  [346911.188003]  ? kthread_create_worker_on_cpu+0x70/0x70
  [346911.188004]  ret_from_fork+0x35/0x40

  [346911.188015] INFO: task btrfs-transacti:858 blocked for more than 120 
seconds.
  [346911.188031]   Not tainted 4.15.0-112-generic #113-Ubuntu
  [346911.188043] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [346911.188060] btrfs-transacti D0   858  2 0x8000
  [346911.188061] Call Trace:
  [346911.188062]  __schedule+0x24e/0x880
  [346911.188063]  ? bit_wait+0x60/0x60
  [346911.188063]  schedule+0x2c/0x80
  [346911.188064]  io_schedule+0x16/0x40
  [346911.188065]  bit_wait_io+0x11/0x60
  [346911.188066]  __wait_on_bit+0x4c/0x90
  [346911.188066]  ? bit_wait+0x60/0x60
  [346911.188067]  out_of_line_wait_on_bit+0x90/0xb0
  [346911.188068]  ? bit_waitqueue+0x40/0x40
  [346911.188080]  lock_extent_buffer_for_io+0x100/0x2a0 [btrfs]
  [346911.188090]  btree_write_cache_pages+0x1b8/0x420 [btrfs]
  [346911.188092]  ? native_sched_clock_from_tsc+0x30/0x70
  [346911.188092]  ? update_load_avg+0x423/0x780
  [346911.188101]  btree_writepages+0x5d/0x70 [btrfs]
  [346911.188102]  do_writepages+0x4b/0xe0
  [346911.188102]  ? enqueue_task_fair+0xb6/0x300
  [346911.188111]  ? merge_state.part.47+0x44/0x130 [btrfs]
  [346911.188112]  __filemap_fdatawrite_range+0xcf/0x100
  [346911.188113]  ? __filemap_fdatawrite_range+0xcf/0x100
  [346911.188114]  filemap_fdatawrite_range+0x13/0x20
  [346911.188122]  btrfs_write_marked_extents+0x68/0x140 [btrfs]
  [346911.188129]  btrfs_write_and_wait_marked_extents.constprop.20+0x4f/0x90 
[btrfs]
  [346911.188136]  btrfs_commit_transaction+0x696/0x910 [btrfs]
  [346911.188143]  ? btrfs_commit_transaction+0x696/0x910 [btrfs]
  [346911.188144]  ? wait_woken+0x80/0x80
  [346911.188151]  transaction_kthread+0x18d/0x1b0 [btrfs]
  [346911.188152]  kthread+0x121/0x140
  [346911.188158]  ? btrfs_cleanup_transaction+0x570/0x570 [btrfs]
  [346911.188159]  ? kthread_create_worker_on_cpu+0x70/0x70
  [346911.188160]  ret_from_fork+0x35/0x40

  Example 2:
  2020-08-11T20:23:03.533+01:00  kernel: INFO: task kcompactd0:53 blocked 
for more than 120 seconds.
  2020-08-11T20:23:03.533+01:00  kernel:   Not tainted 
4.15.0-112-generic #113-Ubuntu
  2020-08-11T20:23:03.533+01:00  kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2020-08-11T20:23:03.533+01:00  kernel: kcompactd0  D053 
 2 0x8000
  2020-08-11T20:23:03.533+01:00  kernel: Call Trace:
  2020-08-11T20:23:03.533+01:00  kernel:  __schedule+0x24e/0x880
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
btree_releasepage+0x42/0x50 [btrfs]
  2020-08-11T20:23:03.533+01:00  kernel:  schedule+0x2c/0x80
  2020-08-11T20:23:03.533+01:00  kernel:  io_schedule+0x16/0x40
  2020-08-11T20:23:03.533+01:00  kernel:  __lock_page+0xff/0x140
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
page_cache_tree_insert+0xe0/0xe0
  2020-08-11T20:23:03.533+01:00  kernel:  migrate_pages+0x91f/0xb80
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
__ClearPageMovable+0x10/0x10
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
isolate_freepages_block+0x3b0/0x3b0
  2020-08-11T20:23:03.533+01:00  kernel:  compact_zone+0x681/0x950
  2020-08-11T20:23:03.533+01:00  kernel:  kcompactd_do_work+0xfe/0x2a0
  2020-08-11T20:23:03.533+01:00  kernel:  ? __switch_to_asm+0x35/0x70
  2020-08-11

[Kernel-packages] [Bug 1891773] Re: kcompactd0 and btrfs-transaction keep deadlocking with each other

[Bogdan Mart]

Have same issue:

[ 2538.464378] INFO: task kcompactd0:27 blocked for more than 120 seconds.
[ 2538.466729]   Not tainted 4.15.0-122-generic #124-Ubuntu
[ 2538.468652] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 2538.471451] kcompactd0  D027  2 0x8000
[ 2538.471453] Call Trace:
[ 2538.471462]  __schedule+0x24e/0x880
[ 2538.471464]  schedule+0x2c/0x80
[ 2538.471466]  io_schedule+0x16/0x40
[ 2538.471468]  __lock_page+0xff/0x140
[ 2538.471472]  ? page_cache_tree_insert+0xe0/0xe0
[ 2538.471476]  migrate_pages+0x91f/0xb80
[ 2538.471479]  ? __ClearPageMovable+0x10/0x10
[ 2538.471482]  ? isolate_freepages_block+0x3b0/0x3b0
[ 2538.471484]  compact_zone+0x681/0x950
[ 2538.471486]  kcompactd_do_work+0xfe/0x2a0
[ 2538.471489]  ? __switch_to_asm+0x35/0x70
[ 2538.471491]  ? __switch_to_asm+0x41/0x70
[ 2538.471494]  kcompactd+0x86/0x1c0
[ 2538.471495]  ? kcompactd+0x86/0x1c0
[ 2538.471499]  ? wait_woken+0x80/0x80
[ 2538.471502]  kthread+0x121/0x140
[ 2538.471504]  ? kcompactd_do_work+0x2a0/0x2a0
[ 2538.471506]  ? kthread_create_worker_on_cpu+0x70/0x70
[ 2538.471508]  ret_from_fork+0x35/0x40

Kernel: 4.15.120

few days before it was hanging inside btrfs:
[12688.280246] INFO: task btrfs-transacti:597 blocked for more than 120 seconds.
[12688.285589]   Not tainted 4.15.0-122-generic #124-Ubuntu
[12688.292217] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[12688.305038] btrfs-transacti D0   597  2 0x8000
[12688.305042] Call Trace:
[12688.305054]  __schedule+0x24e/0x880
[12688.305058]  ? bit_wait+0x60/0x60
[12688.305059]  schedule+0x2c/0x80
[12688.305061]  io_schedule+0x16/0x40
[12688.305063]  bit_wait_io+0x11/0x60
[12688.305065]  __wait_on_bit+0x4c/0x90
[12688.305067]  ? bit_wait+0x60/0x60
[12688.305068]  out_of_line_wait_on_bit+0x90/0xb0
[12688.305075]  ? bit_waitqueue+0x40/0x40
[12688.305116]  lock_extent_buffer_for_io+0x100/0x2a0 [btrfs]
[12688.305136]  btree_write_cache_pages+0x1b8/0x420 [btrfs]
[12688.305153]  btree_writepages+0x5d/0x70 [btrfs]
[12688.305156]  do_writepages+0x4b/0xe0
[12688.305174]  ? free_extent_state+0x48/0xc0 [btrfs]
[12688.305188]  ? merge_state.part.47+0x44/0x130 [btrfs]
[12688.305191]  __filemap_fdatawrite_range+0xcf/0x100
[12688.305193]  ? __filemap_fdatawrite_range+0xcf/0x100
[12688.305195]  filemap_fdatawrite_range+0x13/0x20
[12688.305211]  btrfs_write_marked_extents+0x68/0x140 [btrfs]
[12688.305226]  btrfs_write_and_wait_marked_extents.constprop.20+0x4f/0x90 
[btrfs]
[12688.305241]  btrfs_commit_transaction+0x696/0x910 [btrfs]
[12688.305255]  ? btrfs_commit_transaction+0x696/0x910 [btrfs]
[12688.305268]  ? start_transaction+0x191/0x430 [btrfs]
[12688.305283]  transaction_kthread+0x18d/0x1b0 [btrfs]
[12688.305286]  kthread+0x121/0x140
[12688.305300]  ? btrfs_cleanup_transaction+0x570/0x570 [btrfs]
[12688.305302]  ? kthread_create_worker_on_cpu+0x70/0x70
[12688.305305]  ret_from_fork+0x35/0x40
[12688.305320] INFO: task postgres:1121 blocked for more than 120 seconds.
[12688.311393]   Not tainted 4.15.0-122-generic #124-Ubuntu
[12688.314307] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[12688.326485] postgresD0  1121   1101 0x
[12688.326490] Call Trace:
[12688.326502]  __schedule+0x24e/0x880
[12688.326509]  ? lookup_fast+0xcc/0x320
[12688.326512]  schedule+0x2c/0x80
[12688.326516]  schedule_preempt_disabled+0xe/0x10
[12688.326518]  __mutex_lock.isra.5+0x276/0x4e0
[12688.326522]  ? find_get_pages_range_tag+0x151/0x270
[12688.326524]  __mutex_lock_slowpath+0x13/0x20
[12688.326526]  ? __mutex_lock_slowpath+0x13/0x20
[12688.326528]  mutex_lock+0x2f/0x40
[12688.326583]  btrfs_log_inode_parent+0x17a/0xa80 [btrfs]
[12688.326585]  ? __filemap_fdatawait_range+0x95/0x170
[12688.326587]  ? __filemap_fdatawrite_range+0x50/0x100
[12688.326606]  ? wait_current_trans+0x33/0x110 [btrfs]
[12688.326608]  ? _cond_resched+0x19/0x40
[12688.326623]  ? join_transaction+0x27/0x420 [btrfs]
[12688.326641]  btrfs_log_dentry_safe+0x60/0x80 [btrfs]
[12688.326659]  btrfs_sync_file+0x375/0x530 [btrfs]
[12688.326667]  vfs_fsync_range+0x51/0xb0
[12688.326670]  do_fsync+0x3d/0x70
[12688.326672]  SyS_fsync+0x10/0x20
[12688.326677]  do_syscall_64+0x73/0x130
[12688.326681]  entry_SYSCALL_64_after_hwframe+0x41/0xa6
[12688.326683] RIP: 0033:0x7f2f790e5af1
[12688.326684] RSP: 002b:7fffb2bbb6f8 EFLAGS: 0246 ORIG_RAX: 
004a
[12688.326686] RAX: ffda RBX: 564356da18f0 RCX: 7f2f790e5af1
[12688.326687] RDX: 7f2f6e9d26a0 RSI: 0a0e RDI: 0044
[12688.326688] RBP: 7fffb2bbb710 R08: 7fffb2bd2000 R09: 0c80c0ae158d
[12688.326689] R10: 7fffb2bbb700 R11: 0246 R12: 0a0e
[12688.326690] R13: 0008 R14: 564356d93db0 R15: 564356d83bb8
[19487.948941] SGI XFS with ACLs, security attributes, realtime, no debug 
enabled

can upload kernel dump. Workload was postgres. It repeasts ev

[Kernel-packages] [Bug 1891773] Re: kcompactd0 and btrfs-transaction keep deadlocking with each other

[Bogdan Mart]

I confirm that downgrading to 4.15.0-106 fixed the issue for me.

-- 
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/1891773

Title:
  kcompactd0 and btrfs-transaction keep deadlocking with each other

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Example 1:
  [346911.187920] INFO: task kcompactd0:53 blocked for more than 120 seconds.
  [346911.187938]   Not tainted 4.15.0-112-generic #113-Ubuntu
  [346911.187951] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [346911.187968] kcompactd0  D053  2 0x8000
  [346911.187969] Call Trace:
  [346911.187973]  __schedule+0x24e/0x880
  [346911.187986]  ? btree_releasepage+0x42/0x50 [btrfs]
  [346911.187987]  schedule+0x2c/0x80
  [346911.187988]  io_schedule+0x16/0x40
  [346911.187989]  __lock_page+0xff/0x140
  [346911.187990]  ? page_cache_tree_insert+0xe0/0xe0
  [346911.187992]  migrate_pages+0x91f/0xb80
  [346911.187993]  ? __ClearPageMovable+0x10/0x10
  [346911.187994]  ? isolate_freepages_block+0x3b0/0x3b0
  [346911.187995]  compact_zone+0x681/0x950
  [346911.187995]  kcompactd_do_work+0xfe/0x2a0
  [346911.187996]  ? __switch_to_asm+0x35/0x70
  [346911.187997]  ? __switch_to_asm+0x41/0x70
  [346911.187998]  kcompactd+0x86/0x1c0
  [346911.187999]  ? kcompactd+0x86/0x1c0
  [346911.188001]  ? wait_woken+0x80/0x80
  [346911.188002]  kthread+0x121/0x140
  [346911.188003]  ? kcompactd_do_work+0x2a0/0x2a0
  [346911.188003]  ? kthread_create_worker_on_cpu+0x70/0x70
  [346911.188004]  ret_from_fork+0x35/0x40

  [346911.188015] INFO: task btrfs-transacti:858 blocked for more than 120 
seconds.
  [346911.188031]   Not tainted 4.15.0-112-generic #113-Ubuntu
  [346911.188043] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [346911.188060] btrfs-transacti D0   858  2 0x8000
  [346911.188061] Call Trace:
  [346911.188062]  __schedule+0x24e/0x880
  [346911.188063]  ? bit_wait+0x60/0x60
  [346911.188063]  schedule+0x2c/0x80
  [346911.188064]  io_schedule+0x16/0x40
  [346911.188065]  bit_wait_io+0x11/0x60
  [346911.188066]  __wait_on_bit+0x4c/0x90
  [346911.188066]  ? bit_wait+0x60/0x60
  [346911.188067]  out_of_line_wait_on_bit+0x90/0xb0
  [346911.188068]  ? bit_waitqueue+0x40/0x40
  [346911.188080]  lock_extent_buffer_for_io+0x100/0x2a0 [btrfs]
  [346911.188090]  btree_write_cache_pages+0x1b8/0x420 [btrfs]
  [346911.188092]  ? native_sched_clock_from_tsc+0x30/0x70
  [346911.188092]  ? update_load_avg+0x423/0x780
  [346911.188101]  btree_writepages+0x5d/0x70 [btrfs]
  [346911.188102]  do_writepages+0x4b/0xe0
  [346911.188102]  ? enqueue_task_fair+0xb6/0x300
  [346911.188111]  ? merge_state.part.47+0x44/0x130 [btrfs]
  [346911.188112]  __filemap_fdatawrite_range+0xcf/0x100
  [346911.188113]  ? __filemap_fdatawrite_range+0xcf/0x100
  [346911.188114]  filemap_fdatawrite_range+0x13/0x20
  [346911.188122]  btrfs_write_marked_extents+0x68/0x140 [btrfs]
  [346911.188129]  btrfs_write_and_wait_marked_extents.constprop.20+0x4f/0x90 
[btrfs]
  [346911.188136]  btrfs_commit_transaction+0x696/0x910 [btrfs]
  [346911.188143]  ? btrfs_commit_transaction+0x696/0x910 [btrfs]
  [346911.188144]  ? wait_woken+0x80/0x80
  [346911.188151]  transaction_kthread+0x18d/0x1b0 [btrfs]
  [346911.188152]  kthread+0x121/0x140
  [346911.188158]  ? btrfs_cleanup_transaction+0x570/0x570 [btrfs]
  [346911.188159]  ? kthread_create_worker_on_cpu+0x70/0x70
  [346911.188160]  ret_from_fork+0x35/0x40

  Example 2:
  2020-08-11T20:23:03.533+01:00  kernel: INFO: task kcompactd0:53 blocked 
for more than 120 seconds.
  2020-08-11T20:23:03.533+01:00  kernel:   Not tainted 
4.15.0-112-generic #113-Ubuntu
  2020-08-11T20:23:03.533+01:00  kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2020-08-11T20:23:03.533+01:00  kernel: kcompactd0  D053 
 2 0x8000
  2020-08-11T20:23:03.533+01:00  kernel: Call Trace:
  2020-08-11T20:23:03.533+01:00  kernel:  __schedule+0x24e/0x880
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
btree_releasepage+0x42/0x50 [btrfs]
  2020-08-11T20:23:03.533+01:00  kernel:  schedule+0x2c/0x80
  2020-08-11T20:23:03.533+01:00  kernel:  io_schedule+0x16/0x40
  2020-08-11T20:23:03.533+01:00  kernel:  __lock_page+0xff/0x140
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
page_cache_tree_insert+0xe0/0xe0
  2020-08-11T20:23:03.533+01:00  kernel:  migrate_pages+0x91f/0xb80
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
__ClearPageMovable+0x10/0x10
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
isolate_freepages_block+0x3b0/0x3b0
  2020-08-11T20:23:03.533+01:00  kernel:  compact_zone+0x681/0x950
  2020-08-11T20:23:03.533+01:00  kernel:  kcompactd_do_work+0xfe/0x2a0
  2020-08-11T20:23:03.533+01:00  kernel:  ? __switch_to_asm+0x35/0x70
  2020-08-11T20:23:03.533+01:00  kernel:  ? __switch_to_asm+0x41/0x70
  2020-08-11T20:23:03.533+01:00  kernel:  ?

[Kernel-packages] [Bug 1891773] Re: kcompactd0 and btrfs-transaction keep deadlocking with each other

[Bogdan Mart]

** Also affects: postgresql-11 (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/1891773

Title:
  kcompactd0 and btrfs-transaction keep deadlocking with each other

Status in linux package in Ubuntu:
  Confirmed
Status in postgresql-11 package in Ubuntu:
  New

Bug description:
  Example 1:
  [346911.187920] INFO: task kcompactd0:53 blocked for more than 120 seconds.
  [346911.187938]   Not tainted 4.15.0-112-generic #113-Ubuntu
  [346911.187951] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [346911.187968] kcompactd0  D053  2 0x8000
  [346911.187969] Call Trace:
  [346911.187973]  __schedule+0x24e/0x880
  [346911.187986]  ? btree_releasepage+0x42/0x50 [btrfs]
  [346911.187987]  schedule+0x2c/0x80
  [346911.187988]  io_schedule+0x16/0x40
  [346911.187989]  __lock_page+0xff/0x140
  [346911.187990]  ? page_cache_tree_insert+0xe0/0xe0
  [346911.187992]  migrate_pages+0x91f/0xb80
  [346911.187993]  ? __ClearPageMovable+0x10/0x10
  [346911.187994]  ? isolate_freepages_block+0x3b0/0x3b0
  [346911.187995]  compact_zone+0x681/0x950
  [346911.187995]  kcompactd_do_work+0xfe/0x2a0
  [346911.187996]  ? __switch_to_asm+0x35/0x70
  [346911.187997]  ? __switch_to_asm+0x41/0x70
  [346911.187998]  kcompactd+0x86/0x1c0
  [346911.187999]  ? kcompactd+0x86/0x1c0
  [346911.188001]  ? wait_woken+0x80/0x80
  [346911.188002]  kthread+0x121/0x140
  [346911.188003]  ? kcompactd_do_work+0x2a0/0x2a0
  [346911.188003]  ? kthread_create_worker_on_cpu+0x70/0x70
  [346911.188004]  ret_from_fork+0x35/0x40

  [346911.188015] INFO: task btrfs-transacti:858 blocked for more than 120 
seconds.
  [346911.188031]   Not tainted 4.15.0-112-generic #113-Ubuntu
  [346911.188043] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [346911.188060] btrfs-transacti D0   858  2 0x8000
  [346911.188061] Call Trace:
  [346911.188062]  __schedule+0x24e/0x880
  [346911.188063]  ? bit_wait+0x60/0x60
  [346911.188063]  schedule+0x2c/0x80
  [346911.188064]  io_schedule+0x16/0x40
  [346911.188065]  bit_wait_io+0x11/0x60
  [346911.188066]  __wait_on_bit+0x4c/0x90
  [346911.188066]  ? bit_wait+0x60/0x60
  [346911.188067]  out_of_line_wait_on_bit+0x90/0xb0
  [346911.188068]  ? bit_waitqueue+0x40/0x40
  [346911.188080]  lock_extent_buffer_for_io+0x100/0x2a0 [btrfs]
  [346911.188090]  btree_write_cache_pages+0x1b8/0x420 [btrfs]
  [346911.188092]  ? native_sched_clock_from_tsc+0x30/0x70
  [346911.188092]  ? update_load_avg+0x423/0x780
  [346911.188101]  btree_writepages+0x5d/0x70 [btrfs]
  [346911.188102]  do_writepages+0x4b/0xe0
  [346911.188102]  ? enqueue_task_fair+0xb6/0x300
  [346911.188111]  ? merge_state.part.47+0x44/0x130 [btrfs]
  [346911.188112]  __filemap_fdatawrite_range+0xcf/0x100
  [346911.188113]  ? __filemap_fdatawrite_range+0xcf/0x100
  [346911.188114]  filemap_fdatawrite_range+0x13/0x20
  [346911.188122]  btrfs_write_marked_extents+0x68/0x140 [btrfs]
  [346911.188129]  btrfs_write_and_wait_marked_extents.constprop.20+0x4f/0x90 
[btrfs]
  [346911.188136]  btrfs_commit_transaction+0x696/0x910 [btrfs]
  [346911.188143]  ? btrfs_commit_transaction+0x696/0x910 [btrfs]
  [346911.188144]  ? wait_woken+0x80/0x80
  [346911.188151]  transaction_kthread+0x18d/0x1b0 [btrfs]
  [346911.188152]  kthread+0x121/0x140
  [346911.188158]  ? btrfs_cleanup_transaction+0x570/0x570 [btrfs]
  [346911.188159]  ? kthread_create_worker_on_cpu+0x70/0x70
  [346911.188160]  ret_from_fork+0x35/0x40

  Example 2:
  2020-08-11T20:23:03.533+01:00  kernel: INFO: task kcompactd0:53 blocked 
for more than 120 seconds.
  2020-08-11T20:23:03.533+01:00  kernel:   Not tainted 
4.15.0-112-generic #113-Ubuntu
  2020-08-11T20:23:03.533+01:00  kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2020-08-11T20:23:03.533+01:00  kernel: kcompactd0  D053 
 2 0x8000
  2020-08-11T20:23:03.533+01:00  kernel: Call Trace:
  2020-08-11T20:23:03.533+01:00  kernel:  __schedule+0x24e/0x880
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
btree_releasepage+0x42/0x50 [btrfs]
  2020-08-11T20:23:03.533+01:00  kernel:  schedule+0x2c/0x80
  2020-08-11T20:23:03.533+01:00  kernel:  io_schedule+0x16/0x40
  2020-08-11T20:23:03.533+01:00  kernel:  __lock_page+0xff/0x140
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
page_cache_tree_insert+0xe0/0xe0
  2020-08-11T20:23:03.533+01:00  kernel:  migrate_pages+0x91f/0xb80
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
__ClearPageMovable+0x10/0x10
  2020-08-11T20:23:03.533+01:00  kernel:  ? 
isolate_freepages_block+0x3b0/0x3b0
  2020-08-11T20:23:03.533+01:00  kernel:  compact_zone+0x681/0x950
  2020-08-11T20:23:03.533+01:00  kernel:  kcompactd_do_work+0xfe/0x2a0
  2020-08-11T20:23:03.533+01:00  kernel:  ? __switch_to_asm+0x35/0x70
  2020-08-11T20:23:03.533+01:00  kernel:  ? _

[Kernel-packages] [Bug 1303574] [NEW] ...

[Bogdan Arabadzhi]

Public bug reported:

...

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-23-generic 3.13.0-23.45
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
Annotation: This occured during a previous hibernate and prevented it from 
resuming properly.
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bogdan 1835 F pulseaudio
 /dev/snd/controlC0:  bogdan 1835 F pulseaudio
CRDA:
 country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
Date: Mon Apr  7 07:27:02 2014
ExecutablePath: /usr/share/apport/apportcheckresume
InstallationDate: Installed on 2014-03-16 (21 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140315)
InterpreterPath: /usr/bin/python3.4
MachineType: Acer Aspire V5-573G
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed 
root=UUID=56986803-23c9-4d3a-ab19-f799d378306c ro elevator=noop
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-23-generic N/A
 linux-backports-modules-3.13.0-23-generic  N/A
 linux-firmware 1.127
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 10/22/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.24
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Dazzle_HW
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.24:bd10/22/2013:svnAcer:pnAspireV5-573G:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V5-573G
dmi.product.version: TBD by OEM
dmi.sys.vendor: Acer

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-kerneloops trusty

-- 
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/1303574

Title:
  ...

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  ...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-23-generic 3.13.0-23.45
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  Annotation: This occured during a previous hibernate and prevented it from 
resuming properly.
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bogdan 1835 F pulseaudio
   /dev/snd/controlC0:  bogdan 1835 F pulseaudio
  CRDA:
   country RU:
(2402 - 2482 @ 40), (N/A, 20)
(5735 - 5835 @ 20), (N/A, 30)
  Date: Mon Apr  7 07:27:02 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  InstallationDate: Installed on 2014-03-16 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140315)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Acer Aspire V5-573G
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic.efi.signed 
root=UUID=56986803-23c9-4d3a-ab19-f799d378306c ro elevator=noop
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-23-generic N/A
   linux-backports-modules-3.13.0-23-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/22/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Dazzle_HW
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.24:bd10/22/2013:svnAcer:pnAspireV5-573G:pvrTBDbyOEM:rvnAcer:rnDazzle_HW:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V5-573G
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1303574/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe 

[Kernel-packages] [Bug 1445222] Re: external keyboard doesn't work

[Bogdan Stefan]

Joseph,

thank you for your reply.

I tried rebooting by completely shutting down the power before
submitting the bug and it still persisted, however, a day later I just
plugged out the wireless receiver of the keyboard & mouse and plugged it
into another USB port and now it works fine.

[83657.244102] usb 5-1: USB disconnect, device number 4
[83659.784037] usb 7-1: new low-speed USB device number 2 using uhci_hcd
[83659.996053] usb 7-1: New USB device found, idVendor=040b, idProduct=2014
[83659.996058] usb 7-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[83659.996061] usb 7-1: Product: 2.4GHz keyboard and mouse
[83660.014593] input: 2.4GHz keyboard and mouse as 
/devices/pci:00/:00:1d.2/usb7/7-1/7-1:1.0/input/input22
[83660.014721] hid-generic 0003:040B:2014.0007: input,hidraw0: USB HID v1.10 
Keyboard [2.4GHz keyboard and mouse] on usb-:00:1d.2-1/input0
[83660.048199] input: 2.4GHz keyboard and mouse as 
/devices/pci:00/:00:1d.2/usb7/7-1/7-1:1.1/input/input23
[83660.048399] hid-generic 0003:040B:2014.0008: input,hiddev0,hidraw1: USB HID 
v1.10 Mouse [2.4GHz keyboard and mouse] on usb-:00:1d.2-1/input1

It seems I have a hardware problem with that USB port, so sorry for
taking up your time. I got mislead by this post:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/990870

I'll check the USB connector on my motherboard and see if the problem
persists but this bug can be closed.

Sorry again for wasting your time :(

Regards,
Bogdan

-- 
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/1445222

Title:
  external keyboard doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the software on my machine to the last version, the external 
keyboard stopped working.
  I tried with two keyboards - one didn't work at all and on the other only the 
letters worked.
  Both keyboards work on another computer.

  I listed the tail of /var/log/apt/history.log so you can see which
  packages were last updated before I had this issue:

  Start-Date: 2015-04-15  14:24:44
  Upgrade: python3-problem-report:amd64 (2.14.1-0ubuntu3.8, 2.14.1-0ubuntu3.9), 
py
  thon-urllib3:amd64 (1.7.1-1ubuntu0.1, 1.7.1-1ubuntu3), python3-chardet:amd64 
(2.
  0.1-1, 2.2.1-2~ubuntu1), libgnome-desktop-3-7:amd64 (3.8.4-0ubuntu3, 
3.8.4-0ubun
  tu3.1), flashplugin-installer:amd64 (11.2.202.451ubuntu0.14.04.1, 
11.2.202.457ub
  untu0.14.04.1), gnome-desktop3-data:amd64 (3.8.4-0ubuntu3, 3.8.4-0ubuntu3.1), 
ap
  port-gtk:amd64 (2.14.1-0ubuntu3.8, 2.14.1-0ubuntu3.9), apport:amd64 
(2.14.1-0ubu
  ntu3.8, 2.14.1-0ubuntu3.9), python3-apport:amd64 (2.14.1-0ubuntu3.8, 
2.14.1-0ubu
  ntu3.9)
  End-Date: 2015-04-15  14:25:48

  Start-Date: 2015-04-16  18:58:23
  Upgrade: isc-dhcp-common:amd64 (4.2.4-7ubuntu12, 4.2.4-7ubuntu12.1), 
gstreamer0.
  10-plugins-bad:amd64 (0.10.23-7.2ubuntu1, 0.10.23-7.2ubuntu1.1), patch:amd64 
(2.
  7.1-4ubuntu1, 2.7.1-4ubuntu2), isc-dhcp-client:amd64 (4.2.4-7ubuntu12, 
4.2.4-7ub
  untu12.1), libgstreamer-plugins-bad0.10-0:amd64 (0.10.23-7.2ubuntu1, 
0.10.23-7.2ubuntu1.1)
  End-Date: 2015-04-16  18:58:43

  Start-Date: 2015-04-16  22:46:54
  Commandline: aptdaemon role='role-commit-packages' sender=':1.59'
  Upgrade: python3-problem-report:amd64 (2.14.1-0ubuntu3.9, 
2.14.1-0ubuntu3.10), apport-gtk:amd64 (2.14.1-0ubuntu3.9, 2.14.1-0ubuntu3.10), 
apport:amd64 (2.14.1-0ubuntu3.9, 2.14.1-0ubuntu3.10), python3-apport:amd64 
(2.14.1-0ubuntu3.9, 2.14.1-0ubuntu3.10)
  End-Date: 2015-04-16  22:47:42

  Start-Date: 2015-04-17  00:16:31
  Commandline: apt-get install python-apport
  Install: python-keyring:amd64 (3.5-1, automatic), python-apport:amd64 
(2.14.1-0ubuntu3.10), python-oauth:amd64 (1.0.1-3build2, automatic), 
python-wadllib:amd64 (1.3.2-2build1, automatic), python-problem-report:amd64 
(2.14.1-0ubuntu3.10, automatic), python-secretstorage:amd64 (2.0.0-1ubuntu1.1, 
automatic), libjs-jquery:amd64 (1.7.2+dfsg-2ubuntu1, automatic), 
python-simplejson:amd64 (3.3.1-1ubuntu6, automatic), python-lazr.uri:amd64 
(1.0.3-1build1, automatic), python-launchpadlib:amd64 (1.10.2+ds-2, automatic), 
python-lazr.restfulclient:amd64 (0.13.3-1build1, automatic)
  End-Date: 2015-04-17  00:16:47

  Please let me know if you need any other details.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.11
  ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  CurrentDesktop: MATE
  CustomUdevRuleFiles: 81-canonij_prn.rules 80-canon_mfp.rules
  Date: Fri Apr 17 00:21:52 2015
  InstallationDate: Installed on 2015-03-14 (33 days ago)
  InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014)
  MachineType: FUJITSU SIEMENS AMILO Pi 2515
  ProcKernelCmdLine: BOOT

[Kernel-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode

[Buzea Bogdan]

I can' t reproduce myself... Was an anoying bug, but it disapaer today
with OTA-11 update.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1488170

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed
Status in urfkill package in Ubuntu:
  Confirmed

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

  Boot with bluetooth disabled
  Turn on flight mode
  turn off flight mode
  Bluetooth gets enabled

  See bug #1421249 for related symptoms

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+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 1209503] [NEW] [Acer Extensa 5220] suspend/resume failure

[Bogdan Arabadzhi]

Public bug reported:

After boot it's appeared..

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-6-generic 3.10.0-6.17
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic i686
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.12-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bogdan 1776 F pulseaudio
CRDA:
 country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
Date: Tue Aug  6 12:27:33 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=29645983-b508-4fa3-95df-26be802a8c59
InstallationDate: Installed on 2013-08-04 (3 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130804)
InterpreterPath: /usr/bin/python3.3
MachineType: Acer Extensa 5220
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic 
root=UUID=c92f5314-e9e0-4c87-a6bb-c478701a0127 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not 
responding.
RelatedPackageVersions:
 linux-restricted-modules-3.10.0-6-generic N/A
 linux-backports-modules-3.10.0-6-generic  N/A
 linux-firmware1.113
SourcePackage: linux
Title: [Acer Extensa 5220] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 07/03/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.35
dmi.board.name: Columbia
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5220
dmi.product.version: 0100
dmi.sys.vendor: Acer

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-kerneloops i386 resume saucy 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/1209503

Title:
  [Acer Extensa 5220] suspend/resume failure

Status in “linux” package in Ubuntu:
  New

Bug description:
  After boot it's appeared..

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.10.0-6-generic 3.10.0-6.17
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  Uname: Linux 3.10.0-6-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bogdan 1776 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Date: Tue Aug  6 12:27:33 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=29645983-b508-4fa3-95df-26be802a8c59
  InstallationDate: Installed on 2013-08-04 (3 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130804)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Acer Extensa 5220
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic 
root=UUID=c92f5314-e9e0-4c87-a6bb-c478701a0127 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.10.0-6-generic N/A
   linux-backports-modules-3.10.0-6-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  Title: [Acer Extensa 5220] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr

[Kernel-packages] [Bug 1208257] Re: [HP ProBook 4540s] brightness control problems

[Bogdan Iavorskyi]

i can confirm this on hp 4740s on 13.04,
tried last kernel 3.11 - problem still are, and wifi don't 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/1208257

Title:
  [HP ProBook 4540s] brightness control problems

Status in “linux” package in Ubuntu:
  Incomplete
Status in “linux” package in Baltix:
  Triaged

Bug description:
  I bought a laptop in December 2012, immediately tried to put Ubuntu
  12.10, got broken wi-fi and non-working graphics acceleration. Updated
  kernel to version 3.6, with graphic acceleration was all right, even
  partially earned wi-fi. After some time wi-fi hang, helped only
  restart the network subsystem.

  Updated kernel to 3.7, with the wi-fi was all became normal, but
  stopped working brightness control with the Fn keys. Progress bar
  indicates that the brightness changes, but in fact nothing happens.

  Tried the new distribution 13.04, on 3.8 kernels, 3.9, 3.10, nothing
  changes. Upon adjustment has broken in 3.7 kernel. It turns out that
  this is a regression.

  WORKAROUND: Problem gone with kernel parameter acpi_backlight=vendor.

  ---
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA:
   country UA:
    (2402 - 2482 @ 40), (N/A, 20)
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2013-08-04 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=f5b4658c-870e-449d-a9d7-5caaa6eec2f3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  raring
  Uname: Linux 3.8.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/20/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.41
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.41:bd05/20/2013:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard
  ---
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3887 F pulseaudio
    ubuntu14062 F pulseaudio
  CRDA:
   country UA:
    (2400 - 2483 @ 40), (N/A, 20), NO-OUTDOOR
    (5150 - 5350 @ 40), (N/A, 20), NO-OUTDOOR
    (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR
  CasperVersion: 1.336
  DistroRelease: Ubuntu 13.10
  LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130807)
  MachineType: Hewlett-Packard HP ProBook 4540s
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper persistent 
initrd=/casper/initrd.lz splash -- maybe-ubiquity
  ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
  RelatedPackageVersions:
   linux-restricted-modules-3.10.0-6-generic N/A
   linux-backports-modules-3.10.0-6-generic  N/A
   linux-firmware1.113
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  saucy
  Uname: Linux 3.10.0-6-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 05/20/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.41
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.41:bd05/20/2013:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4540s
  dmi.product.version: A1018C1100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208257/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.n

[Kernel-packages] [Bug 1222513] [NEW] [Acer Extensa 5220] suspend/resume failure

[Bogdan Arabadzhi]

Public bug reported:

Again...

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-5-generic 3.11.0-5.10
ProcVersionSignature: Ubuntu 3.11.0-5.10-generic 3.11.0
Uname: Linux 3.11.0-5-generic i686
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bogdan 1501 F pulseaudio
CRDA:
 country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
Date: Fri Sep  6 15:48:08 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=b33b4089-787e-47a4-be22-0d9e0f3564b3
InstallationDate: Installed on 2013-09-05 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130804)
InterpreterPath: /usr/bin/python3.3
MachineType: Acer Extensa 5220
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=e9e16142-cf79-49e3-bb50-6c0dc1bd3e36 ro 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-5-generic N/A
 linux-backports-modules-3.11.0-5-generic  N/A
 linux-firmware1.113
SourcePackage: linux
Title: [Acer Extensa 5220] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 07/03/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.35
dmi.board.name: Columbia
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5220
dmi.product.version: 0100
dmi.sys.vendor: Acer

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-kerneloops i386 package-from-proposed resume saucy 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/1222513

Title:
  [Acer Extensa 5220] suspend/resume failure

Status in “linux” package in Ubuntu:
  New

Bug description:
  Again...

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-5-generic 3.11.0-5.10
  ProcVersionSignature: Ubuntu 3.11.0-5.10-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bogdan 1501 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  Date: Fri Sep  6 15:48:08 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=b33b4089-787e-47a4-be22-0d9e0f3564b3
  InstallationDate: Installed on 2013-09-05 (2 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130804)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Acer Extensa 5220
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=e9e16142-cf79-49e3-bb50-6c0dc1bd3e36 ro 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-5-generic N/A
   linux-backports-modules-3.11.0-5-generic  N/A
   linux-firmware1.113
  SourcePackage: linux
  Title: [Acer Extensa 5220] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/03/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.35
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnExtensa5220:pvr0100:rvnAcer:rnColumbia:

[Kernel-packages] [Bug 1509237] [NEW] dm-cache: clean cache resyncs to origin on every boot

[Bogdan Vasiliev]

Public bug reported:

On every boot an entire dm-cache resyncs to an origin device, even if it
was clean before on shutdown. It takes time and full bandwidth of an
origin device. There is the simple solution from the upstream:

commit 7e0a9739fd9e72dc51490bdff92796400b12a34f
Author: Joe Thornber 
Date:   Thu Oct 22 18:10:55 2015 +0100

[dm-cache] The CLEAN_SHUTDOWN flag was not being set

or rather, it was being set on the disk, then immediately cleared again.

If the CLEAN_SHUTDOWN flag is not set when a cache is loaded then all cache
blocks are marked as dirty and a full writeback occurs.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "dm-cache-metadata.patch"
   
https://bugs.launchpad.net/bugs/1509237/+attachment/4502948/+files/dm-cache-metadata.patch

-- 
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/1509237

Title:
  dm-cache: clean cache resyncs to origin on every boot

Status in linux package in Ubuntu:
  New

Bug description:
  On every boot an entire dm-cache resyncs to an origin device, even if
  it was clean before on shutdown. It takes time and full bandwidth of
  an origin device. There is the simple solution from the upstream:

  commit 7e0a9739fd9e72dc51490bdff92796400b12a34f
  Author: Joe Thornber 
  Date:   Thu Oct 22 18:10:55 2015 +0100

  [dm-cache] The CLEAN_SHUTDOWN flag was not being set
  
  or rather, it was being set on the disk, then immediately cleared again.
  
  If the CLEAN_SHUTDOWN flag is not set when a cache is loaded then all 
cache
  blocks are marked as dirty and a full writeback occurs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509237/+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 1509237] Re: dm-cache: clean cache resyncs to origin on every boot

[Bogdan Vasiliev]

** 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/1509237

Title:
  dm-cache: clean cache resyncs to origin on every boot

Status in linux package in Ubuntu:
  New

Bug description:
  On every boot an entire dm-cache resyncs to an origin device, even if
  it was clean before on shutdown. It takes time and full bandwidth of
  an origin device. There is the simple solution from the upstream:

  commit 7e0a9739fd9e72dc51490bdff92796400b12a34f
  Author: Joe Thornber 
  Date:   Thu Oct 22 18:10:55 2015 +0100

  [dm-cache] The CLEAN_SHUTDOWN flag was not being set
  
  or rather, it was being set on the disk, then immediately cleared again.
  
  If the CLEAN_SHUTDOWN flag is not set when a cache is loaded then all 
cache
  blocks are marked as dirty and a full writeback occurs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509237/+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 2062280] [NEW] Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

[Bogdan Mitrea]

Public bug reported:

Starting with kernel 6.5 the external Bluetooth USB dongle based on
Realtek stop working.

This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
version is > 6.5. On a lower kernel version it works as we were using it
for almost 2 years without issues.

Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor 
Corp. Bluetooth Radio

```
$ uname -a
Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```

```
$ lsusb | grep -i bluetooth
Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
```

Journalctl logs after the OS is starting
```
journalctl -b | egrep -i bluetooth
Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager 
initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection manager 
initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
```

I have installed BlueZ package https://www.bluez.org/ and trying to
discover the device which worked but i am always getting errors when
trying to connect to the device via BT (after pairing)

```
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() 
sending Set Discoverable command for index 0
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0007
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0007 complete: 0x00
Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0006
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0006 complete: 0x00
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:property_set_mode_complete() Success (0x00)
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:new_settings_callback() Settings: 0x0adb
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Changed settings: 0x0008
Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Pending settings: 0x0002
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] event 0x000b
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/adapter.c:connected_callback() 
hci0 device 74:9E:F5:28:3C:4C connected eir_len 15
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] event 0x000f
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: 
src/adapter.c:user_confirm_request_callback() hci0 74:9E:F5:28:3C:4C 
confirm_hint 0
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/device.c:new_auth() Requesting 
agent authentication for 74:9E:F5:28:3C:4C
Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/agent.c:ag

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Bogdan Melnik]

I think I have the same issue which translates to the fact that I can't
boot the x13s image from https://cdimage.ubuntu.com/daily-live/current/
(2024-04-17 06:17).

-- 
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/2060868

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Noble:
  Confirmed

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

[Bogdan Mitrea]

Steps to reproduce the bug:
* install bluez
* make sure a USB Bluetooth dongle is attached to your computer
* Start bluetoothctl 
* Run discoverable on 
* Discover the device using the Android BT manager
* On the phone you are ask to confirm the pair key -> Pair
* In the bluetoothctl type yes
* Connection is establish and it fails immediately with a disconnect error 
message -> type BR/EDR disconnected with reason 2

-- 
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/2062280

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting with kernel 6.5 the external Bluetooth USB dongle based on
  Realtek stop working.

  This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
  version is > 6.5. On a lower kernel version it works as we were using
  it for almost 2 years without issues.

  Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
  USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor 
Corp. Bluetooth Radio

  ```
  $ uname -a
  Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth
  Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
  ```

  Journalctl logs after the OS is starting
  ```
  journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  ```

  I have installed BlueZ package https://www.bluez.org/ and trying to
  discover the device which worked but i am always getting errors when
  trying to connect to the device via BT (after pairing)

  ```
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() 
sending Set Discoverable command for index 0
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0007
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0007 complete: 0x00
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0006
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0006 complete: 0x00
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:property_set_mode_complete() Success (0x00)
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:new_settings_callback() Settings: 0x0adb
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: s

[Kernel-packages] [Bug 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

[Bogdan Mitrea]

i have used also ubuntu-bug to send logs

-- 
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/2062280

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting with kernel 6.5 the external Bluetooth USB dongle based on
  Realtek stop working.

  This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
  version is > 6.5. On a lower kernel version it works as we were using
  it for almost 2 years without issues.

  Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
  USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor 
Corp. Bluetooth Radio

  ```
  $ uname -a
  Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth
  Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
  ```

  Journalctl logs after the OS is starting
  ```
  journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  ```

  I have installed BlueZ package https://www.bluez.org/ and trying to
  discover the device which worked but i am always getting errors when
  trying to connect to the device via BT (after pairing)

  ```
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() 
sending Set Discoverable command for index 0
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0007
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0007 complete: 0x00
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0006
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0006 complete: 0x00
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:property_set_mode_complete() Success (0x00)
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:new_settings_callback() Settings: 0x0adb
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Changed settings: 0x0008
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Pending settings: 0x0002
  Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] event 0x000b
  Apr 18 09:23:07 bomi-edge bluetoothd[2413]: 
src/adapter.c:connected_callback() hci0 device 74:9E:F5:28

[Kernel-packages] [Bug 2062280] Re: Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

[Bogdan Mitrea]

i have done again. It says that it might take minutes to send data but
was done in seconds :)

can you please check again?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2062280

Title:
  Bluetooth Broken In Kernel Versions 6.5+ (Realtek)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Starting with kernel 6.5 the external Bluetooth USB dongle based on
  Realtek stop working.

  This issue occurs on either UBuntu 22.04, 23.10 and 24.04 when kernel
  version is > 6.5. On a lower kernel version it works as we were using
  it for almost 2 years without issues.

  Version signature: Ubuntu 6.8.0-22.22-generic 6.8.1
  USB bluetooth device: Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor 
Corp. Bluetooth Radio

  ```
  $ uname -a
  Linux bomi-edge 6.8.0-22-generic #22-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  4 
22:30:32 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
  ```

  ```
  $ lsusb | grep -i bluetooth
  Bus 001 Device 003: ID 0bda:a729 Realtek Semiconductor Corp. Bluetooth Radio
  ```

  Journalctl logs after the OS is starting
  ```
  journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  root@bomi-edge:/home/edge# journalctl -b | egrep -i bluetooth
  Apr 18 07:16:29 bomi-edge kernel: usb 1-9: Product: Bluetooth Radio
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: Core ver 2.22
  Apr 18 07:16:30 bomi-edge kernel: NET: Registered PF_BLUETOOTH protocol family
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI device and connection 
manager initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: HCI socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: L2CAP socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: SCO socket layer initialized
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 
30210
  Apr 18 07:16:30 bomi-edge systemd[1]: Reached target bluetooth.target - 
Bluetooth Support.
  Apr 18 07:16:30 bomi-edge kernel: Bluetooth: hci0: RTL: fw version 0xdfc6d922
  ```

  I have installed BlueZ package https://www.bluez.org/ and trying to
  discover the device which worked but i am always getting errors when
  trying to connect to the device via BT (after pairing)

  ```
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/adapter.c:property_set_mode() 
sending Set Discoverable command for index 0
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0007
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0007 complete: 0x00
  Apr 18 09:22:36 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:send_request() 
[0x] command 0x0006
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] command 0x0006 complete: 0x00
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:property_set_mode_complete() Success (0x00)
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: 
src/adapter.c:new_settings_callback() Settings: 0x0adb
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Changed settings: 0x0008
  Apr 18 09:22:37 bomi-edge bluetoothd[2413]: src/adapter.c:settings_changed() 
Pending settings: 0x0002
  Apr 18 09:23:07 bomi-edge bluetoothd[2413]: src/shared/mgmt.c:can_read_data() 
[0x] event 0x000b
  Apr 18 09:23:07 bomi-

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Bogdan Melnik]

Same questions. Should we expect that daily builds will become bootable
or we should manually upgrade from 23.10 and install new package
manually?

-- 
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/2060868

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Noble:
  Confirmed

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060868/+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 1964539] Re: [nouveau] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked

[Bogdan Negru]

I have the same issue Matthew has. 
Also checked the additional software and I don't see the driver for Intel(R) 
UHD Graphics 620 (WHL GT2).
Before upgrading (I had ubuntu 18.04) I had the driver for the graphics card 
listed there.
Also, I cannot set the refresh rate for my laptop to 120hz, may be the missing 
driver causing it.
How can I install that driver on ubuntu 22?

** Changed in: mutter (Ubuntu)
   Status: Expired => 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/1964539

Title:
  [nouveau] 42beta: screen unlock gets stuck on primary display,
  secondary display is unlocked

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  Occasionally, when the screen has been locked for a medium length of
  time, > 5 mins, when you press the spacebar, enter your password, the
  primary display freezes and the lockscreen slider does not slide up.
  The secondary screen is fine, and unlocks.

  See screenshot for what it looks like.

  You can click, interact with the secondary screen. On the primary
  screen, you can super key and launch an application, but you won't be
  able to interact with it. You can't see what you are doing.

  The way to fix is to re-lock the screen, wait a bit, and attempt to
  unlock. Sometimes you won't be able to unlock immediately, as it is
  difficult to get the monitor to power on again, it appears gnome-shell
  does not send the wakeup signal.

  gnome-shell 42~beta-1ubuntu2 from -proposed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-02 (68 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu1
  Tags: wayland-session third-party-packages jammy package-from-proposed
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964539/+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