[Kernel-packages] [Bug 2043299] Re: Linux 6.5 breaks Novation Components web MIDI application
As mentioned above, this turns out to have been a Chrome/Chromium bug
exposed by the new kernel. It has been fixed in Chrome 123, which is now
the stable release. This issue can be closed.
--
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/2043299
Title:
Linux 6.5 breaks Novation Components web MIDI application
Status in linux package in Ubuntu:
Confirmed
Bug description:
Ubuntu version: 23.10
Kernel version: 6.5.0-10
Steps to recreate:
1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
2. Navigate to https://components.novationmusic.com/
3. Connect a Novation Circuit Tracks via USB
Expected behaviour (demonstrated by
linux-image-unsigned-6.4.16-060416-generic):
- Circuit Tracks shows up in UI with a state of "Connected"
Observed behaviour:
- Circuit Tracks shows up in UI with a state of "Connecting" and eventually
"Connection error"
Notes:
- Basic MIDI functions are present (sending notes, clocks etc.)
- loading the snd_usb_audio module with midi2_enable=N midi2_ump_probe=N
makes no difference
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ecoffey2236 F wireplumber
/dev/snd/controlC1: ecoffey2236 F wireplumber
/dev/snd/seq:ecoffey2218 F pipewire
ecoffey4055 F chrome
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 12 16:25:39 2023
InstallationDate: Installed on 2022-12-14 (333 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=f1b3d983-74a2-4982-ba7f-158c5c64fc68 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-04-21 (205 days ago)
dmi.bios.date: 10/14/2022
dmi.bios.release: 20.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2014
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-P WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2014:bd10/14/2022:br20.14:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043299/+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 2043299] Re: Linux 6.5 breaks Novation Components web MIDI application
Mainline kernel 6.6.1 also exhibits this regression.
--
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/2043299
Title:
Linux 6.5 breaks Novation Components web MIDI application
Status in linux package in Ubuntu:
Incomplete
Bug description:
Ubuntu version: 23.10
Kernel version: 6.5.0-10
Steps to recreate:
1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
2. Navigate to https://components.novationmusic.com/
3. Connect a Novation Circuit Tracks via USB
Expected behaviour (demonstrated by
linux-image-unsigned-6.4.16-060416-generic):
- Circuit Tracks shows up in UI with a state of "Connected"
Observed behaviour:
- Circuit Tracks shows up in UI with a state of "Connecting" and eventually
"Connection error"
Notes:
- Basic MIDI functions are present (sending notes, clocks etc.)
- loading the snd_usb_audio module with midi2_enable=N midi2_ump_probe=N
makes no difference
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ecoffey2236 F wireplumber
/dev/snd/controlC1: ecoffey2236 F wireplumber
/dev/snd/seq:ecoffey2218 F pipewire
ecoffey4055 F chrome
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 12 16:25:39 2023
InstallationDate: Installed on 2022-12-14 (333 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=f1b3d983-74a2-4982-ba7f-158c5c64fc68 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-04-21 (205 days ago)
dmi.bios.date: 10/14/2022
dmi.bios.release: 20.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2014
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-P WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2014:bd10/14/2022:br20.14:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043299/+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 2043299] Re: Linux 6.5 breaks Novation Components web MIDI application
And here's the syslog for the last 6.4 kernel, from the moment the
device is plugged in to the moment the app states the connection is
good. Other than some slight timing changes and the absence of the
"falling back to MIDI 1.0" message, not much has changed.
** Attachment added: "syslog-6.4.16-060416-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043299/+attachment/5718993/+files/syslog-6.4.16-060416-generic
--
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/2043299
Title:
Linux 6.5 breaks Novation Components web MIDI application
Status in linux package in Ubuntu:
Incomplete
Bug description:
Ubuntu version: 23.10
Kernel version: 6.5.0-10
Steps to recreate:
1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
2. Navigate to https://components.novationmusic.com/
3. Connect a Novation Circuit Tracks via USB
Expected behaviour (demonstrated by
linux-image-unsigned-6.4.16-060416-generic):
- Circuit Tracks shows up in UI with a state of "Connected"
Observed behaviour:
- Circuit Tracks shows up in UI with a state of "Connecting" and eventually
"Connection error"
Notes:
- Basic MIDI functions are present (sending notes, clocks etc.)
- loading the snd_usb_audio module with midi2_enable=N midi2_ump_probe=N
makes no difference
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ecoffey2236 F wireplumber
/dev/snd/controlC1: ecoffey2236 F wireplumber
/dev/snd/seq:ecoffey2218 F pipewire
ecoffey4055 F chrome
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 12 16:25:39 2023
InstallationDate: Installed on 2022-12-14 (333 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=f1b3d983-74a2-4982-ba7f-158c5c64fc68 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-04-21 (205 days ago)
dmi.bios.date: 10/14/2022
dmi.bios.release: 20.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2014
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-P WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2014:bd10/14/2022:br20.14:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043299/+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 2043299] Re: Linux 6.5 breaks Novation Components web MIDI application
Yes it's a regression. Here's the syslog using the current kernel from
the moment the device is plugged in to the moment the app gives up on
communication.
** Attachment added: "syslog-6.5.0-10"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043299/+attachment/5718992/+files/syslog-6.5.0-10
--
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/2043299
Title:
Linux 6.5 breaks Novation Components web MIDI application
Status in linux package in Ubuntu:
Incomplete
Bug description:
Ubuntu version: 23.10
Kernel version: 6.5.0-10
Steps to recreate:
1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
2. Navigate to https://components.novationmusic.com/
3. Connect a Novation Circuit Tracks via USB
Expected behaviour (demonstrated by
linux-image-unsigned-6.4.16-060416-generic):
- Circuit Tracks shows up in UI with a state of "Connected"
Observed behaviour:
- Circuit Tracks shows up in UI with a state of "Connecting" and eventually
"Connection error"
Notes:
- Basic MIDI functions are present (sending notes, clocks etc.)
- loading the snd_usb_audio module with midi2_enable=N midi2_ump_probe=N
makes no difference
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ecoffey2236 F wireplumber
/dev/snd/controlC1: ecoffey2236 F wireplumber
/dev/snd/seq:ecoffey2218 F pipewire
ecoffey4055 F chrome
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 12 16:25:39 2023
InstallationDate: Installed on 2022-12-14 (333 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=f1b3d983-74a2-4982-ba7f-158c5c64fc68 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-04-21 (205 days ago)
dmi.bios.date: 10/14/2022
dmi.bios.release: 20.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2014
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-P WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2014:bd10/14/2022:br20.14:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043299/+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 2043299] [NEW] Linux 6.5 breaks Novation Components web MIDI application
Public bug reported:
Ubuntu version: 23.10
Kernel version: 6.5.0-10
Steps to recreate:
1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
2. Navigate to https://components.novationmusic.com/
3. Connect a Novation Circuit Tracks via USB
Expected behaviour (demonstrated by linux-image-unsigned-6.4.16-060416-generic):
- Circuit Tracks shows up in UI with a state of "Connected"
Observed behaviour:
- Circuit Tracks shows up in UI with a state of "Connecting" and eventually
"Connection error"
Notes:
- Basic MIDI functions are present (sending notes, clocks etc.)
- loading the snd_usb_audio module with midi2_enable=N midi2_ump_probe=N makes
no difference
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ecoffey2236 F wireplumber
/dev/snd/controlC1: ecoffey2236 F wireplumber
/dev/snd/seq:ecoffey2218 F pipewire
ecoffey4055 F chrome
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 12 16:25:39 2023
InstallationDate: Installed on 2022-12-14 (333 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=f1b3d983-74a2-4982-ba7f-158c5c64fc68 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-04-21 (205 days ago)
dmi.bios.date: 10/14/2022
dmi.bios.release: 20.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2014
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z690-P WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2014:bd10/14/2022:br20.14:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
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/2043299
Title:
Linux 6.5 breaks Novation Components web MIDI application
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu version: 23.10
Kernel version: 6.5.0-10
Steps to recreate:
1. Open Google Chrome (possibly Chromium, or the .deb version of Firefox)
2. Navigate to https://components.novationmusic.com/
3. Connect a Novation Circuit Tracks via USB
Expected behaviour (demonstrated by
linux-image-unsigned-6.4.16-060416-generic):
- Circuit Tracks shows up in UI with a state of "Connected"
Observed behaviour:
- Circuit Tracks shows up in UI with a state of "Connecting" and eventually
"Connection error"
Notes:
- Basic MIDI functions are present (sending notes, clocks etc.)
- loading the snd_usb_audio module with midi2_enable=N midi2_ump_probe=N
makes no difference
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ecoffey2236 F wireplumber
/dev/snd/controlC1: ecoffey2236 F wireplumber
/dev/snd/seq:ecoffey2218 F pipewire
ecoffey4055 F chrome
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 12 16:25:39 2023
InstallationDate: Installed on 2022-12-14 (333 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=f1b3d983-74a2-4982-ba7f-158c5c64fc68 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
[Kernel-packages] [Bug 2039375] Re: Green screen
I have the same problem. The Release Notes for 21.2 has a section titled "Solving freezes during the boot sequence" that sounds similar this problem. Even though I have an AMD video board instead of NVIDIA, I tried the listed fixes to no avail. I gave up and went back to vmlinuz-5.15.0-84-generic. My system info is at this pastebin: https://paste.ubuntu.com/p/S6Q7qYRHkq/ -- 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/2039375 Title: Green screen Status in linux package in Ubuntu: Confirmed Bug description: This morning I did the kernel update that arrived yesterday. Now, after I login I get a solid green screen and that's where it stays. the upgrade took the machine from: vmlinuz-5.15.0-84-generic To: vmlinuz-5.15.0-86-generic I rebooted into 84-generic and everything worked correctly, as pre- update. See more : https://forums.linuxmint.com/viewtopic.php?t=405203=1=unread#unread To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039375/+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 2033419] [NEW] package linux-image-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: It's a system error. Don't know what to write. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edward 2854 F wireplumber /dev/snd/seq:edward 2850 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Mon Aug 14 15:05:10 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-11-03 (299 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP ProBook 450 G5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=27507466-844d-4d02-95e6-9defd668245c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-07-10 (50 days ago) dmi.bios.date: 11/29/2022 dmi.bios.release: 23.0 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.23.00 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.41.00 dmi.chassis.asset.tag: 5CD8095KWD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.65 dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.23.00:bd11/29/2022:br23.0:efr2.65:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.41.00:cvnHP:ct10:cvr:sku2XZ73ES#ACB: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 2XZ73ES#ACB dmi.sys.vendor: HP ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2033419 Title: package linux-image-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: It's a system error. Don't know what to write. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-27-generic 6.2.0-27.28 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edward 2854 F wireplumber /dev/snd/seq:edward 2850 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Mon Aug 14 15:05:10 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2022-11-03 (299 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP ProBook 450 G5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=27507466-844d-4d02-95e6-9defd668245c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-27-generic 6.2.0-27.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: Upgraded to lunar on 2023-07-10 (50 days ago) dmi.bios.date: 11/29/2022 dmi.bios.release: 23.0 dmi.bios.vendor: HP dmi.bios.version: Q85 Ver. 01.23.00 dmi.board.name: 837D dmi.board.vendor: HP dmi.board.version: KBC Version 02.41.00 dmi.chassis.asset.tag: 5CD8095KWD dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.65 dmi.modalias: dmi:bvnHP:bvrQ85Ver.01.23.00:bd11/29/2022:br23.0:efr2.65:svnHP:pnHPProBook450G5:pvr:rvnHP:rn837D:rvrKBCVersion02.41.00:cvnHP:ct10:cvr:sku2XZ73ES#ACB: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G5 dmi.product.sku: 2XZ73ES#ACB dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2033419/+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 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen
@kmhallen0. I discovered that reinstalling driver 525.85.12 worked as well. I think that the real problem is that Ubuntu Software Updater did not install the NVIDIA drivers correctly. I have not tried the 5.19.0-32 kernel. Thanks for responding. -- 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/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen
I ran "apport-collect 2009226" while booted to 5.19.0-32, not while booted to 5.19.0-35 because X/Wayland doesn't start in 5.19.0-35. If apport-collect will run in a terminal window then I can boot to 5.19.0-35 and run apport-collect if needed/helpful. -- 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/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651503/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651504/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651502/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651499/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651501/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651498/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651497/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651500/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651496/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651495/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651494/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651493/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651491/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651492/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651490/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/23/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: - I updated software this morning and on reboot ubuntu kernel 5.19.0-35 - gives black screen. It appears to be an issue with graphics as I can - access a console and login. I am able boot and run normally with - 5.19.0-32-generic. I am using nvidia drivers. + I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: ehwelbon 200265 F pulseaudio + /dev/snd/controlC1: ehwelbon 200265 F pulseaudio + /dev/snd/controlC0: ehwelbon 200265 F pulseaudio + /dev/snd/controlC2: ehwelbon 200265 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-11-12 (111 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + IwConfig: + lono wireless extensions. + + enp5s0no wireless extensions. + + enp6s0no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-32-generic N/A + linux-backports-modules-5.19.0-32-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.10 + RfKill: + + Tags: jammy wayland-session + Uname: Linux 5.19.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip floppy lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/23/2009 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: FD + dmi.board.name: EP45-UD3P + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd11/23/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: + dmi.product.name: EP45-UD3P + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2009226/+attachment/5651489/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Confirmed Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: ehwelbon 200265 F pulseaudio /dev/snd/controlC1: ehwelbon 200265 F pulseaudio /dev/snd/controlC0: ehwelbon 200265 F pulseaudio /dev/snd/controlC2: ehwelbon 200265 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-12 (111 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic root=UUID=e6b6f51c-9df1-418d-b1ed-c750e195f6cd ro audit=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags:
[Kernel-packages] [Bug 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen
** Description changed: - I update this morning and ubuntu kernel 5.19.0-35 gives black screen. - It appears to be an issue with graphics as I can access a console and - login. I am able boot with 5.19.0-32-generic. I am using nvidia - drivers. + I updated software this morning and on reboot ubuntu kernel 5.19.0-35 + gives black screen. It appears to be an issue with graphics as I can + access a console and login. I am able boot and run normally with + 5.19.0-32-generic. I am using nvidia drivers. -- 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/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Incomplete Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen
I am not running in problematic update but I have attached sudo lspci -vnvn > lspci-vnvn.log ** Attachment added: "output of sudo lspci -vnvn > lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+attachment/5651446/+files/lspci-vnvn.log -- 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/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: New Bug description: I update this morning and ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot with 5.19.0-32-generic. I am using nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 2009226] [NEW] updating to ubuntu kernel 5.19.0-35 gives black screen
Public bug reported: I update this morning and ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot with 5.19.0-32-generic. I am using nvidia drivers. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: New Bug description: I update this morning and ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot with 5.19.0-32-generic. I am using nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+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 1995126] Re: upgrade from 20.04 to 22.04.1 fails
May have been solved by: sudo pip uninstall distro-info sudo apt install --reinstall python3-distro-info ref: https://askubuntu.com/questions/1137645/python-error-when- upgrading-from-18-10-to-19-04 -- 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/1995126 Title: upgrade from 20.04 to 22.04.1 fails Status in linux package in Ubuntu: Confirmed Bug description: $ sudo do-release-upgrade -d Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,265 kB] Fetched 1,266 kB in 0s (0 B/s) authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg' extracting 'jammy.tar.gz' [screen blanks here] Reading cache Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Hit http://archive.canonical.com/ubuntu focal InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit http://security.ubuntu.com/ubuntu focal-security InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease Hit http://dl.google.com/linux/chrome/deb stable InRelease Hit http://ppa.launchpad.net/mutlaqja/ppa/ubuntu focal InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done === Command detached from window (Fri Oct 28 11:16:34 2022) === === Command terminated with exit status 1 (Fri Oct 28 11:16:44 2022) === [screen is terminating] $ uname -a Linux tempo 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/*elease* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.5 LTS" NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-131-generic 5.4.0-131.147 ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Uname: Linux 5.4.0-131-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: edik 1914 F pulseaudio /dev/snd/controlC0: edik 1914 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 28 11:21:00 2022 InstallationDate: Installed on 2019-05-30 (1246 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. eno0 no wireless extensions. ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-131-generic root=UUID=a501cd51-bc07-496b-a8dd-bee5e1db7c02 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-131-generic N/A linux-backports-modules-5.4.0-131-generic N/A linux-firmware 1.187.33 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-10-28 (0 days ago) dmi.bios.date: 05/21/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.5531.2010.0521.1135 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55SB dmi.board.vendor: Intel Corporation dmi.board.version: AAE47220-304 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.5531.2010.0521.1135:bd05/21/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55SB:rvrAAE47220-304:cvn:ct2:cvr: To manage notifications about this bug go to:
[Kernel-packages] [Bug 1995126] Re: upgrade from 20.04 to 22.04.1 fails
I made the terminal window several screens' tall, to see the following
(before the screen gets blanked by the install process - why would it do
that?):
Reading cache
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://security.ubuntu.com/ubuntu focal-security InRelease
Hit http://ca.archive.ubuntu.com/ubuntu focal InRelease
Hit http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit http://archive.canonical.com/ubuntu focal InRelease
Hit http://dl.google.com/linux/chrome/deb stable InRelease
Hit http://ppa.launchpad.net/mutlaqja/ppa/ubuntu focal InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Traceback (most recent call last):
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
205, in _get_from_and_to_version
di.version('%s' % self.controller.fromDist).split()[0]
AttributeError: 'UbuntuDistroInfo' object has no attribute 'version'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-hq1pt_14/jammy", line 8, in
sys.exit(main())
File "/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeMain.py",
line 241, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 2042, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 1873, in fullUpgrade
if not self.doPostInitialUpdate():
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 906, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
99, in run
func()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
118, in jammyPostInitialUpdate
self._get_from_and_to_version()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
211, in _get_from_and_to_version
(r.version for r in di.get_all("object")
AttributeError: 'UbuntuDistroInfo' object has no attribute 'get_all'
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in
add_to_existing
self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
block = f.read(1048576)
File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid
start byte
Original exception was:
Traceback (most recent call last):
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
205, in _get_from_and_to_version
di.version('%s' % self.controller.fromDist).split()[0]
AttributeError: 'UbuntuDistroInfo' object has no attribute 'version'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-hq1pt_14/jammy", line 8, in
sys.exit(main())
File "/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeMain.py",
line 241, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 2042, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 1873, in fullUpgrade
if not self.doPostInitialUpdate():
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 906, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
99, in run
func()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
118, in jammyPostInitialUpdate
self._get_from_and_to_version()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
211, in _get_from_and_to_version
(r.version for r in di.get_all("object")
AttributeError: 'UbuntuDistroInfo' object has no attribute 'get_all'
=== Command detached from window (Fri Oct 28 11:44:51 2022) ===
=== Command terminated with exit status 1 (Fri Oct 28 11:45:01 2022) ===
--
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/1995126
Title:
upgrade from 20.04 to 22.04.1 fails
Status in linux package in Ubuntu:
New
Bug description:
$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
[Kernel-packages] [Bug 1995126] [NEW] upgrade from 20.04 to 22.04.1 fails
Public bug reported: $ sudo do-release-upgrade -d Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,265 kB] Fetched 1,266 kB in 0s (0 B/s) authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg' extracting 'jammy.tar.gz' [screen blanks here] Reading cache Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Hit http://archive.canonical.com/ubuntu focal InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit http://security.ubuntu.com/ubuntu focal-security InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease Hit http://dl.google.com/linux/chrome/deb stable InRelease Hit http://ppa.launchpad.net/mutlaqja/ppa/ubuntu focal InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done === Command detached from window (Fri Oct 28 11:16:34 2022) === === Command terminated with exit status 1 (Fri Oct 28 11:16:44 2022) === [screen is terminating] $ uname -a Linux tempo 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/*elease* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.5 LTS" NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-131-generic 5.4.0-131.147 ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Uname: Linux 5.4.0-131-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: edik 1914 F pulseaudio /dev/snd/controlC0: edik 1914 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 28 11:21:00 2022 InstallationDate: Installed on 2019-05-30 (1246 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. eno0 no wireless extensions. ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-131-generic root=UUID=a501cd51-bc07-496b-a8dd-bee5e1db7c02 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-131-generic N/A linux-backports-modules-5.4.0-131-generic N/A linux-firmware 1.187.33 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-10-28 (0 days ago) dmi.bios.date: 05/21/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.5531.2010.0521.1135 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55SB dmi.board.vendor: Intel Corporation dmi.board.version: AAE47220-304 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.5531.2010.0521.1135:bd05/21/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55SB:rvrAAE47220-304:cvn:ct2:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1995126 Title: upgrade from 20.04 to 22.04.1 fails Status in linux package in Ubuntu: New Bug description: $ sudo do-release-upgrade -d Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,265 kB]
[Kernel-packages] [Bug 1984036] [NEW] Second Monitor via HDMI flicking on and off , and green flares
Public bug reported: Tired X.org, Other Nvidia Drivers, swapping and changing cables, lowering refresh rates, swapping over the HDMI to other monitor (ThinkVision can not remeber) now the second monitor has the exact same problem and the first one via DP is perfect (not a problem of the monitor or cable of the DP port). Need this setup for work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-515 515.65.01-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 9 08:17:19 2022 InstallationDate: Installed on 2022-07-27 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nvidia-graphics-drivers-515 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1984036 Title: Second Monitor via HDMI flicking on and off ,and green flares Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: Tired X.org, Other Nvidia Drivers, swapping and changing cables, lowering refresh rates, swapping over the HDMI to other monitor (ThinkVision can not remeber) now the second monitor has the exact same problem and the first one via DP is perfect (not a problem of the monitor or cable of the DP port). Need this setup for work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-515 515.65.01-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Aug 9 08:17:19 2022 InstallationDate: Installed on 2022-07-27 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nvidia-graphics-drivers-515 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1984036/+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 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
@andch You're a genius. Turns out I just needed to reset the BIOS to default settings! Thanks a ton! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3:
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
@kchsieh No, the webcam light doesn't turn on even on webcamtest. I don't think I have tried the oem image from Dell's website. Do you think you could attach a link to it? I can't seem to find it. I ran $ journalctl -k -b and the results of this are attached in "results.txt". I also ran $ cat /sys/class/dmi/id/product_sku and this was the result: 0AF3 Thanks. ** Attachment added: "results.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955383/+attachment/5605122/+files/results.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
@kchsieh Hi, so I tried following the wiki for 20.04, but that didn't work, so I just ended up upgrading to 22.04 and tried what comment #79 mentioned but I'm still getting a black screen. I ran $ dpkg-query -W again and here are the results: accountsservice 22.07.5-2ubuntu1.3 acl 2.3.1-1 acpi-support0.144 acpid 1:2.0.33-1ubuntu1 adduser 3.118ubuntu5 adwaita-icon-theme 41.0-1ubuntu1 aisleriot 1:3.22.22-1 alsa-base 1.0.25+dfsg-0ubuntu7 alsa-topology-conf 1.2.5.1-2 alsa-ucm-conf 1.2.6.3-1ubuntu1 alsa-utils 1.2.6-1ubuntu1 amd64-microcode 3.20191218.1ubuntu2 anacron 2.3-31ubuntu2 apg 2.2.3.dfsg.1-5build2 apparmor3.0.4-2ubuntu2.1 apport 2.20.11-0ubuntu82.1 apport-gtk 2.20.11-0ubuntu82.1 apport-symptoms 0.24 appstream 0.15.2-2 apt 2.4.5 apt-config-icons0.15.2-2 apt-config-icons-hidpi 0.15.2-2 apt-utils 2.4.5 aptdaemon 1.1.1+bzr982-0ubuntu39 aptdaemon-data 1.1.1+bzr982-0ubuntu39 apturl 0.5.2ubuntu22 apturl-common 0.5.2ubuntu22 aspell 0.60.8-4build1 aspell-en 2018.04.16-0-1 at-spi2-core2.44.0-3 avahi-autoipd 0.8-5ubuntu5 avahi-daemon0.8-5ubuntu5 avahi-utils 0.8-5ubuntu5 baobab 41.0-2 base-files 12ubuntu4.1 base-passwd 3.5.52build1 bash5.1-6ubuntu1 bash-completion 1:2.11-5ubuntu1 bc 1.07.1-3build1 bind9-dnsutils 1:9.18.1-1ubuntu1.1 bind9-host 1:9.18.1-1ubuntu1.1 bind9-libs:amd641:9.18.1-1ubuntu1.1 binutils2.38-3ubuntu1 binutils-common:amd64 2.38-3ubuntu1 binutils-x86-64-linux-gnu 2.38-3ubuntu1 bluez 5.64-0ubuntu1 bluez-cups 5.64-0ubuntu1 bluez-obexd 5.64-0ubuntu1 bolt0.9.2-1 branding-ubuntu 0.10 brltty 6.4-4ubuntu2 bsdextrautils 2.37.2-4ubuntu3 bsdmainutils12.1.7+nmu3ubuntu2 bsdutils1:2.37.2-4ubuntu3 bubblewrap 0.6.1-1 build-essential 12.9ubuntu3 busybox-initramfs 1:1.30.1-7ubuntu3 busybox-static 1:1.30.1-7ubuntu3 bzip2 1.0.8-5build1 ca-certificates 20211016 ca-certificates-java20190909 cheese 41.1-1build1 cheese-common 41.1-1build1 colord 1.4.6-1 colord-data 1.4.6-1 command-not-found 22.04.0 console-setup 1.205ubuntu3 console-setup-linux 1.205ubuntu3 coreutils 8.32-4.1ubuntu1 cpio2.13+dfsg-7 cpp 4:11.2.0-1ubuntu1 cpp-11 11.2.0-19ubuntu1 cpp-9 9.4.0-5ubuntu1 cracklib-runtime2.9.6-3.4build4 crda3.18-1build1 cron3.0pl1-137ubuntu3 cups2.4.1op1-1ubuntu4.1 cups-browsed1.28.15-0ubuntu1 cups-bsd2.4.1op1-1ubuntu4.1 cups-client 2.4.1op1-1ubuntu4.1 cups-common 2.4.1op1-1ubuntu4.1 cups-core-drivers 2.4.1op1-1ubuntu4.1 cups-daemon 2.4.1op1-1ubuntu4.1 cups-filters1.28.15-0ubuntu1 cups-filters-core-drivers 1.28.15-0ubuntu1 cups-ipp-utils 2.4.1op1-1ubuntu4.1 cups-pk-helper 0.2.6-1ubuntu5 cups-ppdc 2.4.1op1-1ubuntu4.1 cups-server-common 2.4.1op1-1ubuntu4.1 dash0.5.11+git20210903+057cd650a4ed-3build1 dbus1.12.20-2ubuntu4 dbus-user-session 1.12.20-2ubuntu4 dbus-x111.12.20-2ubuntu4 dc 1.07.1-3build1 dconf-cli 0.40.0-3 dconf-gsettings-backend:amd64 0.40.0-3 dconf-service 0.40.0-3 dctrl-tools 2.24-3build2 debconf 1.5.79ubuntu1 debconf-i18n1.5.79ubuntu1 debianutils 5.5-1ubuntu2 deja-dup42.9-1ubuntu3 desktop-file-utils 0.26-1ubuntu3 dictionaries-common 1.28.14 diffutils 1:3.8-0ubuntu2 dirmngr 2.2.27-3ubuntu2.1 distro-info 1.1build1 distro-info-data0.52ubuntu0.1 dkms2.8.7-2ubuntu2 dmidecode 3.3-3 dmsetup 2:1.02.175-2.1ubuntu4 dmz-cursor-theme0.4.5ubuntu1 dns-root-data 2021011101 dnsmasq-base2.86-1.1ubuntu0.1 docbook-xml 4.5-11 dosfstools 4.2-1build3 dpkg1.21.1ubuntu2.1 dpkg-dev1.21.1ubuntu2.1 duplicity 0.8.21-1build1 e2fsprogs 1.46.5-2ubuntu1.1 ed 1.18-1 efibootmgr 17-1ubuntu2 eject 2.37.2-4ubuntu3 emacsen-common 3.0.4 enchant-2 2.3.2-1ubuntu2 eog 42.0-1 espeak-ng-data:amd641.50+dfsg-10 ethtool 1:5.16-1 evince 42.3-0ubuntu2 evince-common 42.3-0ubuntu2 evolution-data-server 3.44.2-0ubuntu1 evolution-data-server-common3.44.2-0ubuntu1 fakeroot1.28-1ubuntu1 fdisk 2.37.2-4ubuntu3 ffmpeg 7:4.4.2-0ubuntu0.22.04.1 file1:5.41-3 file-roller 3.42.0-1 findutils 4.8.0-1ubuntu3 firefox 1:1snap1-0ubuntu2 firmware-sof-signed 2.0-1ubuntu3 fontconfig 2.13.1-4.2ubuntu5 fontconfig-config 2.13.1-4.2ubuntu5 fonts-beng 2:1.3 fonts-beng-extra3.2.1-1 fonts-dejavu-core 2.37-2build1 fonts-deva 2:1.3 fonts-deva-extra3.0-5 fonts-droid-fallback1:6.0.1r16-1.1build1 fonts-freefont-ttf 20120503-10build1 fonts-gargi 2.0-5 fonts-gubbi 1.3-5build1 fonts-gujr 2:1.4 fonts-gujr-extra1.0.1-1 fonts-guru 2:1.3 fonts-guru-extra2.0-5 fonts-indic 2:1.4 fonts-kacst 2.01+mry-15 fonts-kacst-one 5.0+svn11846-10 fonts-kalapi1.0-4 fonts-khmeros-core 5.0-9ubuntu1
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
@kchsieh I tried doing what you said by enabling the oem meta then upgrading the distro, but I'm still getting a black screen with the webcam. I also ran $ dpkg-query -W and here are the results: accountsservice 0.6.55-0ubuntu12~20.04.5 acl 2.2.53-6 acpi-support0.143 acpid 1:2.0.32-1ubuntu1 adduser 3.118ubuntu2 adwaita-icon-theme 3.36.1-2ubuntu0.20.04.2 aisleriot 1:3.22.9-1 alsa-base 1.0.25+dfsg-0ubuntu5 alsa-topology-conf 1.2.2-1 alsa-ucm-conf 1.2.2-1ubuntu0.13 alsa-utils 1.2.2-1ubuntu2.1 amd64-microcode 3.20191218.1ubuntu1 anacron 2.3-29 apg 2.2.3.dfsg.1-5 app-install-data-partner19.04 apparmor2.13.3-7ubuntu5.1 apport 2.20.11-0ubuntu27.24 apport-gtk 2.20.11-0ubuntu27.24 apport-symptoms 0.23 appstream 0.12.10-2 apt 2.0.9 apt-config-icons0.12.10-2 apt-config-icons-hidpi 0.12.10-2 apt-utils 2.0.9 aptdaemon 1.1.1+bzr982-0ubuntu32.3 aptdaemon-data 1.1.1+bzr982-0ubuntu32.3 apturl 0.5.2ubuntu19 apturl-common 0.5.2ubuntu19 aspell 0.60.8-1ubuntu0.1 aspell-en 2018.04.16-0-1 at-spi2-core2.36.0-2 avahi-autoipd 0.7-4ubuntu7.1 avahi-daemon0.7-4ubuntu7.1 avahi-utils 0.7-4ubuntu7.1 baobab 3.34.0-1 base-files 11ubuntu5.5 base-passwd 3.5.47 bash5.0-6ubuntu1.2 bash-completion 1:2.10-1ubuntu1 bc 1.07.1-2build1 bind9-dnsutils 1:9.16.1-0ubuntu2.10 bind9-host 1:9.16.1-0ubuntu2.10 bind9-libs:amd641:9.16.1-0ubuntu2.10 binutils2.34-6ubuntu1.3 binutils-common:amd64 2.34-6ubuntu1.3 binutils-x86-64-linux-gnu 2.34-6ubuntu1.3 bluez 5.53-0ubuntu3.6 bluez-cups 5.53-0ubuntu3.6 bluez-obexd 5.53-0ubuntu3.6 bolt0.9.1-2~ubuntu20.04.1 branding-ubuntu 0.10 brltty 6.0+dfsg-4ubuntu6 bsdmainutils11.1.2ubuntu3 bsdutils1:2.34-0.1ubuntu9.3 bubblewrap 0.4.0-1ubuntu4 build-essential 12.8ubuntu1.1 busybox-initramfs 1:1.30.1-4ubuntu6.4 busybox-static 1:1.30.1-4ubuntu6.4 bzip2 1.0.8-2 ca-certificates 20211016~20.04.1 cheese 3.34.0-1ubuntu1 cheese-common 3.34.0-1ubuntu1 colord 1.4.4-2 colord-data 1.4.4-2 command-not-found 20.04.6 console-setup 1.194ubuntu3 console-setup-linux 1.194ubuntu3 coreutils 8.30-3ubuntu2 cpio2.13+dfsg-2ubuntu0.3 cpp 4:9.3.0-1ubuntu2 cpp-9 9.4.0-1ubuntu1~20.04.1 cracklib-runtime2.9.6-3.2 crda3.18-1build1 cron3.0pl1-136ubuntu1 cups2.3.1-9ubuntu1.2 cups-browsed1.27.4-1 cups-bsd2.3.1-9ubuntu1.2 cups-client 2.3.1-9ubuntu1.2 cups-common 2.3.1-9ubuntu1.2 cups-core-drivers 2.3.1-9ubuntu1.2 cups-daemon 2.3.1-9ubuntu1.2 cups-filters1.27.4-1 cups-filters-core-drivers 1.27.4-1 cups-ipp-utils 2.3.1-9ubuntu1.2 cups-pk-helper 0.2.6-1ubuntu3 cups-ppdc 2.3.1-9ubuntu1.2 cups-server-common 2.3.1-9ubuntu1.2 dash0.5.10.2-6 dbus1.12.16-2ubuntu2.2 dbus-user-session 1.12.16-2ubuntu2.2 dbus-x111.12.16-2ubuntu2.2 dc 1.07.1-2build1 dconf-cli 0.36.0-1 dconf-gsettings-backend:amd64 0.36.0-1 dconf-service 0.36.0-1 dctrl-tools 2.24-3 debconf 1.5.73 debconf-i18n1.5.73 debianutils 4.9.1 deja-dup40.7-0ubuntu1 desktop-file-utils 0.24-1ubuntu3 dictionaries-common 1.28.1 diffutils 1:3.7-3 dirmngr 2.2.19-3ubuntu2.2 distro-info 0.23ubuntu1 distro-info-data0.43ubuntu1.10 dkms2.8.1-5ubuntu2 dmidecode 3.2-3 dmsetup 2:1.02.167-1ubuntu1 dmz-cursor-theme0.4.5ubuntu1 dns-root-data 2019052802 dnsmasq-base2.80-1.1ubuntu1.5 docbook-xml 4.5-9 dosfstools 4.1-2 dpkg1.19.7ubuntu3.2 dpkg-dev1.19.7ubuntu3.2 duplicity 0.8.11.1612-1 e2fsprogs 1.45.5-2ubuntu1.1 ed 1.16-1 efibootmgr 17-1 eject 2.1.5+deb1+cvs20081104-14 emacsen-common 3.0.4 enchant-2 2.2.8-1ubuntu0.20.04.1 eog 3.36.3-0ubuntu1 espeak-ng-data:amd641.50+dfsg-6 evince 3.36.10-0ubuntu1 evince-common 3.36.10-0ubuntu1 evolution-data-server 3.36.5-0ubuntu1 evolution-data-server-common3.36.5-0ubuntu1 fakeroot1.24-1 fdisk 2.34-0.1ubuntu9.3 ffmpeg 7:4.2.7-0ubuntu0.1 file1:5.38-4 file-roller 3.36.3-0ubuntu1.1 findutils 4.7.0-1ubuntu1 firefox 102.0+build2-0ubuntu0.20.04.1 firefox-locale-en 102.0+build2-0ubuntu0.20.04.1 fontconfig 2.13.1-2ubuntu3 fontconfig-config 2.13.1-2ubuntu3 fonts-beng 2:1.2 fonts-beng-extra1.0-7 fonts-dejavu-core 2.37-1 fonts-deva 2:1.2 fonts-deva-extra3.0-5 fonts-droid-fallback1:6.0.1r16-1.1 fonts-freefont-ttf 20120503-10 fonts-gargi 2.0-4 fonts-gubbi 1.3-3 fonts-gujr 2:1.3 fonts-gujr-extra1.0.1-1 fonts-guru 2:1.2 fonts-guru-extra2.0-5 fonts-indic 2:1.3 fonts-kacst 2.01+mry-14 fonts-kacst-one 5.0+svn11846-10 fonts-kalapi1.0-3 fonts-khmeros-core 5.0-7ubuntu1 fonts-knda 2:1.2 fonts-lao 0.0.20060226-9ubuntu1 fonts-liberation1:1.07.4-11 fonts-liberation2 2.1.0-1
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
I just got a new XPS 13 plus 9320 and it came with Windows 11. I replaced it with Ubuntu 22.04, but the Webcam wasn't working so I replaced that with Ubuntu 20.04, but the webcam still doesn't seem to be working. I tried: $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 $ sudo apt install libcamhal-ipu6ep0 And now Firefox can detect it but https://webcamtests.com/ and Cheese just show a black screen. I'm pretty sure the hardware is fine since I tested it when it still had Windows 11 and it was running fine. I'm also fairly new to Linux so I feel like I just didn't install something, but anyone know what could be up with this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64
[Kernel-packages] [Bug 1911360] Re: Nvidia-Graphics-Drivers-460 Causes System To Not Boot
** Project changed: maas-deployer => maas -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911360 Title: Nvidia-Graphics-Drivers-460 Causes System To Not Boot Status in MAAS: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: After installing version 460, my 18.04 laptop stopping booting. Error reported: hdaudio hdaudioC0D2: Unable to bind codec. If I boot to grub, press 'e' and remove nomodeset, the systems boots normally. sudo lshw -C display *-display UNCLAIMED description: VGA compatible controller product: GM107GLM [Quadro M1000M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller cap_list configuration: latency=0 resources: memory:dc00-dcff memory:b000-bfff memory:c000-c1ff ioport:e000(size=128) memory:dd00-dd07 *-display UNCLAIMED description: VGA compatible controller product: HD Graphics P530 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list configuration: latency=0 resources: memory:db00-dbff memory:7000-7fff ioport:f000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1911360/+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 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I am seeing the same problem on a Dell Precision 7750. Ubuntu 20.04LTS kernel: 5.11.0-27-generic #29~20.04.1-Ubuntu SMP graphics: VGA compatible controller: NVIDIA Corporation TU106GLM [Quadro RTX 3000 Mobile / Max-Q] (rev a1) plus Intel i915 processor: Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz With nvidia-prime installed, running nvidia-settings presents three options: NVIDIA (Performance Mode), NVIDIA On-Demand, Power Save In Performance Mode, only the external HDMI port is active. Booting with no external monitor produces a blank laptop LCD display, but the external monitor is active. Using System Settings / Display, only the external monitor is detected. The keyboard secondary function key Fn F8 has no effect. Laptop screen is blank if booted without an external monitor connected. In On-Demand mode, only the laptop display is active and the external monitor has no output. System Settings / Display detects both monitors. The Fn F8 key pops up a display mode selection tool to select how the screens will be configured, if the external-monitor-only mode is selected, the laptop screen is blank, and there is no display on the external monitor. All other selections have no effect. In Power Save mode, only the laptop display is active and the external monitor has no output. System Settings / Display detects only the laptop monitor. The keyboard secondary function key Fn F8 has no effect. -- 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/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Chris, With the following packages installed and the workaround removed the issue no longer occurs for me when enabling Automatic Login via Settings. I have tested rebooting and starting from off several times and it worked as expected each time. Previously the issue occurred on every boot. gdm3 (3.36.3-0ubuntu0.20.04.1) libgdm1 (3.36.3-0ubuntu0.20.04.1) gir1.2-gdm-1.0:amd64 (3.36.3-0ubuntu0.20.04.1) nvidia-driver-450 (450.66-0ubuntu0.20.04.1) /etc/default/grub ``` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" ``` Of note, when the desktop loaded I was greeted with the Ubuntu new user "Connect Your Online Accounts" setup screen and what appeared to be a fresh users settings. If this happens to anyone here there's a helpful README.txt in ~/ reminding you that you encrypted your home directory, and to run ecryptfs-mount-private to gain access. Oh yeah... You can also expect to be prompted to unlock your login keyring at some random moment a few minutes after the desktop loads. Anyway, wonderful work, and thanks to everyone who helped fix this, at least for me. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: In Progress Status in gdm3 package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-430 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-435 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-440 package in Ubuntu: Invalid Status in gdm3 source package in Focal: Fix Committed Status in gnome-session source package in Focal: Invalid Status in grub2 source package in Focal: Invalid Status in nvidia-graphics-drivers-390 source package in Focal: Invalid Status in nvidia-graphics-drivers-430 source package in Focal: Invalid Status in nvidia-graphics-drivers-435 source package in Focal: Invalid Status in nvidia-graphics-drivers-440 source package in Focal: Invalid Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default
[Kernel-packages] [Bug 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode
I had difficulties installing Kernel 5.8-rc3. But I tested 5.8.1: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.1/ Lenovo Ideapad L340-17API (81LY000KGE): No black screen in 6 attempts. The notebook also booted much faster. Before, there had always been a kind of "pause", during which it may be that the further boot process either failed (black screen) or continued. -- 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/1870971 Title: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode Status in linux package in Ubuntu: Confirmed Status in vlc package in Ubuntu: Invalid Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05
[Kernel-packages] [Bug 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode
... further to # 30: it would have been nice, but actually the Lenovo Ideapad L340-17API (81LY000KGE) still occasionally gets a "black screen". Weird: after numerous positive attempts (something like 10), the odd boot goes to black screen. Then a "series" of black screens seems to start. -- 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/1870971 Title: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode Status in linux package in Ubuntu: Confirmed Status in vlc package in Ubuntu: Invalid Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180 RSI: 8cc9ac4609f8 RDI: апр 05 20:46:45 kernel: RBP: a4dc806d7d60 R08: 047a R09: 0004 апр 05 20:46:45 kernel: R10: R11: 0001 R12: 8cc9ac463c00 апр 05 20:46:45 kernel: R13: 8cc9a63c7980 R14: 8cc9ac460800 R15: 8cc9a6fc9140 апр 05 20:46:45 kernel: FS: () GS:8cc9b88c() knlGS: апр 05 20:46:45 kernel: CS: 0010 DS: ES: CR0: 80050033 апр 05 20:46:45 kernel: CR2: 7f275ff6c000 CR3: 0001af148000 CR4: 003406e0 апр 05 20:46:45 kernel: Call Trace: апр 05 20:46:45 kernel:
[Kernel-packages] [Bug 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode
I have experienced the problem with the black screen in battery mode in all my (fairly new) AMD notebooks (bought this year; all AMD Ryzen 5 3500U), running Kubuntu 20.04. As of today the status is as follows: - Lenovo Ideapad L340-17API (81LY000KGE) (possibly identical to the one in #21). Kernel 5.4.0-42 generic: The problem now seems to be fixed, with all available updates installed (I booted 10 times without power cord: works perfectly). - HP Notebook - 17-ca1010ng (8XM98EA). Only used to boot to black screen from April to June 2020 (100%). Current status: Kernel 5.4.0-42 generic: 50% hit-and-miss rate. For ten boot attempts, about 5 result in a black screen and five in a flawless start. The workaround here is to just keep booting, until the notebook finally starts properly. - HP Notebook - 17-ca1124ng (8KW34EA): The black-screen problem was 100% in evidence in June 2020 with all updates installed. The computer is out of my hands, so I don't know the current status. -- 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/1870971 Title: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode Status in linux package in Ubuntu: Confirmed Status in vlc package in Ubuntu: Invalid Bug description: Freshly installed Xubuntu 20.04 shows black screen instead of login screen upon boot on Lenovo Ideapad L340-17API. It is not possible to chvt to text terminal when boot is stuck on black screen. Booting with 'nomodeset' kernel option works properly but is not an option (e.g. screen brightness is not adjustable in this case). Another workaround is to ssh to laptop and run systemctl restart display-manager.service. After 5-10 seconds upon executing this command perfectly working login screen appears. Check dmesg. There is apparently related messages from amdgpu driver: ... апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3 апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start апр 05 20:46:45 kernel: [drm] recover vram bo from shadow done апр 05 20:46:45 kernel: [drm] Skip scheduling IBs! апр 05 20:46:45 kernel: [ cut here ] апр 05 20:46:45 kernel: WARNING: CPU: 3 PID: 793 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Modules linked in: cmac algif_hash algif_skcipher af_alg bnep zram nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_nhlt snd_hda_codec > апр 05 20:46:45 kernel: CPU: 3 PID: 793 Comm: kworker/3:4 Tainted: G OE 5.4.0-21-generic #25-Ubuntu апр 05 20:46:45 kernel: Hardware name: LENOVO 81LY/LNVNB161216, BIOS ARCN32WW 07/11/2019 апр 05 20:46:45 kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] апр 05 20:46:45 kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] апр 05 20:46:45 kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 83 7f 4c апр 05 20:46:45 kernel: RSP: 0018:a4dc806d7d28 EFLAGS: 00010246 апр 05 20:46:45 kernel: RAX: RBX: 0001 RCX: апр 05 20:46:45 kernel: RDX: 8cc9a6fc9180
[Kernel-packages] [Bug 1848771] Re: Reboot after resume from suspend (deep)
So I don't know if this will help or not, but I have troubleshot my P50 turns off on resume from sleep issue. I have Ubuntu on a 2 TB Samsung 970 EVO NVME SSD (with 2B2QEXM7 firmware). If I remove the password (User and Master) from this disk resume from sleep works. I have 2 other Samsung SSDs in the machine (a 1 TB 840 EVO SATA and 1 TB 960 Pro NVME) and I can put passwords on both of them with no problem. Looking on various forums lots of people are reporting sleep/wake issues with the 970 EVO NVME drive. Windows users report that removing the Samsung driver and just using the Windows driver resolves the problems, but I don't know how to change a driver on Ubuntu, or if it's even possible. A Mac user reported that upgrading the drive firmware seemed to fix the problem, but I seem to already be at the latest firmware version. Any tips on how to switch drivers or what to do next would be appreciated. I can run with the drive not password protected, but I don't like it. -- 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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+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 1848771] Re: Reboot after resume from suspend (deep)
So my fix worked for a couple of days, then stopped working. I think there was a kernal upgrade a couple of days ago (on Ubuntu 20.04, now running 5.4.0-37-generic), and I am now shutting down on resume. Sleeps normally, LED blinking, displays off, no heat produced. When I open the lid the LED in the power switch goes out after a second so and I need to press it to reboot. -- 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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+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 1848771] Re: Reboot after resume from suspend (deep)
Add me to the list of those having this issue, but also have a partial fix. I am running a Thinkpad P50 with Nvidia display adapter. 18.04 was great, never any issues with suspend or resume. I upgraded to 20.04 a couple of weeks ago and immediately began encountering the reboot on resume issue. Suspend worked fine, the LED on the cover dimmed and brightened to indicate it was asleep, external displays went into power save, etc. But when trying to resume it rebooted from scratch every time. I found this article https://itsfoss.com/ubuntu-close-lid-suspend/ and followed the steps in it. To my surprise, pm-utils was not installed, so I installed it. I also made the suggested edits to /etc/systemd/logind.conf plus a few more, my edited file is below. After these steps, I can now resume from suspend successfully. My laptop display remains dark but the external monitors come on and show the desktop. If I logout and back in then all is fine and all displays work. Here is my edited config file: [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 HandlePowerKey=suspend HandleSuspendKey=suspend #HandleHibernateKey=hibernate HandleLidSwitch=suspend HandleLidSwitchExternalPower=suspend HandleLidSwitchDocked=suspend PowerKeyIgnoreInhibited=no SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no LidSwitchIgnoreInhibited=no #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=819 -- 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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+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 1835660] Re: initramfs unpacking failed
Regenerating initramfs as suggested by Dan resolved this issue for me. I did not attempt to change compression or change any settings in the BIOS. -- 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/1835660 Title: initramfs unpacking failed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+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 1858231] Re: QCA6174 Wifi adapter not functional
I upgraded to 5.5-rc6 and this appeared to fix things. I did not need to update the firmware. -- 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/1858231 Title: QCA6174 Wifi adapter not functional Status in linux package in Ubuntu: Incomplete Bug description: The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from the live cd and an install. It is functional in a 18.04 install. At boot, the kernel log contains the following messages in 19.10: [ 15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity mapping [ 15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12 [ 15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 0: -12 [ 15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: -12 [ 15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12 [ 15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ed 1932 F pulseaudio /dev/snd/controlC0: ed 1932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 14:31:15 2020 InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. Precision 7540 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0499T7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd07/24/2019:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858231/+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 1858231] Re: QCA6174 Wifi adapter not functional
Sorry, wasn't getting launchpad emails. I'll try with the latest kernel and firmware shortly. -- 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/1858231 Title: QCA6174 Wifi adapter not functional Status in linux package in Ubuntu: Incomplete Bug description: The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from the live cd and an install. It is functional in a 18.04 install. At boot, the kernel log contains the following messages in 19.10: [ 15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity mapping [ 15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12 [ 15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 0: -12 [ 15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: -12 [ 15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12 [ 15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ed 1932 F pulseaudio /dev/snd/controlC0: ed 1932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 14:31:15 2020 InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. Precision 7540 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0499T7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd07/24/2019:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858231/+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 1858231] Re: QCA6174 Wifi adapter not functional
** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858231/+attachment/5317468/+files/lspci-vnvn.log -- 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/1858231 Title: QCA6174 Wifi adapter not functional Status in linux package in Ubuntu: New Bug description: The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from the live cd and an install. It is functional in a 18.04 install. At boot, the kernel log contains the following messages in 19.10: [ 15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity mapping [ 15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12 [ 15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 0: -12 [ 15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: -12 [ 15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12 [ 15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ed 1932 F pulseaudio /dev/snd/controlC0: ed 1932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 14:31:15 2020 InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. Precision 7540 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0499T7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd07/24/2019:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858231/+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 1858231] [NEW] QCA6174 Wifi adapter not functional
Public bug reported: The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from the live cd and an install. It is functional in a 18.04 install. At boot, the kernel log contains the following messages in 19.10: [ 15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity mapping [ 15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12 [ 15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 0: -12 [ 15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: -12 [ 15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12 [ 15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ed 1932 F pulseaudio /dev/snd/controlC0: ed 1932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 14:31:15 2020 InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. Precision 7540 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0499T7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd07/24/2019:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0499T7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "kernel version" https://bugs.launchpad.net/bugs/1858231/+attachment/5317453/+files/version.log -- 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/1858231 Title: QCA6174 Wifi adapter not functional Status in linux package in Ubuntu: New Bug description: The QCA6174 Wifi adapter is not functional in Ubuntu 19.10, both from the live cd and an install. It is functional in a 18.04 install. At boot, the kernel log contains the following messages in 19.10: [ 15.665517] ath10k_pci :6f:00.0: DMAR: 32bit DMA uses non-identity mapping [ 15.665524] ath10k_pci :6f:00.0: failed to alloc CE src ring 0: -12 [ 15.665527] ath10k_pci :6f:00.0: failed to allocate copy engine pipe 0: -12 [ 15.665528] ath10k_pci :6f:00.0: failed to allocate copy engine pipes: -12 [ 15.665530] ath10k_pci :6f:00.0: failed to setup resource: -12 [ 15.667627] ath10k_pci: probe of :6f:00.0 failed with error -12 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ed 1932 F pulseaudio /dev/snd/controlC0: ed 1932 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 14:31:15 2020 InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. Precision 7540 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=UUID=f393b98c-0896-48e8-a242-e6d8d5b262bf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Dell
[Kernel-packages] [Bug 1848739] Re: [linux-azure] Patch to prevent possible data corruption
For reference, this is the extensive upstream kernel discussion
https://bugzilla.kernel.org/show_bug.cgi?id=201685
The filesystem corruption issue is real, not theoretical, and
was the extensive discussion of problems experienced during the early days of
4.19:
** Bug watch added: Linux Kernel Bug Tracker #201685
https://bugzilla.kernel.org/show_bug.cgi?id=201685
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1848739
Title:
[linux-azure] Patch to prevent possible data corruption
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
There are three patches that prevent possible data corruption. The
three commits are:
aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when
requeue")
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")
18.04 has all three of these patches. 16.04 has two out of the three,
but it is missing commit c616cbee97ae.
We would like to request commit c616cbee97ae be included in the 16.04 kernel:
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+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 1848739] Re: [linux-azure] Patch to prevent possible data corruption
This data corruption issue was written about extensively here
https://lwn.net/Articles/774440/
as part of the early 4.19 days when a number of folks were seeing ext4
filesystem corruption as a consequence of the blk-mq bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1848739
Title:
[linux-azure] Patch to prevent possible data corruption
Status in linux-azure package in Ubuntu:
Confirmed
Bug description:
There are three patches that prevent possible data corruption. The
three commits are:
aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when
requeue")
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")
18.04 has all three of these patches. 16.04 has two out of the three,
but it is missing commit c616cbee97ae.
We would like to request commit c616cbee97ae be included in the 16.04 kernel:
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+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 1808251] Re: systemctl disable fails to clean up override
No applicable logs ** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808251 Title: systemctl disable fails to clean up override Status in systemd package in Ubuntu: Confirmed Bug description: I am using Ubuntu 16.04.4 LTS and package version systemd: Installed: 229-4ubuntu21.10 Candidate: 229-4ubuntu21.10 Version table: *** 229-4ubuntu21.10 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages When a unit is enabled with systemctl enable and overrides are applied with systemctl edit and subsequently the unit is disabled with systemctl disable the override file that is created and its directory /etc/systemd/system/.d/override.conf is not removed. Subsequent attempts to enable the same unit will fail with the misleading and unhelpful error message Failed to execute operation: Invalid argument Removing the override file and directory will fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808251/+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 1808251] Re: systemctl disable fails to clean up override
This bug is easily reproduced and will not leave any meaningful log entries. -- 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/1808251 Title: systemctl disable fails to clean up override Status in systemd package in Ubuntu: Confirmed Bug description: I am using Ubuntu 16.04.4 LTS and package version systemd: Installed: 229-4ubuntu21.10 Candidate: 229-4ubuntu21.10 Version table: *** 229-4ubuntu21.10 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages When a unit is enabled with systemctl enable and overrides are applied with systemctl edit and subsequently the unit is disabled with systemctl disable the override file that is created and its directory /etc/systemd/system/.d/override.conf is not removed. Subsequent attempts to enable the same unit will fail with the misleading and unhelpful error message Failed to execute operation: Invalid argument Removing the override file and directory will fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808251/+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 1808251] [NEW] systemctl disable fails to clean up override
Public bug reported: I am using Ubuntu 16.04.4 LTS and package version systemd: Installed: 229-4ubuntu21.10 Candidate: 229-4ubuntu21.10 Version table: *** 229-4ubuntu21.10 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages When a unit is enabled with systemctl enable and overrides are applied with systemctl edit and subsequently the unit is disabled with systemctl disable the override file that is created and its directory /etc/systemd/system/.d/override.conf is not removed. Subsequent attempts to enable the same unit will fail with the misleading and unhelpful error message Failed to execute operation: Invalid argument Removing the override file and directory will fix the problem. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808251 Title: systemctl disable fails to clean up override Status in linux package in Ubuntu: New Bug description: I am using Ubuntu 16.04.4 LTS and package version systemd: Installed: 229-4ubuntu21.10 Candidate: 229-4ubuntu21.10 Version table: *** 229-4ubuntu21.10 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages When a unit is enabled with systemctl enable and overrides are applied with systemctl edit and subsequently the unit is disabled with systemctl disable the override file that is created and its directory /etc/systemd/system/.d/override.conf is not removed. Subsequent attempts to enable the same unit will fail with the misleading and unhelpful error message Failed to execute operation: Invalid argument Removing the override file and directory will fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808251/+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 1585364] Re: CVE-2014-8181
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Edward Haigh (funcylambda) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1585364 Title: CVE-2014-8181 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Won't Fix Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Won't Fix Status in linux-lts-utopic source package in Vivid: Won't Fix Status in linux-lts-vivid source package in Vivid: Won't Fix Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Won't Fix Status in linux-raspi2 source package in Vivid: Won't Fix Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: Won't Fix Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta sou
[Kernel-packages] [Bug 1585364] Re: CVE-2014-8181
** Changed in: linux (Ubuntu Xenial) Assignee: Edward Haigh (funcylambda) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1585364 Title: CVE-2014-8181 Status in linux package in Ubuntu: New Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: New Status in linux-armadaxp source package in Precise: New Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: New Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: New Status in linux source package in Trusty: New Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: New Status in linux-lts-vivid source package in Trusty: New Status in linux-lts-wily source package in Trusty: New Status in linux-lts-xenial source package in Trusty: New Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Won't Fix Status in linux-armadaxp source package in Vivid: New Status in linux-flo source package in Vivid: New Status in linux-goldfish source package in Vivid: New Status in linux-lts-quantal source package in Vivid: New Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Won't Fix Status in linux-lts-utopic source package in Vivid: Won't Fix Status in linux-lts-vivid source package in Vivid: Won't Fix Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: Won't Fix Status in linux-raspi2 source package in Vivid: Won't Fix Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: Won't Fix Status in linux source package in Wily: New Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid Status in linux-lts-saucy source package in Wily: Invalid Status in linux-lts-trusty source package in Wily: Invalid Status in linux-lts-utopic source package in Wily: Invalid Status in linux-lts-vivid source package in Wily: Invalid Status in linux-lts-wily source package in Wily: Invalid Status in linux-lts-xenial source package in Wily: Invalid Status in linux-mako source package in Wily: New Status in linux-manta sou
[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460
HI guys, Im trying to use my second Monitor with this videocard, i do not know if i have the same issue but my HDMI monitor just would not work. it worked before the update and only with kernels until 4.13... i don't know if i have to put some info here or somewhere else. thanks. -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1764645] Re: Bluetooth not working
I am on Linux version 4.15.0-33-generic (buildd@lcy01-amd64-024) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #36-Ubuntu SMP and the bluetooth
is not working.
Please help.
--
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/1764645
Title:
Bluetooth not working
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
== SRU Justification ==
A regression was discovered in Bionic. The regression was introduced by
mainline commit f44cb4b19ed4, which then made it's way into Bionic in
4.15.0-14 as commit c91729972ac6 via stable updates.
This regression is fixed by mainline commit 803cdb8ce584. Commit
803cdb8ce584 was also cc'd to stable. However, it has not landed in
upstream stable 4.15 or Bionic.
== Fix ==
803cdb8ce584 ("Bluetooth: btusb: Apply QCA Rome patches for some ATH3012
models")
== Regression Potential ==
Low. This fix has also been cc'd to upstream stable, so it has had
additonal upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I've installed the Ubuntu Bionic Beta 2 and everything works fine but
the bluetooth (perfectly working with Xenial). In bluetooth control
panel the slider is impossible to move to "on".
1) Ubuntu Release (via 'lsb_release -rd')
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
2) Version of package (apt-cache policy gnome-bluetooth)
gnome-bluetooth:
Installato: 3.28.0-2
Candidato: 3.28.0-2
Tabella versione:
*** 3.28.0-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
I expected to switch on the bluetooth.
4) What happened instead
Bluetooth won't switch on.
5) Output of rfkill list is:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is:
03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless
Network Adapter [168c:0034] (rev 01)
Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half-
size Mini PCIe Card [1a56:2003]
Kernel driver in use: ath9k
Kernel modules: ath9k
04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit
Ethernet [1969:10a1] (rev 10)
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd
Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc.
AR3012 Bluetooth 4.0
Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 17.715399] Bluetooth: Core ver 2.22
[ 17.715414] Bluetooth: HCI device and connection manager initialized
[ 17.715416] Bluetooth: HCI socket layer initialized
[ 17.715418] Bluetooth: L2CAP socket layer initialized
[ 17.715422] Bluetooth: SCO socket layer initialized
[ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102
[ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 18.600649] Bluetooth: BNEP filters: protocol multicast
[ 18.600651] Bluetooth: BNEP socket layer initialized
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stormy 1484 F pulseaudio
/dev/snd/controlC0: stormy 1484 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 08:46:30 2018
HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: ASUSTeK COMPUTER INC. G750JH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
[Kernel-packages] [Bug 1764645] Re: Bluetooth not working
i have the same exact problem lsusb | grep -i blue Bus 003 Device 002: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 uname -a Linux ednote 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic -- 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/1764645 Title: Bluetooth not working Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: I've installed the Ubuntu Bionic Beta 2 and everything works fine but the bluetooth (perfectly working with Xenial). In bluetooth control panel the slider is impossible to move to "on". 1) Ubuntu Release (via 'lsb_release -rd') Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) Version of package (apt-cache policy gnome-bluetooth) gnome-bluetooth: Installato: 3.28.0-2 Candidato: 3.28.0-2 Tabella versione: *** 3.28.0-2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I expected to switch on the bluetooth. 4) What happened instead Bluetooth won't switch on. 5) Output of rfkill list is: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 6) Output of lspci -knn | grep Net -A3; lsusb; dmesg | grep -i blue is: 03:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1202 Half- size Mini PCIe Card [1a56:2003] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 04f2:b414 Chicony Electronics Co., Ltd Bus 003 Device 003: ID 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Bus 003 Device 002: ID 0b05:17c4 ASUSTek Computer, Inc. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 17.715399] Bluetooth: Core ver 2.22 [ 17.715414] Bluetooth: HCI device and connection manager initialized [ 17.715416] Bluetooth: HCI socket layer initialized [ 17.715418] Bluetooth: L2CAP socket layer initialized [ 17.715422] Bluetooth: SCO socket layer initialized [ 17.723207] Bluetooth: hci0: don't support firmware rome 0x1102 [ 18.600648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.600649] Bluetooth: BNEP filters: protocol multicast [ 18.600651] Bluetooth: BNEP socket layer initialized ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stormy 1484 F pulseaudio /dev/snd/controlC0: stormy 1484 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 08:46:30 2018 HibernationDevice: RESUME=UUID=3f513ca9-6817-4099-9718-fee68d68ec11 InstallationDate: Installed on 2018-04-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: ASUSTeK COMPUTER INC. G750JH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JH.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC.
[Kernel-packages] [Bug 1736593] Re: ThunderX: TX failure unless checksum offload disabled
Thanks Dann. Scott is testing this and has found an additional issue, but we're not sure yet whether it's directly related or independent. He'll file a more detailed report or open another Launchpad as appropriate. -- 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/1736593 Title: ThunderX: TX failure unless checksum offload disabled Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: [Impact] Most attempts to use IPv6 on the ThunderX NIC will fail. [Test Case] Attempt an IPv6 TCP connection: $ wget -6 'http://www.kernel.org/' The connection will time out. [Regression Risk] The fix is upstream, and is limited to the ThunderX nicvf driver. [Workaround] Disable TX checksum offload: $ ethtool -K eth0 tx off [More Details] The issue first appears in Linux 4.12. A fix from Cavium has been merged upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736593/+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 1736593] Re: ThunderX: TX failure unless checksum offload disabled
Thank you. We will be testing this new kernel at Packet and will report results. -- 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/1736593 Title: ThunderX: TX failure unless checksum offload disabled Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: Fix Committed Bug description: [Impact] Most attempts to use IPv6 on the ThunderX NIC will fail. [Test Case] Attempt an IPv6 TCP connection: $ wget -6 'http://www.kernel.org/' The connection will time out. [Regression Risk] The fix is upstream, and is limited to the ThunderX nicvf driver. [Workaround] Disable TX checksum offload: $ ethtool -K eth0 tx off [More Details] The issue first appears in Linux 4.12. A fix from Cavium has been merged upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736593/+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 1683587] Re: LSI Harpoon support in megaraid_sas module
What I did to get it working for now is creating a modified ISO with kernel version v4.11.12 that has support for this RAID controller. Works fine, so hope this patch is applied to the default kernel that is shipped with Ubuntu soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683587 Title: LSI Harpoon support in megaraid_sas module Status in linux package in Ubuntu: Confirmed Bug description: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. The kernel patch to support these new devices is: https://github.com/torvalds/linux/commit/45f4f2eb3da3cbff02c3d77c784c81320c733056 The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Trusty onwards. The upstream commit is going in for 4.11, so this will need to be backported to v3.13/v4.4/v4.8/v4.10. I am working on SRU patches for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683587/+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 1683587] Re: LSI Harpoon support in megaraid_sas module
Hi I have a new Dell PowerEdge R640 server a PERC H740P RAID Controller. I tried to install the latest 16.04 LTS Ubuntu on it, but during installation it failed to detect any disks. After pulling my hair out while diagnosing this issue for hours I finally found this thread. Can anyone confirm that the behavior I'm seeing (no disks showing up during setup) is because of the lacking support? If so, is there any way I can test this or to help to speed up the release, as I need to setup this server with Ubuntu but basically I'm stuck due to this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683587 Title: LSI Harpoon support in megaraid_sas module Status in linux package in Ubuntu: Confirmed Bug description: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. The kernel patch to support these new devices is: https://github.com/torvalds/linux/commit/45f4f2eb3da3cbff02c3d77c784c81320c733056 The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Trusty onwards. The upstream commit is going in for 4.11, so this will need to be backported to v3.13/v4.4/v4.8/v4.10. I am working on SRU patches for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683587/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
@Marc, thanks a lot mate! you are saving the day of all of us. Hope u are not from the NSA heheheh. thanks a lot mate! -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Hi guys, i think we should do something about this gigabyte-situation, kinda of writing then a bunch of letters from all of us, there is also a bunch of ppl on reddit having this same problem, and still, gigabyte is not giving a breath to address this situation... do we really have to accept this kinda answers "we do not support linux, see by yourself what u do"... i think we should make us ourselves to a big voice of this thing, so that gigabyte stop threating our problem like nothing they have to do with... any suggestions? -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+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 1687241] Re: package linux-headers-4.10.0-20 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': O
Just attempting to install package results in: root@edwardnewman-MacBookPro:~# dpkg -i /var/cache/apt/archives/linux-headers-4.10.0-20_4.10.0-20.22_all.deb (Reading database ... 194747 files and directories currently installed.) Preparing to unpack .../linux-headers-4.10.0-20_4.10.0-20.22_all.deb ... Unpacking linux-headers-4.10.0-20 (4.10.0-20.22) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.10.0-20_4.10.0-20.22_all.deb (--install): unable to open '/usr/src/linux-headers-4.10.0-20/drivers/dma-buf/Kconfig.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-headers-4.10.0-20_4.10.0-20.22_all.deb -- 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/1687241 Title: package linux-headers-4.10.0-20 (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: Trying to upgrade Linux ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-headers-4.10.0-20 (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: edwardnewman 2325 F pulseaudio /dev/snd/controlC0: edwardnewman 2325 F pulseaudio Date: Sat Apr 29 21:45:39 2017 DuplicateSignature: package:linux-headers-4.10.0-20:(not installed) Unpacking linux-image-extra-4.10.0-20-generic (4.10.0-20.22) ... dpkg: error processing archive /tmp/apt-dpkg-install-CzdVt6/13-linux-image-extra-4.10.0-20-generic_4.10.0-20.22_amd64.deb (--unpack): unable to open '/lib/modules/4.10.0-20-generic/kernel/drivers/nfc/fdp/fdp.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=387f71ce-92f9-40b3-9ad6-937b9da0b515 InstallationDate: Installed on 2017-04-22 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-4.10.0-20 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B21.1612230252 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B21.1612230252:bd12/23/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687241/+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 1687241] Re: package linux-headers-4.10.0-20 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': O
@jsalisbury Ran steps with same result root@edwardnewman-MacBookPro:~# apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-headers-4.10.0-20 The following NEW packages will be installed: linux-headers-4.10.0-20 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. 27 not fully installed or removed. Need to get 0 B/10.6 MB of archives. After this operation, 74.3 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 194747 files and directories currently installed.) Preparing to unpack .../linux-headers-4.10.0-20_4.10.0-20.22_all.deb ... Unpacking linux-headers-4.10.0-20 (4.10.0-20.22) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.10.0-20_4.10.0-20.22_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.10.0-20/include/linux/parser.h.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-headers-4.10.0-20_4.10.0-20.22_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@edwardnewman-MacBookPro:~# apt-get clean root@edwardnewman-MacBookPro:~# apt-get update Hit:1 http://repo.saltstack.com/apt/ubuntu/16.04/amd64/latest xenial InRelease Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease Hit:3 http://us.archive.ubuntu.com/ubuntu zesty InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu zesty-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu zesty-backports InRelease Hit:6 http://dl.google.com/linux/chrome/deb stable Release Get:7 http://security.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB] Hit:8 http://ppa.launchpad.net/nm-l2tp/network-manager-l2tp/ubuntu zesty InRelease Fetched 89.2 kB in 20s (4,297 B/s) Reading package lists... Done root@edwardnewman-MacBookPro:~# apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-headers-4.10.0-20 The following NEW packages will be installed: linux-headers-4.10.0-20 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. 27 not fully installed or removed. Need to get 10.6 MB of archives. After this operation, 74.3 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu zesty-updates/main amd64 linux-headers-4.10.0-20 all 4.10.0-20.22 [10.6 MB] Fetched 10.6 MB in 22s (473 kB/s) (Reading database ... 194747 files and directories currently installed.) Preparing to unpack .../linux-headers-4.10.0-20_4.10.0-20.22_all.deb ... Unpacking linux-headers-4.10.0-20 (4.10.0-20.22) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-4.10.0-20_4.10.0-20.22_all.deb (--unpack): unable to open '/usr/src/linux-headers-4.10.0-20/arch/x86/ras/Makefile.dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-headers-4.10.0-20_4.10.0-20.22_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) root@edwardnewman-MacBookPro:~# -- 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/1687241 Title: package linux-headers-4.10.0-20 (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Incomplete Bug description: Trying to upgrade Linux ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-headers-4.10.0-20 (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: edwardnewman 2325 F pulseaudio /dev/snd/controlC0: edwardnewman 2325 F pulseaudio Date: Sat Apr 29 21:45:39 2017 DuplicateSignature: package:linux-headers-4.10.0-20:(not installed) Unpacking linux-image-extra-4.10.0-20-generic (4.10.0-20.22) ... dpkg: error processing archive /tmp/apt-dpkg-install-CzdVt6/13-linux-image-extra-4.10.0-20-generic_4.10.0-20.22_amd64.deb (--unpack): unable to open
[Kernel-packages] [Bug 1687241] [NEW] package linux-headers-4.10.0-20 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new':
Public bug reported: Trying to upgrade Linux ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-headers-4.10.0-20 (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: edwardnewman 2325 F pulseaudio /dev/snd/controlC0: edwardnewman 2325 F pulseaudio Date: Sat Apr 29 21:45:39 2017 DuplicateSignature: package:linux-headers-4.10.0-20:(not installed) Unpacking linux-image-extra-4.10.0-20-generic (4.10.0-20.22) ... dpkg: error processing archive /tmp/apt-dpkg-install-CzdVt6/13-linux-image-extra-4.10.0-20-generic_4.10.0-20.22_amd64.deb (--unpack): unable to open '/lib/modules/4.10.0-20-generic/kernel/drivers/nfc/fdp/fdp.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=387f71ce-92f9-40b3-9ad6-937b9da0b515 InstallationDate: Installed on 2017-04-22 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-4.10.0-20 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B21.1612230252 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B21.1612230252:bd12/23/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check zesty -- 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/1687241 Title: package linux-headers-4.10.0-20 (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: New Bug description: Trying to upgrade Linux ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-headers-4.10.0-20 (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: edwardnewman 2325 F pulseaudio /dev/snd/controlC0: edwardnewman 2325 F pulseaudio Date: Sat Apr 29 21:45:39 2017 DuplicateSignature: package:linux-headers-4.10.0-20:(not installed) Unpacking linux-image-extra-4.10.0-20-generic (4.10.0-20.22) ... dpkg: error processing archive /tmp/apt-dpkg-install-CzdVt6/13-linux-image-extra-4.10.0-20-generic_4.10.0-20.22_amd64.deb (--unpack): unable to open '/lib/modules/4.10.0-20-generic/kernel/drivers/nfc/fdp/fdp.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.10.0-20/include/linux/agp_backend.h.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=387f71ce-92f9-40b3-9ad6-937b9da0b515 InstallationDate: Installed on 2017-04-22 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
i tried the wrong kernel, now i am using that 4.10.3 (ryzen) kernel, it works fine -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
i dont understand why i the Joseph's kernel wont let me type (kernel is on, but aint gonna work) anything :( it looks like the solution for me for, at least temporal... :( -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Hi Marc, yep i got that.. i desinstalled it so that it would work better. im running 16.04, i dont know actually what to do, cuz i fond now way to boot using the keyboard with that kernel, and also both monitors (i might solve that with the graphic card, but i need to use the keyboard for that.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
i need to find* sorry, i am writing from my Android device. -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
i treid to boot with Joseph's kernel and the machine booted, but there is no way for me to use my keyboard :S -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Hi again guys, ive tried Joseph's kernel but this is what i got... linux-headers-4.10.0-19-generic (4.10.0-19.21~lp1671360) wird eingerichtet ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic Error! Bad return status for module build on kernel: 4.10.0-19-generic (x86_64) Consult /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/make.log for more information. linux-image-4.10.0-19-generic (4.10.0-19.21~lp1671360) wird eingerichtet ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/rtl8812au-dkms.0.crash' Error! Bad return status for module build on kernel: 4.10.0-19-generic (x86_64) Consult /var/lib/dkms/rtl8812au/4.3.8.12175.20140902+dfsg/build/make.log for more information. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic update-initramfs: Generating /boot/initrd.img-4.10.0-19-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.10.0-19-generic /boot/vmlinuz-4.10.0-19-generic it looks like the driver of one of my cards does not like this kernel :S -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Thanks Milosz! actually i couldnt start the pc like that, im still using the kernel 4.7.8, the good thing is that all cores wore good, like i said... the problem is that the Network cards are totally crazy and the soundcard just does not work anylonger since a couple of weeks. -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
i forgot to mention that i use the f4 version of the bios -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
hi guys, maybe my information helps a bit (at least a hope) my PC is a 1700x with the gaming aorus 5 from gigabyte (GA-AX370-Gaming K5), got 32 GB RAM but i dont think that it has much to do with all the problems metioned above. i got all those errors, and i can only use my computer with my new graphic card (all cores and stuff) using the kernel "4.7.8-040708-generic"... there is no other kernel that works with that graphic card (rx 460) for that reason im using it... and other newer kernel just failed... i have like 24 newer kernels installed... all of em come with this IRQ erros and stuff... but i did some check, i changed the default grub, i wrote (if am not mistaken) acpi=off noacpi or something like that (sorry i cant remember it right now, im not at my pc) and i got this irq 7 issue even with the kernel im using... so i had to changed the default grub... and i could work again with the 4.7.8... kernel i hope this information can help you somehow. -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio
kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: Edward-admin 1721 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28 HotplugNewDevices: - + HotplugNewMounts: - + InstallationDate: Installed on 2016-12-19 (15 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: - Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. -Users in the 'systemd-journal' group can see all messages. Pass -q to -turn off this notice. - No journal files were opened due to insufficient permissions. + Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. + Users in the 'systemd-journal' group can see all messages. Pass -q to + turn off this notice. + No journal files were opened due to insufficient permissions. MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-57-lowlatency N/A - linux-backports-modules-4.4.0-57-lowlatency N/A - linux-firmware 1.157.6 + linux-restricted-modules-4.4.0-57-lowlatency N/A + linux-backports-modules-4.4.0-57-lowlatency N/A + linux-firmware 1.157.6 SourcePackage: linux Symptom: storage UdevMonitorLog: - monitor will print the received events for: - UDEV - the event which udev sends out after rule processing + monitor will print the received events for: + UDEV - the event which udev sends out after rule processing UdisksMonitorLog: - Monitoring the udisks daemon. Press Ctrl+C to exit. - 13:37:57.897: The udisks-daemon is running (name-owner :1.52). + Monitoring the udisks daemon. Press Ctrl+C to exit. + 13:37:57.897: The udisks-daemon is running (name-owner :1.52). UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: - + dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ZBOX-CI320NANO series dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC ** Summary changed: - eSATA external drive not recognized by Ubuntu Studio + eSATA external drive not recognized by Ubuntu Studio kernel-bug-exists-upstream -- 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/1653796 Title: eSATA external drive not recognized by Ubuntu Studio kernel-bug- exists-upstream Status in linux package in Ubuntu: Confirmed Bug description: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. Hibe
[Kernel-packages] [Bug 1653796] Re: eSATA external drive not recognized by Ubuntu Studio
possible progress here: dmesg | grep -i "attached " [3.045731] sd 0:0:0:0: Attached scsi generic sg0 type 0 [3.051706] sd 0:0:0:0: [sda] Attached SCSI disk sda obviously my internal drive, which leaves that sg0 is my eSATA drive? -- 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/1653796 Title: eSATA external drive not recognized by Ubuntu Studio Status in linux package in Ubuntu: Incomplete Bug description: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-12-19 (15 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-lowlatency N/A linux-backports-modules-4.4.0-57-lowlatency N/A linux-firmware 1.157.6 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 13:37:57.897: The udisks-daemon is running (name-owner :1.52). UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ZBOX-CI320NANO series dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio
still not showing after reboot with new kernel. uname -r shows v4.10. ** Attachment added: "still-not-showing-by-rescanning.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+attachment/4803036/+files/still-not-showing-by-rescanning.png -- 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/1653796 Title: eSATA external drive not recognized by Ubuntu Studio Status in linux package in Ubuntu: Incomplete Bug description: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-12-19 (15 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-lowlatency N/A linux-backports-modules-4.4.0-57-lowlatency N/A linux-firmware 1.157.6 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 13:37:57.897: The udisks-daemon is running (name-owner :1.52). UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ZBOX-CI320NANO series dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio
using "all" header package installed ok. Then after that the image packages for generic and low latency both installed but with error "Possible missing firmware" see attached. haven't reboot yet.. ** Attachment added: "possible-missing-firmware.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+attachment/4803035/+files/possible-missing-firmware.png -- 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/1653796 Title: eSATA external drive not recognized by Ubuntu Studio Status in linux package in Ubuntu: Incomplete Bug description: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-12-19 (15 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-lowlatency N/A linux-backports-modules-4.4.0-57-lowlatency N/A linux-firmware 1.157.6 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 13:37:57.897: The udisks-daemon is running (name-owner :1.52). UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ZBOX-CI320NANO series dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio
First new kernel install attempt failed. See attached. ** Attachment added: "Errors-EncounteredWhileProcessing.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+attachment/4803034/+files/Errors-EncounteredWhileProcessing.png -- 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/1653796 Title: eSATA external drive not recognized by Ubuntu Studio Status in linux package in Ubuntu: Incomplete Bug description: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-12-19 (15 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-lowlatency N/A linux-backports-modules-4.4.0-57-lowlatency N/A linux-firmware 1.157.6 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 13:37:57.897: The udisks-daemon is running (name-owner :1.52). UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ZBOX-CI320NANO series dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio
above comment shows that it may have to do with my dual boot system of Centos 7 and Ubuntu Studio. -- 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/1653796 Title: eSATA external drive not recognized by Ubuntu Studio Status in linux package in Ubuntu: Incomplete Bug description: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-12-19 (15 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-lowlatency N/A linux-backports-modules-4.4.0-57-lowlatency N/A linux-firmware 1.157.6 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 13:37:57.897: The udisks-daemon is running (name-owner :1.52). UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ZBOX-CI320NANO series dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1653796] Re: eSATA external drive not recognized by Ubuntu Studio
I will be following the instructions from https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show=KernelMainlineBuilds to try out the newest upstream kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1653796 Title: eSATA external drive not recognized by Ubuntu Studio Status in linux package in Ubuntu: Incomplete Bug description: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-12-19 (15 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-lowlatency N/A linux-backports-modules-4.4.0-57-lowlatency N/A linux-firmware 1.157.6 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 13:37:57.897: The udisks-daemon is running (name-owner :1.52). UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ZBOX-CI320NANO series dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653796/+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 1653796] [NEW] eSATA external drive not recognized by Ubuntu Studio
Public bug reported: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-12-19 (15 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-lowlatency N/A linux-backports-modules-4.4.0-57-lowlatency N/A linux-firmware 1.157.6 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 13:37:57.897: The udisks-daemon is running (name-owner :1.52). UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ZBOX-CI320NANO series dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "bug-eSATA-attach-to-report" https://bugs.launchpad.net/bugs/1653796/+attachment/4799539/+files/bug-eSATA-attach-to-report -- 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/1653796 Title: eSATA external drive not recognized by Ubuntu Studio Status in linux package in Ubuntu: New Bug description: did a search for similar problems and found an old bug from earlier versions of Ubuntu: bug 153768. old bug report said to try some of these things, which I did.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-lowlatency 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: Edward-admin 1721 F pulseaudio CurrentDesktop: XFCE Date: Tue Jan 3 13:37:32 2017 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=cd636119-7499-4207-a479-13ab3d7c7d28 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-12-19 (15 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Motherboard by ZOTAC ZBOX-CI320NANO series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=838e029d-694d-496b-b3ef-116bf1ff4afa ro quiet splash intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-lowlatency N/A linux-backports-modules-4.4.0-57-low
[Kernel-packages] [Bug 1633629] Re: arm64: KASLR breaks MODVERSIONS
I was able to replicate this failure on an ARMv8 (aarch64) xenial system, using the supplied instructions for QEMU and getting the modprobe error. -- 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/1633629 Title: arm64: KASLR breaks MODVERSIONS Status in linux package in Ubuntu: In Progress Status in linux source package in Yakkety: In Progress Bug description: [Impact] On certain arm64 platforms, modules will not load. This doesn't impact any certified hardware to date, but is known to impact some pre-release platforms, as well as QEMU when a virtio-rng-pci device is attached. [Test Case] On a xenial/arm64 host, run: sudo apt install qemu-system-arm qemu-efi wget http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-arm64/20101020ubuntu483/images/netboot/mini.iso cp /usr/share/AAVMF/AAVMF_CODE.fd flash0.img cp /usr/share/AAVMF/AAVMF_VARS.fd flash1.img sudo qemu-system-aarch64 -enable-kvm -m 2048 -cpu host -M virt,gic_version=host -nographic -pflash flash0.img -pflash flash1.img -drive file=mini.iso,id=cdrom,if=none,media=cdrom -device virtio-scsi-device -device scsi-cd,drive=cdrom -device virtio-rng-pci Select Install from the GRUB menu, and continue through the installer menus to "Detect network hardware". On failure, the installer will report 'Error while running "modprobe -v -b usb-storage"'. On success, it'll continue through to the network configuration screens. [Regression Risk] This will be a simple cherry pick from upstream, so we'll have upstream support w/ any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633629/+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 1518457] Re: kswapd0 100% CPU usage
** Bug watch added: Linux Kernel Bug Tracker #65201 http://bugzilla.kernel.org/show_bug.cgi?id=65201 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=65201 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1518457 Title: kswapd0 100% CPU usage Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: As per bug 721896 and various others: I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory). Occasionally (about once a day), kswapd0 falls into a busy loop and spins on 100% CPU usage indefinitely. This can be provoked by copying/writing large files (e.g. dding a 256MB file), but it happens occasionally otherwise. System memory usage (not including buffers/caches) currently sits at 36%, which is typical[1]. Initially I had no swap space configured; I've since tried enabling a 256MB swap file, but the problem continues to occur and no swap space is used. The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`. Happy to provide further information/take further debugging actions. [1] Full output from `free`: total used free sharedbuffers cached Mem: 1014936 483448 531488 28556 9756 112700 -/+ buffers/cache: 360992 653944 Swap: 262140 0 262140 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 19:40 seq crw-rw 1 root audio 116, 33 Nov 19 19:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Fri Nov 20 20:44:30 2015 Ec2AMI: ami-1c552a76 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 xen ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 net.ifnames=0 RelatedPackageVersions: linux-restricted-modules-4.2.0-18-generic N/A linux-backports-modules-4.2.0-18-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2015 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1518457/+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 1461738] Re: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms
Yes, I'm relatively sure. -- 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/1461738 Title: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms Status in linux package in Ubuntu: Incomplete Bug description: After using wireless for some period of time, it stops working. dmesg report is attached. Rebooting the machine makes the wireless driver work again (for a little bit anyway). I haven't checked if it's related to suspend/resume, but I use this a lot. I can try bisecting for a kernel which doesn't have this problem, although between when I started having problems, I upgraded to Vivid (which didn't fix the problem.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ezyang 3167 F...m pulseaudio /dev/snd/controlC0: ezyang 3167 F pulseaudio Date: Wed Jun 3 20:09:04 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/sabre-swap InstallationDate: Installed on 2013-11-21 (560 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 7762K3U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago) dmi.bios.date: 02/21/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET25WW (1.11 ) dmi.board.name: 7762K3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7762K3U dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461738/+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 1479031] Re: attached block devices not showing up
** Description changed: I have Ubuntu Precise guests running in kvm to which I attach volumes immediately after boot. Sometimes I notice that the devices do not show up in the guest e.g. they are not visible in /proc/partitions and dmesg boot log shows no sign of then being noticed. Qemu itself shows that the devices are attached and if I do a rescan within the guest the devices appear. A reboot also cause the devices to appear. So, it feels like there is enough evidence to suggest that the devices were properly attached by qemu/seabios but they just didn't get noticed by the guest. This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal) and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it would appear that something changed between 3.8 and 3.11 that resolved this issue and if we can identify it we should backport to 3.2. - I am currently able to reproduce this issue using openstack to spin up - vms and attach volumes using the following script: + I am able to reproduce this issue using Openstack to spin up vms and + attach volumes using the following script: http://pastebin.ubuntu.com/11954253/ - I currently hit this issue with 1/2 instrances. + I hit this issue with 1/2 instances. -- 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/1479031 Title: attached block devices not showing up Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: New Bug description: I have Ubuntu Precise guests running in kvm to which I attach volumes immediately after boot. Sometimes I notice that the devices do not show up in the guest e.g. they are not visible in /proc/partitions and dmesg boot log shows no sign of then being noticed. Qemu itself shows that the devices are attached and if I do a rescan within the guest the devices appear. A reboot also cause the devices to appear. So, it feels like there is enough evidence to suggest that the devices were properly attached by qemu/seabios but they just didn't get noticed by the guest. This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal) and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it would appear that something changed between 3.8 and 3.11 that resolved this issue and if we can identify it we should backport to 3.2. I am able to reproduce this issue using Openstack to spin up vms and attach volumes using the following script: http://pastebin.ubuntu.com/11954253/ I hit this issue with 1/2 instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+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 1479031] [NEW] attached block devices not showing up
Public bug reported: I have Ubuntu Precise guests running in kvm to which I attach volumes immediately after boot. Sometimes I notice that the devices do not show up in the guest e.g. they are not visible in /proc/partitions and dmesg boot log shows no sign of then being noticed. Qemu itself shows that the devices are attached and if I do a rescan within the guest the devices appear. A reboot also cause the devices to appear. So, it feels like there is enough evidence to suggest that the devices were properly attached by qemu/seabios but they just didn't get noticed by the guest. This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal) and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it would appear that something changed between 3.8 and 3.11 that resolved this issue and if we can identify it we should backport to 3.2. I am able to reproduce this issue using Openstack to spin up vms and attach volumes using the following script: http://pastebin.ubuntu.com/11954253/ I hit this issue with 1/2 instances. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Precise) Importance: Undecided Assignee: Chris J Arges (arges) 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/1479031 Title: attached block devices not showing up Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: New Bug description: I have Ubuntu Precise guests running in kvm to which I attach volumes immediately after boot. Sometimes I notice that the devices do not show up in the guest e.g. they are not visible in /proc/partitions and dmesg boot log shows no sign of then being noticed. Qemu itself shows that the devices are attached and if I do a rescan within the guest the devices appear. A reboot also cause the devices to appear. So, it feels like there is enough evidence to suggest that the devices were properly attached by qemu/seabios but they just didn't get noticed by the guest. This issue is reproducible with Precise running 3.2, 3.5 (lts-quantal) and 3.8 (lts-raring) kernels but not as of 3.11 (lts-saucy) so it would appear that something changed between 3.8 and 3.11 that resolved this issue and if we can identify it we should backport to 3.2. I am able to reproduce this issue using Openstack to spin up vms and attach volumes using the following script: http://pastebin.ubuntu.com/11954253/ I hit this issue with 1/2 instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479031/+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 1461738] Re: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms
Utopic. Looking at leftover kernels on my system, probably 3.16.0-36? -- 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/1461738 Title: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms Status in linux package in Ubuntu: Incomplete Bug description: After using wireless for some period of time, it stops working. dmesg report is attached. Rebooting the machine makes the wireless driver work again (for a little bit anyway). I haven't checked if it's related to suspend/resume, but I use this a lot. I can try bisecting for a kernel which doesn't have this problem, although between when I started having problems, I upgraded to Vivid (which didn't fix the problem.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ezyang 3167 F...m pulseaudio /dev/snd/controlC0: ezyang 3167 F pulseaudio Date: Wed Jun 3 20:09:04 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/sabre-swap InstallationDate: Installed on 2013-11-21 (560 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 7762K3U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago) dmi.bios.date: 02/21/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET25WW (1.11 ) dmi.board.name: 7762K3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7762K3U dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461738/+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 1461738] Re: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms
This problem did occur in a release prior to vivid. It's hard for me to report exactly when the problem started occurring, because most of the time I use ethernet, and there seem to be some wireless networks which are more likely to tickle the problem than others. -- 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/1461738 Title: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms Status in linux package in Ubuntu: Incomplete Bug description: After using wireless for some period of time, it stops working. dmesg report is attached. Rebooting the machine makes the wireless driver work again (for a little bit anyway). I haven't checked if it's related to suspend/resume, but I use this a lot. I can try bisecting for a kernel which doesn't have this problem, although between when I started having problems, I upgraded to Vivid (which didn't fix the problem.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ezyang 3167 F...m pulseaudio /dev/snd/controlC0: ezyang 3167 F pulseaudio Date: Wed Jun 3 20:09:04 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/sabre-swap InstallationDate: Installed on 2013-11-21 (560 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 7762K3U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago) dmi.bios.date: 02/21/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET25WW (1.11 ) dmi.board.name: 7762K3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7762K3U dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461738/+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 1461738] Re: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms
Tested on upstream kernel, bug exists, marking confirmed as per instructions. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.1rc6 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461738 Title: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms Status in linux package in Ubuntu: Confirmed Bug description: After using wireless for some period of time, it stops working. dmesg report is attached. Rebooting the machine makes the wireless driver work again (for a little bit anyway). I haven't checked if it's related to suspend/resume, but I use this a lot. I can try bisecting for a kernel which doesn't have this problem, although between when I started having problems, I upgraded to Vivid (which didn't fix the problem.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ezyang 3167 F...m pulseaudio /dev/snd/controlC0: ezyang 3167 F pulseaudio Date: Wed Jun 3 20:09:04 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/sabre-swap InstallationDate: Installed on 2013-11-21 (560 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 7762K3U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago) dmi.bios.date: 02/21/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET25WW (1.11 ) dmi.board.name: 7762K3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7762K3U dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461738/+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 1461738] Re: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms
OK, I've updated my BIOS and I will see if the problem happens again. If not I'll close this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461738 Title: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms Status in linux package in Ubuntu: Incomplete Bug description: After using wireless for some period of time, it stops working. dmesg report is attached. Rebooting the machine makes the wireless driver work again (for a little bit anyway). I haven't checked if it's related to suspend/resume, but I use this a lot. I can try bisecting for a kernel which doesn't have this problem, although between when I started having problems, I upgraded to Vivid (which didn't fix the problem.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ezyang 3167 F...m pulseaudio /dev/snd/controlC0: ezyang 3167 F pulseaudio Date: Wed Jun 3 20:09:04 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/sabre-swap InstallationDate: Installed on 2013-11-21 (560 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 7762K3U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago) dmi.bios.date: 02/21/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET25WW (1.11 ) dmi.board.name: 7762K3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7762K3U dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461738/+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 1461738] Re: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms
I regretfully report that I can reproduce the error, with the same error in dmesg. ezyang@sabre:~$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date [sudo] password for ezyang: 7SET39WW (1.25 ) 03/22/2011 Here's just the starting bit of dmesg from the re-reprod. [ 3190.312074] iwl3945 :03:00.0: Error sending C_POWER_TBL: time out after 500ms. [ 3190.312083] iwl3945 :03:00.0: set power fail, ret = -110 [ 3191.844055] iwl3945 :03:00.0: Queue 4 stuck for 2500 ms. [ 3191.844063] iwl3945 :03:00.0: On demand firmware reload [ 3191.880643] ieee80211 phy0: Hardware restart was requested [ 3191.929397] iwl3945 :03:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3191.929402] iwl3945 :03:00.0: Unable to set up bootstrap uCode: -5 [ 3191.976108] iwl3945 :03:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3191.976112] iwl3945 :03:00.0: Unable to set up bootstrap uCode: -5 [ 3192.022807] iwl3945 :03:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3192.022811] iwl3945 :03:00.0: Unable to set up bootstrap uCode: -5 [ 3192.069513] iwl3945 :03:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3192.069516] iwl3945 :03:00.0: Unable to set up bootstrap uCode: -5 [ 3192.116219] iwl3945 :03:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3192.116222] iwl3945 :03:00.0: Unable to set up bootstrap uCode: -5 [ 3192.152637] iwl3945 :03:00.0: Unable to initialize device after 5 attempts. -- 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/1461738 Title: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms Status in linux package in Ubuntu: Incomplete Bug description: After using wireless for some period of time, it stops working. dmesg report is attached. Rebooting the machine makes the wireless driver work again (for a little bit anyway). I haven't checked if it's related to suspend/resume, but I use this a lot. I can try bisecting for a kernel which doesn't have this problem, although between when I started having problems, I upgraded to Vivid (which didn't fix the problem.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ezyang 3167 F...m pulseaudio /dev/snd/controlC0: ezyang 3167 F pulseaudio Date: Wed Jun 3 20:09:04 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/sabre-swap InstallationDate: Installed on 2013-11-21 (560 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 7762K3U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago) dmi.bios.date: 02/21/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET25WW (1.11 ) dmi.board.name: 7762K3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7762K3U dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461738/+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 1461738] Re: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms
Oh, I also have another X61 which I could dust off and use to test for the bug, if that would be helpful. -- 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/1461738 Title: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms Status in linux package in Ubuntu: Confirmed Bug description: After using wireless for some period of time, it stops working. dmesg report is attached. Rebooting the machine makes the wireless driver work again (for a little bit anyway). I haven't checked if it's related to suspend/resume, but I use this a lot. I can try bisecting for a kernel which doesn't have this problem, although between when I started having problems, I upgraded to Vivid (which didn't fix the problem.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ezyang 3167 F...m pulseaudio /dev/snd/controlC0: ezyang 3167 F pulseaudio Date: Wed Jun 3 20:09:04 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/sabre-swap InstallationDate: Installed on 2013-11-21 (560 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 7762K3U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago) dmi.bios.date: 02/21/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET25WW (1.11 ) dmi.board.name: 7762K3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7762K3U dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1461738/+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 1461738] [NEW] iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms
Public bug reported: After using wireless for some period of time, it stops working. dmesg report is attached. Rebooting the machine makes the wireless driver work again (for a little bit anyway). I haven't checked if it's related to suspend/resume, but I use this a lot. I can try bisecting for a kernel which doesn't have this problem, although between when I started having problems, I upgraded to Vivid (which didn't fix the problem.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ezyang 3167 F...m pulseaudio /dev/snd/controlC0: ezyang 3167 F pulseaudio Date: Wed Jun 3 20:09:04 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/sabre-swap InstallationDate: Installed on 2013-11-21 (560 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 7762K3U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago) dmi.bios.date: 02/21/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET25WW (1.11 ) dmi.board.name: 7762K3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7762K3U dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug vivid ** Attachment added: relevant dmesg output https://bugs.launchpad.net/bugs/1461738/+attachment/4409492/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1461738 Title: iwl3945 on X61T crashes with Error sending C_POWER_TBL: time out after 500ms Status in linux package in Ubuntu: Confirmed Bug description: After using wireless for some period of time, it stops working. dmesg report is attached. Rebooting the machine makes the wireless driver work again (for a little bit anyway). I haven't checked if it's related to suspend/resume, but I use this a lot. I can try bisecting for a kernel which doesn't have this problem, although between when I started having problems, I upgraded to Vivid (which didn't fix the problem.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ezyang 3167 F...m pulseaudio /dev/snd/controlC0: ezyang 3167 F pulseaudio Date: Wed Jun 3 20:09:04 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/sabre-swap InstallationDate: Installed on 2013-11-21 (560 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 7762K3U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-29 (6 days ago) dmi.bios.date: 02/21/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7SET25WW (1.11 ) dmi.board.name: 7762K3U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7SET25WW(1.11):bd02/21/2008:svnLENOVO:pn7762K3U:pvrThinkPadX61Tablet:rvnLENOVO:rn7762K3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7762K3U dmi.product.version: ThinkPad X61 Tablet dmi.sys.vendor:
[Kernel-packages] [Bug 1432837] Re: HP Proliant Servers - Kernel Panic - NMI - DL360 DL380 - HPWDT module loaded
Per Linda Knippers (HP) : Why are you blacklisting the watchdog timers? It seems like if corosync wants to use them, which is why it would open /dev/watchdog, then there's either a corosync bug or there's something in the configuration that isn't right. Is anyone looking into that? For cluster configurations, you probably really do want a watchdog so that hung systems can crash, reboot and rejoin the cluster. And what about non-corosync configurations? Other distros run the watchdog timers just fine. Blacklisting the watchdog timer just hides underlying problems. -- 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/1432837 Title: HP Proliant Servers - Kernel Panic - NMI - DL360 DL380 - HPWDT module loaded Status in linux package in Ubuntu: Fix Committed Status in linux source package in Precise: Fix Committed Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Bug description: It was brought to me several situations where users where facing kernel panics when machine was apparently idling (for some HP Proliant Servers like DL 360, DL 380). ILO: 76 CriticalSystem Error03/12/2015 12:4203/12/2015 12:072 An Unrecoverable System Error (NMI) has occurred (System error code 0x002B, 0x) Examples: PID: 0 TASK: 81c1a480 CPU: 0 COMMAND: swapper/0 #0 [88085fc05c88] machine_kexec at 8104eac2 #1 [88085fc05cd8] crash_kexec at 810f26a3 #2 [88085fc05da0] panic at 8175b3f2 #3 [88085fc05e20] sched_clock at 8101c3b9 #4 [88085fc05e30] nmi_handle at 810170e8 #5 [88085fc05e90] io_check_error at 8101758e #6 [88085fc05eb0] default_do_nmi at 810176a9 #7 [88085fc05ed8] do_nmi at 810177d8 #8 [88085fc05ef0] end_repeat_nmi at 8176da21 [exception RIP: native_safe_halt+6] RIP: 81055186 RSP: 81c03e90 RFLAGS: 0246 RAX: 0010 RBX: 0010 RCX: 0246 RDX: 81c03e90 RSI: 0018 RDI: 0001 RBP: 81055186 R8: 81055186 R9: 0018 R10: 81c03e90 R11: 0246 R12: R13: R14: R15: ORIG_RAX: CS: 0010 SS: 0018 --- DOUBLEFAULT exception stack --- #9 [81c03e90] native_safe_halt at 81055186 #10 [81c03e98] default_idle at 8101d37f #11 [81c03eb8] arch_cpu_idle at 8101dcaf #12 [81c03ec8] cpu_startup_entry at 810b5325 #13 [81c03f40] rest_init at 81751a37 #14 [81c03f50] start_kernel at 81d320b7 #15 [81c03f90] x86_64_start_reservations at 81d315ee #16 [81c03fa0] x86_64_start_kernel at 81d31733 OR PID: 0 TASK: 81c14440 CPU: 0 COMMAND: swapper/0 #0 [880fffa07c40] machine_kexec at 8104b391 #1 [880fffa07cb0] crash_kexec at 810d5fb8 #2 [880fffa07d80] panic at 81730335 #3 [880fffa07e00] hpwdt_pretimeout at a02378b5 [hpwdt] #4 [880fffa07e20] nmi_handle at 8174a76a #5 [880fffa07ea0] default_do_nmi at 8174aacd #6 [880fffa07ed0] do_nmi at 8174abe0 #7 [880fffa07ef0] end_repeat_nmi at 81749c81 [exception RIP: intel_idle+204] RIP: 813f07ec RSP: 81c01d88 RFLAGS: 0046 RAX: 0010 RBX: 0010 RCX: 0046 RDX: 81c01d88 RSI: 0018 RDI: 0001 RBP: 813f07ec R8: 813f07ec R9: 0018 R10: 81c01d88 R11: 0046 R12: R13: 01c0d000 R14: 81c01fd8 R15: ORIG_RAX: CS: 0010 SS: 0018 --- NMI exception stack --- #8 [81c01d88] intel_idle at 813f07ec #9 [81c01dc0] cpuidle_enter_state at 815e76cf It turned out that after investigating all idling situations and diverse kernel dump files - where we had most of the CPUs either MWAITing and or relaxing, we discovered that HPWDT was loaded and corosync was opening /dev/watchdog file, triggering the ILO watchdog timer and not updating frequently enough as ILO expected. As described in /etc/modprobe.d/blacklist-watchdog.conf: # Watchdog drivers should not be loaded automatically, but only if a # watchdog daemon is installed. We should blacklist module hpwdt by default for all Ubuntu versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
