[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04
So it didn't work. Apparently someone found ways to workaround this issue: https://github.com/kuba-moo/mt7601u/issues/64 ** Bug watch added: github.com/kuba-moo/mt7601u/issues #64 https://github.com/kuba-moo/mt7601u/issues/64 -- 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/1716301 Title: wifi driver: mt7601u not work on 16.04 Status in linux package in Ubuntu: Confirmed Status in usb-modeswitch-data package in Ubuntu: Confirmed Bug description: In the beginning, when the adapter is pluged in, it's mounted as a disk including driver files for Windows, and $> lsusb Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp. after eject the disk, $> lsusb Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter I tried following 3 drivers: 1) the default mt7601u included in the kernel: 4.4.0-91-generic after eject the disk, $> lsmod|grep mt mt7601u 102400 0 mac80211 737280 1 mt7601u cfg80211 565248 2 mac80211,mt7601u binfmt_misc 20480 1 $> modinfo mt7601u filename: /lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko srcversion: E8B632D369E0C2A9F1CF7D8 alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in* .. depends: mac80211,cfg80211 intree: Y vermagic: 4.4.0-91-generic SMP mod_unload modversions $> dmesg // begin [ 4581.094119] usb 3-4: USB disconnect, device number 6 [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4585.001416] usb 3-4: Product: Љ [ 4585.001418] usb 3-4: Manufacturer: Љ [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4585.001873] scsi host6: usb-storage 3-4:1.0 [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5 [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4619.691737] ISOFS: changing to secondary root [ 4691.563347] usb 3-4: USB disconnect, device number 7 [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4693.766903] usb 3-4: Product: Љ [ 4693.766905] usb 3-4: Manufacturer: Љ [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4693.768063] scsi host7: usb-storage 3-4:1.0 [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0 [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5 [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4728.427856] ISOFS: changing to secondary root [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00 [ 4733.824218] usb 3-4: USB disconnect, device number 8 [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 00 00 00 00 00 [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601 [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4734.238757] usb 3-4: Product: 802.11 n WLAN [ 4734.238772] usb 3-4: Manufacturer: MediaTek [ 4734.238775] usb 3-4: SerialNumber: 1.0 [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500 [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146 [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110 [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110 [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110 [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110 [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110 [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110 [ 4757.730870] usbcore: registe
[Kernel-packages] [Bug 1730895] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1730895
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730895
Title:
aio-dio-invalidate-failure test failed with event res -22 on s390x
Status in linux package in Ubuntu:
Incomplete
Bug description:
This bug is for tracking purpose, this is not a regression for current
cycle as this issue exists for a long time.
Steps:
1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git
2. make -C autotest-client-tests/aio_dio_bugs/src
3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-invalidate-failure
poo
Result:
event res -22
From the code itself, it's expecting a -EIO return value:
if (event.res == -EIO) {
printf("invalidation returned -EIO, OK\n");
exit(0);
}
The actual return value is -22, which I think is -EINVAL
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-100-generic 4.4.0-100.123
ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
Uname: Linux 4.4.0-100-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
Date: Wed Nov 8 01:57:40 2017
HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-4.4.0-100-generic N/A
linux-backports-modules-4.4.0-100-generic N/A
linux-firmware 1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730895/+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 1730895] [NEW] aio-dio-invalidate-failure test failed with event res -22 on s390x
Public bug reported:
This bug is for tracking purpose, this is not a regression for current
cycle as this issue exists for a long time.
Steps:
1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git
2. make -C autotest-client-tests/aio_dio_bugs/src
3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-invalidate-failure poo
Result:
event res -22
>From the code itself, it's expecting a -EIO return value:
if (event.res == -EIO) {
printf("invalidation returned -EIO, OK\n");
exit(0);
}
The actual return value is -22, which I think is -EINVAL
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-100-generic 4.4.0-100.123
ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
Uname: Linux 4.4.0-100-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2:
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not
found.
CurrentDmesg:
Date: Wed Nov 8 01:57:40 2017
HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-4.4.0-100-generic N/A
linux-backports-modules-4.4.0-100-generic N/A
linux-firmware 1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug package-from-proposed s390x third-party-packages xenial
--
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/1730895
Title:
aio-dio-invalidate-failure test failed with event res -22 on s390x
Status in linux package in Ubuntu:
New
Bug description:
This bug is for tracking purpose, this is not a regression for current
cycle as this issue exists for a long time.
Steps:
1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git
2. make -C autotest-client-tests/aio_dio_bugs/src
3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-invalidate-failure
poo
Result:
event res -22
From the code itself, it's expecting a -EIO return value:
if (event.res == -EIO) {
printf("invalidation returned -EIO, OK\n");
exit(0);
}
The actual return value is -22, which I think is -EINVAL
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-100-generic 4.4.0-100.123
ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
Uname: Linux 4.4.0-100-generic s390x
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
Date: Wed Nov 8 01:57:40 2017
HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-4.4.0-100-generic N/A
linux-backports-modules-4.4.0-100-generic N/A
linux-firmware 1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730895/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
** Bug watch added: Linux Kernel Bug Tracker #197809 https://bugzilla.kernel.org/show_bug.cgi?id=197809 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=197809 Importance: Unknown Status: Unknown ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727544] Re: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install
Hi, please try this kernel, http://people.canonical.com/~khfeng/lp1727544-3/ It's an Artful kernel with the pinctrl-amd commit. If that commit along fixes the issue, I'll ask maintainer to include the patch to linux-stable. -- 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/1727544 Title: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 16.04 on my new Lenovo Ideapad 320 14AST. The touchpad is not working. I have followed this tutorial https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux and it doesn't work. The touchpad is working fine on Windows. My kernel version is 4.10.0-37-generic. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: agasigp1605 F pulseaudio /dev/snd/controlC1: agasigp1605 F pulseaudio CRDA: country ID: DFS-JP (2402 - 2482 @ 20), (N/A, 20), (N/A) (5735 - 5815 @ 20), (N/A, 23), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=da16f5a9-567e-4dd7-994a-eb64b6797690 InstallationDate: Installed on 2017-10-25 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 80XU Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=457b1305-a90d-462a-92c2-11d129eb1580 ro i8042.kbdreset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.157.12 Tags: xenial Uname: Linux 4.10.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5PCN18WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-14AST dmi.modalias: dmi:bvnLENOVO:bvr5PCN18WW:bd09/28/2017:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320-14AST: dmi.product.name: 80XU dmi.product.version: Lenovo ideapad 320-14AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1726159] PCIe BUS Error causing really slow laptop performance
Can you attach the output of `cat /sys/class/scsi_host/host*/link_power_management_policy` when the issue happens? You probably need to disable TLP prior that. Kai-Heng > On 7 Nov 2017, at 2:08 AM, George Mathioudakis <1726...@bugs.launchpad.net> > wrote: > > I modified all settings ending on _BAT and some that were related to > storage/sata. > > 2017-11-06 3:23 GMT+02:00 Kai-Heng Feng : > >>> On 3 Nov 2017, at 10:11 PM, George Mathioudakis < >> 1726...@bugs.launchpad.net> wrote: >>> >>> I modified tlp for max performance but tlp starts only when desktop >> boots. >>> So, kernel boot is slow. >> >> Sounds like not the SATA link power management? So which value exactly? >> >>> >>> 2017-11-02 8:57 GMT+02:00 Kai-Heng Feng : >>> Did you change the SATA link power management or other settings? Can you attach the diff of your TLP setting? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1726159 Title: PCIe BUS Error causing really slow laptop performance Status in linux package in Ubuntu: Confirmed Bug description: I recently bought the following laptop: Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB) It came pre-installed with Win10 and I did a fresh install of Ubuntu 16.04 LTS. The screen was flickering for some reason and installing Ubuntu 17.04 fixed the issue. The real problem is that when I'm booting the laptop, the following error is being shown on my screen: [ 12.866073] pcieport :00:1c.5: can't find device of ID00e5 [ 12.898481] pcieport :00:1c.5: AER: Multiple Corrected error received: id=00e5 [ 12.898488] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e5(Receiver ID) [ 12.898491] pcieport :00:1c.5: device [8086:9d15] error status/mask=2041/2000 [ 12.898492] pcieport :00:1c.5:[ 0] Receiver Error (First) [ 12.898493] pcieport :00:1c.5:[ 6] Bad TLP I know that this error can be hid with one of the following kernel boot arguments: pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf. The weird thing is that the above output is only being shown when the laptop is on AC Power (charging). When the laptop is not connected to AC (battery-mode), it has performance issues (slow boot and slow application launching). I was trying all day long to fix the problem. I removed everything that had to do with power-saving, reinstalled, re-tweaked for performance, tried different kernels but had no luck. While diagnosing, I had the idea to benchmark the "M2 SATA-3 SSD" that my laptop had. The results are: * On AC Power: 522MB/s (READ) | 416MB/s (WRITE) * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE) This explains everyting. That's why I'm having a slow boot and slow application launching! Commands "lspci" and "dmesg" say that the error comes from the >> following device: 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) I will attach lspci and dmesg output on a tar.gz file. -- UPDATE: When the laptop is fully charged and still on AC (but not charging since it is 100% charged), the errors appear again but the SSD speed is normal (~500 Read/Write). -- UPDATE: I installed 'tlp' Advanced Power Management package and when using the command 'tlp ac', the SSD speed gets back to normal! The >> option does not persist across reboots. -- ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: georgem2557 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sun Oct 22 23:17:57 2017 InstallationDate: Installed on 2017-10-20 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 >> (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3496 IMC Networks Bus 001 Device 003: ID 13d3:5a01 IMC Networks Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X54
[Kernel-packages] [Bug 1730152] Re: Internal microsd card reader does not work in Ubuntu 17.10
Unless someone writes driver for the card reader, it's not going to work. ** Changed in: linux (Ubuntu) Importance: Medium => Wishlist -- 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/1730152 Title: Internal microsd card reader does not work in Ubuntu 17.10 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 x86_64 of Wayland-Session is running on a HP Envy 13-ad1xx notbook with a internal microsd card reader. The system gives no response when inserting different micro sd cards, which work fine on Windows 10. I report this bug in hope that the upstream may notice and make some change on the suited driver or kernel module. I would provide more information under further direction. According to `lspci` output, the model name is 'Alcor Micro Device 6625'. `udevadm monitor --env` gives no related events when inserting or pulling out the microsd card, in which only thermal_zone changes are recorded. No related events are recoded in /var/log/kern.log either. With sd card being inserted, `sudo fdisk -l` and `sudo blkid` gives no related information. The outputs are all about partitions on the local disk. No sdhc or mmc device is found in /dev/ either. The only implication now is the system notice the existence of the card reader, in terms of `lspci` outputs, the '01:00.0 Unassigned class [ff00]: Alcor Micro Device 6625', even when a sd card is inserted: ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: limorg 1514 F...m pulseaudio /dev/snd/controlC0: limorg 1514 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 10:29:26 2017 HibernationDevice: RESUME=UUID=8f370e7c-280d-4864-b687-a2c81ce87247 InstallationDate: Installed on 2017-10-22 (13 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:5620 Realtek Semiconductor Corp. Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ENVY Laptop 13-ad1xx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=67e321d1-4810-4157-8c29-09c51ea7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-29 (6 days ago) dmi.bios.date: 07/26/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A8 dmi.board.vendor: HP dmi.board.version: KBC Version 39.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd07/26/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A8:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ad1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730152/+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 1716301] Re: wifi driver: mt7601u not work on 16.04
Thanks for all your efforts. $ uname -a Linux video-box 4.13.0-17-generic #20~lp1716301+corequirks SMP Mon Nov 6 04:37:44 EST 2017 x86_64 x86_64 x86_64 GNU/Linux $ dmesg > dmesg_4.13.0-17.20~lp1716301+corequirks.txt ** Attachment added: "dmesg_4.13.0-17.20~lp1716301+corequirks.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716301/+attachment/5005678/+files/dmesg_4.13.0-17.20~lp1716301+corequirks.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/1716301 Title: wifi driver: mt7601u not work on 16.04 Status in linux package in Ubuntu: Confirmed Status in usb-modeswitch-data package in Ubuntu: Confirmed Bug description: In the beginning, when the adapter is pluged in, it's mounted as a disk including driver files for Windows, and $> lsusb Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp. after eject the disk, $> lsusb Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter I tried following 3 drivers: 1) the default mt7601u included in the kernel: 4.4.0-91-generic after eject the disk, $> lsmod|grep mt mt7601u 102400 0 mac80211 737280 1 mt7601u cfg80211 565248 2 mac80211,mt7601u binfmt_misc 20480 1 $> modinfo mt7601u filename: /lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko srcversion: E8B632D369E0C2A9F1CF7D8 alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in* .. depends: mac80211,cfg80211 intree: Y vermagic: 4.4.0-91-generic SMP mod_unload modversions $> dmesg // begin [ 4581.094119] usb 3-4: USB disconnect, device number 6 [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4585.001416] usb 3-4: Product: Љ [ 4585.001418] usb 3-4: Manufacturer: Љ [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4585.001873] scsi host6: usb-storage 3-4:1.0 [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5 [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4619.691737] ISOFS: changing to secondary root [ 4691.563347] usb 3-4: USB disconnect, device number 7 [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4693.766903] usb 3-4: Product: Љ [ 4693.766905] usb 3-4: Manufacturer: Љ [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4693.768063] scsi host7: usb-storage 3-4:1.0 [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0 [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5 [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4728.427856] ISOFS: changing to secondary root [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00 [ 4733.824218] usb 3-4: USB disconnect, device number 8 [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 00 00 00 00 00 [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601 [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4734.238757] usb 3-4: Product: 802.11 n WLAN [ 4734.238772] usb 3-4: Manufacturer: MediaTek [ 4734.238775] usb 3-4: SerialNumber: 1.0 [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500 [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146 [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110 [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110 [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110 [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110 [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110 [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:00
[Kernel-packages] [Bug 1721400] Re: Screen dim during encryption unlock prompt
it does reproduce on 4.12.0-13. Not sure exactly what kernel I was running when it was last working, but will try a few more and report back after finishing testing mainline for a separate 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/1721400 Title: Screen dim during encryption unlock prompt Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: In Artful, since 4.13 kernel, the screen gets super dim after the grub prompt while displaying the hard drive encryption unlock screen. Soon after unlocking the hard drive, the screen returns to normal brightness, but it's hard to even see that the unlock screen is being displayed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jbarnett 2842 F pulseaudio /dev/snd/controlC3: jbarnett 2842 F pulseaudio /dev/snd/controlC0: jbarnett 2842 F pulseaudio /dev/snd/controlC1: jbarnett 2842 F pulseaudio CurrentDesktop: GNOME Date: Wed Oct 4 14:36:01 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (775 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 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/1721400/+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 1730864] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1730864 Title: Shutdown crashing when connected to AC adapter Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I'm using Ubuntu 17.10 (fully updated) and my system is crashing at shutdown when connected to an AC adapter. The error is: Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294280] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294336] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1 Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294384] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 640C (len 68, WS 0, PS 8) @ 0x6430] This behavior is only happening when my laptop is charging. When running on battery I got a clean shutdown/reboot. Already tried to run the latest kernel package (from Mainline) and the problem is exactly the same. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rene 1249 F pulseaudio /dev/snd/controlC0: rene 1249 F pulseaudio CurrentDesktop: GNOME Date: Wed Nov 8 01:00:51 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2 InstallationDate: Installed on 2017-11-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Inspiron 5447 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash acpi_backlight=intel_backlight RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0MHP6R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.family: 00 dmi.product.name: Inspiron 5447 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730864/+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 1730864] [NEW] Shutdown crashing when connected to AC adapter
Public bug reported: Hello there, I'm using Ubuntu 17.10 (fully updated) and my system is crashing at shutdown when connected to an AC adapter. The error is: Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294280] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294336] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1 Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294384] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 640C (len 68, WS 0, PS 8) @ 0x6430] This behavior is only happening when my laptop is charging. When running on battery I got a clean shutdown/reboot. Already tried to run the latest kernel package (from Mainline) and the problem is exactly the same. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rene 1249 F pulseaudio /dev/snd/controlC0: rene 1249 F pulseaudio CurrentDesktop: GNOME Date: Wed Nov 8 01:00:51 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2 InstallationDate: Installed on 2017-11-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Inspiron 5447 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash acpi_backlight=intel_backlight RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0MHP6R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.family: 00 dmi.product.name: Inspiron 5447 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1730864 Title: Shutdown crashing when connected to AC adapter Status in linux package in Ubuntu: New Bug description: Hello there, I'm using Ubuntu 17.10 (fully updated) and my system is crashing at shutdown when connected to an AC adapter. The error is: Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294280] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294336] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1 Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294384] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 640C (len 68, WS 0, PS 8) @ 0x6430] This behavior is only happening when my laptop is charging. When running on battery I got a clean shutdown/reboot. Already tried to run the latest kernel package (from Mainline) and the problem is exactly the same. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: boot/vmlinuz-4.13.0-16-generic] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rene 1249 F pulseaudio /dev/snd/controlC0: rene 1249 F pulseaudio CurrentDesktop: GNOME Date: Wed Nov 8 01:00:51 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2 InstallationDate: Installed on 2017-11-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. Inspiron 5447 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash acpi_backlight=intel_backlight RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169
[Kernel-packages] [Bug 1730862] Re: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/in
** Tags removed: need-duplicate-check -- 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/1730862 Title: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I ran software update and agreed to report several system probblems when prompted. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-17-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doc4488 F pulseaudio /dev/snd/controlC1: doc4488 F pulseaudio Date: Tue Nov 7 22:40:02 2017 DuplicateSignature: package:linux-image-extra-4.13.0-17-generic:(not installed) Unpacking linux-image-extra-4.13.0-17-generic (4.13.0-17.20) ... dpkg: error processing archive /tmp/apt-dpkg-install-2jmHF3/09-linux-image-extra-4.13.0-17-generic_4.13.0-17.20_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072 InstallationDate: Installed on 2016-01-18 (659 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: EVGA 122-CK-NF68 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 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. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: SourcePackage: linux Title: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to artful on 2017-10-23 (16 days ago) dmi.bios.date: 01/22/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 122-CK-NF68 dmi.board.vendor: EVGA dmi.board.version: 2 dmi.chassis.type: 3 dmi.chassis.vendor: EVGA dmi.chassis.version: 122-CK-NF68 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68: dmi.product.name: 122-CK-NF68 dmi.product.version: 2 dmi.sys.vendor: EVGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730862/+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 1730852] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1730852 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730852 Title: Device hotplugging with MPT SAS cannot work for VMWare ESXi Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The hotplugging disk cannot be detected with the simulated MPT SAS device on VMWare ESXi. [Fix] Author: Hannes Reinecke Date: Thu Aug 24 14:52:43 2017 +0200 scsi: mptsas: Fixup device hotplug for VMWare ESXi VMWare ESXi emulates an mptsas HBA, but exposes all drives as direct-attached SAS drives. This it not how the driver originally envisioned things; SAS drives were supposed to be connected via an expander, and only SATA drives would be direct attached. As such, any hotplug event for direct-attach SAS drives was silently ignored, and the guest failed to detect new drives from within a VMWare ESXi environment. [Test] The patch has been verified based on the Ubuntu kernel v4.4.0-97.120. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730852/+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 1730862] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1730862 Title: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I ran software update and agreed to report several system probblems when prompted. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-17-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doc4488 F pulseaudio /dev/snd/controlC1: doc4488 F pulseaudio Date: Tue Nov 7 22:40:02 2017 DuplicateSignature: package:linux-image-extra-4.13.0-17-generic:(not installed) Unpacking linux-image-extra-4.13.0-17-generic (4.13.0-17.20) ... dpkg: error processing archive /tmp/apt-dpkg-install-2jmHF3/09-linux-image-extra-4.13.0-17-generic_4.13.0-17.20_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072 InstallationDate: Installed on 2016-01-18 (659 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: EVGA 122-CK-NF68 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 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. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: SourcePackage: linux Title: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to artful on 2017-10-23 (16 days ago) dmi.bios.date: 01/22/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 122-CK-NF68 dmi.board.vendor: EVGA dmi.board.version: 2 dmi.chassis.type: 3 dmi.chassis.vendor: EVGA dmi.chassis.version: 122-CK-NF68 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68: dmi.product.name: 122-CK-NF68 dmi.product.version: 2 dmi.sys.vendor: EVGA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730862/+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 1730862] [NEW] package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/
Public bug reported: I ran software update and agreed to report several system probblems when prompted. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-17-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doc4488 F pulseaudio /dev/snd/controlC1: doc4488 F pulseaudio Date: Tue Nov 7 22:40:02 2017 DuplicateSignature: package:linux-image-extra-4.13.0-17-generic:(not installed) Unpacking linux-image-extra-4.13.0-17-generic (4.13.0-17.20) ... dpkg: error processing archive /tmp/apt-dpkg-install-2jmHF3/09-linux-image-extra-4.13.0-17-generic_4.13.0-17.20_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072 InstallationDate: Installed on 2016-01-18 (659 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: EVGA 122-CK-NF68 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 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. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: SourcePackage: linux Title: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to artful on 2017-10-23 (16 days ago) dmi.bios.date: 01/22/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 122-CK-NF68 dmi.board.vendor: EVGA dmi.board.version: 2 dmi.chassis.type: 3 dmi.chassis.vendor: EVGA dmi.chassis.version: 122-CK-NF68 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68: dmi.product.name: 122-CK-NF68 dmi.product.version: 2 dmi.sys.vendor: EVGA ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730862 Title: package linux-image-extra-4.13.0-17-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko .dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: I ran software update and agreed to report several system probblems when prompted. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-17-generic (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doc4488 F pulseaudio /dev/snd/controlC1: doc4488 F pulseaudio Date: Tue Nov 7 22:40:02 2017 DuplicateSignature: package:linux-image-extra-4.13.0-17-generic:(not installed) Unpacking linux-image-extra-4.13.0-17-generic (4.13.0-17.20) ... dpkg: error processing archive /tmp/apt-dpkg-install-2jmHF3/09-linux-image-extra-4.13.0-17-generic_4.13.0-17.20_amd64.deb (--unpack): unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/4.13.0-17-generic/kernel/drivers/net/wireless/intersil/hostap/hostap.ko.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072 InstallationDate: Installed on 2016-01-18 (659 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: EVGA 122-CK-NF68 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 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. Python3Details: /usr/bin/python3.6, Python 3
[Kernel-packages] [Bug 1730852] [NEW] Device hotplugging with MPT SAS cannot work for VMWare ESXi
Public bug reported: [Impact] The hotplugging disk cannot be detected with the simulated MPT SAS device on VMWare ESXi. [Fix] Author: Hannes Reinecke Date: Thu Aug 24 14:52:43 2017 +0200 scsi: mptsas: Fixup device hotplug for VMWare ESXi VMWare ESXi emulates an mptsas HBA, but exposes all drives as direct-attached SAS drives. This it not how the driver originally envisioned things; SAS drives were supposed to be connected via an expander, and only SATA drives would be direct attached. As such, any hotplug event for direct-attach SAS drives was silently ignored, and the guest failed to detect new drives from within a VMWare ESXi environment. [Test] The patch has been verified based on the Ubuntu kernel v4.4.0-97.120. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Gavin Guo (mimi0213kimo) Status: New ** Tags: sts -- 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/1730852 Title: Device hotplugging with MPT SAS cannot work for VMWare ESXi Status in linux package in Ubuntu: New Bug description: [Impact] The hotplugging disk cannot be detected with the simulated MPT SAS device on VMWare ESXi. [Fix] Author: Hannes Reinecke Date: Thu Aug 24 14:52:43 2017 +0200 scsi: mptsas: Fixup device hotplug for VMWare ESXi VMWare ESXi emulates an mptsas HBA, but exposes all drives as direct-attached SAS drives. This it not how the driver originally envisioned things; SAS drives were supposed to be connected via an expander, and only SATA drives would be direct attached. As such, any hotplug event for direct-attach SAS drives was silently ignored, and the guest failed to detect new drives from within a VMWare ESXi environment. [Test] The patch has been verified based on the Ubuntu kernel v4.4.0-97.120. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730852/+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 1721987] Re: No sound from right audio channel
** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=197801 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/1721987 Title: No sound from right audio channel Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: No audio comes out of the right speaker on the laptop. When playing a test video such as https://www.youtube.com/watch?v=hTvJoYnpeRQ the right-channel audio is never heard (i.e., it does not get converted into mono and played through the left speaker). When plugging in headphones, audio is heard from both channels. In Windows, both speakers work, so it is not a physical problem with the speakers. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1127 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 12:58:01 2017 InstallationDate: Installed on 2017-10-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: HUAWEI HUAWEI MateBook X ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=f0a69f35-7c1e-4280-b325-6b7fec6e174a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2017 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.12 dmi.board.name: HUAWEI MateBook X dmi.board.vendor: HUAWEI dmi.board.version: 2.0 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.modalias: dmi:bvnHUAWEI:bvr1.12:bd08/14/2017:svnHUAWEI:pnHUAWEIMateBookX:pvr2.0:rvnHUAWEI:rnHUAWEIMateBookX:rvr2.0:cvnHUAWEI:ct10:cvr: dmi.product.family: HUAWEI MateBook dmi.product.name: HUAWEI MateBook X dmi.product.version: 2.0 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721987/+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 1721400] Re: Screen dim during encryption unlock prompt
As Joseph said, does this issue go away if you boot back into the prior 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/1721400 Title: Screen dim during encryption unlock prompt Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: In Artful, since 4.13 kernel, the screen gets super dim after the grub prompt while displaying the hard drive encryption unlock screen. Soon after unlocking the hard drive, the screen returns to normal brightness, but it's hard to even see that the unlock screen is being displayed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jbarnett 2842 F pulseaudio /dev/snd/controlC3: jbarnett 2842 F pulseaudio /dev/snd/controlC0: jbarnett 2842 F pulseaudio /dev/snd/controlC1: jbarnett 2842 F pulseaudio CurrentDesktop: GNOME Date: Wed Oct 4 14:36:01 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (775 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 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/1721400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1730069] Re: kernel 4.10 fails to boot on AMD E-350D APU
> On 8 Nov 2017, at 6:53 AM, Patrick Mackinlay <1730...@bugs.launchpad.net> > wrote: > > All the linux kernels above 4.8 that I have tried have failed, currently > this includes: Then regression happens between v4.8 and v4.10. Make sure mainline v4.8 from [1] doesn’t have the issue, and mainline v4.10 has the issue. After that, can you try Linux v4.9? [1] http://kernel.ubuntu.com/~kernel-ppa/mainline > > linux-image-4.10.0-30-generic > linux-image-4.10.0-32-generic > linux-image-4.10.0-33-generic > linux-image-4.10.0-38-generic > linux-image-4.13.0-16-generic > > > ** Description changed: > > - I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8 > motherboard). This has always worked fine until the kernel was upgraded to > 4.10 as part of the regular system upgrades. Since then the machine wont > boot, there are no errors, the screen just stays blank. If I boot using a > previous kernel (such as 4.8.0-58-generic) then it all works fine. > - --- > + I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8 > + motherboard). This has always worked fine until the kernel was upgraded > + to 4.10 as part of the regular system upgrades. Since then the machine > + wont boot, there are no errors, the screen just stays blank. If I boot > + using a previous kernel (such as 4.8.0-58-generic) then it all works > + fine. > + > + As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have > + tried have failed, currently this includes: > + > + linux-image-4.10.0-30-generic > + linux-image-4.10.0-32-generic > + linux-image-4.10.0-33-generic > + linux-image-4.10.0-38-generic > + linux-image-4.13.0-16-generic > + > + --- > ApportVersion: 2.20.1-0ubuntu2.10 > Architecture: amd64 > AudioDevicesInUse: > - USERPID ACCESS COMMAND > - /dev/snd/controlC1: pim1369 F pulseaudio > - /dev/snd/controlC0: pim1369 F pulseaudio > + USERPID ACCESS COMMAND > + /dev/snd/controlC1: pim1369 F pulseaudio > + /dev/snd/controlC0: pim1369 F pulseaudio > DistroRelease: Ubuntu 16.04 > HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18 > InstallationDate: Installed on 2017-03-11 (238 days ago) > InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 > (20170215) > IwConfig: > - enp2s0no wireless extensions. > - > - lono wireless extensions. > + enp2s0no wireless extensions. > + > + lono wireless extensions. > MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. > Package: linux (not installed) > ProcEnviron: > - LANGUAGE=en_GB:en > - TERM=screen > - PATH=(custom, no user) > - LANG=en_GB.UTF-8 > - SHELL=/bin/bash > + LANGUAGE=en_GB:en > + TERM=screen > + PATH=(custom, no user) > + LANG=en_GB.UTF-8 > + SHELL=/bin/bash > ProcFB: 0 radeondrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed > root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash > ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 > PulseList: > - Error: command ['pacmd', 'list'] failed with exit code 1: Home directory > not accessible: Permission denied > - No PulseAudio daemon running, or not running as session daemon. > + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory > not accessible: Permission denied > + No PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: > - linux-restricted-modules-4.8.0-58-generic N/A > - linux-backports-modules-4.8.0-58-generic N/A > - linux-firmware1.157.13 > + linux-restricted-modules-4.8.0-58-generic N/A > + linux-backports-modules-4.8.0-58-generic N/A > + linux-firmware1.157.13 > RfKill: > - > + > Tags: xenial > Uname: Linux 4.8.0-58-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > - > + > _MarkForUpload: True > dmi.bios.date: 01/18/2013 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: F3 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: E350N WIN8 > dmi.board.vendor: Gigabyte Technology Co., Ltd. > dmi.board.version: x.x > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Gigabyte Technology Co., Ltd. > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnE350NWIN8:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: > dmi.product.name: To be filled by O.E.M. > dmi.product.version: To be filled by O.E.M. > dmi.sys.vendor: Gigabyte Technology Co., Ltd. > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1730069 > > Title: > kernel 4.10 fails to boot on AMD E-350D A
Re: [Kernel-packages] [Bug 1726061] Re: Inspiron 5565 suspend issues after 17.10 upgrade
It seems to be two separate issues, > On 7 Nov 2017, at 10:03 PM, Aaron Peromsik <1726...@bugs.launchpad.net> wrote: > > To summarize my earlier comments: All the below relates to > suspend/resume of 17.10. > > Suspend/resume works fine if I boot with the 4.10-based Ubuntu kernel > from 17.04, or any 4.13 mainline kernel starting from 4.13.5 . > > The mainline kernels from 4.13 through 4.13.4, upon which the Ubuntu > kernel is built, all suspend OK but have problems on resume-- the > machine comes up but wifi does not connect. Once that happens I cannot > reboot or shut down normally, only by holding the power button. > > The mainline kernels from 4.13.5 to 4.13.11 resume OK. This means some commits from v4.13.4 to v4.13.5 fixes your resume problem. The good news is that v4.13.5 based Ubuntu kernel is landing soon. > > The mainline kernels from 4.14.rc1 to 4.14.rc7 have issues on suspend > and cannot properly resume -- display does not come on and the machine > does not respond to ssh from elsewhere. Again I am forced to hold the > power button down for hard shutdown. This means some commits from v4.13 to v4.14-rc1 cause the suspend issue. You probably will hit this issue when you upgrade the system to 18.04, which uses 4.15 based kernel. Do you know how to do kernel bisect? I can build kernel for you if you don’t know how. > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1726061 > > Title: > Inspiron 5565 suspend issues after 17.10 upgrade > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to > suspend. Suspend shuts off the display but doesn't seem to actually > shut off the CPU -- fans still run. When I move the mouse the display > comes back on but upon entering my password sometimes the session > crashes and I am dumped back to the login screen; sometimes the > session is still there but wifi is either disabled (all wifi-related > menu items gone) or visible (with question mark) but non-functional. > In any case once I have suspended I cannot shut down or reboot any way > other than the hard way, by holding the power button for several > seconds. Doesn't seem to matter whether I am using X or Wayland. > > Suspend works mostly fine if I choose the 4.10 kernel from GRUB... > although I am prompted for login more times than necessary on resume. > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: linux-image-4.13.0-16-generic 4.13.0-16.19 > ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 > Uname: Linux 4.10.0-37-generic x86_64 > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC0: aaron 2489 F pulseaudio > /dev/snd/controlC1: aaron 2489 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sun Oct 22 12:22:13 2017 > HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32 > InstallationDate: Installed on 2016-12-25 (301 days ago) > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) > MachineType: Dell Inc. Inspiron 5565 > ProcFB: 0 amdgpudrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed > root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7 > RelatedPackageVersions: > linux-restricted-modules-4.10.0-37-generic N/A > linux-backports-modules-4.10.0-37-generic N/A > linux-firmware 1.169 > SourcePackage: linux > UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) > dmi.bios.date: 07/20/2016 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.0.2 > dmi.board.name: 0RVKF9 > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: 1.0.2 > dmi.modalias: > dmi:bvnDellInc.:bvr1.0.2:bd07/20/2016:svnDellInc.:pnInspiron5565:pvr1.0.2:rvnDellInc.:rn0RVKF9:rvrA00:cvnDellInc.:ct10:cvr1.0.2: > dmi.product.name: Inspiron 5565 > dmi.product.version: 1.0.2 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726061/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1726061 Title: Inspiron 5565 suspend issues after 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to suspend. Suspend shuts off the display but doesn't seem to actually shut off the CPU -- fans still run. When I move the mouse the display comes back on but upon entering my password sometimes the session crashes and I am dumped back to the login screen; sometimes the session is still there but wifi is ei
Re: [Kernel-packages] [Bug 1729618] Re: usb 4-1: string descriptor 0 read error: -22
> On 7 Nov 2017, at 9:33 PM, Ivan Chernyshev <1729...@bugs.launchpad.net> wrote: > > Аt the moment i have: > > [ 16.365650] usb 4-1: new full-speed USB device number 3 using ohci-pci > [ 16.538098] usb 4-1: string descriptor 0 read error: -22 > [ 16.538109] usb 4-1: New USB device found, idVendor=0cf3, idProduct=3004 > [ 16.538113] usb 4-1: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > > How can I reduce the log level? It's not dangerous? I am in a discussion with upstream maintainer to lower the log level. Currently you can’t do it as a user. No, it’s not dangerous. Kai-Heng > >> Вторник, 7 ноября 2017, 11:31 +03:00 от Kai-Heng Feng >> : >> >>> On 6 Nov 2017, at 5:34 PM, Ivan Chernyshev < 1729...@bugs.launchpad.net > >>> wrote: >>> >>> Yes. The USB device still works correctly. With Windows and with >>> elementary. >> >> We should lower its log level so people won’t panic about this message. >> >>> >>> В Понедельник, 6 ноя. 2017 в 4:44 , Kai-Heng Feng >>> < kai.heng.f...@canonical.com > написал: IIUC the USB device still works correctly, right? >>> >>> -- >>> You received this bug notification because you are subscribed to linux >>> in Ubuntu. >>> https://bugs.launchpad.net/bugs/1729618 >>> >>> Title: >>> usb 4-1: string descriptor 0 read error: -22 >>> >>> Status in linux package in Ubuntu: >>> Incomplete >>> >>> Bug description: >>> ~$ dmesg -lerr >>> [2.227682] usb 4-1: string descriptor 0 read error: -22 >>> >>> ~$ dmesg >>> [2.227682] usb 4-1: string descriptor 0 read error: -22 >>> [2.227691] usb 4-1: New USB device found, idVendor=0cf3, idProduct=3004 >>> [2.227695] usb 4-1: New USB device strings: Mfr=1, Product=2, >>> SerialNumber=3 >>> >>> ProblemType: Bug >>> DistroRelease: elementary 0.4.1 >>> Package: linux-image-4.4.0-98-generic 4.4.0-98.121 [origin: Ubuntu] >>> ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 >>> Uname: Linux 4.4.0-98-generic x86_64 >>> NonfreeKernelModules: wl >>> ApportVersion: 2.20.1-0ubuntu2.10 >>> Architecture: amd64 >>> AudioDevicesInUse: >>> USERPID ACCESS COMMAND >>> /dev/snd/pcmC1D0p: mrcrabs2287 F...m pulseaudio >>> /dev/snd/controlC1: mrcrabs2287 F pulseaudio >>> /dev/snd/controlC0: mrcrabs2287 F pulseaudio >>> CurrentDesktop: Pantheon >>> Date: Thu Nov 2 17:11:14 2017 >>> HibernationDevice: RESUME=UUID=087015d3-079d-43ad-ae2c-44bd69b448a4 >>> InstallationDate: Installed on 2017-10-29 (3 days ago) >>> InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) >>> MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C >>> ProcFB: 0 radeondrmfb >>> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic >>> root=UUID=ac5af5d0-9847-4205-8b63-6c02267949db ro quiet splash vt.handoff=7 >>> RelatedPackageVersions: >>> linux-restricted-modules-4.4.0-98-generic N/A >>> linux-backports-modules-4.4.0-98-generic N/A >>> linux-firmware1.157.13 >>> SourcePackage: linux >>> UpgradeStatus: No upgrade log present (probably fresh install) >>> dmi.bios.date: 04/03/2013 >>> dmi.bios.vendor: American Megatrends Inc. >>> dmi.bios.version: P07RAG.N53.130403.LEO >>> dmi.board.asset.tag: No Asset Tag >>> dmi.board.name: SAMSUNG_NP1234567890 >>> dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. >>> dmi.board.version: SEC_SW_REVISION_1234567890ABCD >>> dmi.chassis.asset.tag: No Asset Tag >>> dmi.chassis.type: 9 >>> dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. >>> dmi.chassis.version: N/A >>> dmi.modalias: >>> dmi:bvnAmericanMegatrendsInc.:bvrP07RAG.N53.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP07RAG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: >>> dmi.product.name: 535U3C >>> dmi.product.version: P07RAG >>> dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. >>> >>> To manage notifications about this bug go to: >>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729618/+subscriptions >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1729618 >> >> Title: >> usb 4-1: string descriptor 0 read error: -22 >> >> Status in linux package in Ubuntu: >> Incomplete >> >> Bug description: >> ~$ dmesg -lerr >> [2.227682] usb 4-1: string descriptor 0 read error: -22 >> >> ~$ dmesg >> [2.227682] usb 4-1: string descriptor 0 read error: -22 >> [2.227691] usb 4-1: New USB device found, idVendor=0cf3, idProduct=3004 >> [2.227695] usb 4-1: New USB device strings: Mfr=1, Product=2, >> SerialNumber=3 >> >> ProblemType: Bug >> DistroRelease: elementary 0.4.1 >> Package: linux-image-4.4.0-98-generic 4.4.0-98.121 [origin: Ubuntu] >> ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 >> Uname: Linux 4.4.0-98-generic x86_64 >> NonfreeKernelModules: wl >> ApportVersion: 2.20.1-0ubuntu2.10 >> Architecture: amd64
[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
** Also affects: bluez (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1500407 Importance: Unknown Status: Unknown ** Package changed: bluez (Fedora) => linux (Fedora) ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** No longer affects: linux (Fedora) ** Bug watch removed: Red Hat Bugzilla #1500407 https://bugzilla.redhat.com/show_bug.cgi?id=1500407 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+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 1724752] Re: No headphones sound after a boot up
** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=197799 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/1724752 Title: No headphones sound after a boot up Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: If there's a headphones plugged into the laptop and I boot up Linux Mint 18.2 there's no sound coming from the headphones nor the laptop speakers while the sound volume is set (not muted). If I change sound volume nothing happens. If I unplug headphones speakers starts playing and if I plug headphones back they play normally. P.S. When booting up I hear cracking noises from my headphones. I'm using the latest version of the BIOS in the Dell Inspiron 3567 laptop. Current version is 2.0.3 released in 17 Oct 2017. Package versions: pulseaudio 1:8.0-0ubuntu3.4 --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: d 1444 F...m pulseaudio /dev/snd/controlC0: d 1444 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.2 HibernationDevice: RESUME=UUID=d7ef911d-537d-4e41-98ac-aa09f96e3a92 InstallationDate: Installed on 2017-10-15 (3 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 MachineType: Dell Inc. Inspiron 15-3567 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-53-generic root=UUID=de6abe68-3448-4f7a-904f-2300ba14edbe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-53-generic N/A linux-backports-modules-4.8.0-53-generic N/A linux-firmware1.157.12 Tags: sonya Uname: Linux 4.8.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.06.00 dmi.board.name: 0D53F5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0D53F5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1724752/+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 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter
The attachment "target fix for artful" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in kexec-tools source package in Trusty: New Status in makedumpfile source package in Trusty: New Status in kexec-tools source package in Xenial: New Status in makedumpfile source package in Xenial: In Progress Status in kexec-tools source package in Zesty: New Status in makedumpfile source package in Zesty: New Status in kexec-tools source package in Artful: Invalid Status in makedumpfile source package in Artful: In Progress Bug description: [Impact] On Power Systems, some interrupts are missed, and dumping the crash will fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix this. [Test Case] Setting up kdump to target a virtio-scsi device on a Power System. [Regression Potential] The parameter could be interpreted differently on a different platform and kdump would fail. However, it has been verified that no other platform uses such parameter. If another parameter would have been incorrectly removed on the patch, kdump could fail on other systems. == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this
[Kernel-packages] [Bug 1728115] Re: crashkernel offset prevents kernel boot
The attachment "makedumpfile_1.6.1-2ubuntu0.1.diff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728115 Title: crashkernel offset prevents kernel boot Status in linux package in Ubuntu: Incomplete Status in makedumpfile package in Ubuntu: In Progress Bug description: [Impact] On Power Systems, the kernel won't boot when given a crashkernel parameter with an offset/start address of 32M. No output will be shown, giving no clue to the user why the system has not booted, or what the problem is. [Test Case] Installing kdump-tools on artful, then booting the system. It won't boot. With the fix, it boots and the crash kernel is reserved. [Regression Potential] Some Power Systems might have problems loading the kernel at this address. LP#1567539 is not really clear if PowerNV systems won't kdump when using an address different from 32M. However, it has been requested from an IBM person to test it with 128M instead, and no particular problem was shown. It's possible that there was no reason at first to use 32M, and no problems will be found on either PowerNV or other systems on the field. On the other hand, it's possible they might break kdump. But, right now, those systems won't even boot the first kernel without this change. The linux kernel won't boot when crashkernel parameter tells it to load a crash kernel at 32Mi on ppc64el on artful. This happens because the artful kernel is too big. In fact, multiple requirements on the architecture lead to that: Kernel memory at address 0 is reserved. crashkernel must be at first RMO, so architecture puts it at 128Mi. However, kdump-tools currently puts it at @32Mi because of bug https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539. PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they take more than 5MB and 2MiB, respectively. With the kernel now taking around 25MB from stext to _end, the kernel can't reserve enough memory for PACA or LPPACA right after boot, and it panics. So, right after installing kdump-tools on artful, and rebooting, the kernel won't boot, with no sign of life as we haven't even started any console. Investigation for this issue took an entire day. The fix would be setting the loading address to 128MiB, and start reducing size of PACA and maybe remove some of the requirements for the location of PACA and crash kernel. I would not even set the loading address of the crash kernel in the parameter itself, and leave it to the kernel to decide it, which it already does and already would put it at 128Mi. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728115/+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 1730680] Re: Shutdown failure in 17.10 with Nvidia Nouveau Driver
kernel-bug-exists-upstream Kernel v4.14-rc8 did not fix the problem. -- 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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] Re: Shutdown failure in 17.10 with Nvidia Nouveau Driver
kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
See if the following provides a workaround... $ sudo gedit /etc/modprobe.d/iwlwifi.conf # Add to the end: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - options iwlwifi bt_coex_active=0 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # Restart This was suggsted on the following RedHat bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1500407 ** Bug watch added: Red Hat Bugzilla #1500407 https://bugzilla.redhat.com/show_bug.cgi?id=1500407 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1713751] Re: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel
OK, I'm trying out 4.13.0-16-generic ( and extra ) from artful now on an 8 hour shutdown cycle, it may take a few days to know if the problem will occur. -- 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/1713751 Title: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: In Progress Bug description: Instead of normal complete shutdowns we're getting soft lockup failures. This started when 16.04 hwe packages switched to the 4.10 kernel about a month ago. I help manage a few hundred machines spanning several different sites and several different hardware models and they're all experiencing this intermittently, approximately 5% get stuck on shutdown each day. Here is an example of what is on the screen after it happens, the machine is unresponsive and requires a hard reset. I can't see anything in syslog or dmesg that differs when this happens, I think all logging has stopped at this point in the shutdown. [54566.220003] ? (t=6450529 jiffies g=141935 c=141934 q=1288) [54592.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54620.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54648.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54676.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54704.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54732.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54746.232003] INFO: rcu_sched self-detected stall on CPU [54746.232003] ?1-...: (6495431 ticks this GP) idle=5c7/141/0 softirq=218389/218389 fqs=3247712 This repeats every ~ 22 seconds, sometimes it is stuck for 23s instead of 22: ... NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! Reverting to 4.8.0-58 avoids the problem. I believe the problem has been present with every hwe 4.10 kernel package through the current linux-image-4.10.0-33-generic. This bug was filed with data right after it occurred with linux-image-4.10.0-33-generic. This only happens approximately 5% of the time with no discernible pattern. I am able to reproduce the issue on one particular machine by scheduling shutdowns 3 times per day and waiting up to a few days for the problem to occur. Shutting down and starting up more frequently, like every 5 minutes or even an hour, will not trigger the problem, it seems like the machine needs to be running for a while. It does not seem to depend on any user actions, it happens even if you never login. It has happened on reboots as as opposed to shutdowns as well. I found a few similar bug reports but nothing for these exact symptoms. I have tried blacklisting mei_me with no change in behavior. I'm not sure but the majority of the affected machines are using intel video chips. Next I am going to try a mainline 4.10 kernel. lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 apt-cache policy linux-image-4.10.0-33-generic linux-image-4.10.0-33-generic: Installed: 4.10.0-33.37~16.04.1 Candidate: 4.10.0-33.37~16.04.1 Version table: *** 4.10.0-33.37~16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 29 08:57:26 2017 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713751/+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 1730550] Re: e1000e in 4.4.0-97-generic breaks 82574L under heavy load.
Thank you Joseph for talking a look at this bug request. Does your new kernel only include the commit 4aea7a5c5 ? It's my understanding that linux-next commit 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 is also related, as that fixed a race condition due to get_link_status being used for multiple different states. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=19110cfbb34d4af0cdfe14cd243f3b09dc95b013 -- 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/1730550 Title: e1000e in 4.4.0-97-generic breaks 82574L under heavy load. Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: This issue was first reported on the netdev email list by Lennart Sorensen: https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on the 82574L under heavy load. "Unfortunately this commit changed the driver to assume that the Other Causes interrupt can only mean link state change and hence sets the flag that (unfortunately) means both link is down and link state should be checked. Since this now happens 3000 times per second, the chances of it happening while the watchdog_task is checking the link state becomes pretty high, and it if does happen to coincice, then the watchdog_task will reset the adapter, which causes a real loss of link." A fix for this issue was accepted into the net-next branch, along with other e1000e/igb patches: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net- next.git/commit/?id=f44dea3421b47d355a835e9cfcc59ca7318575a9 The original reported experienced this issue on a Supermicro X7SPA- HF-D525 server board. We see this issue on many servers running X9DBL- 1F server boards. Both boards use the Intel 82574L for the network interfaces. We see messages like this under heavy load: [Nov 6 15:42] e1000e: eth0 NIC Link is Down [ +0.001670] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [Nov 6 16:10] e1000e: eth0 NIC Link is Down [ +0.008505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [Nov 7 00:49] e1000e: eth0 NIC Link is Down [ +2.235111] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx We have confirmed that the connected switch sees the link drops also, to these are not false alarms from the e1000e driver. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 I could not cleanly apply the net-next patch to 4.4.0 so I tested with just the following cherry picked changes on the latest 4.4.0 kernel source package. https://patchwork.ozlabs.org/patch/823942/ https://patchwork.ozlabs.org/patch/823945/ https://patchwork.ozlabs.org/patch/823940/ https://patchwork.ozlabs.org/patch/823941/ https://patchwork.ozlabs.org/patch/823939/ Although it's my understanding the first two are the critical ones for the race condition. I have been running with the patches e1000e kernel driver, under network load for 7 days and I no longer see the network interface drops. Could we pull these changes into the Ubuntu 4.4.0 kernel ? Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 19 07:34 seq crw-rw 1 root audio 116, 33 Jul 19 07:34 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=49ca52b8-cf08-4485-b296-0dffb098e557 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DBL-3F/X9DBL-iF Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=957d7126-5452-4606-942d-1d58adbeb253 ro net.ifnames=0 biosdevname=0 quiet splash nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 RfKill: Error: [Errno 2] No such file or directory Tags:
[Kernel-packages] [Bug 1721365] Re: ixgbe/PCIe: Allow drivers to use Relaxed Ordering on capable root ports
** Changed in: linux (Ubuntu Zesty) Status: Confirmed => In Progress -- 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/1721365 Title: ixgbe/PCIe: Allow drivers to use Relaxed Ordering on capable root ports Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Bug description: [Impact] A signficant performance gain can be achieved with the iperf benchmark by allowing the ixgbe driver to take advantage of PCIe Relaxed Ordering, as observed on the HiSilicon D05 system. [Test Case] Setup two servers with dual-port PCIe ixgbe cards, connected back-to-back. = server = taskset -c 0-15 iperf -s -B 192.168.80.11 & taskset -c 16-31 iperf -s -B 192.168.90.11 & = client = taskset -c 0-15 iperf -c 192.168.80.11 -i 3 -t 600 -P 8 & taskset -c 16-31 iperf -c 192.168.90.11 -i 3 -t 600 -P 8 & Without these patches, we observe an aggregate performance of 8.54 Gbit/sec. With these patches, we observe an aggregate performance of 18.82 Gbit/sec. [Regression Risk] The following risk assessment applies to both artful and zesty - but note that the bulk of these changes are *already in artful*. The proposed SRU for artful would just allow an additional driver to take advantage of it. For zesty, an SRU would need to both introduce this feature and enable it for both the cxgb4 and ixgbe drivers. The patchset is careful to only enable Relaxed Ordering if advertised up through the root port. However, it is possible that enabling RO on hardware that supports it could actually regress performance, or that there is hw out there that advertises RO, but has bugs in the implementation. The patch series includes quirks for HW where RO is advertised but known to have issues[*] - but this list maybe incomplete. This would only impact devices w/ drivers that take advantage of RO - currently cxgb4 and (not yet upstream) ixgbe. Also, there is a possibility of a crash caused by a coding error. One such issue has already been found and fixed upstream [**], and is part of this series. The risk of both of these regressions is reduced by the fact that this code is upstream, and has therefore gotten a lot more testing that has not resulted in regressions reports. [*] commit 077fa19c5dfa06a6ae04fb1661680940ff837612 Author: dingtianhong Date: Tue Aug 15 11:23:25 2017 +0800 PCI: Disable Relaxed Ordering Attributes for AMD A110 commit 87e09cdec4dae08acdb4aa49beb793c19d73e73e Author: dingtianhong Date: Tue Aug 15 11:23:24 2017 +0800 PCI: Disable Relaxed Ordering for some Intel processors [**] commit 0e405232871d67bf1b238d56b6b3d500e69ebbf3 Author: dingtianhong Date: Tue Aug 15 23:24:48 2017 +0800 PCI: fix oops when try to find Root Port for a PCI device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721365/+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 1730069] Re: kernel 4.10 fails to boot on AMD E-350D APU
All the linux kernels above 4.8 that I have tried have failed, currently this includes: linux-image-4.10.0-30-generic linux-image-4.10.0-32-generic linux-image-4.10.0-33-generic linux-image-4.10.0-38-generic linux-image-4.13.0-16-generic ** Description changed: - I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8 motherboard). This has always worked fine until the kernel was upgraded to 4.10 as part of the regular system upgrades. Since then the machine wont boot, there are no errors, the screen just stays blank. If I boot using a previous kernel (such as 4.8.0-58-generic) then it all works fine. - --- + I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8 + motherboard). This has always worked fine until the kernel was upgraded + to 4.10 as part of the regular system upgrades. Since then the machine + wont boot, there are no errors, the screen just stays blank. If I boot + using a previous kernel (such as 4.8.0-58-generic) then it all works + fine. + + As of the 7th of Nov 2017, all the linux kernels above 4.8 that I have + tried have failed, currently this includes: + + linux-image-4.10.0-30-generic + linux-image-4.10.0-32-generic + linux-image-4.10.0-33-generic + linux-image-4.10.0-38-generic + linux-image-4.13.0-16-generic + + --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: pim1369 F pulseaudio - /dev/snd/controlC0: pim1369 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: pim1369 F pulseaudio + /dev/snd/controlC0: pim1369 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=46570214-98e0-4bad-9e3c-51fd31c04b18 InstallationDate: Installed on 2017-03-11 (238 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) IwConfig: - enp2s0no wireless extensions. - - lono wireless extensions. + enp2s0no wireless extensions. + + lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcEnviron: - LANGUAGE=en_GB:en - TERM=screen - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + TERM=screen + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic.efi.signed root=UUID=25808329-ef64-4a67-960f-6140c5610dd4 ro quiet splash ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 PulseList: - Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied - No PulseAudio daemon running, or not running as session daemon. + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-4.8.0-58-generic N/A - linux-backports-modules-4.8.0-58-generic N/A - linux-firmware1.157.13 + linux-restricted-modules-4.8.0-58-generic N/A + linux-backports-modules-4.8.0-58-generic N/A + linux-firmware1.157.13 RfKill: - + Tags: xenial Uname: Linux 4.8.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - + _MarkForUpload: True dmi.bios.date: 01/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: E350N WIN8 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnE350NWIN8:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- 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/1730069 Title: kernel 4.10 fails to boot on AMD E-350D APU Status in linux package in Ubuntu: Confirmed Bug description: I am running ubuntu 16.04.3 LTS on an AMD e-350D (GA-E350N-WIN8 motherboard). This has always worked fine until the kernel was upgraded to 4.10 as part of the regular system upgrades. Since then the machine wont boot, there are no errors, the screen just stays blank. If I boot using a previous kernel (such as 4.8.0-58-generic) then it all works fine. As of the 7th of Nov 2017, all the linux kernels
[Kernel-packages] [Bug 1730762] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1730762 Title: 17.10 - suspend/resume failure Status in linux package in Ubuntu: Confirmed Bug description: I'm experiencing a failure in the resume process after the suspend. When I try to resume the system start, but the screen stay black while the disk seem be really busy. The only way to exit from this status is unplug the system before restart it. Let me know how to collect additional info (if necessary). Alessandro- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 1948 F pulseaudio /dev/snd/controlC0: alessandro 1948 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 22:59:45 2017 HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13 InstallationDate: Installed on 2016-07-09 (486 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp2s5no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Packard Bell NEC IMEDIA 5204 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730762/+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 1721365] Re: ixgbe/PCIe: Allow drivers to use Relaxed Ordering on capable root ports
** Description changed: [Impact] A signficant performance gain can be achieved with the iperf benchmark by allowing the ixgbe driver to take advantage of PCIe Relaxed Ordering, as observed on the HiSilicon D05 system. [Test Case] Setup two servers with dual-port PCIe ixgbe cards, connected back-to-back. = server = - taskset -c 0-15 iperf -s -B 192.168.80.11 - taskset -c 16-31 iperf -s -B 192.168.90.11 + taskset -c 0-15 iperf -s -B 192.168.80.11 & + taskset -c 16-31 iperf -s -B 192.168.90.11 & = client = taskset -c 0-15 iperf -c 192.168.80.11 -i 3 -t 600 -P 8 & taskset -c 16-31 iperf -c 192.168.90.11 -i 3 -t 600 -P 8 & Without these patches, we observe an aggregate performance of 8.54 Gbit/sec. With these patches, we observe an aggregate performance of 18.82 Gbit/sec. [Regression Risk] The following risk assessment applies to both artful and zesty - but note that the bulk of these changes are *already in artful*. The proposed SRU for artful would just allow an additional driver to take advantage of it. For zesty, an SRU would need to both introduce this feature and enable it for both the cxgb4 and ixgbe drivers. The patchset is careful to only enable Relaxed Ordering if advertised up through the root port. However, it is possible that enabling RO on hardware that supports it could actually regress performance, or that there is hw out there that advertises RO, but has bugs in the implementation. The patch series includes quirks for HW where RO is advertised but known to have issues[*] - but this list maybe incomplete. This would only impact devices w/ drivers that take advantage of RO - currently cxgb4 and (not yet upstream) ixgbe. Also, there is a possibility of a crash caused by a coding error. One such issue has already been found and fixed upstream [**], and is part of this series. The risk of both of these regressions is reduced by the fact that this code is upstream, and has therefore gotten a lot more testing that has not resulted in regressions reports. [*] commit 077fa19c5dfa06a6ae04fb1661680940ff837612 Author: dingtianhong Date: Tue Aug 15 11:23:25 2017 +0800 PCI: Disable Relaxed Ordering Attributes for AMD A110 commit 87e09cdec4dae08acdb4aa49beb793c19d73e73e Author: dingtianhong Date: Tue Aug 15 11:23:24 2017 +0800 PCI: Disable Relaxed Ordering for some Intel processors [**] commit 0e405232871d67bf1b238d56b6b3d500e69ebbf3 Author: dingtianhong Date: Tue Aug 15 23:24:48 2017 +0800 PCI: fix oops when try to find Root Port for a PCI 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/1721365 Title: ixgbe/PCIe: Allow drivers to use Relaxed Ordering on capable root ports Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: Confirmed Status in linux source package in Artful: In Progress Bug description: [Impact] A signficant performance gain can be achieved with the iperf benchmark by allowing the ixgbe driver to take advantage of PCIe Relaxed Ordering, as observed on the HiSilicon D05 system. [Test Case] Setup two servers with dual-port PCIe ixgbe cards, connected back-to-back. = server = taskset -c 0-15 iperf -s -B 192.168.80.11 & taskset -c 16-31 iperf -s -B 192.168.90.11 & = client = taskset -c 0-15 iperf -c 192.168.80.11 -i 3 -t 600 -P 8 & taskset -c 16-31 iperf -c 192.168.90.11 -i 3 -t 600 -P 8 & Without these patches, we observe an aggregate performance of 8.54 Gbit/sec. With these patches, we observe an aggregate performance of 18.82 Gbit/sec. [Regression Risk] The following risk assessment applies to both artful and zesty - but note that the bulk of these changes are *already in artful*. The proposed SRU for artful would just allow an additional driver to take advantage of it. For zesty, an SRU would need to both introduce this feature and enable it for both the cxgb4 and ixgbe drivers. The patchset is careful to only enable Relaxed Ordering if advertised up through the root port. However, it is possible that enabling RO on hardware that supports it could actually regress performance, or that there is hw out there that advertises RO, but has bugs in the implementation. The patch series includes quirks for HW where RO is advertised but known to have issues[*] - but this list maybe incomplete. This would only impact devices w/ drivers that take advantage of RO - currently cxgb4 and (not yet upstream) ixgbe. Also, there is a possibility of a crash caused by a coding error. One such issue has already been found and fixed upstream [**], and is part of this series. The risk of both of these regressions is reduced by the fact that this code is upstream, and has therefore gotten a lot more testing that has not resulted in regress
[Kernel-packages] [Bug 1730762] [NEW] 17.10 - suspend/resume failure
Public bug reported: I'm experiencing a failure in the resume process after the suspend. When I try to resume the system start, but the screen stay black while the disk seem be really busy. The only way to exit from this status is unplug the system before restart it. Let me know how to collect additional info (if necessary). Alessandro- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 1948 F pulseaudio /dev/snd/controlC0: alessandro 1948 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 22:59:45 2017 HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13 InstallationDate: Installed on 2016-07-09 (486 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp2s5no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Packard Bell NEC IMEDIA 5204 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1730762 Title: 17.10 - suspend/resume failure Status in linux package in Ubuntu: New Bug description: I'm experiencing a failure in the resume process after the suspend. When I try to resume the system start, but the screen stay black while the disk seem be really busy. The only way to exit from this status is unplug the system before restart it. Let me know how to collect additional info (if necessary). Alessandro- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 1948 F pulseaudio /dev/snd/controlC0: alessandro 1948 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 22:59:45 2017 HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13 InstallationDate: Installed on 2016-07-09 (486 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp2s5no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Packard Bell NEC IMEDIA 5204 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.ve
[Kernel-packages] [Bug 1730550] Re: e1000e in 4.4.0-97-generic breaks 82574L under heavy load.
I built a Xenial test kernel with linux-next commit 4aea7a5c5. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1730550/ To install this kernel, please install both the linux-image and linux- image-extra .deb packages. Can you test this kernel and see if it resolves this bug? Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730550 Title: e1000e in 4.4.0-97-generic breaks 82574L under heavy load. Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: This issue was first reported on the netdev email list by Lennart Sorensen: https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on the 82574L under heavy load. "Unfortunately this commit changed the driver to assume that the Other Causes interrupt can only mean link state change and hence sets the flag that (unfortunately) means both link is down and link state should be checked. Since this now happens 3000 times per second, the chances of it happening while the watchdog_task is checking the link state becomes pretty high, and it if does happen to coincice, then the watchdog_task will reset the adapter, which causes a real loss of link." A fix for this issue was accepted into the net-next branch, along with other e1000e/igb patches: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net- next.git/commit/?id=f44dea3421b47d355a835e9cfcc59ca7318575a9 The original reported experienced this issue on a Supermicro X7SPA- HF-D525 server board. We see this issue on many servers running X9DBL- 1F server boards. Both boards use the Intel 82574L for the network interfaces. We see messages like this under heavy load: [Nov 6 15:42] e1000e: eth0 NIC Link is Down [ +0.001670] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [Nov 6 16:10] e1000e: eth0 NIC Link is Down [ +0.008505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [Nov 7 00:49] e1000e: eth0 NIC Link is Down [ +2.235111] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx We have confirmed that the connected switch sees the link drops also, to these are not false alarms from the e1000e driver. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 I could not cleanly apply the net-next patch to 4.4.0 so I tested with just the following cherry picked changes on the latest 4.4.0 kernel source package. https://patchwork.ozlabs.org/patch/823942/ https://patchwork.ozlabs.org/patch/823945/ https://patchwork.ozlabs.org/patch/823940/ https://patchwork.ozlabs.org/patch/823941/ https://patchwork.ozlabs.org/patch/823939/ Although it's my understanding the first two are the critical ones for the race condition. I have been running with the patches e1000e kernel driver, under network load for 7 days and I no longer see the network interface drops. Could we pull these changes into the Ubuntu 4.4.0 kernel ? Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 19 07:34 seq crw-rw 1 root audio 116, 33 Jul 19 07:34 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=49ca52b8-cf08-4485-b296-0dffb098e557 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DBL-3F/X9DBL-iF Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=957d7126-5452-4606-942d-1d58adbeb253 ro net.ifnames=0 biosdevname=0 quiet splash nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N/A linux-firmware1.157.11 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-83-generic x86_64 UnreportableReason: The report belongs to a package
[Kernel-packages] [Bug 1729391] Re: Trackpad stops responding after suspend
My data points: * Broken on 4.13.0-16-generic * Works on 4.10.0-37-generic Both data points were gathered after having upgraded from Ubuntu 17.04 to 17.10 on my Dell XPS 9Q33 laptop. -- 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/1729391 Title: Trackpad stops responding after suspend Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, the trackpad stops working after suspend (it actually works for a few seconds, then doesn't react). I can still use the touch screen. Please tell me which log-files to upload. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729391/+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 836816] Re: unable to enumerate USB device
hi I'm using Linux Mint 18.2 I have an brother mfc-j6520dw , connected by Ethernet for printing and by USB for scanning All work fine after same months ago. When I try scanning with Simple Scan app don't work I check syslog and see erros like this: kernel: [ 3890.418521] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? kernel: [ 3891.274568] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? kernel: [ 3892.134557] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? kernel: [ 3892.134605] usb 1-3.1.1-port3: unable to enumerate USB device Then I use new and old USB cables, from 0,9m to 1,8m, and view same error I connect the printer to various ports, direct to my laptop and by powered USB hubs, same errors I have update kernel, 4.8, 4.10, 4.11, 4.12, 4.13 and today to 4.14.rc8, same errors This is I see now with an new cable: Nov 7 21:11:00 cacharro-x8 kernel: [ 681.823977] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 21:11:01 cacharro-x8 kernel: [ 682.675974] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 21:11:02 cacharro-x8 kernel: [ 683.528179] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 21:11:03 cacharro-x8 kernel: [ 684.380230] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 21:11:03 cacharro-x8 kernel: [ 684.380277] usb 1-3.1.1-port3: unable to enumerate USB device Nov 7 22:01:31 cacharro-x8 kernel: [ 3712.326057] usb 1-3.1.1-port4: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:31 cacharro-x8 kernel: [ 3713.178116] usb 1-3.1.1-port4: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:32 cacharro-x8 kernel: [ 3714.029965] usb 1-3.1.1-port4: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:33 cacharro-x8 kernel: [ 3714.882066] usb 1-3.1.1-port4: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:33 cacharro-x8 kernel: [ 3714.882109] usb 1-3.1.1-port4: unable to enumerate USB device Nov 7 22:01:41 cacharro-x8 kernel: [ 3722.310109] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:41 cacharro-x8 kernel: [ 3723.162112] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:42 cacharro-x8 kernel: [ 3724.014074] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:43 cacharro-x8 kernel: [ 3724.870063] usb 1-3.1.1-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:43 cacharro-x8 kernel: [ 3724.870103] usb 1-3.1.1-port3: unable to enumerate USB device Nov 7 22:01:53 cacharro-x8 kernel: [ 3734.982144] usb 1-3.1.1.2-port2: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:54 cacharro-x8 kernel: [ 3735.838052] usb 1-3.1.1.2-port2: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:55 cacharro-x8 kernel: [ 3736.690156] usb 1-3.1.1.2-port2: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:56 cacharro-x8 kernel: [ 3737.542195] usb 1-3.1.1.2-port2: Cannot enable. Maybe the USB cable is bad? Nov 7 22:01:56 cacharro-x8 kernel: [ 3737.542300] usb 1-3.1.1.2-port2: unable to enumerate USB device Nov 7 22:02:03 cacharro-x8 kernel: [ 3745.114152] usb 1-3.1.1.2-port4: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:04 cacharro-x8 kernel: [ 3745.970241] usb 1-3.1.1.2-port4: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:05 cacharro-x8 kernel: [ 3746.822108] usb 1-3.1.1.2-port4: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:06 cacharro-x8 kernel: [ 3747.674122] usb 1-3.1.1.2-port4: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:06 cacharro-x8 kernel: [ 3747.674212] usb 1-3.1.1.2-port4: unable to enumerate USB device Nov 7 22:02:16 cacharro-x8 kernel: [ 3757.882862] usb 1-3.4-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:17 cacharro-x8 kernel: [ 3758.798463] usb 1-3.4-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:18 cacharro-x8 kernel: [ 3759.710664] usb 1-3.4-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:19 cacharro-x8 kernel: [ 3760.622298] usb 1-3.4-port3: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:19 cacharro-x8 kernel: [ 3760.622454] usb 1-3.4-port3: unable to enumerate USB device Nov 7 22:02:31 cacharro-x8 kernel: [ 3773.070506] usb 1-3-port2: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:32 cacharro-x8 kernel: [ 3773.982452] usb 1-3-port2: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:33 cacharro-x8 kernel: [ 3774.898879] usb 1-3-port2: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:34 cacharro-x8 kernel: [ 3775.818516] usb 1-3-port2: Cannot enable. Maybe the USB cable is bad? Nov 7 22:02:34 cacharro-x8 kernel: [ 3775.818942] usb 1-3-port2: unable to enumerate USB device Nov 7 22:03:30 cacharro-x8 kernel: [ 3831.734361] usb usb1-port4: Cannot enable. Maybe the USB cable is bad? Nov 7 22:03:31 cacharro-x8 kernel: [ 3832.702355] usb usb1-port4: Cannot enable. Maybe the USB cable is bad? N
[Kernel-packages] [Bug 1723785] Re: 'cat /sys/class/power_supply/BAT0/capacity' hangs indefinitely (Dell XPS15, Ubuntu 17.04 w/kernel 4.10.0-37-generic)
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Zesty) Status: In Progress => Fix Released -- 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/1723785 Title: 'cat /sys/class/power_supply/BAT0/capacity' hangs indefinitely (Dell XPS15, Ubuntu 17.04 w/kernel 4.10.0-37-generic) Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: On performing 'cat /sys/class/power_supply/BAT0/capacity' there is a freeze in the terminal, no error message, no feedback. This works just fine with kernel 4.10.0-21-generic. Also, I cannot do 'sudo systemctl suspend' with 4.10.0-37-generic (this also works fine with 4.10.0-21-generic. Additionally, with any kernel later than 4.10.0-21-generic, I need to have 'nouveau.modeset=0' in the GRUB_CMDLINE_LINUX_DEFAULT for it to boot (not needed with the 4.10.0-21 kernel. Hardware = Dell XPS15 (9560) with Ubuntu 17.04 up-to-date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723785/+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 1730658] Re: Random Permanent Screen Freezes.
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730658 Title: Random Permanent Screen Freezes. Status in linux package in Ubuntu: Incomplete Bug description: When I play videos in youtube, vlc or the default videos there are lags and a lot of times the screen freezes. No cursor or keys work. I cannot even skip the video. It freezes almost as frequent as 9 out of 10 times while skipping videos. I think i have 4GB swap just to be safe and about 100GB free space on root partition. I have to hold down the power button to force turn off the pc. I upgraded from 17.04. There were no issues in 17.04. This issue is only in 17.10. I have dual booted with windows 10 and it works fine as well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: noob 2348 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 18:00:37 2017 InstallationDate: Installed on 2017-09-10 (57 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80NT ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=48d2b96e-246f-4470-9561-a37b18d55619 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-01 (5 days ago) dmi.bios.date: 04/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CFCN24WW(V1.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 5 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 500-15ISK dmi.modalias: dmi:bvnLENOVO:bvrCFCN24WW(V1.06):bd04/15/2016:svnLENOVO:pn80NT:pvrLenovoideapad500-15ISK:rvnLENOVO:rnLenovoideapad5:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoideapad500-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80NT dmi.product.version: Lenovo ideapad 500-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730658/+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 1730680] Re: Shutdown failure in 17.10 with Nvidia Nouveau Driver
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Incomplete Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730480] Re: Problem after 17.04 to 17.10 upgrade
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Incomplete Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730596] Re: s390/mm: fix write access check in gup_huge_pmd()
** Tags added: kernel-da-key
--
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/1730596
Title:
s390/mm: fix write access check in gup_huge_pmd()
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
The check for the _SEGMENT_ENTRY_PROTECT bit in gup_huge_pmd() is the
wrong way around. It must not be set for write==1, and not be checked for
write==0. Fix this similar to how it was fixed for ptes long time ago in
commit 25591b0 ("[S390] fix get_user_pages_fast").
One impact of this bug would be unnecessarily using the gup slow path for
write==0 on r/w mappings. A potentially more severe impact would be that
gup_huge_pmd() will succeed for write==1 on r/o mappings.
Addl information
Problem: The check for the _SEGMENT_ENTRY_PROTECT bit in
gup_huge_pmd() is the wrong way around. It must not be set
for write==1, and not be checked for write==0. Allowing
write==1 with protection bit set, instead of breaking out
to the slow path, will result in a missing faultin_page()
to clear the protection bit (for valid writable mappings),
and the async I/O write operation will fail to write to
such a mapping.
Solution: Fix it by correctly checking the protection bit like it is
also done in gup_pte_range() and gup_huge_pud().
Reproduction: Async I/O workload on buffers that are mapped as transparent
hugepages.
Upstream-ID: ba385c0594e723d41790ecfb12c610e6f90c7785
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730596/+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 1730607] Re: mount cifs with SMB 3.0 stop working
This may be a duplicate of bug 1729337. Can you try the test kernel I posted in that bug and see if it resolves your issue? ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1730607 Title: mount cifs with SMB 3.0 stop working Status in linux package in Ubuntu: Triaged Bug description: I have a Ubuntu Server (14.04.5 LTS (GNU/Linux 4.4.0-98-generic x86_64)) and a Windows Server 2012 R2 File Server with a File Share. I mounted a file share to my linux server with a cifs-utils. Everything worked fine until some kernel update installed on Ubuntu. SMB 3.0 stopped working and my share not mounted. sudo mount -t cifs //myserver.xxx.net/WebBackup -o username=user,password=P@ssw0rd,domain=xxx.net,vers=3.0 /backupdrive - not working mount error(5): Input/output error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) if i change to vers=2.1 - it it work --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 7 16:11 seq crw-rw 1 root audio 116, 33 Nov 7 16:11 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (626 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-98.121~14.04.1-generic 4.4.90 RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-98-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 0981-0252-2294-8432-2174-6395-64 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730607/+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 1730746] Re: Processes hang on attempted access of WDC WD30-EZRX 3TB HDD
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Tags added: kernel-da-key -- 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/1730746 Title: Processes hang on attempted access of WDC WD30-EZRX 3TB HDD Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Incomplete Status in linux source package in Bionic: Incomplete Bug description: When booted under kernel 4.13.x, processes (such as parted, boot-info, gparted, etc) always hang when attempting to run due to a Western Digital Green WD30-EZRX 3TB HDD. Drive works as expected under kernel 4.10.x (even when all other things are the same about the system but only booted kernel is different). Full specs of the machine if useful: https://www.support.hp.com/id- en/document/c03277050 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1781 F pulseaudio /dev/snd/controlC0: ubuntu 1781 F pulseaudio CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 20:00:57 2017 IwConfig: eno1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: HP5012436 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: HP5012436 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/+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 1723785] Re: 'cat /sys/class/power_supply/BAT0/capacity' hangs indefinitely (Dell XPS15, Ubuntu 17.04 w/kernel 4.10.0-37-generic)
This can be closed as it is confirmed working with the latest kernel in Ubuntu 17.10 (4.13.0.16.17) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723785 Title: 'cat /sys/class/power_supply/BAT0/capacity' hangs indefinitely (Dell XPS15, Ubuntu 17.04 w/kernel 4.10.0-37-generic) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: On performing 'cat /sys/class/power_supply/BAT0/capacity' there is a freeze in the terminal, no error message, no feedback. This works just fine with kernel 4.10.0-21-generic. Also, I cannot do 'sudo systemctl suspend' with 4.10.0-37-generic (this also works fine with 4.10.0-21-generic. Additionally, with any kernel later than 4.10.0-21-generic, I need to have 'nouveau.modeset=0' in the GRUB_CMDLINE_LINUX_DEFAULT for it to boot (not needed with the 4.10.0-21 kernel. Hardware = Dell XPS15 (9560) with Ubuntu 17.04 up-to-date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723785/+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 1730550] Re: e1000e in 4.4.0-97-generic breaks 82574L under heavy load.
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1730550 Title: e1000e in 4.4.0-97-generic breaks 82574L under heavy load. Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: This issue was first reported on the netdev email list by Lennart Sorensen: https://www.mail-archive.com/netdev@vger.kernel.org/msg178170.html Commit 16ecba59bc333d6282ee057fb02339f77a880beb causes link drops on the 82574L under heavy load. "Unfortunately this commit changed the driver to assume that the Other Causes interrupt can only mean link state change and hence sets the flag that (unfortunately) means both link is down and link state should be checked. Since this now happens 3000 times per second, the chances of it happening while the watchdog_task is checking the link state becomes pretty high, and it if does happen to coincice, then the watchdog_task will reset the adapter, which causes a real loss of link." A fix for this issue was accepted into the net-next branch, along with other e1000e/igb patches: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net- next.git/commit/?id=f44dea3421b47d355a835e9cfcc59ca7318575a9 The original reported experienced this issue on a Supermicro X7SPA- HF-D525 server board. We see this issue on many servers running X9DBL- 1F server boards. Both boards use the Intel 82574L for the network interfaces. We see messages like this under heavy load: [Nov 6 15:42] e1000e: eth0 NIC Link is Down [ +0.001670] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [Nov 6 16:10] e1000e: eth0 NIC Link is Down [ +0.008505] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [Nov 7 00:49] e1000e: eth0 NIC Link is Down [ +2.235111] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx We have confirmed that the connected switch sees the link drops also, to these are not false alarms from the e1000e driver. # lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 I could not cleanly apply the net-next patch to 4.4.0 so I tested with just the following cherry picked changes on the latest 4.4.0 kernel source package. https://patchwork.ozlabs.org/patch/823942/ https://patchwork.ozlabs.org/patch/823945/ https://patchwork.ozlabs.org/patch/823940/ https://patchwork.ozlabs.org/patch/823941/ https://patchwork.ozlabs.org/patch/823939/ Although it's my understanding the first two are the critical ones for the race condition. I have been running with the patches e1000e kernel driver, under network load for 7 days and I no longer see the network interface drops. Could we pull these changes into the Ubuntu 4.4.0 kernel ? Thanks --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 19 07:34 seq crw-rw 1 root audio 116, 33 Jul 19 07:34 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=49ca52b8-cf08-4485-b296-0dffb098e557 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DBL-3F/X9DBL-iF Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=957d7126-5452-4606-942d-1d58adbeb253 ro net.ifnames=0 biosdevname=0 quiet splash nomdmonddf nomdmonisw ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 RelatedPackageVersions: linux-restricted-modules-4.4.0-83-generic N/A linux-backports-modules-4.4.0-83-generic N
[Kernel-packages] [Bug 1729391] Re: Trackpad stops responding after suspend
What kernel version does the bug exist in? Is it 4.10.0-38 and newer? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key -- 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/1729391 Title: Trackpad stops responding after suspend Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, the trackpad stops working after suspend (it actually works for a few seconds, then doesn't react). I can still use the touch screen. Please tell me which log-files to upload. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729391/+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 1730746] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1730746 Title: Processes hang on attempted access of WDC WD30-EZRX 3TB HDD Status in linux package in Ubuntu: Confirmed Bug description: When booted under kernel 4.13.x, processes (such as parted, boot-info, gparted, etc) always hang when attempting to run due to a Western Digital Green WD30-EZRX 3TB HDD. Drive works as expected under kernel 4.10.x (even when all other things are the same about the system but only booted kernel is different). Full specs of the machine if useful: https://www.support.hp.com/id- en/document/c03277050 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1781 F pulseaudio /dev/snd/controlC0: ubuntu 1781 F pulseaudio CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 20:00:57 2017 IwConfig: eno1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: HP5012436 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: HP5012436 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1730479] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gsd-clipboard:1277]
I confirm that Ubuntu is installed and I can access it through the Recovery mode. all checks says everything is correct but I got stuck after I keyed in my password to open my session. Screens are like a multicolor set of parallel lines (I use two screens but starting with one only do not resolve the issue). I may then install other kernels through the recovery mode using a terminal.Le lundi 06 novembre 2017 à 20:42 +, Joseph Salisbury a écrit : > Are you able to install Ubuntu at all, so other kernels can be > tested? > > ** Tags added: kernel-da-key > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730479 Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gsd-clipboard:1277] Status in linux package in Ubuntu: Incomplete Bug description: This is the first start of a fresh install :( with following required elements: Ubuntu version : Ubuntu 4.13.0-16.19-generic 4.13.4 Result of lspci-vnvn: 00:00.0 Host bridge [0600]: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub [8086:2770] (rev 02) Subsystem: Hewlett-Packard Company 82945G/GZ/P/PL Memory Controller Hub [103c:2a57] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port [8086:2771] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port [8086:] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit Latency L0s <256ns, L1 <4us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #0, PowerLimit 0.000W; Interlock- NoCompl- SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Off, PwrInd On, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- Kernel driver in use: pcieport Kernel modules: shpchp 00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 01) Subsystem: Hewlett-Packard Company NM10/ICH7 Family High Definition Audio Controller [103c:2a57] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- Unsup
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
mich@ezbook:~$ dmesg | grep .hid [3.164258] hidraw: raw HID events driver (C) Jiri Kosina [4.305905] usbcore: registered new interface driver usbhid [4.305907] usbhid: USB HID core driver [4.308860] hid-generic 0003:045E:0023.0001: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Optical®] on usb-:00:15.0-2/input0 [6.726802] intel-hid INT33D5:00: platform supports 5 button array [6.869535] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator [6.883919] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261) [6.888901] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/8713) [6.891849] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261) [6.898604] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/23334) [6.901745] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/20745) [6.906804] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/31302) [6.909733] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/29952) [6.918193] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/22281) [7.524580] hid-multitouch 0018:0911:5288.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00 [ 102.817373] hid-generic 0003:045E:0023.0003: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Optical®] on usb-:00:15.0-2/input0 [ 1637.590908] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator [ 1637.597193] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261) [ 1637.599518] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/8713) [ 1637.600674] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261) [ 1637.604096] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/23334) [ 1637.605250] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/20745) [ 1637.608647] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/31302) [ 1637.609845] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/29952) [ 1637.614343] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/22281) [ 1637.643866] hid-multitouch 0018:0911:5288.0004: input,hidraw1: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00 mich@ezbook:~$ uname -r 4.14.0-041400rc8-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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in linux package in Ubuntu: Confirmed Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730746] Re: Processes hang on attempted access of WDC WD30-EZRX 3TB HDD
** Summary changed: - System hangs on attempted access of WDC WD30-EZRX 3TB HDD + Processes hang on attempted access of WDC WD30-EZRX 3TB HDD ** Description changed: - When booted under kernel 4.13.x, my system always hangs when attempting - to access a Western Digital Green WD30-EZRX 3TB HDD. Drive works as - expected under kernel 4.10.x (even when all other things are the same - about the system but only booted kernel is different). + When booted under kernel 4.13.x, processes (such as parted, boot-info, + gparted, etc) always hang when attempting to run due to a Western + Digital Green WD30-EZRX 3TB HDD. Drive works as expected under kernel + 4.10.x (even when all other things are the same about the system but + only booted kernel is different). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: ubuntu 1781 F pulseaudio - /dev/snd/controlC0: ubuntu 1781 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: ubuntu 1781 F pulseaudio + /dev/snd/controlC0: ubuntu 1781 F pulseaudio CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 20:00:57 2017 IwConfig: - eno1 no wireless extensions. - - lono wireless extensions. + eno1 no wireless extensions. + + lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- RelatedPackageVersions: - linux-restricted-modules-4.13.0-16-generic N/A - linux-backports-modules-4.13.0-16-generic N/A - linux-firmware 1.169 + linux-restricted-modules-4.13.0-16-generic N/A + linux-backports-modules-4.13.0-16-generic N/A + linux-firmware 1.169 RfKill: - + SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: HP5012436 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: HP5012436 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard ** Description changed: When booted under kernel 4.13.x, processes (such as parted, boot-info, gparted, etc) always hang when attempting to run due to a Western Digital Green WD30-EZRX 3TB HDD. Drive works as expected under kernel 4.10.x (even when all other things are the same about the system but only booted kernel is different). + + Full specs of the machine if useful: https://www.support.hp.com/id- + en/document/c03277050 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1781 F pulseaudio /dev/snd/controlC0: ubuntu 1781 F pulseaudio CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 20:00:57 2017 IwConfig: eno1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: HP5012436 dmi.board.name: 1589 dmi.board.vendor: Hewle
[Kernel-packages] [Bug 1730746] [NEW] Processes hang on attempted access of WDC WD30-EZRX 3TB HDD
Public bug reported: When booted under kernel 4.13.x, processes (such as parted, boot-info, gparted, etc) always hang when attempting to run due to a Western Digital Green WD30-EZRX 3TB HDD. Drive works as expected under kernel 4.10.x (even when all other things are the same about the system but only booted kernel is different). Full specs of the machine if useful: https://www.support.hp.com/id- en/document/c03277050 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1781 F pulseaudio /dev/snd/controlC0: ubuntu 1781 F pulseaudio CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 20:00:57 2017 IwConfig: eno1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: HP5012436 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: HP5012436 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730746 Title: Processes hang on attempted access of WDC WD30-EZRX 3TB HDD Status in linux package in Ubuntu: New Bug description: When booted under kernel 4.13.x, processes (such as parted, boot-info, gparted, etc) always hang when attempting to run due to a Western Digital Green WD30-EZRX 3TB HDD. Drive works as expected under kernel 4.10.x (even when all other things are the same about the system but only booted kernel is different). Full specs of the machine if useful: https://www.support.hp.com/id- en/document/c03277050 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1781 F pulseaudio /dev/snd/controlC0: ubuntu 1781 F pulseaudio CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 20:00:57 2017 IwConfig: eno1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP Z420 Workstation ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v03.91 dmi.board.asset.tag: HP5012436 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: HP5012436 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v03.91:bd10/17/2016:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1730680] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005557/+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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005556/+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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005554/+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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005559/+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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730515] Re: Request to backport cxlflash patches to 16.04 SRU
I built Zesty, Artful and Bionic test kernels with the requested three patches. The test kernels can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1730515/ Can you test these kernels and see if they resolve this bug? Are these three commits required to fix a specific bug? That info would be needed for a SRU request. -- 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/1730515 Title: Request to backport cxlflash patches to 16.04 SRU Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: ---Problem Description--- We have few cxlflash patches upstream that we would like to be included in the Ubuntu 16.04 HWE kernel. Below patches are in next/master lined up for 4.15 kernel. 285e6670d0229b0157a9167eb8b2626b445a5a0e scsi: cxlflash: Use derived maximum write same length 0d4191305e69e42b3f7f11bbcf077d1d42929f94 scsi: cxlflash: Allow cards without WWPN VPD to configure d84c198f43c50c6c0bd57571acbf0f000165bd56 scsi: cxlflash: Derive pid through accessors Please let me know if there are questions/concerns. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1730515/+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 1730680] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005548/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005552/+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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005553/+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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005560/+files/WifiSyslog.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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/500/+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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] Re: Shutdown failure in 17.10 with Nvidia Nouveau Driver
apport information ** Tags added: apport-collected wayland-session ** Description changed: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. + --- + ApportVersion: 2.20.7-0ubuntu3.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: donp 1203 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2017-11-07 (0 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2a Intel Corp. + Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. Inspiron 7559 + 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 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-16-generic N/A + linux-backports-modules-4.13.0-16-generic N/A + linux-firmware 1.169 + Tags: wayland-session artful + Uname: Linux 4.13.0-16-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/08/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.2.4 + dmi.board.name: 0H87XC + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: Not Specified + dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 7559 + dmi.product.version: 1.2.4 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005547/+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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task
[Kernel-packages] [Bug 1730680] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005551/+files/JournalErrors.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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005558/+files/RfKill.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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005550/+files/IwConfig.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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730680] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1730680/+attachment/5005549/+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/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Confirmed Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: donp 1203 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-07 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: wayland-session artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.version: 1.2.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730505] Re: [MacBookPro12, 1] SD Card Reader not working
*** This bug is a duplicate of bug 1531653 *** https://bugs.launchpad.net/bugs/1531653 I am away from home for a couple of months and don't have access to an sdcard to test with at the moment. Is there anything that's still useful for my to try with this latest kernel, even just if the kernel detects the reader without a card in it since this doesn't currently work at all. -- 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/1730505 Title: [MacBookPro12,1] SD Card Reader not working Status in linux package in Ubuntu: Confirmed Bug description: Related bug to this one: bug #1531653 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jhodapp4369 F pulseaudio /dev/snd/pcmC1D0p: jhodapp4369 F...m pulseaudio /dev/snd/controlC1: jhodapp4369 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 6 15:23:15 2017 HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6 InstallationDate: Installed on 2015-08-02 (827 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B07.1506051617 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.B07.1506051617:bd06/05/2015: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/1730505/+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 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation
Did the bug go away with the linux- image-4.1.0-3-generic_4.1.0-3.3~lp1646277Commit369e26773Reverted_amd64.deb kernel posted in comment #73? -- 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/1646277 Title: Xenial server 16.04.x will have a black screen after PXE installation Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in debian-installer source package in Xenial: Confirmed Status in linux source package in Xenial: Confirmed Bug description: The display will keep black screen after install 16.04.x via PXE(need use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode screen) Quanta team is installing Xenial server using PXE boot. After the installation, the console will show a black screen. Hitting ctl- alt-f1 displays the text mode screen OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+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 1718548] Re: ubuntu-fan autopkgtests are broken against systemd-resolved
I don't understand why this was SRUed to xenial, where we do not use systemd-networkd / systemd-resolved; and there is no SRU test case listed in the bug. Łukasz, why was this accepted and what do you expect for testing? ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1718548 Title: ubuntu-fan autopkgtests are broken against systemd-resolved Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Committed Bug description: Now that 17.10 has migrated to netplan+systemd-networkd+systemd- resolved by default, ubuntu-fan autopkgtests are failing; at least one reason for this failure is wrong detection of the default network interface because autopkgtest environments appear for some reason to be getting multiple default routes: autopkgtest [20:14:59]: test lxd: [--- Error: either "dev" is duplicate, or "ens2" is a garbage. II: Auto-init LXD... LXD has been successfully configured. II: Creating Fan Bridge... /usr/sbin/fanatic: .0.0/16: unknown underlay network format FAIL: Error on enable-fan autopkgtest [20:15:10]: test lxd: ---] (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/amd64/u/ubuntu- fan/20170916_203221_4f037@/log.gz) The other part failure appears to be a race with systemd-resolved in setting up the network inside of docker containers: autopkgtest [17:25:39]: test docker: [--- Running in the Canonical CI environment II: Auto-create Fan Bridge... configuring fan underlay:10.220.0.0/16 overlay:250.0.0.0/8 II: Create docker Fan Network... configuring docker for underlay:10.220.0.0/16 overlay:250.0.0.0/8 (fan-250 250.4 6.84.0/24) 1c8a03aa50ab88b997c3b3aee88bfa6933b14368f1594db4a800c2ae8d62074f II: Test docker... local docker test: pulling container images ... Using default tag: latest latest: Pulling from library/ubuntu d5c6f90da05d: Pulling fs layer [...] 2b8db33536d4: Pull complete Digest: sha256:2b9285d3e340ae9d4297f83fed6a9563493945935fc787e98cc32a69f5687641 Status: Downloaded newer image for ubuntu:latest local docker test: creating test container ... 5cbdd232b71bc0738f27f1fa3eae4360716bfe3f8cea976874bf6309b1843169 slave: installing ping ... W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com' [...] E: Unable to locate package iputils-ping slave: installing nc ... E: Unable to locate package netcat-openbsd test master: ping test (250.46.84.2) ... test slave: ping test (250.46.84.1) ... test slave: ping test ... FAIL --- transcript start --- /bin/sh: 108: ping: not found --- transcript end --- test slave: short data test (250.46.84.2 -> 250.46.84.1) ... test master: ping test ... PASS test master: short data test (250.46.84.1 -> 250.46.84.2) ... autopkgtest [20:12:19]: ERROR: timed out on command [...] I've reproduced this problem locally and prepared a partial patch based on a similar fix to the docker.io package's autopkgtests - but so far this only fixes races in the lxd test, not in the docker test, so it needs further investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1718548/+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 1728115] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1728115 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1728115 Title: crashkernel offset prevents kernel boot Status in linux package in Ubuntu: Incomplete Status in makedumpfile package in Ubuntu: In Progress Bug description: [Impact] On Power Systems, the kernel won't boot when given a crashkernel parameter with an offset/start address of 32M. No output will be shown, giving no clue to the user why the system has not booted, or what the problem is. [Test Case] Installing kdump-tools on artful, then booting the system. It won't boot. With the fix, it boots and the crash kernel is reserved. [Regression Potential] Some Power Systems might have problems loading the kernel at this address. LP#1567539 is not really clear if PowerNV systems won't kdump when using an address different from 32M. However, it has been requested from an IBM person to test it with 128M instead, and no particular problem was shown. It's possible that there was no reason at first to use 32M, and no problems will be found on either PowerNV or other systems on the field. On the other hand, it's possible they might break kdump. But, right now, those systems won't even boot the first kernel without this change. The linux kernel won't boot when crashkernel parameter tells it to load a crash kernel at 32Mi on ppc64el on artful. This happens because the artful kernel is too big. In fact, multiple requirements on the architecture lead to that: Kernel memory at address 0 is reserved. crashkernel must be at first RMO, so architecture puts it at 128Mi. However, kdump-tools currently puts it at @32Mi because of bug https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539. PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they take more than 5MB and 2MiB, respectively. With the kernel now taking around 25MB from stext to _end, the kernel can't reserve enough memory for PACA or LPPACA right after boot, and it panics. So, right after installing kdump-tools on artful, and rebooting, the kernel won't boot, with no sign of life as we haven't even started any console. Investigation for this issue took an entire day. The fix would be setting the loading address to 128MiB, and start reducing size of PACA and maybe remove some of the requirements for the location of PACA and crash kernel. I would not even set the loading address of the crash kernel in the parameter itself, and leave it to the kernel to decide it, which it already does and already would put it at 128Mi. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728115/+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 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
Do you know if this bug is also happening with Zesty, or just Artful and
Bionic(>4.13)?
I'm going to working on bisecting bug 1713751 in case it's related.
Also, it would be good to know if this bug is already fixed in the
latest mainline kernel. Do you have a way to reproduce this bug? If
so, could you give 4.14-rc8 a try? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc8
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Bionic)
Importance: High
Status: Triaged
** Also affects: qemu-kvm (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Status: New => Triaged
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
Triaged
Status in qemu-kvm package in Ubuntu:
New
Status in linux source package in Artful:
Triaged
Status in qemu-kvm source package in Artful:
New
Status in linux source package in Bionic:
Triaged
Status in qemu-kvm source package in Bionic:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+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 1713751] Re: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel
I'd like to perform a bisect to identify the Ubuntu specific commit that introduced this. First can you test the Zesty and Artful kernels to see if the bug has already been fixed in the newer releases? If it has, we can focus of finding the fix with a "Reverse" bisect. The kernels can be downloaded from: Zesty: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13563574 Artful: https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa2/+build/13567624 To install the kernels, just be sure to install both the linux-image and linux-image-extra .deb packages. Thanks in advance! ** Changed in: linux-hwe (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-hwe (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux-hwe (Ubuntu) Status: New => In Progress -- 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/1713751 Title: soft lockup / stall on CPU when shutting down with hwe 4.10 kernel Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: In Progress Bug description: Instead of normal complete shutdowns we're getting soft lockup failures. This started when 16.04 hwe packages switched to the 4.10 kernel about a month ago. I help manage a few hundred machines spanning several different sites and several different hardware models and they're all experiencing this intermittently, approximately 5% get stuck on shutdown each day. Here is an example of what is on the screen after it happens, the machine is unresponsive and requires a hard reset. I can't see anything in syslog or dmesg that differs when this happens, I think all logging has stopped at this point in the shutdown. [54566.220003] ? (t=6450529 jiffies g=141935 c=141934 q=1288) [54592.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54620.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54648.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54676.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54704.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54732.092003] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! (systemd:1) [54746.232003] INFO: rcu_sched self-detected stall on CPU [54746.232003] ?1-...: (6495431 ticks this GP) idle=5c7/141/0 softirq=218389/218389 fqs=3247712 This repeats every ~ 22 seconds, sometimes it is stuck for 23s instead of 22: ... NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! Reverting to 4.8.0-58 avoids the problem. I believe the problem has been present with every hwe 4.10 kernel package through the current linux-image-4.10.0-33-generic. This bug was filed with data right after it occurred with linux-image-4.10.0-33-generic. This only happens approximately 5% of the time with no discernible pattern. I am able to reproduce the issue on one particular machine by scheduling shutdowns 3 times per day and waiting up to a few days for the problem to occur. Shutting down and starting up more frequently, like every 5 minutes or even an hour, will not trigger the problem, it seems like the machine needs to be running for a while. It does not seem to depend on any user actions, it happens even if you never login. It has happened on reboots as as opposed to shutdowns as well. I found a few similar bug reports but nothing for these exact symptoms. I have tried blacklisting mei_me with no change in behavior. I'm not sure but the majority of the affected machines are using intel video chips. Next I am going to try a mainline 4.10 kernel. lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 apt-cache policy linux-image-4.10.0-33-generic linux-image-4.10.0-33-generic: Installed: 4.10.0-33.37~16.04.1 Candidate: 4.10.0-33.37~16.04.1 Version table: *** 4.10.0-33.37~16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 29 08:57:26 2017 SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To mana
[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-key
--
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/1730717
Title:
Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck
for 22s! [systemd:1]"
Status in linux package in Ubuntu:
Triaged
Status in qemu-kvm package in Ubuntu:
New
Status in linux source package in Artful:
Triaged
Status in qemu-kvm source package in Artful:
New
Status in linux source package in Bionic:
Triaged
Status in qemu-kvm source package in Bionic:
New
Bug description:
This is impacting us for ubuntu autopkgtests. Eventually the whole
region ends up dying because each worker is hit by this bug in turn
and backs off until the next reset (6 hourly).
17.10 (and bionic) guests are sometimes failing to reboot. When this
happens, you see the following in the console
[[0;32m OK [0m] Reached target Shutdown.
[ 191.698969] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 219.698438] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]
[ 226.702150] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 226.704958] »(detected by 0, t=15002 jiffies, g=5347, c=5346, q=187)
[ 226.706093] All QSes seen, last rcu_sched kthread activity 15002
(4294949060-4294934058), jiffies_till_next_fqs=1, root ->qsmask 0x0
[ 226.708202] rcu_sched kthread starved for 15002 jiffies! g5347 c5346
f0x2 RCU_GP_WAIT_FQS(3) ->state=0x0
One host that exhibits this behaviour was:
Linux klock 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
guest running:
Linux version 4.13.0-16-generic (buildd@lcy01-02) (gcc version 7.2.0
(Ubuntu 7.2.0-8ubuntu2)) #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
(Ubuntu 4.13.0-16.19-generic 4.13.4)
The affected cloud region is running the xenial/Ocata cloud archive,
so the version of qemu-kvm in there may also be relevant.
Here's how I reproduced it in lcy01:
$ for n in {1..30}; do nova boot --flavor m1.small --image
ubuntu/ubuntu-artful-17.10-amd64-server-20171026.1-disk1.img --key-name
testbed-`hostname` --nic net-name=net_ues_proposed_migration laney-test${n};
done
$ sudo reboot
# wait a minute or so for the instances to all reboot
$ for n in {1..30}; do echo "=== ${n} ==="; nova console-log laney-test${n}
| tail; done
On bad instances you'll see the "soft lockup" message - on good it'll
reboot as normal.
We've seen good and bad instances on multiple compute hosts - it
doesn't feel to me like a host problem but rather a race condition
somewhere that's somehow either triggered or triggered much more often
by what lcy01 is running. I always saw this on the first reboot -
never on first boot, and never on n>1th boot. (But if it's a race then
that might not mean much.)
I'll attach a bad and a good console-log for reference.
If you're at Canonical then see internal rt #107135 for some other
details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730717/+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 1730515] Re: Request to backport cxlflash patches to 16.04 SRU
** Changed in: ubuntu-power-systems Status: New => In Progress -- 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/1730515 Title: Request to backport cxlflash patches to 16.04 SRU Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: ---Problem Description--- We have few cxlflash patches upstream that we would like to be included in the Ubuntu 16.04 HWE kernel. Below patches are in next/master lined up for 4.15 kernel. 285e6670d0229b0157a9167eb8b2626b445a5a0e scsi: cxlflash: Use derived maximum write same length 0d4191305e69e42b3f7f11bbcf077d1d42929f94 scsi: cxlflash: Allow cards without WWPN VPD to configure d84c198f43c50c6c0bd57571acbf0f000165bd56 scsi: cxlflash: Derive pid through accessors Please let me know if there are questions/concerns. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1730515/+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 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter
** Changed in: makedumpfile (Ubuntu Xenial) Status: Confirmed => In Progress ** Patch added: "target fix for artful" https://bugs.launchpad.net/ubuntu/xenial/+source/makedumpfile/+bug/1658733/+attachment/5005516/+files/makedumpfile_1.6.1-2ubuntu0.1.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658733 Title: Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter Status in The Ubuntu-power-systems project: Confirmed Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: In Progress Status in kexec-tools source package in Trusty: New Status in makedumpfile source package in Trusty: New Status in kexec-tools source package in Xenial: New Status in makedumpfile source package in Xenial: In Progress Status in kexec-tools source package in Zesty: New Status in makedumpfile source package in Zesty: New Status in kexec-tools source package in Artful: Invalid Status in makedumpfile source package in Artful: In Progress Bug description: [Impact] On Power Systems, some interrupts are missed, and dumping the crash will fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix this. [Test Case] Setting up kdump to target a virtio-scsi device on a Power System. [Regression Potential] The parameter could be interpreted differently on a different platform and kdump would fail. However, it has been verified that no other platform uses such parameter. If another parameter would have been incorrectly removed on the patch, kdump could fail on other systems. == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 == ---Problem Description--- On a KVM guest installed to a multipath root device, the kdump kernel fails to mount the root file system. This error does not occur in a similar guest installed to a single path device. Full console output of the kdump failure is attached. These messages from the output may be relevant: Begin: Loading multipath modules ... Success: loaded module dm-multipath. done. Begin: Loading multipath hardware handlers ... Failure: failed to load module sc si_dh_alua. Failure: failed to load module scsi_dh_rdac. Failure: failed to load module scsi_dh_emc. done. Begin: Starting multipathd ... done. ---uname output--- Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest ---Steps to Reproduce--- - Install Ubuntu 16.04.1 to a muiltpath target disk - Install kdump-tools package - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg - Run update-grub - Reboot - Initiate a system crash using "echo c > /proc/sysrq-trigger" == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 == Here is the log level 8 kdump console log requested in comment 10. == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 == (In reply to comment #19) > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it > uses .img files which I didn't found as disks). > > Could you please recreate the guest for further debug? Yes, I recreated the guest with its correct multipath lun configuration. I have also attached the guest XML to this bug. > Besides that could you please let us know: > - is the multipath the system's root? I mean / is installed/mounted on the > multipath device? Yes, the guest has only one disk. That disk is actually a LUN from a fiber channel storage device with two paths on the host side. I have passed through both paths to the guest, so the multipath nature of the target disk is known to the guest. In other words, the guest sees a multipath device and is using it as a multipath device. The root file system is called /dev/mapper/mpatha- part2 on the guest. > - how did you attach the device to the guest? Each FC LUN path on the host is mapped to a virtio-scsi controller on the guest using LUN passthrough. (See the guest XML for details on this.) == Comment: #22 - Mauro Sergio Martins Rodrigues - 2017-01-11 09:31:38 == I managed to get kdump to mount rootfs and perform its tasks by setting KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see http://pastebin.hursley.ibm.com/8239 I'm still investigating to figure out what is the reason behind this behavior. Thanks, -- maurosr == Comment: #23 - Mauricio Faria De Oliveira - 2017-01-11 11:56:40 == Mauro, (In reply to comment #22) > I managed to get kdump to mount rootfs and perform its tasks by setting > KDUMP_CMDLI
[Kernel-packages] [Bug 1728115] Re: crashkernel offset prevents kernel boot
** Description changed: + [Impact] + On Power Systems, the kernel won't boot when given a crashkernel parameter with an offset/start address of 32M. No output will be shown, giving no clue to the user why the system has not booted, or what the problem is. + + [Test Case] + Installing kdump-tools on artful, then booting the system. It won't boot. With the fix, it boots and the crash kernel is reserved. + + [Regression Potential] + Some Power Systems might have problems loading the kernel at this address. LP#1567539 is not really clear if PowerNV systems won't kdump when using an address different from 32M. However, it has been requested from an IBM person to test it with 128M instead, and no particular problem was shown. It's possible that there was no reason at first to use 32M, and no problems will be found on either PowerNV or other systems on the field. On the other hand, it's possible they might break kdump. But, right now, those systems won't even boot the first kernel without this change. + + + The linux kernel won't boot when crashkernel parameter tells it to load a crash kernel at 32Mi on ppc64el on artful. This happens because the artful kernel is too big. In fact, multiple requirements on the architecture lead to that: Kernel memory at address 0 is reserved. crashkernel must be at first RMO, so architecture puts it at 128Mi. However, kdump-tools currently puts it at @32Mi because of bug https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539. PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they take more than 5MB and 2MiB, respectively. With the kernel now taking around 25MB from stext to _end, the kernel can't reserve enough memory for PACA or LPPACA right after boot, and it panics. So, right after installing kdump-tools on artful, and rebooting, the kernel won't boot, with no sign of life as we haven't even started any console. Investigation for this issue took an entire day. The fix would be setting the loading address to 128MiB, and start reducing size of PACA and maybe remove some of the requirements for the location of PACA and crash kernel. I would not even set the loading address of the crash kernel in the parameter itself, and leave it to the kernel to decide it, which it already does and already would put it at 128Mi. Cascardo. ** Patch added: "makedumpfile_1.6.1-2ubuntu0.1.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728115/+attachment/5005511/+files/makedumpfile_1.6.1-2ubuntu0.1.diff ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: makedumpfile (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1728115 Title: crashkernel offset prevents kernel boot Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: In Progress Bug description: [Impact] On Power Systems, the kernel won't boot when given a crashkernel parameter with an offset/start address of 32M. No output will be shown, giving no clue to the user why the system has not booted, or what the problem is. [Test Case] Installing kdump-tools on artful, then booting the system. It won't boot. With the fix, it boots and the crash kernel is reserved. [Regression Potential] Some Power Systems might have problems loading the kernel at this address. LP#1567539 is not really clear if PowerNV systems won't kdump when using an address different from 32M. However, it has been requested from an IBM person to test it with 128M instead, and no particular problem was shown. It's possible that there was no reason at first to use 32M, and no problems will be found on either PowerNV or other systems on the field. On the other hand, it's possible they might break kdump. But, right now, those systems won't even boot the first kernel without this change. The linux kernel won't boot when crashkernel parameter tells it to load a crash kernel at 32Mi on ppc64el on artful. This happens because the artful kernel is too big. In fact, multiple requirements on the architecture lead to that: Kernel memory at address 0 is reserved. crashkernel must be at first RMO, so architecture puts it at 128Mi. However, kdump-tools currently puts it at @32Mi because of bug https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1567539. PACA and LPPACA need to be at the first RMO as well, and with 2048 CPUs, they take more than 5MB and 2MiB, respectively. With the kernel now taking around 25MB from stext to _end, the kernel can't reserve enough memory for PACA or LPPACA right after boot, and it panics. So, right after installing kdump-tools on artful, and rebooting, the kernel won't b
[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
** Description changed: - What happens is after I dock my laptop, lock it via clicking the lock icon, and wait ~30 minutes, one of the following three things happen ~50% of the time when I come back to unlock it: + What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the following three things happen ~50% of the time when I come back to unlock it: * Most of the time the computer is found shut down. * Sometimes the notebook screen flickers weirdly and one of the two external monitors show pixelation. * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking works. I have two external monitors attached to the docking station. When I dock my laptop, the battery indicator does recognize its charging. I've not seen this issue when: 1) With the laptop in the dock, while actively using the laptop. 2) With the laptop out of the dock and no external monitors present. This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10. Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 PC temperatures are normal as per lm-sensors. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS2YL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS2YL00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO -- 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/1727662 Title: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Triaged Bug description: What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the following three things happen ~50% of the time when I come back to unlock it: * Most of the time the computer is found shut down. * Sometimes the notebook screen flickers weirdly and one of the two external monitors show pixelation. * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking works. I have two external monitors attached to the docking station. When I dock my laptop, the battery indicator does recognize its charging. I've not seen this issue when: 1) With the laptop in the dock, while actively using the laptop. 2) With the laptop out of the dock and no external monitors present. This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10. Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 PC temperatures are normal as per lm-sensors. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmd
[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
It ahppened to me in ubuntu 16.04 after some upgades trying to update virutal box and a vm was running that's the only one thing i can say trying sudo apt install xserver-xorg-input-all -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Expired Status in linux source package in Yakkety: Won't Fix Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
Removing "quiet splash" from the parameters using the stock ubuntu kernel works as well. These disable the plymouth boot splash however. -- 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/1720930 Title: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Bug description: When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I get a hung shutdown with the message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to load firmware versions that do not exist on the system i.e. versions 33 then 32 of the firmware. It then seems to load version 31 of the firmware. Wireless features seem to work normally. The issues are just at shutdown time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dylan 1621 F pulseaudio CurrentDesktop: GNOME Date: Tue Oct 3 06:12:13 2017 HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX550VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE 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. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720930/+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 1730505] Re: [MacBookPro12, 1] SD Card Reader not working
*** This bug is a duplicate of bug 1531653 *** https://bugs.launchpad.net/bugs/1531653 Jim Hodapp, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following: 1) The one to test is at the very top line at the top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Also, you don't need to apport-collect further unless specifically requested to do so. It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed. Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. Thank you for your 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/1730505 Title: [MacBookPro12,1] SD Card Reader not working Status in linux package in Ubuntu: Confirmed Bug description: Related bug to this one: bug #1531653 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jhodapp4369 F pulseaudio /dev/snd/pcmC1D0p: jhodapp4369 F...m pulseaudio /dev/snd/controlC1: jhodapp4369 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 6 15:23:15 2017 HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6 InstallationDate: Installed on 2015-08-02 (827 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B07.1506051617 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.B07.1506051617:bd06/05/2015: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/1730505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : http
[Kernel-packages] [Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
Using the stock 4.13.8 seems to work, but using the latest ubuntu kernel (with canonical patches) does not despite it being based on 4.13.8. -- 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/1720930 Title: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Bug description: When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I get a hung shutdown with the message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to load firmware versions that do not exist on the system i.e. versions 33 then 32 of the firmware. It then seems to load version 31 of the firmware. Wireless features seem to work normally. The issues are just at shutdown time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dylan 1621 F pulseaudio CurrentDesktop: GNOME Date: Tue Oct 3 06:12:13 2017 HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX550VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE 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. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720930/+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 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)
> I'd say we go with option #2. Please provide information on how to proceed, > and how to > undo any changes we test :) ok, so first, these instructions may cause the card to hang; the system may need to be rebooted or the driver reloaded. The changes here can be undone by resetting the card; rebooting or reloading the driver. Also please note these instructions are ONLY FOR i40e NICs! The process here is to clear all the nic's hardware asserts, and then enable each of them one-by-one and try to reproduce the MDD event. That way, when it reproduces, we know exactly which hw assert triggered it. First, find your nic's pci address, e.g. ethtool -i NIC | grep bus-info Then (as root) cd to "/sys/kernel/debug/i40e/BUSID" (replace BUSID with your nic's actual pci addr). You should see a "command" file there. Now zero out the registers: $ echo write 0xe648c 0 > command $ echo write 0x442f4 0 > command Then, set a single bit; starting with 0x1 on the first register: $ echo write 0xe648c 0x1 > command Do normal testing. There are 3 possibilities at this step: a) you test long enough to be sure the problem was avoided b) your system and/or nic hangs due to an "uncaught" MDD event c) you reproduce the problem, and see the TX error and PF reset For either (a) or (b), that means this bit isn't the one we're looking for, so move to the next bit: $ echo write 0xe648c 0 > command $ echo write 0x442f4 0 > command $ echo write 0xe648c 0x2 > command Then retest. Replace "0x2" with incrementing bits, as you test each bit. Note this is setting individual bits, so the sequence to test is (in hex) 1, 2, 4, 8, 10, 20, 40, 80, 100, etc. This is a 32 bit register so the highest bit to test is 0x8000. If you test all bits in register 0xe648c without reproducing the problem, then move on to register 0x442f4 testing bit-by-bit again starting at 0x1 again. You should be able to reproduce the problem with one of the bits set in one of these two registers, according to what I've been told by Intel. As you set each bit, you should get output in your dmesg and/or syslog or kern.log, indicating the current value of the registers, e.g.: write: 0xe648c = 0x1 You can also manually read the registers at any time with: $ echo read 0xe648c > command $ echo read 0x442f4 > command you should see the results in dmesg/logs, e.g.: read: 0xe648c = 0x1 Once/if you do reproduce the problem, make note of the values for both registers (i.e. what bit was set), and report that back here. I'll check with Intel to find what the specific bit indicates the problem was. 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/1723127 Title: Intel i40e PF reset due to incorrect MDD detection (continues...) Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: This is a continuation from bug 1713553; a patch was added in that bug to attempt to fix this, and it may have helped reduce the issue but appears not to have fixed it, based on more reports. The issue is the i40e driver, when TSO is enabled, sometimes sees the NIC firmware issue a "MDD event" where MDD is "Malicious Driver Detection". This is vaguely defined in the i40e spec, but with no way to tell what the NIC actually saw that it didn't like. So, the driver can do nothing but print an error message and reset the PF (or VF). Unfortunately, this resets the interface, which causes an interruption in network traffic flow while the PF is resetting. See bug 1713553 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723127/+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 1730480] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005478/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] Re: Problem after 17.04 to 17.10 upgrade
I tried to use apport-collect -p linux with I hope success. -- 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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005479/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005474/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005472/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005471/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005477/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005473/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005468/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005475/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005469/+files/JournalErrors.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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730480] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005470/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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 1730680] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1730680 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730680 Title: Shutdown failure in 17.10 with Nvidia Nouveau Driver Status in linux package in Ubuntu: Incomplete Bug description: The following errors display at shutdown. The system never shuts down and I must hold down the power key to turn the system off. The hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX 960M. The display driver in use is the Nouveau driver. wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: rcu_sched self-detected stall on CPU $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 fqs:7490 $ (t=15000 jiffies g=41392 c=41391 q=3432) watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message INFO: task systemd-timesyn:305 blocked for more than 120 seconds. Tained: G DEL 4.13-0-16-generic $19-ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561] At this point I had to hold down the power key to turn off the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730680/+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 1730480] Re: Problem after 17.04 to 17.10 upgrade
apport information ** Tags added: apport-collected artful ** Description changed: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. + --- + ApportVersion: 2.20.7-0ubuntu3.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gherrick 1646 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 17.10 + HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 + InstallationDate: Installed on 2016-05-05 (551 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + IwConfig: + enp2s0no wireless extensions. + + lono wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset + ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-16-generic N/A + linux-backports-modules-4.13.0-16-generic N/A + linux-firmware 1.169 + RfKill: + + Tags: artful + Uname: Linux 4.13.0-16-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/31/2010 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: F10 + dmi.board.name: GA-MA74GMT-S2 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: + dmi.product.name: GA-MA74GMT-S2 + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005466/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-p
[Kernel-packages] [Bug 1730480] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1730480/+attachment/5005476/+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/1730480 Title: Problem after 17.04 to 17.10 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Problem after 17.04 to 17.10 upgrade - seven days ago. I have to boot using Grub, in recovery mode. System works ok. During power down, I get - A Stop Job is Running for Session C3 of User GDM - which waits for 1 minute 30 - and then proceeds to finish. System is an AMD64, with graphics on the motherboard. I will search for more detail if necessary. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gherrick 1646 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=26031761-8323-4a7b-85b2-0dc3fbcdb852 InstallationDate: Installed on 2016-05-05 (551 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA74GMT-S2 Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=f2bc2165-9cb7-467c-a941-8e5ae02ee038 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/31/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-MA74GMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd08/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA74GMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730480/+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
