[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
@Eden bar: If you are asking me: I got it fixed by local computer shop. By local I mean I found 3 in Slovakia capable of changing BIOS chip and this one was the cheapest and able to send courier to pick it up at bring it back with no hassle... I beleive you can find a guy capable of replacing BIOS chip almost anywhere. I know it may be expensive in some countries, if you are from western EU, consider sending the laptop to Slovakia, I can pretty much recommend one guy if you wish. I am still thinking about who should I blame? I told myself I will not install any Linux on my home PCs again. But I did not tell myself I will not buy Lenovo laptop again. Whose fault is this? Linux? Canonical? Lenovo? Bad luck? IDK... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) Lenovo G50-80 Lenovo S20-30 Lenovo Yoga 2 11" - 20332 Lenovo B40-70 Lenovo Z51-70 Lenovo B50-70 Lenovo Flex-10 --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-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/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable
Does the issue happen after a system suspend? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737934 Title: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable Status in linux package in Ubuntu: Incomplete Bug description: Seems related to these bugs: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748 Problem: At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems to lose access to the Samsung SM961 256GB SSD drive it has inside. When this happens the whole OS freezes up and when I try to power down I see a black terminal-like screen that prints the following errors: EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275 (or #741278): comm gmain (or systemd-journal or ...): reading directory iblock 0 This error seems to be repeated endlessly, though I've only let it go for a few minutes. No other errors are printed. This is the only drive it has. I don't know if this occurs in Windows too since I removed Windows and installed Ubuntu immediatly after updating the BIOS. Info: Distro: Ubuntu MATE 17.10 sudo uname -r 4.13.0-19-generic sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250) get-feature:0xc (Autonomous Power State Transition), Current value:0x01 Autonomous Power State Transition Enable (APSTE): Enabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 1] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 2] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 3] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 4] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 5] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 6] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 7] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 8] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 9] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[10] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[11] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[12] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[13] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[14] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[15] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[16] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[17] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[18] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[19] . Idle
[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
Yes I understand you and most people are asking for a resolution to "Not enough free handles to register service". However it is better for a bug's resolution if we focus on the problem that the original reporter was trying to describe. And that's a very different, unrelated problem. We certainly could rename this bug and commandeer it to be about "Not enough free handles to register service". But there's probably no need for that. If anyone would like a resolution to "Not enough free handles to register service" then please start by opening a bug for it here: https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug Very simple and very clean. -- 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/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1711075] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1706033 *** https://bugs.launchpad.net/bugs/1706033 --- Comment From shriy...@in.ibm.com 2017-12-13 23:26 EDT--- Verified with latest kernel on Ubuntu 16.04.03 and it works as expected = root@ltc-wspoon12:/usr/lib/linux-hwe-tools-4.10.0-42# ./perf test 1: vmlinux symtab matches kallsyms: Skip 2: Detect openat syscall event: Ok 3: Detect openat syscall event on all cpus: Ok 4: Read samples using the mmap interface : Ok 5: Parse event definition strings : Ok 6: PERF_RECORD_* events & perf_sample fields : Ok 7: Parse perf pmu format : Ok 8: DSO data read : Ok 9: DSO data cache : Ok 10: DSO data reopen: Ok 11: Roundtrip evsel->name : Ok 12: Parse sched tracepoints fields : Ok 13: syscalls:sys_enter_openat event fields : Ok 14: Setup struct perf_event_attr : Skip 15: Match and link multiple hists : Ok 16: 'import perf' in python: Ok 17: Breakpoint overflow signal handler : FAILED! 18: Breakpoint overflow sampling : FAILED! 19: Number of exit events of a simple workload : Ok 20: Software clock events period values: Ok 21: Object code reading: FAILED! 22: Sample parsing : Ok 23: Use a dummy software event to keep tracking: Ok 24: Parse with no sample_id_all bit set: Ok 25: Filter hist entries: Ok 26: Lookup mmap thread : Ok 27: Share thread mg: Ok 28: Sort output of hist entries: Ok 29: Cumulate child hist entries: Ok 30: Track with sched_switch: Ok 31: Filter fds with revents mask in a fdarray : Ok 32: Add fd to a fdarray, making it autogrow: Ok 33: kmod_path__parse : Ok 34: Thread map : Ok 35: LLVM search and compile: 35.1: Basic BPF llvm compile: Skip 35.2: kbuild searching : Skip 35.3: Compile source for BPF prologue generation: Skip 35.4: Compile source for BPF relocation : Skip 36: Session topology : Ok 37: BPF filter : 37.1: Basic BPF filtering : Skip 37.2: BPF prologue generation : Skip 37.3: BPF relocation checker : Skip 38: Synthesize thread map : Ok 39: Remove thread map : Ok 40: Synthesize cpu map : Ok 41: Synthesize stat config : Ok 42: Synthesize stat: Ok 43: Synthesize stat round : Ok 44: Synthesize attr update : Ok 45: Event times: Ok 46: Read backward ring buffer : Ok 47: Print cpu map : Ok 48: Probe SDT events : Skip 49: is_printable_array : Ok 50: Print bitmap : Ok 51: perf hooks : Ok 52: builtin clang support : Skip (not compiled in) 53: Test dwarf unwind : FAILED! root@ltc-wspoon12:/usr/lib/linux-hwe-tools-4.10.0-42# uname -a Linux ltc-wspoon12 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:55:56 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711075 Title: [Power 9, Power NV][WSP/Boston]Ubuntu 16.04.03 : perf test is hung at Breakpoint overflow signal handler Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Bug description: == Comment: # - Shriya R. Kulkarni <> - 2017-06-14 01:11:02 == Problem Description : = perf test is hung at Breakpoint overflow signal handler. Machine details : == System : WSP , P9 baremetal. OS : Ubuntu 16.04.03 uname -a : Linux ltc-wspoon3 4.10.0-23-generic #25~16.04.1-Ubuntu SMP Fri Jun 9 10:43:34 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Testing: root@ltc-wspoon3:~# perf test 1: vmlinux symtab matches kallsyms: Skip 2: Detect openat syscall event: Ok 3: Detect openat syscall event on all cpus: Ok 4: Read samples using the mmap interface : Ok 5: Parse event definition strings : Ok 6: PERF_RECORD_* events & perf_sample fields : Ok 7: Parse perf pmu format : Ok 8: DSO data read : Ok 9: DSO data
[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
Complement to #56, Ubuntu 16.04.3, Kernel 4.14.4, journalctl -b: Dec 13 20:44:33 alien bluetoothd[928]: Failed to obtain handles for "Service Changed" characteristic Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Error adding Link Loss service Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Current Time Service could not be registered Dec 13 20:44:33 alien bluetoothd[928]: gatt-time-server: Input/output error (5) Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service -- 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/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
This bug effects 128 people and closing it because you don't like the title feels wrong. Two Ask Ubuntu questions point to this Lanuchpad bug report in the hopes it will be solved: https://askubuntu.com/questions/757396/bluetooth-how-to-solve-not- enough-free-handles-to-register-service-error and https://askubuntu.com/questions/773629/16-04-bluetooth-error-not-enough- free-handles-to-register-service A Debian bug report suggests a solution by using -E (experimental) parameter on the systemd service exec doesn't work for Ubuntu 16.04, Kernel 4.14.4: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813949 When a hundred reported people are effected by "Not enough free handles to register service" and you don't want to look at it because the bug title isn't right, why not simply change the title? Something else to consider are the thousands of people effected by bluetooth connection problems, re-pairing, etc. What if the root of their problems was this bug that you don't want to look at? ** Bug watch added: Debian Bug tracker #813949 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813949 -- 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/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
This is also affecting Alpha Litebooks. After installed Ubuntu 17.10 I now get UEFI errors every time my computer starts and cannot restore UEFI boot entries from command line, it's bricked. Luckily I can still boot if I manually choose the grubx64 file on the EFI partition. My USB, PXE boot options are now missing as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) Lenovo G50-80 Lenovo S20-30 Lenovo Yoga 2 11" - 20332 Lenovo B40-70 Lenovo Z51-70 Lenovo B50-70 Lenovo Flex-10 --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-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/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1737942] Re: linux: 4.10.0-43.47 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-zesty ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737944,1737945 derivatives: 1737946 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 18:32 UTC -- swm properties -- + boot-testing-requested: true phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737942 Title: linux: 4.10.0-43.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737944,1737945 derivatives: 1737946 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 18:32 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737942/+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 1738105] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022439/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022437/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022438/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022440/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022441/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022432/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] Re: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot
I was able to boot into ubuntu using recover mode (modeset listed in line beginning with 'linux' after choosing advanced ubuntu in grub menu) ran apport as requested in email sent to me after creating ticket. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022433/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022436/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022435/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022443/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022434/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022442/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022431/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022444/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.303 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.303:bd09/12/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/1738105/+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 1738105] Re: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot
apport information ** Tags added: apport-collected artful ** Description changed: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' - I am so far unable to get a command prompt. I will attached the - requested logs if I am able to. + I am so far unable to get a command prompt. I will attached the requested logs if I am able to. + --- + ApportVersion: 2.20.7-0ubuntu3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: kesten 3015 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 17.10 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 + InstallationDate: Installed on 2017-12-13 (0 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + MachineType: ASUSTeK COMPUTER INC. UX550VE + 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 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset + ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-19-generic N/A + linux-backports-modules-4.13.0-19-generic N/A + linux-firmware 1.169 + Tags: artful + Uname: Linux 4.13.0-19-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/12/2017 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX550VE.303 + 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.303:bd09/12/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. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1738105/+attachment/5022430/+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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kesten 3015 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=9093411b-bc30-4888-a675-167b7cdb5c77 InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. UX550VE 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=1b38d281-e123-4127-80f6-03162125bc89 ro recovery nomodeset ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-19-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/12/2017 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
> #15 says problem went away but is on Kernel 4.4 and Kerne 4.8 > where message was "hacked" to not display. With kernels 4.9, 4.10, > etc... That's not the first time the kernel folks have done that. They do it in the crypto subsystem to hide messages that folks would want to see and fix, like the random number generator having no entropy but startup programs trucking on as if get_random_{u32,u64,int,long} succeeded. It would be nice to see the problem fixed rather than covering them up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584407 Title: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) Status in linux package in Ubuntu: Invalid Bug description: [ 0.016192] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) [ 0.016195] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20150930/psobject-227) [ 0.016222] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20150930/tbxfload-193) [ 0.021348] ACPI Error: 1 table load failures, 7 successful (20150930/tbxfload-214) I have noticed this ACPI error persisting in my syslog and dmesg. Based on what I have learnt from ACPI, acpitool -w and lspci, I think the error is related to Namespaces provided in the DDST on \_SB_.PCI0.XHC_.RHUB.HS11, which I think concerns the Root → System bus tree → PCI bus → USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) in my system. I have not found what .RHUB.HS11 refers too. I have tried changing my UEFI USB settings but to no avail. Appreciate help to fix this bug. I reported it as a question https://answers.launchpad.net/ubuntu/+question/293489 and to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553690. https://launchpad.net/~penalvch advice me to make this ubuntu-bug report. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ uname -r 4.4.0-22-generic MB Bios: ASUS z170m-plus version 0704 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sunbear1604 1905 F pulseaudio /dev/snd/controlC0: sunbear1604 1905 F pulseaudio CurrentDesktop: Unity Date: Sun May 22 07:48:53 2016 HibernationDevice: RESUME=UUID=c1eef599-9978-461e-a399-a04370b6ae59 InstallationDate: Installed on 2016-05-01 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=69a55da3-4a70-4239-8e7e-2430ceac525d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd02/18/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407/+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 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
#15 says problem went away but is on Kernel 4.4 and Kerne 4.8 where message was "hacked" to not display. With kernels 4.9, 4.10, etc. the message reappears as per bug report here: https://bugzilla.kernel.org/show_bug.cgi?id=193531 #17 closing this bug based upon #15 should be reconsidered. Also note this bug is a duplicate of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690502 which has fewer subscribers but more accurate information. There is a third duplicate bug report in launchpad which I don't have the link for just now. ** Bug watch added: Linux Kernel Bug Tracker #193531 https://bugzilla.kernel.org/show_bug.cgi?id=193531 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1584407 Title: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) Status in linux package in Ubuntu: Invalid Bug description: [ 0.016192] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210) [ 0.016195] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20150930/psobject-227) [ 0.016222] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20150930/tbxfload-193) [ 0.021348] ACPI Error: 1 table load failures, 7 successful (20150930/tbxfload-214) I have noticed this ACPI error persisting in my syslog and dmesg. Based on what I have learnt from ACPI, acpitool -w and lspci, I think the error is related to Namespaces provided in the DDST on \_SB_.PCI0.XHC_.RHUB.HS11, which I think concerns the Root → System bus tree → PCI bus → USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) in my system. I have not found what .RHUB.HS11 refers too. I have tried changing my UEFI USB settings but to no avail. Appreciate help to fix this bug. I reported it as a question https://answers.launchpad.net/ubuntu/+question/293489 and to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553690. https://launchpad.net/~penalvch advice me to make this ubuntu-bug report. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ uname -r 4.4.0-22-generic MB Bios: ASUS z170m-plus version 0704 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sunbear1604 1905 F pulseaudio /dev/snd/controlC0: sunbear1604 1905 F pulseaudio CurrentDesktop: Unity Date: Sun May 22 07:48:53 2016 HibernationDevice: RESUME=UUID=c1eef599-9978-461e-a399-a04370b6ae59 InstallationDate: Installed on 2016-05-01 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=69a55da3-4a70-4239-8e7e-2430ceac525d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: Default string dmi.board.name: Z170M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd02/18/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584407/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Yoga 33-11 IBR affected - result is absolute brick without any signs of life. Totally dead. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) Lenovo G50-80 Lenovo S20-30 Lenovo Yoga 2 11" - 20332 Lenovo B40-70 Lenovo Z51-70 Lenovo B50-70 Lenovo Flex-10 --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-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/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1738105] 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 1738105 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/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: Incomplete Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738105/+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 1738105] [NEW] asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot
Public bug reported: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738105 Title: asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card will not boot Status in linux package in Ubuntu: New Bug description: Getting A start job is running for detect the available GPUs and deal with any system changes This looks like a reprise of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692305?comments=all 'I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes "' I am so far unable to get a command prompt. I will attached the requested logs if I am able to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738105/+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 1692305] Re: Ubuntu will not boot on ASUS Zenbook UX501VW-FJ045T
I am seeing the same issue for asus zen ultrabook UX550VE-DB71T with 1050Ti graphics card https://www.amazon.com/gp/product/B07532Y2LL/ref=oh_aui_detailpage_o01_s00?ie=UTF8=1 I am trying to install the official ubuntu 17.10-desktop-amd64.iso downloaded Dec 13th 2017 sha256 = aaf4ba1809e08f6108f1e410174ebcbd49af5cc4f6493ab3d98d0683289bbc6e shasum -a 256 -c SHA256SUMS 2>&1 | grep OK ubuntu-17.10-desktop-amd64.iso: OK so far, I have not been able to successfully boot either from live cd usb trial or with the install. I will attach files from apport if that changes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1692305 Title: Ubuntu will not boot on ASUS Zenbook UX501VW-FJ045T Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu will not boot on my ASUS UX501VW-FJ045T, unless I use the NOMODESET option in GRUB. I disabled the splashscreen and I could see that the system hangs when trying to detect the GPU(s) showing the message: "A start job is running for detect the available GPUs and deal with any system changes " The laptop features Optimus technology, with an Intel HD Graphics 530 and an NVIDIA GeForce GTX 960M You can see the error in the picture attached to the report. Ubuntu version: UBUNTU GNOME 17.04 X64 I am more than willing to help with this with further testing or information, if needed Thank you! --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1525 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=240ae0a6-ce16-4767-808a-ece692b18ad7 InstallationDate: Installed on 2017-05-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. N501VW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=3dc5d201-0ddb-47f7-a48d-c49fde28eaa0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-19-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/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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.:bvrN501VW.207:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501VW 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/1692305/+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 1737639] Re: Touchpad stopped working in Dell XPS13
I installed trisquel_7.0_amd64.iso The touchpad works. I have includes devices under trisquel, with the touchpad below: I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input6 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 ** Attachment added: "cat /proc/bus/input/devices under trisquel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+attachment/5022399/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737639 Title: Touchpad stopped working in Dell XPS13 Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell XPS 13 9343 Recently, the touchpad stopped working. The touchpad works under the BIOS, so I believe that it is not a hardware issue, but a Linux kernel bug. The touchpad does not show up in cat /proc/bus/input/devices For the touchpad, the Vendor name is COMPAL and the Vendor Part Number is PK09000FS0L The problem is currently visible in 4.13.0-16-generic though this kernel originally worked, I believe, and 4.13.0-17 failed. I continued to use 16 for a while, but after the upgrade to 4.13.0-19, 4.13.0-16 stopped working 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 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kevin 6040 F pulseaudio /dev/snd/controlC0: kevin 6040 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:06:29 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b35857db-041a-40cd-ab90-b6bd03ebad0d InstallationDate: Installed on 2015-05-18 (938 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 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-16-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash i915.i915_enable_rc6=1 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.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (52 days ago) dmi.bios.date: 06/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/16/2017:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+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 1737639] Re: Touchpad stopped working in Dell XPS13
I installed trisquel_7.0_amd64.iso The touchpad works. I have includes devices under trisquel, with the touchpad below: I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input6 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 ** Attachment added: "cat /proc/bus/input/devices under trisquel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+attachment/5022398/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737639 Title: Touchpad stopped working in Dell XPS13 Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell XPS 13 9343 Recently, the touchpad stopped working. The touchpad works under the BIOS, so I believe that it is not a hardware issue, but a Linux kernel bug. The touchpad does not show up in cat /proc/bus/input/devices For the touchpad, the Vendor name is COMPAL and the Vendor Part Number is PK09000FS0L The problem is currently visible in 4.13.0-16-generic though this kernel originally worked, I believe, and 4.13.0-17 failed. I continued to use 16 for a while, but after the upgrade to 4.13.0-19, 4.13.0-16 stopped working 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 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kevin 6040 F pulseaudio /dev/snd/controlC0: kevin 6040 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:06:29 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b35857db-041a-40cd-ab90-b6bd03ebad0d InstallationDate: Installed on 2015-05-18 (938 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 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-16-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash i915.i915_enable_rc6=1 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.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (52 days ago) dmi.bios.date: 06/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/16/2017:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+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 1737639] Re: Touchpad stopped working in Dell XPS13
I installed trisquel_7.0_amd64.iso The touchpad works. I have includes devices under trisquel, with the touchpad below: I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input6 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 ** Attachment added: "cat /proc/bus/input/devices under trisquel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+attachment/5022397/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737639 Title: Touchpad stopped working in Dell XPS13 Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell XPS 13 9343 Recently, the touchpad stopped working. The touchpad works under the BIOS, so I believe that it is not a hardware issue, but a Linux kernel bug. The touchpad does not show up in cat /proc/bus/input/devices For the touchpad, the Vendor name is COMPAL and the Vendor Part Number is PK09000FS0L The problem is currently visible in 4.13.0-16-generic though this kernel originally worked, I believe, and 4.13.0-17 failed. I continued to use 16 for a while, but after the upgrade to 4.13.0-19, 4.13.0-16 stopped working 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 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kevin 6040 F pulseaudio /dev/snd/controlC0: kevin 6040 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 15:06:29 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=b35857db-041a-40cd-ab90-b6bd03ebad0d InstallationDate: Installed on 2015-05-18 (938 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 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-16-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash i915.i915_enable_rc6=1 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.1 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (52 days ago) dmi.bios.date: 06/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd06/16/2017:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737639/+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 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting
Upstream kernel test - kernel 4.15-rc3 Test results: https://bugs.freedesktop.org/show_bug.cgi?id=101483#c32 Bug fixed in this upstream kernel! ** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.13-rc4 latest-bios-f.41 ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.15-rc3 latest-bios-f.45 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639517 Title: [HP Pavilion Notebook - 17-g164ng] black screen when booting Status in linux package in Ubuntu: Confirmed Bug description: When booting the screen is black – backlight on – off - on. When HDD is inactive - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or Strg + Alt + Del - remote access e.g. using ssh is possible Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10. My notebook is a HP Pavilion 17-g164ng with an AMD A10-8780P APU and 2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz. It seems very similar to that described in #1597079. The bug report was generated from a remote PC. My HP notebook was started without any workaround parameters. This apport doesn't display the second graphic subsystem Topaz R7 as an apport generated with nomodeset xforcevesa. WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver. WORKAROUND: When booting in UEFI mode, use kernel parameters: nomodeset or: nomodeset xforcevesa Resolution without xforcevesa: 800x600 Resolution with xforcevesa: 1600x900 – the optimal resolution ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 5 23:40:19 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:80b6] InstallationDate: Installed on 2016-11-03 (2 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.41 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B6 dmi.board.vendor: HP dmi.board.version: 81.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Nov 5 23:32:11 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.1 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639517/+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 1731060] Re: package linux-image-extra-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di err
I had this problem using sudo apt-get upgrade apparently, with Nvidia's card activated, the problem persists even if you re-configure dpkg. The solution was to change to Intel's card, perhaps with sudo prime-select intel. Worked for me :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731060 Title: package linux-image-extra-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 Status in linux package in Ubuntu: Incomplete Bug description: The uninstall process run forever with this last line as output: run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-17-generic /boot/vmlinuz-4.13.0-17-generic ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1521 F pulseaudio casa 2790 F pulseaudio /dev/snd/controlC0: gdm1521 F pulseaudio casa 2790 F pulseaudio Date: Wed Nov 8 23:03:53 2017 ErrorMessage: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 HibernationDevice: RESUME=UUID=b1a7755c-92df-48fe-92d2-66de15fbb008 InstallationDate: Installed on 2015-10-23 (747 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20ANCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=942dc08f-9465-4002-8ffb-c1fbe03f7a04 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 SourcePackage: linux Title: package linux-image-extra-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: il sottoprocesso installato script di post-removal ha restituito lo stato di errore 1 UpgradeStatus: Upgraded to artful on 2017-10-21 (18 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GLET80WW (2.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET80WW(2.34):bd07/23/2015:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731060/+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 1737913] Re: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1737911 phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1737913 Title: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1737911 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737913/+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 1721809] Re: The touchpad doesn't work on Lenovo Ideapad 320
Sorry for my late reply. Linux v4.17 gave me the same identical issue. I could not easily post here at the time because of the AppArmor bug. Now I reinstalled (x)ubuntu 17.10 on my laptop, and after I upgraded Linux to the v4.15-rc3 from the mainline, the trackpad works perfectly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721809 Title: The touchpad doesn't work on Lenovo Ideapad 320 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Simply the touchpad doosn't work. Sometimes i can use it for a few seconds when the OS is just turned on and then it stops. I tried to activate it using the hotkey, but unsuccessfully. I can use instead my USB mouse, that works perfectly. 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: enrico 1274 F pulseaudio /dev/snd/controlC1: enrico 1274 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 17:42:57 2017 InstallationDate: Installed on 2017-10-06 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 80XS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=4050ca72-6a32-4a35-9f26-c9013d94abdb 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: 05/22/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN16WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.modalias: dmi:bvnLENOVO:bvr5QCN16WW:bd05/22/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1721809/+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 1737316] Re: Having installed 17.10 I'm getting hardware errors on boot
Hi there. I'm back to 17.10 failing to boot cleanly at all. 16.4LTS boots fine no problem. On 11 December 2017 20:19:24 GMT+00:00, Joseph Salisburywrote: >Would it be possible for you to test the latest upstream kernel? Refer >to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the >latest >v4.15 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.15-rc3 > >** Changed in: linux (Ubuntu) > Importance: Undecided => High > >** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > >** Tags added: kernel-da-key > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1737316 > >Title: > Having installed 17.10 I'm getting hardware errors on boot > >Status in linux package in Ubuntu: > Incomplete > >Bug description: > I'm getting the i915 uncleared fifo underrun on pipe A errors. > > The system won't boot cleanly. I'm using Xorg rather than Wayland as > that appears to be a bit more stable. > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: linux-image-4.13.0-17-generic 4.13.0-17.20 > ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 > Uname: Linux 4.13.0-17-generic x86_64 > ApportVersion: 2.20.7-0ubuntu3.5 > Architecture: amd64 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC1: james 3855 F pulseaudio > /dev/snd/controlC0: james 3855 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Sat Dec 9 12:31:31 2017 > HibernationDevice: RESUME=UUID=d7a968e5-99de-41f8-b764-381e913ec11d > InstallationDate: Installed on 2014-09-12 (1184 days ago) >InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 >(20140722.2) > Lsusb: > Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. > Bus 001 Device 002: ID 8087:8000 Intel Corp. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: Hewlett-Packard HP 15 Notebook PC > ProcFB: 0 inteldrmfb >ProcKernelCmdLine: >BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed >root=UUID=c8fe4fc7-a4b3-4389-a0f7-06593d9cf223 ro quiet splash > RelatedPackageVersions: > linux-restricted-modules-4.13.0-17-generic N/A > linux-backports-modules-4.13.0-17-generic N/A > linux-firmware 1.169 > RfKill: > 0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > SourcePackage: linux > UpgradeStatus: Upgraded to artful on 2017-12-02 (6 days ago) > dmi.bios.date: 05/21/2014 > dmi.bios.vendor: Insyde > dmi.bios.version: F.18 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: 2211 > dmi.board.vendor: Hewlett-Packard > dmi.board.version: 86.28 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: Chassis Version >dmi.modalias: >dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn2211:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV > dmi.product.name: HP 15 Notebook PC > dmi.product.version: 097610405F0620180 > dmi.sys.vendor: Hewlett-Packard > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737316/+subscriptions -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737316 Title: Having installed 17.10 I'm getting hardware errors on boot Status in linux package in Ubuntu: Incomplete Bug description: I'm getting the i915 uncleared fifo underrun on pipe A errors. The system won't boot cleanly. I'm using Xorg rather than Wayland as that appears to be a bit more stable. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-17-generic 4.13.0-17.20 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3855 F pulseaudio /dev/snd/controlC0: james 3855 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 9 12:31:31 2017 HibernationDevice: RESUME=UUID=d7a968e5-99de-41f8-b764-381e913ec11d InstallationDate:
[Kernel-packages] [Bug 1738081] Re: package linux-image-4.4.0-103-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
*** This bug is a duplicate of bug 1737234 *** https://bugs.launchpad.net/bugs/1737234 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1737234, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1737234 package linux-image-4.4.0-103-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738081 Title: package linux-image-4.4.0-103-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux package in Ubuntu: New Bug description: problem : Package broken cause : .../linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb ... This kernel does not support a non-PAE CPU. Installation : Xubuntu 16.04 with option forcepae Material : laptop IBM T41 Similar problem : [Kernel-packages] [Bug 1737234 (https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg260204.html) Below details: jyl@jyl-ThinkPad-T41:~$ cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 jyl@jyl-ThinkPad-T41:~$ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 jyl@jyl-ThinkPad-T41:~$ jyl@jyl-ThinkPad-T41:~$ sudo apt-get clean jyl@jyl-ThinkPad-T41:~$ sudo apt-get update Atteint:1 http://fr.archive.ubuntu.com/ubuntu xenial InRelease Réception de:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Atteint:3 http://fr.archive.ubuntu.com/ubuntu xenial-updates InRelease Atteint:4 http://fr.archive.ubuntu.com/ubuntu xenial-backports InRelease Réception de:5 http://security.ubuntu.com/ubuntu xenial-security/main i386 DEP-11 Metadata [62,4 kB] Réception de:6 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [62,6 kB] Réception de:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 DEP-11 Metadata [51,3 kB] Réception de:8 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [85,1 kB] 364 ko réceptionnés en 2s (153 ko/s) Lecture des listes de paquets... Fait jyl@jyl-ThinkPad-T41:~$ sudo apt-get install -f Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Correction des dépendances... Fait The following additional packages will be installed: linux-image-4.4.0-103-generic Paquets suggérés : fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools Les NOUVEAUX paquets suivants seront installés : linux-image-4.4.0-103-generic 0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour. 3 partiellement installés ou enlevés. Il est nécessaire de prendre 20,6 Mo dans les archives. Après cette opération, 48,7 Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] O Réception de:1 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main i386 linux-image-4.4.0-103-generic i386 4.4.0-103.126 [20,6 MB] 20,6 Mo réceptionnés en 8s (2 368 ko/s) (Lecture de la base de données... 190476 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: erreur de traitement de l'archive /var/cache/apt/archives/linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb (--unpack) : le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-103-generic /boot/vmlinuz-4.4.0-103-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-103-generic /boot/vmlinuz-4.4.0-103-generic Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) jyl@jyl-ThinkPad-T41:~$ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-103-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686
[Kernel-packages] [Bug 1738081] [NEW] package linux-image-4.4.0-103-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Public bug reported: problem : Package broken cause : .../linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb ... This kernel does not support a non-PAE CPU. Installation : Xubuntu 16.04 with option forcepae Material : laptop IBM T41 Similar problem : [Kernel-packages] [Bug 1737234 (https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg260204.html) Below details: jyl@jyl-ThinkPad-T41:~$ cat /proc/version_signature Ubuntu 4.4.0-21.37-generic 4.4.6 jyl@jyl-ThinkPad-T41:~$ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 jyl@jyl-ThinkPad-T41:~$ jyl@jyl-ThinkPad-T41:~$ sudo apt-get clean jyl@jyl-ThinkPad-T41:~$ sudo apt-get update Atteint:1 http://fr.archive.ubuntu.com/ubuntu xenial InRelease Réception de:2 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Atteint:3 http://fr.archive.ubuntu.com/ubuntu xenial-updates InRelease Atteint:4 http://fr.archive.ubuntu.com/ubuntu xenial-backports InRelease Réception de:5 http://security.ubuntu.com/ubuntu xenial-security/main i386 DEP-11 Metadata [62,4 kB] Réception de:6 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 Icons [62,6 kB] Réception de:7 http://security.ubuntu.com/ubuntu xenial-security/universe i386 DEP-11 Metadata [51,3 kB] Réception de:8 http://security.ubuntu.com/ubuntu xenial-security/universe DEP-11 64x64 Icons [85,1 kB] 364 ko réceptionnés en 2s (153 ko/s) Lecture des listes de paquets... Fait jyl@jyl-ThinkPad-T41:~$ sudo apt-get install -f Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Correction des dépendances... Fait The following additional packages will be installed: linux-image-4.4.0-103-generic Paquets suggérés : fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools Les NOUVEAUX paquets suivants seront installés : linux-image-4.4.0-103-generic 0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour. 3 partiellement installés ou enlevés. Il est nécessaire de prendre 20,6 Mo dans les archives. Après cette opération, 48,7 Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] O Réception de:1 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main i386 linux-image-4.4.0-103-generic i386 4.4.0-103.126 [20,6 MB] 20,6 Mo réceptionnés en 8s (2 368 ko/s) (Lecture de la base de données... 190476 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: erreur de traitement de l'archive /var/cache/apt/archives/linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb (--unpack) : le sous-processus nouveau script pre-installation a retourné une erreur de sortie d'état 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-103-generic /boot/vmlinuz-4.4.0-103-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-103-generic /boot/vmlinuz-4.4.0-103-generic Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) jyl@jyl-ThinkPad-T41:~$ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-103-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jyl1031 F pulseaudio Date: Wed Dec 13 20:37:20 2017 DuplicateSignature: package:linux-image-4.4.0-103-generic:(not installed) Preparing to unpack .../linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-103-generic_4.4.0-103.126_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=6a706e1d-8a56-4d05-8505-2c091fa2842b InstallationDate: Installed on 2017-12-13 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 3938:1031 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: IBM 23747JG PccardctlIdent: Socket 0: no product info available Socket 1: no product info available PccardctlStatus: Socket 0: no
[Kernel-packages] [Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
Testing on arm64, the workaround of adding xenial-proposed via maas doesn't work - the newer ubuntu-fan package isn't being installed http://paste.ubuntu.com/26178859/ I don't know how that can be, since the repo is being added (or should be added) before juju installs ubuntu-fan. -- 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/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures Status in juju: Triaged Status in ubuntu-fan package in Ubuntu: Confirmed Status in ubuntu-fan source package in Xenial: Fix Committed Bug description: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+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 1388559] Re: failed command: WRITE FPDMA QUEUED
I got same problem using latest 4.15rc-3 ec 13 20:57:59 bigone kernel: [ 23.575115] ata10.00: status: { DRDY } Dec 13 20:57:59 bigone kernel: [ 23.577829] ata10.00: failed command: WRITE FPDMA QUEUED Dec 13 20:57:59 bigone kernel: [ 23.580536] ata10.00: cmd 61/08:f0:00:08:00/00:00:02:00:00/40 tag 30 ncq dma 4096 out Dec 13 20:57:59 bigone kernel: [ 23.580536] res 40/00:5c:e8:29:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Dec 13 20:57:59 bigone kernel: [ 23.585924] ata10.00: status: { DRDY } Dec 13 20:57:59 bigone kernel: [ 23.588651] ata10: hard resetting link I figured out that the issue appers only when SATA disk connected to the COM4 port of the ASM1062 board while if your try to connect to the other internal connector ( COM3 ) it doesn't report any issue 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/1388559 Title: failed command: WRITE FPDMA QUEUED Status in linux package in Ubuntu: Expired Bug description: When copying files and hdd finished copy or ask about overwriting existing file i see those in log [ 6135.118326] ata7.00: exception Emask 0x10 SAct 0x1 SErr 0x40 action 0x6 frozen [ 6135.118330] ata7.00: irq_stat 0x0800, interface fatal error [ 6135.118332] ata7: SError: { Handshk } [ 6135.118334] ata7.00: failed command: WRITE FPDMA QUEUED [ 6135.118337] ata7.00: cmd 61/68:00:70:7f:f1/00:00:39:00:00/40 tag 0 ncq 53248 out res 40/00:04:70:7f:f1/00:00:39:00:00/40 Emask 0x10 (ATA bus error) [ 6135.118338] ata7.00: status: { DRDY } [ 6135.118341] ata7: hard resetting link [ 6135.610187] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 6135.611918] ata7.00: configured for UDMA/133 [ 6135.611929] ata7: EH complete [ 8448.150362] ata7.00: exception Emask 0x10 SAct 0x200 SErr 0x40 action 0x6 frozen [ 8448.150372] ata7.00: irq_stat 0x0800, interface fatal error [ 8448.150376] ata7: SError: { Handshk } [ 8448.150381] ata7.00: failed command: WRITE FPDMA QUEUED [ 8448.150385] ata7.00: cmd 61/68:48:d0:5e:ea/01:00:39:00:00/40 tag 9 ncq 184320 out res 40/00:4c:d0:5e:ea/00:00:39:00:00/40 Emask 0x10 (ATA bus error) [ 8448.150387] ata7.00: status: { DRDY } [ 8448.150394] ata7: hard resetting link [ 8448.642148] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 8448.643852] ata7.00: configured for UDMA/133 [ 8448.643861] ata7: EH complete Hdd is connected to SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: gore 2187 F...m pulseaudio /dev/snd/controlC0: gore 2187 F pulseaudio /dev/snd/controlC1: gore 2187 F pulseaudio Date: Sun Nov 2 14:20:55 2014 HibernationDevice: RESUME=UUID=224f363e-5d95-4537-8bd6-54c7b2b63b2b InstallationDate: Installed on 2014-10-31 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=597137be-c691-4f7f-9328-cf32dc5905a2 ro quiet splash drm.debug=0 drm.vblankoffdelay=1 i915.semaphores=0 i915.modeset=1 i915.use_mmio_flip=1 i915.powersave=1 i915.enable_ips=1 i915.disable_power_well=1 i915.enable_hangcheck=1 i915.enable_cmd_parser=1 i915.fastboot=0 i915.enable_ppgtt=1 i915.reset=0 i915.lvds_use_ssc=0 i915.enable_psr=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2102:bd07/29/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go
[Kernel-packages] [Bug 1738073] [NEW] thunderx2: i2c driver PEC and ACPI clock fixes
Public bug reported: [Impact] The i2c input frequency is currently hardcoded in the driver. This may not match the actual frequency used by the platform. Upstream has updated the driver to pull the frequency from firmware. [Test Case] The updated driver will detect the CAV9007 ACPI ID: ubuntu@starbuck:~$ dmesg | grep xlp9xx-i2c [ 47.723562] xlp9xx-i2c CAV9007:02: i2c transfer timed out! ^^^ The old driver will not claim this device. [Regression Risk] The changes are restricted to a driver that appears to be only used on MIPS platforms (which we don't support) and Cavium ThunderX2 systems that we've specifically tested upon. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Artful) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => In Progress ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738073 Title: thunderx2: i2c driver PEC and ACPI clock fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: [Impact] The i2c input frequency is currently hardcoded in the driver. This may not match the actual frequency used by the platform. Upstream has updated the driver to pull the frequency from firmware. [Test Case] The updated driver will detect the CAV9007 ACPI ID: ubuntu@starbuck:~$ dmesg | grep xlp9xx-i2c [ 47.723562] xlp9xx-i2c CAV9007:02: i2c transfer timed out! ^^^ The old driver will not claim this device. [Regression Risk] The changes are restricted to a driver that appears to be only used on MIPS platforms (which we don't support) and Cavium ThunderX2 systems that we've specifically tested upon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738073/+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 1737511] Re: linux: 4.4.0-104.127 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing 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/1737511 Title: linux: 4.4.0-104.127 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737512,1737514 derivatives: 1737515,1737516,1737517,1737518,1737519,1737520 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737511/+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 1737515] Re: linux-aws: 4.4.0-1044.53 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1737515 Title: linux-aws: 4.4.0-1044.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1737511 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737515/+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 1737903] Re: linux: 4.13.0-20.23 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737905,1737906,1737907,1737908 derivatives: 1737909 + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 13. December 2017 19:36 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737905,1737906,1737907,1737908 derivatives: 1737909 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 19:36 UTC + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737903 Title: linux: 4.13.0-20.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737905,1737906,1737907,1737908 derivatives: 1737909 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 19:36 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737903/+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 1737942] Re: linux: 4.10.0-43.47 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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/1737942 Title: linux: 4.10.0-43.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737944,1737945 derivatives: 1737946 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 18:32 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737942/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
+1 for this. Tried the BIOS recovery process for bricked laptop (Fn - R with BIOS in USB) completed successfully but settings still remained and can not be modified. Laptop is bricked. Device details below: Product Name: Lenovo Y50-70 BIOS Version: 9ECN43WW(v3.03) EC Version: 9EEC43WW(v3.03) MTM: 20378 Board Number: 3521141700177 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) Lenovo G50-80 Lenovo S20-30 Lenovo Yoga 2 11" - 20332 Lenovo B40-70 Lenovo Z51-70 Lenovo B50-70 Lenovo Flex-10 --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-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/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1738060] 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/1738060 Title: Cherry Trail Support Status in linux package in Ubuntu: Confirmed Bug description: Cherry Trail USb 3.0 support not stable Getting IO error, but with the hub it works. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/comprC1D2', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Wed Dec 13 12:44:41 2017 InstallationDate: Installed on 2017-12-10 (3 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Default string Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=980de5c4-1458-48a8-b8ab-f9a69c7b4e69 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux StagingDrivers: r8723bs UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/18/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.version: Default string dmi.sys.vendor: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1738060/+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 1738060] [NEW] Cherry Trail Support
Public bug reported: Cherry Trail USb 3.0 support not stable Getting IO error, but with the hub it works. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/comprC1D2', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Wed Dec 13 12:44:41 2017 InstallationDate: Installed on 2017-12-10 (3 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Default string Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=980de5c4-1458-48a8-b8ab-f9a69c7b4e69 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-19-generic N/A linux-backports-modules-4.13.0-19-generic N/A linux-firmware 1.169.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux StagingDrivers: r8723bs UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/18/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.version: Default string dmi.sys.vendor: Default string ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1738060 Title: Cherry Trail Support Status in linux package in Ubuntu: New Bug description: Cherry Trail USb 3.0 support not stable Getting IO error, but with the hub it works. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-19-generic 4.13.0-19.22 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-19-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/comprC1D2', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Wed Dec 13 12:44:41 2017 InstallationDate: Installed on 2017-12-10 (3 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Default string Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed
[Kernel-packages] [Bug 1737942] Re: linux: 4.10.0-43.47 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737944,1737945 derivatives: 1737946 + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 13. December 2017 18:32 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737944,1737945 derivatives: 1737946 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 18:32 UTC + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737942 Title: linux: 4.10.0-43.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737944,1737945 derivatives: 1737946 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 18:32 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737942/+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 1711104] Comment bridged from LTC Bugzilla
--- Comment From shriy...@in.ibm.com 2017-12-13 13:32 EDT--- (In reply to comment #17) > Yes, that commit is in the test kernel posted at: > http://kernel.ubuntu.com/~jsalisbury/lp1711104/ Tested the kernel given in the above link : uname -a : Linux ltc-wspoon12 4.10.0-33-generic #37~lp1711104 SMP Wed Sep 13 19:55:56 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Hardware : Witherspoon + DD2.1 FW : 1742Eg root@ltc-wspoon12:~# cat /etc/os-release NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial Test results : Testing looks good and results are as expected. root@ltc-wspoon12:~# ./perf stat -e r4d05e -- sleep 1 Performance counter stats for 'sleep 1': 95,723 r4d05e 1.001016884 seconds time elapsed root@ltc-wspoon12:~# ./perf stat -e r4d05e -- sleep 2 Performance counter stats for 'sleep 2': 95,859 r4d05e 2.000996600 seconds time elapsed root@ltc-wspoon12:~# ./perf stat -e r3e054 -- sleep 3 Performance counter stats for 'sleep 3': 8,973 r3e054 3.001030248 seconds time elapsed root@ltc-wspoon12:~# ./perf stat -e r400f0 -- sleep 3 Performance counter stats for 'sleep 3': 8,905 r400f0 3.000995167 seconds time elapsed -- root@ltc-wspoon12:~# ./perf stat -e r200f4 -- sleep 3 Performance counter stats for 'sleep 3': 1,411,106 r200f4 3.000942725 seconds time elapsed root@ltc-wspoon12:~# ^C root@ltc-wspoon12:~# ./perf stat -e r400fa -- sleep 3 Performance counter stats for 'sleep 3': 544,977 r400fa 3.000928921 seconds time elapsed -- root@ltc-wspoon12:~# ./perf stat -e r500fa -- sleep 3 Performance counter stats for 'sleep 3': 550,846 r500fa 3.000949027 seconds time elapsed - root@ltc-wspoon12:~/ebizzy-0.3# ./perf record -e r67340101ea -d --weight ./ebizzy -m -n 100 -P -R -s 5120 -S 50 -t 3 ^C[ perf record: Woken up 93 times to write data ] [ perf record: Captured and wrote 24.162 MB perf.data (32508 samples) ] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1711104 Title: [P9][Ubuntu 16.04.03] Additional PMU fixes for P9 Status in The Ubuntu-power-systems project: Incomplete Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Status in perforate source package in Zesty: New Bug description: == Comment: #0 - Shriya R. Kulkarni- 2017-08-16 04:07:45 == Please integrate the following PMU fixes for P9. 93fc5ca9a0048c ('powerpc/perf: Cleanup of PM_BR_CMPL vs. PM_BRU_CMPL in Power9 event list') 91e0bd1e62519b ('powerpc/perf: Add PM_LD_MISS_L1 and PM_BR_2PATH to power9 event list') 70a7e720998d5b ('powerpc/perf: Factor out PPMU_ONLY_COUNT_RUN check code from power8') 7aa345d84245a7 ('powerpc/perf: Update default sdar_mode value for power9') 101dd590a7fa37 ('powerpc/perf: Avoid spurious PMU interrupts after idle') bdd21ddb919d28 ('powerpc/perf: Avoid spurious PMU interrupts after idle on Power9') 3f0bd8dad0db73 ('powerpc/perf: Add POWER9 alternate PM_RUN_CYC and PM_RUN_INST_CMPL events') 20dd4c624d2515 ('powerpc/perf: Fix SDAR_MODE value for continous sampling on Power9') 24bedcb7c81137 ('powerpc/perf: Fix branch event code for power9') 8c218578fcbbbd ('powerpc/perf: Fix Power9 test_adder fields') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1711104/+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 1736770] Re: debian-installer/main-menu changes priority
I take this back, it is still an issue with the amd64 ISO: https://paste.ubuntu.com/26178135/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736770 Title: debian-installer/main-menu changes priority Status in debconf package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: During a test install of Bionic it appears that the debian-installer /main-menu option changes priority from medium to critical part way through the test: Dec 6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu Dec 6 04:18:55 debconf: <-- 30 question skipped Dec 6 04:18:55 debconf: --> GO ... Dec 6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title Description Dec 6 04:19:54 debconf: <-- 0 Install the system Dec 6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system Dec 6 04:19:54 debconf: <-- 0 value set Dec 6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu Dec 6 04:19:54 debconf: <-- 0 question will be asked Dec 6 04:19:54 debconf: --> GO Working test on Dec 1: https://paste.ubuntu.com/26126878/ Failing test on Dec 6: https://paste.ubuntu.com/26126090/ Steps to reproduce: 1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ 2. Pull out the kernel and initrd $ mkdir iso $ bsdtar xfp bionic-server-amd64.iso -C iso $ cp iso/install/vmlinuz . $ cp iso/install/initrd.gz . 3. Create QEMU disk $ qemu-img create -f qcow2 vdisk.img 4G 4. Launch ISO via QEMU $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \ -initrd initrd.gz -kernel vmlinuz -display none -nographic \ -hda vdisk.img -cdrom bionic-server-amd64.iso \ -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical' 5. Proceed with the install by 1) enter user info and 2) select disk 6. Eventually the "Ubuntu installer main menu" will appear. Even if you click on "Install the system" the installation step will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Zesty) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Artful) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => 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/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in linux source package in Zesty: Incomplete Status in linux source package in Artful: Incomplete Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+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 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
I can verify the fix works in my environment using whats in xenial- proposed http://paste.ubuntu.com/26178059/ Thanks! -- 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/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures Status in juju: Triaged Status in ubuntu-fan package in Ubuntu: Confirmed Status in ubuntu-fan source package in Xenial: Fix Committed Bug description: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+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] target fix for artful
Default Comment by Bridge ** Attachment added: "target fix for artful" https://bugs.launchpad.net/bugs/1658733/+attachment/5022248/+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: Fix Released 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 Status in kexec-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Released 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
[Kernel-packages] [Bug 1693566] Re: Ubuntu 16.04.03: "NMI watchdog: BUG: soft lockup" occurs while running stress-ng on PowerNV machine.
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => 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/1693566 Title: Ubuntu 16.04.03: "NMI watchdog: BUG: soft lockup" occurs while running stress-ng on PowerNV machine. Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Incomplete Bug description: == Comment: #0 - PAVITHRA R. PRAKASH- 2017-05-17 05:55:38 == --- Problem description Ubuntu 16.04.03: "NMI watchdog: BUG: soft lockup" occurs while running stress-ng on NV machine. --- Steps to recreate-- 1. Install ubuntu16.04.03. 2. Run "stress-ng -a 0". Logs: [ 2660.437087] INFO: rcu_sched self-detected stall on CPU [ 2660.437111]22-...: (5247 ticks this GP) idle=e19/141/0 softirq=905/905 fqs=2380 [ 2660.437114] (t=5251 jiffies g=95606 c=95605 q=2545946) [ 2660.437750]24-...: (5250 ticks this GP) idle=0b7/141/0 softirq=5805/5805 fqs=2380 [ 2660.437859] [ 2664.172796] NMI watchdog: BUG: soft lockup - CPU#22 stuck for 23s! [stress-ng-mmap:3509] [ 2664.172808] NMI watchdog: BUG: soft lockup - CPU#24 stuck for 23s! [stress-ng-mrema:3536] [ 2674.848037] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 33s! [stress-ng-fork:3381] [ 2676.172894] NMI watchdog: BUG: soft lockup - CPU#30 stuck for 22s! [kswapd0:992] [ 2680.336844] NMI watchdog: BUG: soft lockup - CPU#98 stuck for 23s! [stress-ng-clock:5099] [ 2686.140931] NMI watchdog: BUG: soft lockup - CPU#16 stuck for 39s! [stress-ng-clone:3366] [ 2686.987192] xhci_hcd 0003:09:00.0: HC died; cleaning up [ 2686.987212] usb 1-3-port3: cannot reset (err = -108) After few hours machine will become completely unresponsive [pavithra@localhost ~]$ ping 9.47.69.255 PING 9.47.69.255 (9.47.69.255) 56(84) bytes of data. ^C --- 9.47.69.255 ping statistics --- 12 packets transmitted, 0 received, 100% packet loss, time 11000ms Thanks, Pavithra == Comment: #6 - VIPIN K. PARASHAR - 2017-05-25 03:32:26 == ubuntu@ltc-firep2:~$ hostname -i 9.47.69.255 ubuntu@ltc-firep2:~$ uname -a Linux ltc-firep2 4.10.0-21-generic #23~16.04.1-Ubuntu SMP Tue May 2 12:54:57 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux ubuntu@ltc-firep2:~$ cat /etc/os-release NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial ubuntu@ltc-firep2:~$ tail /proc/cpuinfo processor : 159 cpu : POWER8 (raw), altivec supported clock : 2061.00MHz revision : 2.0 (pvr 004d 0200) timebase : 51200 platform : PowerNV model : 8335-GTA machine : PowerNV 8335-GTA firmware : OPAL ubuntu@ltc-firep2:~$ == Comment: #11 - VIPIN K. PARASHAR - 2017-05-25 06:27:12 == System Memory stats == ubuntu@ltc-firep2:~$ numactl -H available: 2 nodes (0,8) node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 node 0 size: 61321 MB node 0 free: 60297 MB node 8 cpus: 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 node 8 size: 65303 MB node 8 free: 64923 MB node distances: node 0 8 0: 10 40 8: 40 10 ubuntu@ltc-firep2:~$ free -h totalusedfree shared buff/cache available Mem: 123G534M122G 20M868M 121G Swap: 37G 0B 37G ubuntu@ltc-firep2:~$ sudo sysctl vm | grep free vm.min_free_kbytes = 360448 ubuntu@ltc-firep2:~$ Host is having 123 GB of memory spread across two nodes. Swap is configured to be 37GB and VM min free bytes is set to 360MB. == Comment: #13 - VIPIN K. PARASHAR - 2017-05-25 07:25:35 == [ 280.494345] NMI watchdog: BUG: soft lockup - CPU#5 stuck for 23s! [stress-ng-mmap:4172] [ 280.495250] CPU: 5 PID: 4172 Comm: stress-ng-mmap Not tainted 4.10.0-21-generic #23~16.04.1-Ubuntu [ 280.495262] task: c00fe318c600 task.stack:
[Kernel-packages] [Bug 1729442] Re: Prevent timer value 0 for MWAITX
** Changed in: linux (Ubuntu) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Zesty) Status: In Progress => 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/1729442 Title: Prevent timer value 0 for MWAITX Status in amd: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Zesty: Incomplete Bug description: Newer hardware has uncovered a bug in the software implementation of using MWAITX for the delay function. A value of 0 for the timer is meant to indicate that a timeout will not be used to exit MWAITX. On newer hardware this can result in MWAITX never returning, resulting in NMI soft lockup messages being printed. On older hardware, some of the other conditions under which MWAITX can exit masked this issue. The AMD APM does not currently document this and will be updated. Please refer to http://marc.info/?l=kvm=148950623231140 for information regarding NMI soft lockup messages on an AMD Ryzen 1800X. This has been root-caused as a 0 passed to MWAITX causing it to wait indefinitely. This change has the added benefit of avoiding the unnecessary setup of MONITORX/MWAITX when the delay value is zero. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1729442/+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
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => 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/1730607 Title: mount cifs with SMB 3.0 stop working Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete 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 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 21 11:15 seq crw-rw 1 root audio 116, 33 Nov 21 11:15 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.27 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 (639 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-101-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-101.124~14.04.1-generic 4.4.95
[Kernel-packages] [Bug 1731031] Re: Kernel Oops with 17.10
Can you see if the bug happens with 4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1731031 Title: Kernel Oops with 17.10 Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: have captured dmesg just before oops ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Nov 8 20:41:14 2017 DistUpgraded: 2017-11-07 01:49:14,657 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: kubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011a] LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1762): WARNING **: Failed to load user image: Failed to open file '/home/hmeyer/.face': No such file or directory MachineType: Apple Inc. MacBookPro11,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=fbc61d79-8b51-4801-8e2b-175ff6daa14f ro quiet splash apparmor=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-11-07 (1 days ago) dmi.bios.date: 02/22/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B17.1602221718 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B17.1602221718:bd02/22/2016:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Nov 8 20:39:06 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731031/+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 1721856] Re: Suspend ends after seconds and laptop resumes
** Changed in: linux (Ubuntu Zesty) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Incomplete Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+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 1711407] Re: unregister_netdevice: waiting for lo to become free
> So if there is something to test or debug, I would be happy to help fixing this issue. yes, I'm hoping to have a kernel build with some added debug to track/list exactly what socket(s) are still holding lo device references when the container is killed/shutdown, so testing with that would help clarify the specifics of this problem, once I have the debug kernel ready and built. I will update this bug once I have something ready to test. > Also already tried the latest kernel from http://kernel.ubuntu.com /~kernel-ppa/mainline/: and I assume that did not help, correct? This problem still exists upstream (assuming we're all encountering the same problem that I'm debugging) and will require an upstream 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/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: 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: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+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 1725350] Re: KVM on 17.10 crashes the machine
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Artful) Status: Fix Committed => 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/1725350 Title: KVM on 17.10 crashes the machine Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Artful: Fix Released Bug description: When you start qemu on a 17.10 machine, the whole machine goes down and crashes: [ 90.689627] Unable to handle kernel paging request for data at address 0xf2d3bda0 [ 90.689705] Faulting instruction address: 0xc0361224 [ 90.689840] Oops: Kernel access of bad area, sig: 11 [#1] [ 90.689911] SMP NR_CPUS=2048 [ 90.689912] NUMA [ 90.690053] PowerNV [ 90.690092] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack_netlink nf_conntrack nfnetlink idt_89hpesx snd_hda_codec_hdmi xfs joydev input_leds mac_hid snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd soundcore ofpart opal_prd cmdlinepart powernv_flash mtd at24 ipmi_powernv ipmi_devintf ipmi_msghandler powernv_rng uio_pdrv_genirq vmx_crypto ibmpowernv uio ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables [ 90.690724] autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage ast crct10dif_vpmsum i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm tg3 ahci libahci [ 90.690937] CPU: 48 PID: 3986 Comm: qemu-system-ppc Not tainted 4.13.0-12-generic #13-Ubuntu [ 90.691001] task: c00b122d8700 task.stack: c00b431cc000 [ 90.691167] NIP: c0361224 LR: c0998960 CTR: c09a19b0 [ 90.691223] REGS: c00bff61b800 TRAP: 0300 Not tainted (4.13.0-12-generic) [ 90.691277] MSR: 90009033[ 90.691282] CR: 88002844 XER: [ 90.691347] CFAR: c099895c DAR: f2d3bda0 DSISR: 4000 SOFTE: 0 [ 90.691347] GPR00: c0998960 c00bff61ba80 c15e3000 c00b4ef61f20 [ 90.691347] GPR04: c00b44c61680 001f 001f [ 90.691347] GPR08: 001f 02d3bd80 c178e8e8 c00b5a0c26f0 [ 90.691347] GPR12: 28002842 cfadf800 c00b52d07880 c00b44c61680 [ 90.691347] GPR16: 001f 001f c553a560 [ 90.691347] GPR20: 0001 0002 08000553a560 c00b5c62a228 [ 90.691347] GPR24: c5531110 c00b5c632238 0210 [ 90.691347] GPR28: c0998960 c00bff61bc20 c00b4ef61f20 f2d3bd80 [ 90.692089] NIP [c0361224] kfree+0x54/0x270 [ 90.692133] LR [c0998960] xhci_urb_free_priv+0x20/0x40 [ 90.692325] Call Trace: [ 90.692345] [c00bff61ba80] [c00bff61bad0] 0xc00bff61bad0 (unreliable) [ 90.692402] [c00bff61bac0] [c0998960] xhci_urb_free_priv+0x20/0x40 [ 90.692459] [c00bff61bae0] [c099bfc8] xhci_giveback_urb_in_irq.isra.22+0x78/0x190 [ 90.692645] [c00bff61bb40] [c099c350] xhci_td_cleanup+0x130/0x200 [ 90.692702] [c00bff61bbc0] [c09a175c] handle_tx_event+0x74c/0x1380 [ 90.692759] [c00bff61bcc0] [c09a2894] xhci_irq+0x504/0xf20 [ 90.692808] [c00bff61bde0] [c017b110] __handle_irq_event_percpu+0x90/0x300 [ 90.692977] [c00bff61bea0] [c017b3b8] handle_irq_event_percpu+0x38/0x90 [ 90.693038] [c00bff61bee0] [c017b474] handle_irq_event+0x64/0xb0 [ 90.693094] [c00bff61bf10] [c0180da0] handle_fasteoi_irq+0xc0/0x230 [ 90.693155] [c00bff61bf40] [c017972c] generic_handle_irq+0x4c/0x70 [ 90.693332] [c00bff61bf60] [c001767c] __do_irq+0x7c/0x1c0 [ 90.693383] [c00bff61bf90] [c002ab70] call_do_irq+0x14/0x24 [ 90.693431] [c00b431cf9d0] [c001785c] do_IRQ+0x9c/0x130 [ 90.693478] [c00b431cfa20] [c0008ac4] hardware_interrupt_common+0x114/0x120 [ 90.693663] --- interrupt: 501 at __copy_tofrom_user_power7+0x1f4/0x7cc [ 90.693663] LR = _copy_to_user+0x3c/0x60 [ 90.693736] [c00b431cfd10]
[Kernel-packages] [Bug 1730958] Re: nuvoton-cir not working after boot
** 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/1730958 Title: nuvoton-cir not working after boot Status in linux package in Ubuntu: Incomplete Bug description: Current setup/failing setup: Linux frontend01 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 4.13.0-17.20-generic 4.13.8 Ubuntu 17.10, 4.13.0-17-generic Nuvoton w836x7hg Infrared Remote Transceiver Zotac ID42 Working setup: Ubuntu 17.10, 4.4.8-040408-generic I'm not able to get the remote working after a normal reboot (using 4.13 kernel) It does actually after a suspend and wake-up, and do a echo 'auto' to resources. Please find snapshot of dmesg below: [ 14.067757] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 14.468143] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 14.468227] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input7 [ 14.468484] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 14.468526] nuvoton-cir 00:0a: driver has been successfully loaded modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 66.231365] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 66.231610] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 66.231758] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input13 [ 66.232140] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 66.232240] nuvoton-cir 00:0a: driver has been successfully loaded suspend/resume [ 105.890769] nuvoton-cir 00:0a: disabled [ 106.651982] nuvoton-cir 00:0a: activated modprobe -r nuvoton-cir echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources modprobe nuvoton-cir [ 138.549572] nuvoton-cir 00:0a: found NCT6776F or compatible: chip id: 0xc3 0x33 [ 138.549839] rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0 [ 138.551225] input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:0a/rc/rc0/input17 [ 138.552171] rc rc0: lirc_dev: driver ir-lirc-codec (nuvoton-cir) registered at minor = 0 [ 138.552256] nuvoton-cir 00:0a: driver has been successfully loaded In order to get the device working I need the following in this order: * suspend/resume * echo "auto" > /sys/bus/acpi/devices/NTN0530\:00/physical_node/resources --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=d95eb1c2-ba63-486d-9da0-8b4c785342d6 InstallationDate: Installed on 2014-04-01 (1317 days ago) InstallationMedia: Mythbuntu 12.04.3 "Precise Pangolin" - Release amd64 (20130820) MachineType: ZOTAC ZBOX-ID42-BE NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=e870e449-a4ea-4551-b4a6-32e3966a1789 ro splash quiet vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-17-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-11-05 (2 days ago) UserGroups: adm audio cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B201P010 dmi.board.asset.tag: NA dmi.board.name: ZBOX-ID42-BE dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: NA dmi.chassis.type: 3 dmi.chassis.vendor: NA dmi.chassis.version: NA dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB201P010:bd05/03/2013:svnZOTAC:pnZBOX-ID42-BE:pvrXX:rvnZOTAC:rnZBOX-ID42-BE:rvrXX:cvnNA:ct3:cvrNA: dmi.product.family: NA dmi.product.name: ZBOX-ID42-BE dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730958/+subscriptions
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
Would you be able to test some test kernels? If so, we can try to bisect down to which commit introduced the regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in openvswitch package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in openvswitch source package in Bionic: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
thinking this is the same bug/duplicate I'm hitting here https://bugs.launchpad.net/juju/+bug/1736022 I'm deploying a few nodes to test the fix in proposed now -- 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/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures Status in juju: Triaged Status in ubuntu-fan package in Ubuntu: Confirmed Status in ubuntu-fan source package in Xenial: Fix Committed Bug description: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+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] Re: crashkernel offset prevents kernel boot
This bug was fixed in the package makedumpfile - 1:1.6.2-1ubuntu1 --- makedumpfile (1:1.6.2-1ubuntu1) bionic; urgency=medium * KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's only used by ppc64el, it's not required to be conditionally added. (LP: #1658733) * Set crashkernel for ppc64el to load at 128M instead of 32M. That allows larger kernels to boot. (LP: #1728115) -- Thadeu Lima de Souza CascardoTue, 07 Nov 2017 12:23:33 + ** Changed in: makedumpfile (Ubuntu Bionic) 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/1728115 Title: crashkernel offset prevents kernel boot Status in linux package in Ubuntu: Incomplete Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Artful: New Status in makedumpfile source package in Artful: In Progress Status in linux source package in Bionic: Incomplete Status in makedumpfile source package in Bionic: Fix Released 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 1715609] Re: kernel warning: skb_warn_bad_offload
Just a note that I'm seeing far less skb_warn_bad_offload warnings in Xenial with the last 3 or 4 official 4.10 kernels (4.10.0-42, 4.10.0-40, 4.10.0-38, etc). Sometimes I don't see any warnings for a week or so, sometimes a few pop out. So it looks much better now, I'm just not sure it is fixed completely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715609 Title: kernel warning: skb_warn_bad_offload Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Bug description: Since upgrading to kernel version 4.10.0-33.37, we're seeing a lot of call traces triggered by skb_warn_bad_offload in the syslog. Regression introduced when fixing this bug? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705447 kernel: [570943.49] [ cut here ] kernel: [570943.494448] WARNING: CPU: 3 PID: 21982 at /build/linux-hwe-YA6IuF/linux-hwe-4.10.0/net/core/dev.c:2576 skb_warn_bad_offload+0xd1/0x120 kernel: [570943.494450] e1000e: caps=(0x0030002149a9, 0x) len=1701 data_len=1659 gso_size=1480 gso_type=2 ip_summed=0 kernel: [570943.494451] Modules linked in: udp_diag tcp_diag inet_diag echainiv authenc xfrm4_mode_tunnel xt_state binfmt_misc veth xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo bridge stp llc iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf hci_uart ie31200_edac btbcm edac_core intel_pch_thermal btqca serio_raw btintel bluetooth parport_pc parport mac_hid intel_lpss_acpi acpi_pad intel_lpss autofs4 kernel: [570943.494500] btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e psmouse ptp ahci pps_core libahci wmi pinctrl_sunrisepoint i2c_hid video pinctrl_intel hid fjes kernel: [570943.494524] CPU: 3 PID: 21982 Comm: charon Tainted: GW 4.10.0-33-generic #37~16.04.1-Ubuntu kernel: [570943.494524] Hardware name: ... kernel: [570943.494525] Call Trace: kernel: [570943.494541] kernel: [570943.494544] dump_stack+0x63/0x90 kernel: [570943.494545] __warn+0xcb/0xf0 kernel: [570943.494546] warn_slowpath_fmt+0x5f/0x80 kernel: [570943.494547] ? ___ratelimit+0xa2/0xf0 kernel: [570943.494549] skb_warn_bad_offload+0xd1/0x120 kernel: [570943.494550] __skb_gso_segment+0x17d/0x190 kernel: [570943.494564] validate_xmit_skb+0x14f/0x2a0 kernel: [570943.494565] validate_xmit_skb_list+0x43/0x70 kernel: [570943.494567] sch_direct_xmit+0x16b/0x1c0 kernel: [570943.494568] __dev_queue_xmit+0x47e/0x690 kernel: [570943.494569] dev_queue_xmit+0x10/0x20 kernel: [570943.494570] ip_finish_output2+0x27a/0x370 kernel: [570943.494571] ip_finish_output+0x176/0x270 kernel: [570943.494571] ip_output+0x76/0xe0 kernel: [570943.494572] ? ip_fragment.constprop.49+0x80/0x80 kernel: [570943.494573] ip_forward_finish+0x43/0x70 kernel: [570943.494574] ip_forward+0x385/0x460 kernel: [570943.494575] ? ip_frag_mem+0x50/0x50 kernel: [570943.494575] ip_rcv_finish+0x11b/0x400 kernel: [570943.494576] ip_rcv+0x28b/0x3a0 ... kernel: [570943.494632] ---[ end trace f01d0adcc1256afe ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715609/+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
This bug was fixed in the package makedumpfile - 1:1.6.2-1ubuntu1 --- makedumpfile (1:1.6.2-1ubuntu1) bionic; urgency=medium * KDUMP_CMDLINE_APPEND: add noirqdistrib to default command line. As it's only used by ppc64el, it's not required to be conditionally added. (LP: #1658733) * Set crashkernel for ppc64el to load at 128M instead of 32M. That allows larger kernels to boot. (LP: #1728115) -- Thadeu Lima de Souza CascardoTue, 07 Nov 2017 12:23:33 + ** Changed in: makedumpfile (Ubuntu Bionic) Status: In Progress => Fix Released -- 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: Fix Released 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 Status in kexec-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Released 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
Re: [Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Hello Anthony, My situation is: Lenovo Ideapad Flex 10. Came with windows 8 installed and updated to windows 10. I then installed Ubuntu 14.04 as dual boot and had each release of Ubuntu updated since 14.04. I was dual booting using legacy for Ubuntu and UEFI for occasional access to windows 10. Only recent change has been upgrade to version 17.10. I can no longer save changes to the boot order in the BIOS. I cannot therefore boot from USB and am not able to boot into windows. I can boot into 17.10. The trigger for this problem arising was clearly the upgrade from 17.04 to 17.10. I also have a Lenovo G710 with Xubuntu installed and no other OS. It is booting using "Legacy". I have also upgraded this from 17.04 to 17.10 and do not have a problem with the BIOS on this laptop. I live in Cologne, Germany but work away in Mainz-Kastel, Germany during the week. My telephone number is 00491713568623. Kev Hennessey From: boun...@canonical.comon behalf of Anthony Wong Sent: 13 December 2017 08:10 To: kevhennes...@hotmail.com Subject: [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Dear users, We are treating this issue very seriously and sorry that this has happened. We have been working with Lenovo in China at full speed since last week to find out the root cause. Meanwhile, if you hit this issue, please send me an email at anthony.w...@canonical.com with your laptop's model name and the city where you live, optionally you can leave your phone number so that Lenovo can call you back if they need more information. It will also be very helpful if you can also provide a brief description of what you did (e.g. upgrade from 17.04 to 17.10, or fresh install 17.10, etc). Regards, Anthony -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo Y50-70 Lenovo G40-30 Lenovo U31-70 Lenovo G50-70 Lenovo Z50-70 Lenovo Yoga Thinkpad (20C0) Lenovo G50-80 Lenovo S20-30 Lenovo Yoga 2 11" - 20332 Lenovo B40-70 Lenovo Z51-70 Lenovo B50-70 Lenovo Flex-10 --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tob1608 F pulseaudio /dev/snd/controlC0: tob1608 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-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/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70
[Kernel-packages] [Bug 1737515] Re: linux-aws: 4.4.0-1044.53 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1737515 Title: linux-aws: 4.4.0-1044.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1737511 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737515/+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 1737512] Re: linux-aws: 4.4.0-1006.6 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1737512 Title: linux-aws: 4.4.0-1006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1737511 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737512/+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 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
Looking at the test history - artful passed tests with 4.11 and 4.12 kernels with 2.8.0, but appears to have started failing sporadically when 4.13 entered the archive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in openvswitch package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in openvswitch source package in Bionic: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1737511] Re: linux: 4.4.0-104.127 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing 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/1737511 Title: linux: 4.4.0-104.127 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737512,1737514 derivatives: 1737515,1737516,1737517,1737518,1737519,1737520 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737511/+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 1737515] Re: linux-aws: 4.4.0-1044.53 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1737515 Title: linux-aws: 4.4.0-1044.53 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1737511 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737515/+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 1737511] Re: linux: 4.4.0-104.127 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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/1737511 Title: linux: 4.4.0-104.127 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737512,1737514 derivatives: 1737515,1737516,1737517,1737518,1737519,1737520 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737511/+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 1737916] Re: linux: 4.4.0-105.128 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.4.0-105.128 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737916 Title: linux: 4.4.0-105.128 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737918,1737919 derivatives: 1737920,1737921,1737922,1737923,1737925,1737927 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737916/+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 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
I just tested this also and can verify it fixed it in the environment/test where it was originally reported as broken. -- 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/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures Status in juju: Triaged Status in ubuntu-fan package in Ubuntu: Confirmed Status in ubuntu-fan source package in Xenial: Fix Committed Bug description: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+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 1737903] Re: linux: 4.13.0-20.23 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.13.0-20.23 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737903 Title: linux: 4.13.0-20.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737905,1737906,1737907,1737908 derivatives: 1737909 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737903/+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 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
Changing tag to verified as per comments #13 & #14. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures Status in juju: Triaged Status in ubuntu-fan package in Ubuntu: Confirmed Status in ubuntu-fan source package in Xenial: Fix Committed Bug description: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+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 1736617] Re: Port nvidia-settings to gtk3
It already uses gtk3. It builds in this complicated way where it can use either gtk3 or gtk2 at runtime, but presumably you can just stop building the gtk2 support in. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1736617 Title: Port nvidia-settings to gtk3 Status in nvidia-settings package in Ubuntu: New Bug description: gtk3 was declared stable in September 2016 with the gtk 3.22 release. nvidia-settings should switch to gtk3. nvidia-settings is one of the last dozen packages to keep gtk2 in main. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=gtk2-demotion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1736617/+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 1737913] Re: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1737913 Title: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1737911 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737913/+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 1737033] Re: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection
Thanks @davecore and @benjamin-long for verifying the fix! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737033 Title: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection Status in ceph package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in ceph source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: After clients have upgraded to 4.4.0-103.126 they can no longer connect to the Ceph network. Using the Grub menu to boot the previous kernel fixes the issue. The error in dmesg is: [ 46.811897] FS-Cache: Loaded [ 46.843670] Key type ceph registered [ 46.844177] libceph: loaded (mon/osd proto 15/24) [ 46.863107] FS-Cache: Netfs 'ceph' registered for caching [ 46.863116] ceph: loaded (mds proto 32) [ 46.884392] libceph: client3354099 fsid 2efbeab1-4903-4c4c-8365-6778afecbcbd [ 46.886856] libceph: mon0 10.10.2.111:6789 session established [ 46.897487] ceph: problem parsing mds trace -5 [ 46.897491] ceph: mds parse_reply err -5 [ 46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1) All clients are running ceph client version: ii ceph-fs-common10.2.9-0ubuntu0.16.04.1 Server nodes are running 10.2.6 packages as supplied by Ceph. All 10.2.* versions are compatible. Using the previous kernel allows the connection to work. --- ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1310 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-103-generic N/A linux-backports-modules-4.4.0-103-generic N/A linux-firmware 1.157.14 RfKill: Tags: xenial xenial Uname: Linux 4.4.0-103-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1737033/+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 1737033] Re: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection
I also confirm the kernel 4.4.0-104.127 in xenial-proposed fixes the issue. I am able to mount my CephFS filesystem normally. Benjamin also confirmed the kernel works for him in comments #26 and #27. I am changing the tag to verification-done-xenial. Thanks! ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1737033 Title: upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection Status in ceph package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in ceph source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: After clients have upgraded to 4.4.0-103.126 they can no longer connect to the Ceph network. Using the Grub menu to boot the previous kernel fixes the issue. The error in dmesg is: [ 46.811897] FS-Cache: Loaded [ 46.843670] Key type ceph registered [ 46.844177] libceph: loaded (mon/osd proto 15/24) [ 46.863107] FS-Cache: Netfs 'ceph' registered for caching [ 46.863116] ceph: loaded (mds proto 32) [ 46.884392] libceph: client3354099 fsid 2efbeab1-4903-4c4c-8365-6778afecbcbd [ 46.886856] libceph: mon0 10.10.2.111:6789 session established [ 46.897487] ceph: problem parsing mds trace -5 [ 46.897491] ceph: mds parse_reply err -5 [ 46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1) All clients are running ceph client version: ii ceph-fs-common10.2.9-0ubuntu0.16.04.1 Server nodes are running 10.2.6 packages as supplied by Ceph. All 10.2.* versions are compatible. Using the previous kernel allows the connection to work. --- ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1310 F pulseaudio DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=9e3c38ba-10bd-4183-b073-68d9d9a30a9b IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic root=UUID=5a37e891-beb9-477f-b934-3c05651acf68 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-103-generic N/A linux-backports-modules-4.4.0-103-generic N/A linux-firmware 1.157.14 RfKill: Tags: xenial xenial Uname: Linux 4.4.0-103-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1737033/+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 1737913] Re: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1737911 + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 13. December 2017 15:33 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1737911 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Wednesday, 13. December 2017 15:33 UTC + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1737913 Title: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1737911 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737913/+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 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
I don't have a data point for 4.11, but at 4.10 (as shipped in zesty) ovs 2.8.1 tests are OK. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in openvswitch package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in openvswitch source package in Bionic: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1737911] Re: linux: 3.13.0-138.187 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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/1737911 Title: linux: 3.13.0-138.187 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737913 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 14:33 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737911/+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 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
Can you see if using earlier kernel versions makes the bug go away? http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/ http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in openvswitch package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in openvswitch source package in Bionic: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1736593] Re: ThunderX: IPv6 TX failure unless checksum offload disabled
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736593 Title: ThunderX: IPv6 TX failure unless checksum offload disabled Status in linux package in Ubuntu: Fix Committed Status in linux source package in Artful: In Progress Bug description: [Impact] Most attempts to use IPv6 on the ThunderX NIC will fail. [Test Case] Attempt an IPv6 TCP connection: $ wget -6 'http://www.kernel.org/' The connection will time out. [Regression Risk] The fix is upstream, and is limited to the ThunderX nicvf driver. [Workaround] Disable TX checksum offload: $ ethtool -K eth0 tx off [More Details] The issue first appears in Linux 4.12. A fix from Cavium has been merged upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/cavium/thunder/nicvf_queues.c?id=fa6d7cb5d76cf0467c61420fc9238045aedfd379 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731041] Re: kernel
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 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.15-rc3 ** 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/1731041 Title: kernel Status in linux package in Ubuntu: Incomplete Bug description: a tela do notbook fica piscando quando uso um kernel que nao seja o 4.7 no momento estou usando o ubuntu 16.04.03 com o kernel 4.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 8 18:12:15 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2017-11-06 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 006: ID 0cf3:0036 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6a04 Microdia Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3442 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed root=UUID=5161f7a5-7954-4ae1-b1f8-7a786aea4d23 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0WVGRF dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/14/2014:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0WVGRF:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3442 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731041/+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 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736774 Title: arm64/thunderx: Unhandled context faults in ACPI mode Status in linux package in Ubuntu: Fix Committed Status in linux source package in Zesty: New Status in linux source package in Artful: In Progress Bug description: [Impact] Booting a Cavium ThunderX node in ACPI mode results in constant messages like this to the console: arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, iova=0x0fffc000, fsynr=0x10081, cb=1 In some configurations, this causes the SATA controller to fail to initialize, making the system unbootable. (Note to self: this occurs on our internal system known as "alekhin"). [Test Case] Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the console. [Regression Risk] The fixes are restricted to quirks for Cavium ThunderX hardware, which is hardware we've tested directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+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 1737934] Re: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.15 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.15-rc3 ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => High ** 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/1737934 Title: Samsung SM961 NVMe SSD randomly unmounts/loses connection/unavailable Status in linux package in Ubuntu: Incomplete Bug description: Seems related to these bugs: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1682704 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748 Problem: At seemingly random times my computer (brand new Lenovo Thinkpad T470) seems to lose access to the Samsung SM961 256GB SSD drive it has inside. When this happens the whole OS freezes up and when I try to power down I see a black terminal-like screen that prints the following errors: EXT4-fs error (device nvme0n1p2): ext4_find_entry:1431: inode #7471275 (or #741278): comm gmain (or systemd-journal or ...): reading directory iblock 0 This error seems to be repeated endlessly, though I've only let it go for a few minutes. No other errors are printed. This is the only drive it has. I don't know if this occurs in Windows too since I removed Windows and installed Ubuntu immediatly after updating the BIOS. Info: Distro: Ubuntu MATE 17.10 sudo uname -r 4.13.0-19-generic sudo nvme get-feature -f 0x0c -H /dev/nvme0 (with latency set to 250) get-feature:0xc (Autonomous Power State Transition), Current value:0x01 Autonomous Power State Transition Enable (APSTE): Enabled Auto PST Entries. Entry[ 0] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 1] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 2] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 3] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 4] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 5] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 6] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 7] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 8] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[ 9] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[10] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[11] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[12] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[13] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[14] . Idle Time Prior to Transition (ITPT): 0 ms Idle Transition Power State (ITPS): 0 . Entry[15] . Idle Time Prior to Transition (ITPT): 0 ms
[Kernel-packages] [Bug 1737992] [NEW] Bionic update to v4.14.5 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The v4.14.5 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the v4.14.5 stable release shall be applied: drm/fsl-dcu: avoid disabling pixel clock twice on suspend drm/fsl-dcu: enable IRQ before drm_atomic_helper_resume() drm/amdgpu: Use unsigned ring indices in amdgpu_queue_mgr_map s390/runtime instrumentation: simplify task exit handling usbip: fix usbip attach to find a port that matches the requested speed usbip: Fix USB device hang due to wrong enabling of scatter-gather uas: Always apply US_FL_NO_ATA_1X quirk to Seagate devices usb: quirks: Add no-lpm quirk for KY-688 USB 3.1 Type-C Hub serial: 8250_pci: Add Amazon PCI serial device ID ANDROID: binder: fix transaction leak. USB: serial: option: add Quectel BG96 id USB: serial: usb_debug: add new USB device id serial: 8250_early: Only set divisor if valid clk & baud MIPS: Add custom serial.h with BASE_BAUD override for generic kernel ima: fix hash algorithm initialization s390: vfio-ccw: Do not attempt to free no-op, test and tic cda. PM / Domains: Fix genpd to deal with drivers returning 1 from ->prepare() s390/pci: do not require AIS facility selftests/x86/ldt_get: Add a few additional tests for limits selftests/x86/ldt_gdt: Robustify against set_thread_area() and LAR oddities staging: greybus: loopback: Fix iteration count on async path m68k: fix ColdFire node shift size calculation serial: 8250_fintek: Fix rs485 disablement on invalid ioctl() staging: rtl8822be: fix wrong dma unmap len staging: rtl8188eu: avoid a null dereference on pmlmepriv spi: sh-msiof: Fix DMA transfer size check spi: spi-axi: fix potential use-after-free after deregistration mmc: tmio: check mmc_regulator_get_supply return value mmc: sdhci-msm: fix issue with power irq hwmon: (pmbus/core) Prevent unintentional setting of page to 0xFF perf/core: Fix __perf_read_group_add() locking usb: phy: tahvo: fix error handling in tahvo_usb_probe() PCI: dra7xx: Create functional dependency between PCIe and PHY x86/intel_rdt: Initialize bitmask of shareable resource if CDP enabled x86/intel_rdt: Fix potential deadlock during resctrl mount serial: 8250: Preserve DLD[7:4] for PORT_XR17V35X kprobes: Use synchronize_rcu_tasks() for optprobe with CONFIG_PREEMPT=y x86/entry: Use SYSCALL_DEFINE() macros for sys_modify_ldt() clocksource/drivers/arm_arch_timer: Validate CNTFRQ after enabling frame dt-bindings: timer: renesas, cmt: Fix SoC-specific compatible values EDAC, sb_edac: Fix missing break in switch usb: mtu3: fix error return code in ssusb_gadget_init() staging: fsl-dpaa2/eth: Account for Rx FD buffers on error path staging: rtl8822be: Keep array subscript no lower than zero ARM: cpuidle: Correct driver unregistration if init fails usb: xhci: Return error when host is dead in xhci_disable_slot() sysrq : fix Show Regs call trace on ARM serial: sh-sci: suppress warning for ports without dma channels usbip: tools: Install all headers needed for libusbip development serial: imx: Update cached mctrl value when changing RTS staging: fsl-mc/dpio: Fix incorrect comparison perf test attr: Fix ignored test case result perf test attr: Fix python error on empty result kprobes/x86: Disable preemption in ftrace-based jprobes locking/refcounts, x86/asm: Use unique .text section for refcount exceptions s390/ptrace: fix guarded storage regset handling tools include: Do not use poison with C++ perf tools: Fix leaking rec_argv in error cases mm, x86/mm: Fix performance regression in get_user_pages_fast() iio: adc: ti-ads1015: add 10% to conversion wait time iio: multiplexer: add NULL check on devm_kzalloc() and devm_kmemdup() return values locking/refcounts, x86/asm: Enable CONFIG_ARCH_HAS_REFCOUNT powerpc/jprobes: Disable preemption when triggered through ftrace powerpc/kprobes: Disable preemption before invoking probe handler for optprobes dma-buf/sw_sync: force signal all unsignaled fences on dying timeline staging: ccree: fix leak of import() after init() usb: hub: Cycle HUB power when initialization fails USB: ulpi: fix bus-node lookup xhci: Don't show incorrect WARN message about events for empty rings usb: xhci: fix panic in xhci_free_virt_devices_depth_first USB: core: Add type-specific length check of BOS descriptors USB: usbfs: Filter flags passed in from user space usb: host: fix incorrect updating of offset locking/refcounts: Do not force refcount_t usage as GPL-only export Linux 4.14.5 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee
[Kernel-packages] [Bug 1668356] Re: Hard lockup after 4 hours uptime
Hi, We can confirm that this issue still persists as of 4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux this update. It only happens on a soft reboot, i.e. 'sudo reboot'. Not sure if there is a work around for it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1668356 Title: Hard lockup after 4 hours uptime Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: We have recently deployed intel NUC6i5 devices in store for POS display and are encountering strange inexplicable freezes on several devices. What is very strange is that all devices are freezing exactly 4h after boot. We have had this exact same issue on more than 20 devices (over 100), with parts from different batches, and all did freeze exactly 4h after boot (but it's not reproducible, it won't freeze every day). Some devices are playing MPV videos, while other run chromium. They are running non-stop, but are all rebooting daily at 05h05. Looks like it might be related to https://lkml.org/lkml/2015/6/11/787 That seem to have been fixed and backported already https://lkml.org/lkml/2015/10/17/259 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Mon Feb 27 21:06:44 2017 InstallationDate: Installed on 2016-06-08 (264 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed root=UUID=1f60f9c9-bbf1-45df-bdc3-9b4da883839e ro quiet splash net.ifnames=0 vt.handoff=7 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.board.name: NUC6i5SYB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668356/+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 1737913] Re: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker
** Summary changed: - linux-lts-trusty: -proposed tracker + linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1737913 Title: linux-lts-trusty: 3.13.0-138.187~precise1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1737911 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737913/+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 1737911] Re: linux: 3.13.0-138.187 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737913 derivatives: + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 13. December 2017 14:33 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737913 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 14:33 UTC + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737911 Title: linux: 3.13.0-138.187 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1737913 derivatives: kernel-stable-phase:Uploaded kernel-stable-phase-changed:Wednesday, 13. December 2017 14:33 UTC -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737911/+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 1545542] Re: Enable arm64 emulation of removed ARMv7 instructions
Fix committed to bionic. ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1545542 Title: Enable arm64 emulation of removed ARMv7 instructions Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: New Status in linux source package in Artful: New Status in linux source package in Bionic: Fix Committed Bug description: Linux now supports emulation of three deprecated ARMv7 features that were removed from ARMv8: SWP(B), CP15ISB/DSB/DMB, and SETEND. At least CP15DMB is used by some armhf archive binaries (notably pandoc), so we need emulation enabled on the kernels that scalingstack uses. I haven't checked which version added which, but they appeared some time between 3.13 and 4.2, and I only care about 4.2 onwards. So please enable ARMV8_DEPRECATED, SWP_EMULATION, CP15_BARRIER_EMULATION and SETEND_EMULATION in arm64 kernels for wily onwards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1545542/+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 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
root 16037 1 0 12:39 ?00:00:00 ovsdb-server: monitoring pid 16038 (healthy) root 16038 16037 0 12:39 ?00:00:00 ovsdb-server /etc/openvswitch/conf.db -vconsole:emer -vsyslog:err -vfile:info --remote=punix:/var/run/openvswitch/db.sock --private-key=db:Open_vSwitch root 16051 1 0 12:39 ?00:00:00 ovs-vswitchd: monitoring pid 16052 (healthy) root 16052 16051 0 12:39 ?00:00:00 [ovs-vswitchd] and root 17517 16216 0 12:40 pts/000:00:00 ovs-vsctl --if-exists del-br s1 -- --if-exists del-br s2 ** Also affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in openvswitch package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in openvswitch source package in Bionic: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
More log output from ovs: 2017-12-13T12:40:23.502Z|5|dpif(revalidator20)|WARN|system@ovs-system: failed to put[modify] (Invalid argument) ufid:684991e8-860e-44eb-ab44-bd8bd41520e1 recirc_id(0),dp_hash(0/0),skb_priority(0/0),in_port(3),skb_mark(0/0),ct_state(0/0),ct_zone(0/0),ct_mark(0/0),ct_label(0/0),eth(src=76:bd:b5:1d:36:0f,dst=33:33:00:00:00:02),eth_type(0x86dd),ipv6(src=fe80::74bd:b5ff:fe1d:360f/::,dst=ff02::2/::,label=0/0,proto=58/0,tclass=0/0,hlimit=255/0,frag=no),icmpv6(type=133/0,code=0/0), actions:userspace(pid=0,slow_path(controller)) 2017-12-13T12:40:23.502Z|6|dpif(revalidator20)|WARN|system@ovs-system: failed to put[modify] (Invalid argument) ufid:526e564d-5dba-42da-b433-dbb77cddef23 recirc_id(0),dp_hash(0/0),skb_priority(0/0),in_port(10),skb_mark(0/0),ct_state(0/0),ct_zone(0/0),ct_mark(0/0),ct_label(0/0),eth(src=42:f1:94:53:48:5b,dst=33:33:00:00:00:02),eth_type(0x86dd),ipv6(src=fe80::40f1:94ff:fe53:485b/::,dst=ff02::2/::,label=0/0,proto=58/0,tclass=0/0,hlimit=255/0,frag=no),icmpv6(type=133/0,code=0/0), actions:userspace(pid=0,slow_path(controller)) 2017-12-13T12:40:23.505Z|00162|bridge|INFO|bridge s1: deleted interface s1 on port 65534 2017-12-13T12:40:23.505Z|00163|bridge|INFO|bridge s1: deleted interface s1-eth8 on port 8 2017-12-13T12:40:23.526Z|00164|bridge|INFO|bridge s2: deleted interface s2-eth4 on port 4 2017-12-13T12:40:23.526Z|00165|bridge|INFO|bridge s2: deleted interface s2-eth8 on port 8 2017-12-13T12:40:23.526Z|00166|bridge|INFO|bridge s2: deleted interface s2 on port 65534 2017-12-13T12:40:23.526Z|00167|bridge|INFO|bridge s2: deleted interface s2-eth6 on port 6 2017-12-13T12:40:23.526Z|00168|bridge|INFO|bridge s2: deleted interface s2-eth7 on port 7 2017-12-13T12:40:23.526Z|00169|bridge|INFO|bridge s2: deleted interface s2-eth2 on port 2 2017-12-13T12:40:23.527Z|00170|bridge|INFO|bridge s2: deleted interface s2-eth5 on port 5 2017-12-13T12:40:23.527Z|00171|bridge|INFO|bridge s2: deleted interface s2-eth3 on port 3 2017-12-13T12:40:23.527Z|00172|bridge|INFO|bridge s2: deleted interface s2-eth1 on port 1 2017-12-13T12:40:24.543Z|1|ovs_rcu(urcu5)|WARN|blocked 1005 ms waiting for main to quiesce 2017-12-13T12:40:25.539Z|2|ovs_rcu(urcu5)|WARN|blocked 2001 ms waiting for main to quiesce 2017-12-13T12:40:27.545Z|3|ovs_rcu(urcu5)|WARN|blocked 4007 ms waiting for main to quiesce 2017-12-13T12:40:31.542Z|4|ovs_rcu(urcu5)|WARN|blocked 8004 ms waiting for main to quiesce 2017-12-13T12:40:39.546Z|5|ovs_rcu(urcu5)|WARN|blocked 16008 ms waiting for main to quiesce -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in openvswitch package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in openvswitch source package in Bionic: New Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768]
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386
And some more testing: xenial: ovs 2.8.1 + 4.4 - OK xenial: ovs 2.8.1 + 4.10 - OK so the issue appears to be the combination of ovs 2.8.1 (and 2.8.0) with the 4.13 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/1736390 Title: openvswitch: kernel opps destroying interfaces on i386 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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