[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
The dump looks like below bug. Was the bug already fixed in 4.13.0-25.29 ? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1731031 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734327 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742622] 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/1742622 Title: package linux-headers-4.13.0-25 (not installed) failed to install/upgrade: '/usr/src/linux-headers-4.13.0-25/include/net/xfrm.h .dpkg-new' をオープンできません: 許可されていない操作です Status in linux package in Ubuntu: Confirmed Bug description: virtualboxのubuntu ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-headers-4.13.0-25 (not installed) ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: main 3538 F pulseaudio Date: Thu Jan 11 15:45:57 2018 ErrorMessage: '/usr/src/linux-headers-4.13.0-25/include/net/xfrm.h.dpkg-new' をオープンできません: 許可されていない操作です IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 003: ID 056a:0010 Wacom Co., Ltd Graphire Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=56500155-90ed-475e-bdfc-d9583a9a20c5 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: SourcePackage: linux Title: package linux-headers-4.13.0-25 (not installed) failed to install/upgrade: '/usr/src/linux-headers-4.13.0-25/include/net/xfrm.h.dpkg-new' をオープンできません: 許可されていない操作です UpgradeStatus: No upgrade log present (probably fresh install) 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.family: Virtual Machine 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/linux/+bug/1742622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741934] Re: Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix)
On 14.04 with LTS Enablement Stack I can confirm that 4.4.0-108 was broken in the described way (trap on kfree) and 4.4.0-109 works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741934 Title: Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: ### HOW TO BOOT INTO PREVIOUS KERNEL IF UNABLE TO BOOT ### If you hit this bug and are unable to boot, you can boot back into the last working kernel. To do that, select that version(Probably 4.4.0-104) from the GRUB menu. The GRUB menu can be accessed by holding the 'Shift' key after powering on the system(Some systems require the 'ESC' key to be held instead of Shift). Detailed information about GRUB can be found here: https://help.ubuntu.com/community/Grub2 [Description] When using PPA https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/pti/ to fetch the candidate kernels for CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same kernel trace shown in many different pre-installed Ubuntu images of different platform. So far these platform are known to reproduce this issue: CID 201606-22340 (Dell Vostro 5468) CID 201606-22349 (Dell Inspiron 7560) CID 201606-22365 (Dell Inspiron 5767) [Steps to Reproduce] 1. Install the target pre-installed image (Xenial 4.4-based stack) for the platform. 2. Fetch the kernel 4.4.0-108.131 from this PPA https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/ 3. Update the system by "sudo apt-get dist-upgrade" 4. After the system update, reboot it. 5. Check the syslog after the system is ready to use again. [Expected Result] No kernel trace message. [Actual Result] Kernel trace message as: Jan 9 00:33:33 201606-22365 kernel: [ 37.701226] [ cut here ] Jan 9 00:33:33 201606-22365 kernel: [ 37.701243] kernel BUG at /build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627! Jan 9 00:33:33 201606-22365 kernel: [ 37.701261] invalid opcode: [#1] SMP Jan 9 00:33:33 201606-22365 kernel: [ 37.701273] Modules linked in: nvram msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Jan 9 00:33:33 201606-22365 kernel: [ 37.701735] CPU: 3 PID: 21 Comm: watchdog/3 Tainted: G OE 4.4.0-108-generic #131-Ubuntu Jan 9 00:33:33 201606-22365 kernel: [ 37.701756] Hardware name: Dell Inc. Inspiron 5767/ , BIOS 1.0.0 07/14/2016 Jan 9 00:33:33 201606-22365 kernel: [ 37.701774] task: 880169df6900 ti: 880169a1c000 task.ti: 880169a1c000 Jan 9 00:33:33 201606-22365 kernel: [ 37.701792] RIP: 0010:[] [] kfree+0x147/0x150 Jan 9 00:33:33 201606-22365 kernel: [ 37.701814] RSP: 0018:880169a1fd58 EFLAGS: 00010246 Jan 9 00:33:33 201606-22365 kernel: [ 37.701827] RAX: ea0005bd0120 RBX: 88016f404840 RCX: 88016f7fa220 Jan 9 00:33:33 201606-22365 kernel: [ 37.701843] RDX: ea0005a64420 RSI: ea0005a64820 RDI: ea0005bd0100 Jan 9 00:33:33 201606-22365 kernel: [ 37.701860] RBP: 880169a1fd70 R08: 0009 R09: ff80003f Jan 9 00:33:33 201606-22365 kernel: [ 37.701877] R10: ea0005bd0100 R11: 0001 R12: Jan 9 00
Re: [Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386
On Wed, Jan 10, 2018 at 5:45 PM, Joseph Salisbury wrote: > Thanks for the feedback, Christian. I would much rather install them > manually. I am able to do that without a problem. However, I am unable > to access the GRUB menu in the usual way to select a specific kernel. If you test through autotest, then there isn't a good way to manually intercept "while" running. > I tried all the usual way, holding shift, modifying /etc/default/grub > setting, but none seem to work. Other than just making sure that grub picks the right default by making sue the to-be-tested kernel is the latest I worked by modifying grub. Checking again if this still works ... I had a zesty testbed to remove anyway, so I could kill it if needed. By default it does boot "4.8.0-26-generic" Note: working in guest image via: $ qemu-system-x86_64 -m 1024 -smp 1 -nographic -net nic,model=virtio -net user -enable-kvm -cpu kvm64,+vmx,+lahf_lm ~/work/autopkgtest-zesty-amd64.img I installed 4.7.10-040710_4.7.10-040710.201610220847 from mainline builds as it is older and therefore would not be selected by grub automatically. After install I checked autopkgtest output... autopkgtest [07:54:48]: testbed running kernel: Linux 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:39:52 UTC 2016 Ok, now lets modify grub to boot the older kernel: I found that (at least in this case) the BIOS boot partition kind of breaks update-grub. /dev/sda1 227328 25583582 25356255 12.1G Linux filesystem /dev/sda14 204810239 81924M BIOS boot /dev/sda15 10240 227327 217088 106M EFI System The middle one is the odd one - that is the non efi compat grub img storage area. Anyway - to get around that I was adding: $ apt-get install --reinstall grub-efi $ echo "GRUB_DISABLE_OS_PROBER=true" | sudo tee -a /etc/default/grub So as usual e.g.: echo 'GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 4.7.10-040710-generic"' | sudo tee -a /etc/default/grub $ sudo update-grub And e voila: autopkgtest [08:20:29]: testbed running kernel: Linux 4.7.10-040710-generic #201610220847 SMP Sat Oct 22 12:50:14 UTC 2016 Other than the extra hoop I had to jump for the BIOS boot there was nothing special in my try. And I'd assume that could as much appear on real HW. I hope that helps to drive your test kernels. -- You 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 oops destroying interfaces on i386 Status in linux package in Ubuntu: Fix Committed Status in openvswitch package in Ubuntu: Confirmed Status in linux source package in Artful: In Progress Status in openvswitch source package in Artful: Confirmed Status in linux source package in Bionic: Fix Committed Status in openvswitch source package in Bionic: Confirmed 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.430
[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
Possible duplicate bug 1742160 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. 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/1742302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742622] [NEW] package linux-headers-4.13.0-25 (not installed) failed to install/upgrade: '/usr/src/linux-headers-4.13.0-25/include/net/xfrm.h.dpkg-new' をオープンできません: 許可されていない操作です
Public bug reported: virtualboxのubuntu ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-headers-4.13.0-25 (not installed) ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: main 3538 F pulseaudio Date: Thu Jan 11 15:45:57 2018 ErrorMessage: '/usr/src/linux-headers-4.13.0-25/include/net/xfrm.h.dpkg-new' をオープンできません: 許可されていない操作です IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 003: ID 056a:0010 Wacom Co., Ltd Graphire Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=56500155-90ed-475e-bdfc-d9583a9a20c5 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: SourcePackage: linux Title: package linux-headers-4.13.0-25 (not installed) failed to install/upgrade: '/usr/src/linux-headers-4.13.0-25/include/net/xfrm.h.dpkg-new' をオープンできません: 許可されていない操作です UpgradeStatus: No upgrade log present (probably fresh install) 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.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742622 Title: package linux-headers-4.13.0-25 (not installed) failed to install/upgrade: '/usr/src/linux-headers-4.13.0-25/include/net/xfrm.h .dpkg-new' をオープンできません: 許可されていない操作です Status in linux package in Ubuntu: New Bug description: virtualboxのubuntu ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-headers-4.13.0-25 (not installed) ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: main 3538 F pulseaudio Date: Thu Jan 11 15:45:57 2018 ErrorMessage: '/usr/src/linux-headers-4.13.0-25/include/net/xfrm.h.dpkg-new' をオープンできません: 許可されていない操作です IwConfig: enp0s3no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 003: ID 056a:0010 Wacom Co., Ltd Graphire Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=56500155-90ed-475e-bdfc-d9583a9a20c5 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 RfKill: SourcePackage: linux Title: package linux-headers-4.13.0-25 (not installed) failed to install/upgrade: '/usr/src/linux-headers-4.13.0-25/include/net/xfrm.h.dpkg-new' をオープンできません: 許可されていない操作です UpgradeStatus: No upgrade log present (probably fresh install) 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.family: Virtual Machine 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/linux/+bug/1742622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Ever since I installed Ubuntu 17.10 bete on my Lenovo Thinkpad S540, there was a message on boot and reboot "Configuration changed - restart" and the laptop would reboot. I was still able to boot from USB though and even updated the BIOS from USB. But that didn't solve the problem. Also the latest kernel update did not solve problem. After following the steps described in this post http://dailylinuxuser.com/2018/01/how-to-fix-your-bios-after-installing- ubuntu-17-10-on-a-lenovo-laptop.html this problem has been solved. 1.Boot into Ubuntu 2.Open a web browser and type the following into the address bar: http://people.canonical.com/~ypwong/lp1734147/linux- image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3.Open a terminal window (press ctrl, alt and T at the same time) or click on activities and type term into the search bar and click the icon that appears. 4.Go to the downloads folder by typing the following command cd ~/Downloads 5.Type the following command to install the package: sudo dpkg -i linux- image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 6.If the command completes without error reboot your computer and choose the new kernel. To get the grub menu to appear try pressing and holding the shift key before the Ubuntu logo appears. If the Ubuntu logo appears reboot again and press the escape key before the Ubuntu logo appears. >From the grub menu choose the version of Ubuntu with the highest Kernel number. (which should be 4.15.0) 7.Reboot your computer and open your BIOS settings and check to see if you can boot from USB and save BIOS changes. If you can boot from USB and change BIOS settings then you have successfully repaired your computer and you can skip to the last point. 8.If this hasn’t worked reboot your computer and choose the new kernel. Reboot your computer again and choose the new kernel. Now reboot your computer and check your BIOS settings. If your BIOS can be amended and you can boot from USB then you have successfully repaired your computer and you can skip to the last point. 9.Still not working? Don’t panic, open a web browser and type the following into the address bar: http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb 10.Open a terminal window (press CTRL, ALT and T or click activities, type Term into the search bar and click the icon) 11.Go to the downloads folder by typing the following command cd ~/Downloads 12.Type the following command to install the package: sudo dpkg -i http://people.canonical.com/~ypwong/lp1734147/linux- image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb 13.Wait for the package to install and if it is successful reboot your computer and press either the shift or escape key to bring up the grub menu and choose the new kernel that has appeared. 14.After Ubuntu loads reboot your computer and enter the BIOS settings. If you can change the settings and save them and you can boot from a USB drive then the issue is fixed. 15.Finally remove the packages you installed by typing the following command in a terminal window: sudo dpkg -r linux- image-4.15.0-041500rc6-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot
[Kernel-packages] [Bug 1740309] Re: user space process hangs when reading partition table of disk
It already happens with: 4.12.0-041200rc1-generic #201705131731
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1740309
Title:
user space process hangs when reading partition table of disk
Status in linux package in Ubuntu:
Confirmed
Bug description:
user space process as in parted or fdisk or update-grub2 that read partition
tables freeze on my system:
/dev/sda/ GPT disk with efi, swap and ubuntu artful partition
/dev/sdb old style partition table with one ext4 partition
/dev/sdc GPT disk with efi partition, windows 10
I.e. if I run as root :
# fdisk -l
Disk /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 56FF6AB0-076F-483C-890F-EC4B4FAF6313
DeviceStart End Sectors Size Type
/dev/sda1 2048 2000895 1998848 976M EFI System
/dev/sda2 2000896 1383 7999488 3,8G Linux swap
/dev/sda3 1384 488396799 478396416 228,1G Linux filesystem
Disk /dev/sdb: 489,1 GiB, 525112713216 bytes, 1025610768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2f11f9c4
Device Boot StartEndSectors Size Id Type
/dev/sdb12048 1025609727 1025607680 489G 83 Linux
<...process hangs here forever...>
With gdb I stepped through fdisk -l and saw that the call to open
('dev/sdc'..) never returns.
--
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D3p: andreas1807 F...m pulseaudio
/dev/snd/controlC0: andreas1807 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=8a7a6077-0a3e-4641-8f15-bd6f09826510
InstallationDate: Installed on 2017-12-26 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IwConfig:
lono wireless extensions.
enp8s0no wireless extensions.
enp12s0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux-image-4.13.0-21-generic 4.13.0-21.24
PackageArchitecture: amd64
ProcFB:
0 radeondrmfb
1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed
root=UUID=4f18ad67-a4f0-4e03-b061-66615751538e ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-21-generic N/A
linux-backports-modules-4.13.0-21-generic N/A
linux-firmware 1.169.1
RfKill:
Tags: artful
Uname: Linux 4.13.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/09/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: EP2C602
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd12/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnEP2C602:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740309/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737671] Re: Blu-ray burner no longer detected
The problem still exists in kernel 4.4.0-109. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737671 Title: Blu-ray burner no longer detected Status in linux package in Ubuntu: Incomplete Bug description: Linux Kernel 97 is the last kernel in which my Blu-ray burner is still detected. Booting with all following kernels makes it undetectable, and I can't use it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-103-generic 4.4.0-103.126 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: misthalu 1913 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 12 08:00:12 2017 HibernationDevice: RESUME=UUID=d22d1aa7-36b9-44ab-936e-f713d1f79a40 InstallationDate: Installed on 2016-05-19 (571 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp8s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic root=UUID=9b2e1b7a-2bbd-4a36-990f-6ba56f567b2d ro quiet splash vt.handoff=7 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: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-Gaming 3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z170X-Gaming 3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
This seems to be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742095 on which I found a workaround for the DKMS build process. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. 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/1742302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742602] Re: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26
Here's the packed apport file. ** Attachment added: "apport.linux.2.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742602/+attachment/5034906/+files/apport.linux.2.apport -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742602 Title: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26 Status in linux package in Ubuntu: Confirmed Bug description: I'm following the HWE kernels in Ubuntu 16.04, so my kernel was upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the splash screen and disk encryption passphrase prompt showed correctly, but when X started, the screen went blank. Logs showed everything running as normal despite the blank screen. Rebooting with the "nomodeset" kernel parameter fixed the issue but is not suitable as a permanent workaround since it disables my external monitor. Rebooting back into 4.10 also fixed the issue. I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried both intel and fbdev X drivers, both gave a blank screen. lsb_release: Ubuntu 16.04.3 LTS dpkg-query -W: linux-signed-image-generic-hwe-16.04 4.13.0.26.46 xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1 xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1 xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1 In Xorg.0.log with fbdev, I saw: [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument repeated 239 times. Typical kernel messages attached (from kern.log, reformatted to look like dmesg). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742602] Re: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26
I ran apport-collect, selected "keep", and edited the resulting file to remove private information. But I couldn't find any way to upload such a file to an existing bug report. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Attachment removed: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742602/+attachment/5034871/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742602 Title: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26 Status in linux package in Ubuntu: Confirmed Bug description: I'm following the HWE kernels in Ubuntu 16.04, so my kernel was upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the splash screen and disk encryption passphrase prompt showed correctly, but when X started, the screen went blank. Logs showed everything running as normal despite the blank screen. Rebooting with the "nomodeset" kernel parameter fixed the issue but is not suitable as a permanent workaround since it disables my external monitor. Rebooting back into 4.10 also fixed the issue. I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried both intel and fbdev X drivers, both gave a blank screen. lsb_release: Ubuntu 16.04.3 LTS dpkg-query -W: linux-signed-image-generic-hwe-16.04 4.13.0.26.46 xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1 xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1 xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1 In Xorg.0.log with fbdev, I saw: [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument repeated 239 times. Typical kernel messages attached (from kern.log, reformatted to look like dmesg). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742095] Re: kernel 4.13.0-24 not working with nvidia drivers, monitor flickering
Now, I managed to compile the drivers and since the package was already installed, all I had to do was add the missing header: cd /usr/src/nvidia-387-387.26/nvidia-uvm sudo sed '1i#include ' -i uvm8_va_block.c Then compile and install: sudo dkms autoinstall -k $(uname -r) And lastly reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742095 Title: kernel 4.13.0-24 not working with nvidia drivers, monitor flickering Status in linux package in Ubuntu: Incomplete Bug description: After update to kernel 4.13.0-24 gnome will not start and the monitors will be flickering... It is impossible to see were it stops on the startup since the flickering is too fast (I may have to film it and pause to check) Running: Ubuntu 17.10, 64 bit OS HP ZBooks G2 15" with latest bios update Processor: Intel® Xeon(R) CPU E3-1505M v5 @ 2.80GHz × 8 Memory: 15.6 GB GNOME: 3.26.2 vanilla with nvidia-387 drivers System is working fine if I keep using kernel 4.13.0-22 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlo 4669 F pulseaudio /dev/snd/controlC2: carlo 4669 F pulseaudio /dev/snd/controlC0: carlo 4669 F pulseaudio DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/vg-swap InstallationDate: Installed on 2016-04-25 (624 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: HP HP ZBook Studio G3 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-24-generic root=/dev/mapper/vg-data ro ProcVersionSignature: Ubuntu 4.13.0-24.28-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-24-generic N/A linux-backports-modules-4.13.0-24-generic N/A linux-firmware 1.169.2 Tags: artful Uname: Linux 4.13.0-24-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (81 days ago) UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: HP dmi.bios.version: N82 Ver. 01.19 dmi.board.name: 80D4 dmi.board.vendor: HP dmi.board.version: KBC Version 11.6F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN82Ver.01.19:bd09/26/2017:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ZBook Studio G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. 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/1742302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1697450] Re: Whole machine freezes at startup using kernels after 4.8
Zesty has this problem, right? Then please try Linux kernel v4.9 in http://kernel.ubuntu.com/~kernel- ppa/mainline/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697450 Title: Whole machine freezes at startup using kernels after 4.8 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to install from the daily Artful desktop image (20170612). After boot, the gnome session hangs at startup, while the "zoom" animation is being shown. I have an intel card: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f780 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 I'm not sure how to debug this further, but I had similar issues with the installer from Zesty as well (see https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846) With Artful, at least it gets past the splash screen but then it hangs. Note that the system is currently running Yakkety with no issue. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-07-30 (71 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Tags: artful wayland-session Uname: Linux 4.8.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1661876] Re: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged
So what's the output of `acpitool -a -b` when the icon disappears? Also, what's the output of `gsettings get com.canonical.indicator.power icon-policy`? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1661876 Title: [Asus UX360UA] battery status in unity-panel is not changing when battery is being charged Status in linux package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile. When I start charging my computer the battery icon on the unity-panel is not changing (it stays in the 98% complete). This is strange because this is a fresh installation so I didn't change any configuration yet. Also, when I tried this ubuntu in the live pen, I noticed that the icon changed when I started charging the laptop. That's why I think it is a bug. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tjiagom1806 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933 InstallationDate: Installed on 2017-02-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX360UA Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 RelatedPackageVersions: linux-restricted-modules-4.4.0-62-generic N/A linux-backports-modules-4.4.0-62-generic N/A linux-firmware1.157.6 Tags: xenial Uname: Linux 4.4.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX360UA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX360UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX360UA 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/1661876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727228] Re: ath9k can't connect to wifi AP
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1727228 Title: ath9k can't connect to wifi AP Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: iwlist scan can search the available wifi APs, but can't get connected. On new Intel platforms like ApolloLake, legacy interrupt mechanism (INTx) is not supported, so WLAN modules are not working because interrupts are missing. The affected and listed platforms are Dell Inspiron 24-3460 Dell Inspiron 14-3473 Dell Inspiron 3472 Dell Inspiron 3576 Dell Vostro 3262 Dell Vostro 15-3572 Dell Vostro 3578 There should not be any regression potential. These are newly enabled machines and quirks are applied based on DMI_PRODUCT_NAME to only use MSI on such machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1727228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742323] Re: Meltdown Update Kernel doesnt boot
*** This bug is a duplicate of bug 1741934 *** https://bugs.launchpad.net/bugs/1741934 Many thanks to the Kernel Team for this speedy 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/1742323 Title: Meltdown Update Kernel doesnt boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Using a Dell Poweredge T20 and Ubuntu 16.04 with the 4.4 Kernel. Just got the Meltdown update to kernel linux-image-4.4.0-108-generic but this doesnt boot at all. It just hangs after grub. There is no logs from syslog or such. SysReq Keys dont work neither. The last kernel linux-image-4.4.0-104-generic still boots fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-104-generic 4.4.0-104.127 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-104-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/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' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Wed Jan 10 01:36:01 2018 HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99 InstallationDate: Installed on 2017-05-17 (237 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge T20 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic.efi.signed root=UUID=9edb2ffb-791e-4988-b3a9-7ce73227802c ro RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0VD5HY dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/11/2017:svnDellInc.:pnPowerEdgeT20:pvr00:rvnDellInc.:rn0VD5HY:rvrA07:cvnDellInc.:ct6:cvr: dmi.product.name: PowerEdge T20 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1433987] Re: [Realtek 0bda:b728] Bluetooth is useless after installed 14.04.2
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1433987 Title: [Realtek 0bda:b728] Bluetooth is useless after installed 14.04.2 Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Expired Bug description: CID : 201407-15368 Lenovo E450 (A+A) with 14.04.2 (utopic) CID : 201408-15472 Lenovo E555 (A+A) with 14.04.2 (utopic) Steps: 1. Install 14.04.2 on E450 or E555 2. Navigate to system Setting -> Bluetooth 3. Try to set up a new device. Expected result: When searching for devices, there are some BT device listed. Actual result: System keeping searching devices, but there is no BT device could be searched. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 05:30:41 2015 InstallationDate: Installed on 2015-03-18 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1433987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1358704] Re: Atheros AR8161[1969:1091] and AR8162 [1969:1090] mac address would change after powered off for a while
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1358704 Title: Atheros AR8161[1969:1091] and AR8162 [1969:1090] mac address would change after powered off for a while Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Expired Bug description: CID: 201202-10508 CID: 201202-10511 CID: 201202-10527 The MAC address would change after you power off the system for a while (few days) 201202-10508 and 201202-10511 equipped with AR8162 [1969:1090] 201202-10527 equipped with AR8161[1969:1091] I found this issue when trying to install 12.04.5 via PXE network installation. The MAC address changing pattern is interesting, there is a common address they will change into - 00:13:74:00:00:00 This looks like a HW issue, but I'm not very confident about it. Maybe not a big deal, but this issue would prevent these system from being selected into our SRU pool, the worse scenario is that this system is attached to a MAC-address-registered network (my dormitory network back into university require users to register they MAC address) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Aug 19 06:00:11 2014 InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1433920] Re: [Lenovo E450] ([Radeon R7 M260] [1002:6900]) [Lenovo E550] ([Radeon R7 M265] [1002:6604]) Display abnormally on both screen under extend mode.
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1433920 Title: [Lenovo E450] ([Radeon R7 M260] [1002:6900]) [Lenovo E550] ([Radeon R7 M265] [1002:6604]) Display abnormally on both screen under extend mode. Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Expired Bug description: CID : 201411-16166 Lenovo E450 (I+A) with 14.04.2 (utopic) CID : 201411-16167 Lenovo E550 (I+A) with 14.04.2 (utopic) Steps: 1. Install 14.04.2 on E450. 2. Log in system and install fglrx. 3. Reboot system. 4. Connect HDMI cable. 5. Switch internal, external, mirror and extend modes by display key. Expected result: The 4 modes show normally. Actual result: Display abnormally on both screen under extendl mode. Please refer to picture.jpg ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-30-generic 3.16.0-30.40~14.04.1 [modified: boot/vmlinuz-3.16.0-30-generic] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 02:42:21 2015 InstallationDate: Installed on 2015-03-16 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1433920/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1409616] Re: [AMD Trinity + Thames]: Failed to resume from suspend
[Expired for linux-lts-trusty (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-lts-trusty (Ubuntu) Status: Incomplete => Expired -- 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/1409616 Title: [AMD Trinity + Thames]: Failed to resume from suspend Status in HWE Next: Won't Fix Status in linux-lts-trusty package in Ubuntu: Expired Bug description: System with open source driver unable to resume correctly after suspend. As a verify manually install fglrx driver, resume from suspend is okay. However is not recommended in "Additional Drivers", bug reported sperately here: bug 1390338 Graphic Chipsets: ubuntu@201209-11726:/usr/lib/checkbox/bin$ lspci -nn|grep -i VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72~precise1 ProcVersionSignature: Ubuntu 3.13.0-43.72~precise1-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-43-generic. ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: Generic [HD-Audio Generic], device 0: 92HD87B2/4 Analog [92HD87B2/4 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1852 F pulseaudio /dev/snd/controlC0: ubuntu 1852 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'HDMI'/'HDA ATI HDMI at 0xf0444000 irq 51' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100300' Controls : 7 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'Generic'/'HD-Audio Generic at 0xf044 irq 16' Mixer name : 'IDT 92HD87B2/4' Components : 'HDA:111d76d9,103c184c,00100107' Controls : 23 Simple ctrls : 11 Date: Mon Jan 12 01:54:51 2015 HibernationDevice: RESUME=UUID=59dbefd6-0f07-4ab2-b39c-158e22572e02 InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=3a89e214-edc2-4888-9967-9dcfc27af6ad ro quiet splash initcall_debug vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/ubuntu not ours. No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.79.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 184C dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.34 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr089D1100501020100:rvnHewlett-Packard:rn184C:rvr57.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g7 Notebook PC dmi.product.version: 089D1100501020100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1409616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1439492] Re: [Dell Vostro 3546] Sometimes the clickpad will be malfunctioning on this system
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1439492 Title: [Dell Vostro 3546] Sometimes the clickpad will be malfunctioning on this system Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Expired Bug description: CID: 201404-14997 Dell Vostro 3546 Sometimes the clickpad on this system does not work as expected. It will stop responding to any movments, the only way to move the cursor is click on the touchpad and drag (just like selecting multiple files) I'm not sure what event could trigger this issue, but I do see this twice on this system (and on 201404-14998, another Vostro 3546) One is right after the whole testing process, another is after being suspended for two days. I tried to run the 30 cycle suspend / hibernate and the cpu stress test, but it seems that these are not the trigger. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-48-generic 3.13.0-48.80 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1610 F pulseaudio /dev/snd/controlC1: ubuntu 1610 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Apr 1 22:44:05 2015 HibernationDevice: RESUME=UUID=cb4a77a9-ee15-4ee5-b063-5c0b28a5d789 InstallationDate: Installed on 2015-03-24 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Vostro 3546 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic root=UUID=7d45912a-8768-4c39-8ec0-43eec97c733d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-48-generic N/A linux-backports-modules-3.13.0-48-generic N/A linux-firmware 1.127.11 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 02R010 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnVostro3546:pvrNotSpecified:rvnDellInc.:rn02R010:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3546 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1439492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730176] Re: VMWare Workstation Pro 12.5.7 never works
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730176 Title: VMWare Workstation Pro 12.5.7 never works Status in linux package in Ubuntu: Expired Bug description: Before you can run VMWare, serveral modules must be compiled and loaded into the running kernel. Log Details: 2017-11-05T10:59:17.836+01:00| vthread-4| I125: Log for VMware Workstation pid=4100 version=12.5.7 build=build-5813279 option=Release 2017-11-05T10:59:17.836+01:00| vthread-4| I125: The process is 64-bit. 2017-11-05T10:59:17.836+01:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8 2017-11-05T10:59:17.836+01:00| vthread-4| I125: Host is Linux 4.13.0-16-generic Linux Mint 18.2 Sonya 2017-11-05T10:59:17.836+01:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden. 2017-11-05T10:59:17.836+01:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values. 2017-11-05T10:59:17.836+01:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": Datei oder Verzeichnis nicht gefunden. 2017-11-05T10:59:17.836+01:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values. 2017-11-05T10:59:17.836+01:00| vthread-4| I125: PREF Unable to check permissions for preferences file. 2017-11-05T10:59:17.836+01:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/preferences": Datei oder Verzeichnis nicht gefunden. 2017-11-05T10:59:17.836+01:00| vthread-4| I125: PREF Failed to load user preferences. 2017-11-05T10:59:17.878+01:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-4100.log 2017-11-05T10:59:17.884+01:00| vthread-4| I125: Obtaining info using the running kernel. 2017-11-05T10:59:17.884+01:00| vthread-4| I125: Created new pathsHash. 2017-11-05T10:59:17.884+01:00| vthread-4| I125: Setting header path for 4.13.0-16-generic to "/lib/modules/4.13.0-16-generic/build/include". 2017-11-05T10:59:17.884+01:00| vthread-4| I125: Validating path "/lib/modules/4.13.0-16-generic/build/include" for kernel release "4.13.0-16-generic". 2017-11-05T10:59:17.884+01:00| vthread-4| I125: Failed to find /lib/modules/4.13.0-16-generic/build/include/linux/version.h 2017-11-05T10:59:17.884+01:00| vthread-4| I125: /lib/modules/4.13.0-16-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead. 2017-11-05T10:59:17.884+01:00| vthread-4| I125: using /usr/bin/gcc for preprocess check 2017-11-05T10:59:17.889+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.13.0-16-generic". 2017-11-05T10:59:17.889+01:00| vthread-4| I125: The header path "/lib/modules/4.13.0-16-generic/build/include" for the kernel "4.13.0-16-generic" is valid. Whoohoo! 2017-11-05T10:59:17.978+01:00| vthread-4| I125: found symbol version file /lib/modules/4.13.0-16-generic/build/Module.symvers 2017-11-05T10:59:17.978+01:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.13.0-16-generic/build/Module.symvers. 2017-11-05T10:59:17.994+01:00| vthread-4| I125: Read 22185 symbol versions 2017-11-05T10:59:17.994+01:00| vthread-4| I125: Reading in info for the vmmon module. 2017-11-05T10:59:17.994+01:00| vthread-4| I125: Reading in info for the vmnet module. 2017-11-05T10:59:17.994+01:00| vthread-4| I125: Reading in info for the vmblock module. 2017-11-05T10:59:17.994+01:00| vthread-4| I125: Reading in info for the vmci module. 2017-11-05T10:59:17.994+01:00| vthread-4| I125: Reading in info for the vsock module. 2017-11-05T10:59:17.994+01:00| vthread-4| I125: Setting vsock to depend on vmci. 2017-11-05T10:59:17.994+01:00| vthread-4| I125: Invoking modinfo on "vmmon". 2017-11-05T10:59:17.996+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 0. 2017-11-05T10:59:17.996+01:00| vthread-4| I125: Invoking modinfo on "vmnet". 2017-11-05T10:59:17.998+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2017-11-05T10:59:17.998+01:00| vthread-4| I125: Invoking modinfo on "vmblock". 2017-11-05T10:59:18.000+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2017-11-05T10:59:18.000+01:00| vthread-4| I125: Invoking modinfo on "vmci". 2017-11-05T10:59:18.001+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256. 2017-11-05T10:59:18.001+01:00| vthread-4| I125: Invoking modinfo on "vsock". 2017-11-05T10:59:18.003+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 0. 2017-11-05T10:59:18.015+01:00| vthread-4| I125: to be installed: vmnet status: 0 2017-11-05T10:59:18.029+01:00| vthread-4| I125: Obtaining info using the running kernel.
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
kernel 4.13.0-21 and up has already disabled the intel spi kernel module, whether the kernel has commit d9018976cdb6 should not matter (unless you are building your own kernel using ubuntu 4.13 kernel source with intel-spi enabled). -- You 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: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: 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!! To manage notifications about this bug go to: https://bugs.launchpad.net/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 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Apologies in advance for asking, as I know this isn't the ideal place to ask. I'm having the same problem with Knoppix, at least as far as symptoms are concerned. I'd hoped that using Ubuntu could fix it, but Knoppix is now the only thing that will boot from USB. I have one of the affected models (Lenovo) and the fine people at the Knoppix forums have decided to not approve my topic in any help areas over there...so I thought I might try here where people are more helpful. Anyone have any ideas? Thanks for your time. N00b here. -- You 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: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: 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!! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subs
[Kernel-packages] [Bug 1742318] Re: USB-Storage Quirk for 174c:1356
Can you attach the full dmesg? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742318 Title: USB-Storage Quirk for 174c:1356 Status in linux package in Ubuntu: Incomplete Bug description: A usb-storage quirk is needed for the Mediasonic ProRaid 2 Bay 2.5' SATA HDD / SSD Enclosure - USB 3.1 Gen-II Type-C (HUR6-SU31) for reliable use in Ubuntu/Kubuntu 14-17.10. Using quirk 'u' appears to have fixed disconnect issues during install and use. Linux Version: Ubuntu 4.13.0-16.19-generic 4.13.4 Device ID:174c:1356 ASMedia Technology Inc. usb 9-1: new SuperSpeed USB device number 2 using xhci_hcd usb 9-1: New USB device found, idVendor=174c, idProduct=1356 usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 usb 9-1: Product: ASM1352R-Fast usb 9-1: Manufacturer: ASMT usb 9-1: SerialNumber: 0001 usb 9-1: UAS is blacklisted for this device, using usb-storage instead Note: With/without UAS the issue persisted. I disabled UAS to prevent devices sleeping to eliminate that as a possibility. Symptoms: Before using the quirk, the enclosure would completely stop responding during an install attempt, and the usb host would eventually be disabled. The device's LEDs would continue to blink as if being accessed. Fix: I specified the quirk by appending "usb- storage.quirks=174c:1356:u" to the linux line in Grub. Hopefully others can verify this (if I'm not insane) and include a patch for this upstream in the Kernel. Note: For those who install to a device such as this, you may need to modify your installation before booting it, by creating a file "/etc/modprobe.d/asm1352r-usb-quirk.conf" with contents "options usb- storage quirks=0x174c:0x1356:u". I have seen others (through Google) issuing the same "u" quirk for several ASMedia devices...Perhaps their chipsets need this? This is my first bug report. If any more information is needed, please inform me. I'd like to thank a TJ- in Ubuntu's IRC for helping nail this down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742602] 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 1742602 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: artful -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742602 Title: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26 Status in linux package in Ubuntu: Incomplete Bug description: I'm following the HWE kernels in Ubuntu 16.04, so my kernel was upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the splash screen and disk encryption passphrase prompt showed correctly, but when X started, the screen went blank. Logs showed everything running as normal despite the blank screen. Rebooting with the "nomodeset" kernel parameter fixed the issue but is not suitable as a permanent workaround since it disables my external monitor. Rebooting back into 4.10 also fixed the issue. I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried both intel and fbdev X drivers, both gave a blank screen. lsb_release: Ubuntu 16.04.3 LTS dpkg-query -W: linux-signed-image-generic-hwe-16.04 4.13.0.26.46 xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1 xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1 xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1 In Xorg.0.log with fbdev, I saw: [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument repeated 239 times. Typical kernel messages attached (from kern.log, reformatted to look like dmesg). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742603] 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 1742603 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742603 Title: Kernel 4.13.0-26.29~16.04.2 Causing Crash Status in linux package in Ubuntu: Incomplete Bug description: Upgraded kernel to 4.13.0-26.29~16.04.2 and Cinnamon crashed while display was way off. As you can see in the system specs below, I booted into kernel 4.10 and all is well System:Host: Z97X-UD3H-BK Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0) Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.3 Sylvia Machine: System: Gigabyte product: Z97X-UD3H-BK Mobo: Gigabyte model: Z97X-UD3H-BK-CF v: x.x Bios: American Megatrends v: F8 date: 09/19/2015 CPU: Quad core Intel Core i5-4690 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28000 clock speeds: max: 3900 MHz 1: 897 MHz 2: 830 MHz 3: 1291 MHz 4: 1061 MHz Graphics: Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 Card-2: NVIDIA GM206 [GeForce GTX 950] bus-ID: 01:00.0 Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 2560x1440@59.95hz GLX Renderer: GeForce GTX 950/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes Audio: Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0 Card-2 NVIDIA Device 0fba driver: snd_hda_intel bus-ID: 01:00.1 Card-3 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Card-4 Logitech HD Webcam C910 driver: USB Audio usb-ID: 003-003 Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic Network: Card-1: Intel Ethernet Connection I217-V driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0 IF: eno1 state: down mac: Card-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k bus-ID: 05:00.0 IF: wlp5s0 state: up mac: Drives:HDD Total Size: 2490.5GB (1.1% used) ID-1: /dev/sda model: Crucial_CT240M50 size: 240.1GB ID-2: /dev/sdb model: Samsung_SSD_850 size: 250.1GB ID-3: /dev/sdc model: WDC_WD1002FAEX size: 1000.2GB ID-4: /dev/sdd model: WDC_WD10EFRX size: 1000.2GB Partition: ID-1: / size: 23G used: 14G (63%) fs: ext4 dev: /dev/sdb1 ID-2: /home size: 202G used: 6.5G (4%) fs: ext4 dev: /dev/sdb3 ID-3: swap-1 size: 5.12GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:33C Fan Speeds (in rpm): cpu: N/A Info: Processes: 218 Uptime: 29 min Memory: 1263.6/32009.9MB Init: systemd runlevel: 5 Gcc sys: 5.4.0 Client: Shell (bash 4.3.481) inxi: 2.2.35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742603] [NEW] Kernel 4.13.0-26.29~16.04.2 Causing Crash
Public bug reported: Upgraded kernel to 4.13.0-26.29~16.04.2 and Cinnamon crashed while display was way off. As you can see in the system specs below, I booted into kernel 4.10 and all is well System:Host: Z97X-UD3H-BK Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0) Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.3 Sylvia Machine: System: Gigabyte product: Z97X-UD3H-BK Mobo: Gigabyte model: Z97X-UD3H-BK-CF v: x.x Bios: American Megatrends v: F8 date: 09/19/2015 CPU: Quad core Intel Core i5-4690 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28000 clock speeds: max: 3900 MHz 1: 897 MHz 2: 830 MHz 3: 1291 MHz 4: 1061 MHz Graphics: Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 Card-2: NVIDIA GM206 [GeForce GTX 950] bus-ID: 01:00.0 Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 2560x1440@59.95hz GLX Renderer: GeForce GTX 950/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes Audio: Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0 Card-2 NVIDIA Device 0fba driver: snd_hda_intel bus-ID: 01:00.1 Card-3 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Card-4 Logitech HD Webcam C910 driver: USB Audio usb-ID: 003-003 Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic Network: Card-1: Intel Ethernet Connection I217-V driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0 IF: eno1 state: down mac: Card-2: Qualcomm Atheros AR93xx Wireless Network Adapter driver: ath9k bus-ID: 05:00.0 IF: wlp5s0 state: up mac: Drives:HDD Total Size: 2490.5GB (1.1% used) ID-1: /dev/sda model: Crucial_CT240M50 size: 240.1GB ID-2: /dev/sdb model: Samsung_SSD_850 size: 250.1GB ID-3: /dev/sdc model: WDC_WD1002FAEX size: 1000.2GB ID-4: /dev/sdd model: WDC_WD10EFRX size: 1000.2GB Partition: ID-1: / size: 23G used: 14G (63%) fs: ext4 dev: /dev/sdb1 ID-2: /home size: 202G used: 6.5G (4%) fs: ext4 dev: /dev/sdb3 ID-3: swap-1 size: 5.12GB used: 0.00GB (0%) fs: swap dev: /dev/sdb2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 0.0:33C Fan Speeds (in rpm): cpu: N/A Info: Processes: 218 Uptime: 29 min Memory: 1263.6/32009.9MB Init: systemd runlevel: 5 Gcc sys: 5.4.0 Client: Shell (bash 4.3.481) inxi: 2.2.35 ** 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/1742603 Title: Kernel 4.13.0-26.29~16.04.2 Causing Crash Status in linux package in Ubuntu: New Bug description: Upgraded kernel to 4.13.0-26.29~16.04.2 and Cinnamon crashed while display was way off. As you can see in the system specs below, I booted into kernel 4.10 and all is well System:Host: Z97X-UD3H-BK Kernel: 4.10.0-38-generic x86_64 (64 bit gcc: 5.4.0) Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.3 Sylvia Machine: System: Gigabyte product: Z97X-UD3H-BK Mobo: Gigabyte model: Z97X-UD3H-BK-CF v: x.x Bios: American Megatrends v: F8 date: 09/19/2015 CPU: Quad core Intel Core i5-4690 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28000 clock speeds: max: 3900 MHz 1: 897 MHz 2: 830 MHz 3: 1291 MHz 4: 1061 MHz Graphics: Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 Card-2: NVIDIA GM206 [GeForce GTX 950] bus-ID: 01:00.0 Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 2560x1440@59.95hz GLX Renderer: GeForce GTX 950/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 378.13 Direct Rendering: Yes Audio: Card-1 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0 Card-2 NVIDIA Device 0fba driver: snd_hda_intel bus-ID: 01:00.1 Card-3 Intel 9 Series Family HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Card-4 Logitech HD Webcam C910 driver: USB Audio usb-ID: 003-003 Sound: Advanced Linux Sound Architecture v: k4.10.0-38-generic Network: Card-1: Intel Ethernet Connection I217-V driver
[Kernel-packages] [Bug 1742602] [NEW] Blank screen when starting X after upgrading from 4.10 to 4.13.0-26
Public bug reported: I'm following the HWE kernels in Ubuntu 16.04, so my kernel was upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the splash screen and disk encryption passphrase prompt showed correctly, but when X started, the screen went blank. Logs showed everything running as normal despite the blank screen. Rebooting with the "nomodeset" kernel parameter fixed the issue but is not suitable as a permanent workaround since it disables my external monitor. Rebooting back into 4.10 also fixed the issue. I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried both intel and fbdev X drivers, both gave a blank screen. lsb_release: Ubuntu 16.04.3 LTS dpkg-query -W: linux-signed-image-generic-hwe-16.044.13.0.26.46 xserver-xorg-hwe-16.04 1:7.7+16ubuntu3~16.04.1 xserver-xorg-video-intel-hwe-16.04 2:2.99.917+git20170309-0ubuntu1~16.04.1 xserver-xorg-video-fbdev-hwe-16.04 1:0.4.4-1build6~16.04.1 In Xorg.0.log with fbdev, I saw: [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument repeated 239 times. Typical kernel messages attached (from kern.log, reformatted to look like dmesg). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1742602/+attachment/5034871/+files/dmesg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742602 Title: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26 Status in linux package in Ubuntu: New Bug description: I'm following the HWE kernels in Ubuntu 16.04, so my kernel was upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the splash screen and disk encryption passphrase prompt showed correctly, but when X started, the screen went blank. Logs showed everything running as normal despite the blank screen. Rebooting with the "nomodeset" kernel parameter fixed the issue but is not suitable as a permanent workaround since it disables my external monitor. Rebooting back into 4.10 also fixed the issue. I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried both intel and fbdev X drivers, both gave a blank screen. lsb_release: Ubuntu 16.04.3 LTS dpkg-query -W: linux-signed-image-generic-hwe-16.04 4.13.0.26.46 xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1 xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1 xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1 In Xorg.0.log with fbdev, I saw: [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument repeated 239 times. Typical kernel messages attached (from kern.log, reformatted to look like dmesg). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742474] Re: Bad return status for module build on kernel: 4.13.0-26-generic (i686)
Also, works well with kernel 4.4.0-109.132. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742474 Title: Bad return status for module build on kernel: 4.13.0-26-generic (i686) Status in linux package in Ubuntu: Confirmed Bug description: Distributor ID: LinuxMint Description: Linux Mint 18.3 Sylvia Release: 18.3 Codename: sylvia Linux Asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux Linux Mint 18.3 with HWE Kernel (sudo apt install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04) I've upgraded linux kernel from 4.10.0-4.10.0-42.46~16.04.1 to 4.13.0-26.29~16.04.2. I've got errors while upgrade kernel. And, After rebooting, my linux login screen has been broken. I cannot log in and my linux screen has gone black. Restroing kernel 4.10, then works well. run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-26-generic /boot/vmlinuz-4.13.0-26-generic Error! Bad return status for module build on kernel: 4.13.0-26-generic (i686) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. Belows are /var/lib/dkms/ndiswrapper/1.60/build/make.log. DKMS make.log for ndiswrapper-1.60 for kernel 4.13.0-26-generic (i686) 2018. 01. 11. (목) 00:16:20 KST make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 들어감 AR /var/lib/dkms/ndiswrapper/1.60/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o In file included from /var/lib/dkms/ndiswrapper/1.60/build/ndis.h:19:0, from /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:16: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMAllocateSharedMemory’: /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: error: ‘__GFP_REPEAT’ undeclared (first use in this function) GFP_KERNEL | __GFP_REPEAT) ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of macro ‘PCI_DMA_ALLOC_COHERENT’ *virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, &dma_addr); ^ /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: note: each undeclared identifier is reported only once for each function it appears in GFP_KERNEL | __GFP_REPEAT) ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of macro ‘PCI_DMA_ALLOC_COHERENT’ *virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, &dma_addr); ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMIndicateReceivePacket’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2261:15: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘EthRxIndicateHandler’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2349:14: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMTransferDataComplete’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2464:14: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ scripts/Makefile.build:308: '/var/lib/dkms/ndiswrapper/1.60/build/ndis.o' 타겟에 대한 명령이 실패했습니다 make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/ndis.o] 오류 1 Makefile:1550: '_module_/var/lib/dkms/ndiswrapper/1.60/build' 타겟에 대한 명령이 실패했습니다 make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] 오류 2 make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 나감 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741946] Re: no wifi kernel - regression 4.13.0-24 in lenovo yoga
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1741946 Title: no wifi kernel - regression 4.13.0-24 in lenovo yoga Status in linux package in Ubuntu: Fix Released Bug description: 4.13.0-24-generic does not have a network connection However, Linux bix 4.13.0-22-generic #25-Ubuntu SMP Tue Dec 19 11:13:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and previous kernels work fine description: Notebook product: 80HE (LENOVO_MT_80HE_BU_idea_FM_Lenovo YOGA 3 Pro-1370) vendor: LENOVO version: Lenovo YOGA 3 Pro-1370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
I also installed and booted 4.15-rc7 and attempted to install nvidia-387 and got another crash in the DKMS build process. However I installed nvidia-384 (this would be the just-released 384.111) on 4.13.0-26-generic and it works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in linux package in Ubuntu: Incomplete Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. 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/1742302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741946] Re: no wifi kernel - regression 4.13.0-24 in lenovo yoga
updated to 4.13.0-25 wifi works fine with this newer 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/1741946 Title: no wifi kernel - regression 4.13.0-24 in lenovo yoga Status in linux package in Ubuntu: Incomplete Bug description: 4.13.0-24-generic does not have a network connection However, Linux bix 4.13.0-22-generic #25-Ubuntu SMP Tue Dec 19 11:13:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and previous kernels work fine description: Notebook product: 80HE (LENOVO_MT_80HE_BU_idea_FM_Lenovo YOGA 3 Pro-1370) vendor: LENOVO version: Lenovo YOGA 3 Pro-1370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741946] Re: no wifi kernel - regression 4.13.0-24 in lenovo yoga
Thank you for your support. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741946 Title: no wifi kernel - regression 4.13.0-24 in lenovo yoga Status in linux package in Ubuntu: Incomplete Bug description: 4.13.0-24-generic does not have a network connection However, Linux bix 4.13.0-22-generic #25-Ubuntu SMP Tue Dec 19 11:13:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and previous kernels work fine description: Notebook product: 80HE (LENOVO_MT_80HE_BU_idea_FM_Lenovo YOGA 3 Pro-1370) vendor: LENOVO version: Lenovo YOGA 3 Pro-1370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742095] Re: kernel 4.13.0-24 not working with nvidia drivers, monitor flickering
I noticed that DKMS fails to compile the drivers for this kernel. I have no issues when downgrading to nvidia-384, but as someone said above it breaks CUDA. ** Attachment added: "nvidia-387.0.crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742095/+attachment/5034866/+files/nvidia-387.0.crash -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742095 Title: kernel 4.13.0-24 not working with nvidia drivers, monitor flickering Status in linux package in Ubuntu: Incomplete Bug description: After update to kernel 4.13.0-24 gnome will not start and the monitors will be flickering... It is impossible to see were it stops on the startup since the flickering is too fast (I may have to film it and pause to check) Running: Ubuntu 17.10, 64 bit OS HP ZBooks G2 15" with latest bios update Processor: Intel® Xeon(R) CPU E3-1505M v5 @ 2.80GHz × 8 Memory: 15.6 GB GNOME: 3.26.2 vanilla with nvidia-387 drivers System is working fine if I keep using kernel 4.13.0-22 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlo 4669 F pulseaudio /dev/snd/controlC2: carlo 4669 F pulseaudio /dev/snd/controlC0: carlo 4669 F pulseaudio DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=/dev/mapper/vg-swap InstallationDate: Installed on 2016-04-25 (624 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: HP HP ZBook Studio G3 Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-24-generic root=/dev/mapper/vg-data ro ProcVersionSignature: Ubuntu 4.13.0-24.28-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-24-generic N/A linux-backports-modules-4.13.0-24-generic N/A linux-firmware 1.169.2 Tags: artful Uname: Linux 4.13.0-24-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-20 (81 days ago) UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/26/2017 dmi.bios.vendor: HP dmi.bios.version: N82 Ver. 01.19 dmi.board.name: 80D4 dmi.board.vendor: HP dmi.board.version: KBC Version 11.6F dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN82Ver.01.19:bd09/26/2017:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ZBook Studio G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742474] Re: Bad return status for module build on kernel: 4.13.0-26-generic (i686)
Same issue with 4.15-rc7. I am using UKUU. https://imgur.com/5FdbORs https://imgur.com/WEB83ZH -- System:Host: Asus-1000HE Kernel: 4.10.0-42-generic i686 (32 bit gcc: 5.4.0) Console: tty 5 Distro: Linux Mint 18.3 Sylvia Machine: System: ASUSTeK (portable) product: 1000HE v: x.x Mobo: ASUSTeK model: 1000HE v: x.xx Bios: American Megatrends v: 1104 date: 10/14/2009 CPU: Single core Intel Atom N270 (-HT-) cache: 512 KB flags: (nx pae sse sse2 sse3 ssse3) bmips: 3192 clock speeds: max: 1600 MHz 1: 1333 MHz 2: 800 MHz Graphics: Card: Intel Mobile 945GSE Express Integrated Graphics Controller bus-ID: 00:02.0 Display Server: N/A drivers: intel (unloaded: fbdev,vesa) tty size: 80x24 Advanced Data: N/A out of X Audio: Card Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: Advanced Linux Sound Architecture v: k4.10.0-42-generic Network: Card-1: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) driver: ath9k bus-ID: 01:00.0 IF: wlp1s0 state: up mac: 00:15:af:e0:3e:ed Card-2: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet driver: ATL1E port: ec00 bus-ID: 03:00.0 IF: enp3s0 state: down mac: 00:24:8c:29:5e:49 Drives:HDD Total Size: 128.0GB (6.2% used) ID-1: /dev/sda model: SanDisk_SD6SB1M1 size: 128.0GB Partition: ID-1: / size: 47G used: 7.5G (17%) fs: ext4 dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 50.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 195 Uptime: 1 min Memory: 281.4/2004.7MB Init: systemd runlevel: 5 Gcc sys: 5.4.0 Client: Shell (bash 4.3.481) inxi: 2.2.35 ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742474 Title: Bad return status for module build on kernel: 4.13.0-26-generic (i686) Status in linux package in Ubuntu: Confirmed Bug description: Distributor ID: LinuxMint Description: Linux Mint 18.3 Sylvia Release: 18.3 Codename: sylvia Linux Asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux Linux Mint 18.3 with HWE Kernel (sudo apt install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04) I've upgraded linux kernel from 4.10.0-4.10.0-42.46~16.04.1 to 4.13.0-26.29~16.04.2. I've got errors while upgrade kernel. And, After rebooting, my linux login screen has been broken. I cannot log in and my linux screen has gone black. Restroing kernel 4.10, then works well. run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-26-generic /boot/vmlinuz-4.13.0-26-generic Error! Bad return status for module build on kernel: 4.13.0-26-generic (i686) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. Belows are /var/lib/dkms/ndiswrapper/1.60/build/make.log. DKMS make.log for ndiswrapper-1.60 for kernel 4.13.0-26-generic (i686) 2018. 01. 11. (목) 00:16:20 KST make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 들어감 AR /var/lib/dkms/ndiswrapper/1.60/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o In file included from /var/lib/dkms/ndiswrapper/1.60/build/ndis.h:19:0, from /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:16: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMAllocateSharedMemory’: /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: error: ‘__GFP_REPEAT’ undeclared (first use in this function) GFP_KERNEL | __GFP_REPEAT) ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of macro ‘PCI_DMA_ALLOC_COHERENT’ *virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, &dma_addr); ^ /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: note: each undeclared identifier is reported only once for each function it appears in
[Kernel-packages] [Bug 1742474] Re: Bad return status for module build on kernel: 4.13.0-26-generic (i686)
There was no ndiswrapper error with 4.15-rc7 kernel. But, the problem was same. Same broken screen showed me like Imgur images. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742474 Title: Bad return status for module build on kernel: 4.13.0-26-generic (i686) Status in linux package in Ubuntu: Confirmed Bug description: Distributor ID: LinuxMint Description: Linux Mint 18.3 Sylvia Release: 18.3 Codename: sylvia Linux Asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux Linux Mint 18.3 with HWE Kernel (sudo apt install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04) I've upgraded linux kernel from 4.10.0-4.10.0-42.46~16.04.1 to 4.13.0-26.29~16.04.2. I've got errors while upgrade kernel. And, After rebooting, my linux login screen has been broken. I cannot log in and my linux screen has gone black. Restroing kernel 4.10, then works well. run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-26-generic /boot/vmlinuz-4.13.0-26-generic Error! Bad return status for module build on kernel: 4.13.0-26-generic (i686) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. Belows are /var/lib/dkms/ndiswrapper/1.60/build/make.log. DKMS make.log for ndiswrapper-1.60 for kernel 4.13.0-26-generic (i686) 2018. 01. 11. (목) 00:16:20 KST make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 들어감 AR /var/lib/dkms/ndiswrapper/1.60/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o In file included from /var/lib/dkms/ndiswrapper/1.60/build/ndis.h:19:0, from /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:16: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMAllocateSharedMemory’: /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: error: ‘__GFP_REPEAT’ undeclared (first use in this function) GFP_KERNEL | __GFP_REPEAT) ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of macro ‘PCI_DMA_ALLOC_COHERENT’ *virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, &dma_addr); ^ /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: note: each undeclared identifier is reported only once for each function it appears in GFP_KERNEL | __GFP_REPEAT) ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of macro ‘PCI_DMA_ALLOC_COHERENT’ *virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, &dma_addr); ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMIndicateReceivePacket’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2261:15: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘EthRxIndicateHandler’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2349:14: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMTransferDataComplete’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2464:14: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ scripts/Makefile.build:308: '/var/lib/dkms/ndiswrapper/1.60/build/ndis.o' 타겟에 대한 명령이 실패했습니다 make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/ndis.o] 오류 1 Makefile:1550: '_module_/var/lib/dkms/ndiswrapper/1.60/build' 타겟에 대한 명령이 실패했습니다 make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] 오류 2 make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 나감 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741946] Re: no wifi kernel - regression 4.13.0-24 in lenovo yoga
Thanks, Peter manuel fernandez, can you try to update your kernel and install the bcmwl-kernel-source package? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741946 Title: no wifi kernel - regression 4.13.0-24 in lenovo yoga Status in linux package in Ubuntu: Incomplete Bug description: 4.13.0-24-generic does not have a network connection However, Linux bix 4.13.0-22-generic #25-Ubuntu SMP Tue Dec 19 11:13:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux and previous kernels work fine description: Notebook product: 80HE (LENOVO_MT_80HE_BU_idea_FM_Lenovo YOGA 3 Pro-1370) vendor: LENOVO version: Lenovo YOGA 3 Pro-1370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741946/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
I tested with the mainline kernel4.15rc7, problem still not fixed, still can't boot into desktop. I tried reinstalling the Nvidia driver in kernel 4.10 but build for 4.15 has error, I did it with synaptic and the window closed too soon for me to catch the error message. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in linux package in Ubuntu: Incomplete Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. 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/1742302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Okay, I tested it with 4.15.0-041500rc7-generic and the issue disappeared. Thanks! Does that provide any insight into what exactly the error is and/or a possible workaround? Unfortunately I'm unable to use this kernel in the interim as I rely on the Nvidia kernel modules, which aren't compiling in DKMS. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730544] Re: AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC
** Changed in: linux (Ubuntu) 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/1730544 Title: AQUANTIA AQC107 10G[1D6A:0001] & 2.5/5Gb [1D6A:D108] NIC Status in HWE Next: Triaged Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: New Status in linux-oem source package in Xenial: Fix Released Bug description: From vendor's suggestion, there are some patches in v4.14-rc6 are required to enable the 2 NICs 417a3ae net: aquantia: Bad udp rate on default interrupt coalescing b82ee71 net: aquantia: Enable coalescing management via ethtool interface 6849540 net: aquantia: mmio unmap was not performed on driver removal 4c8bb60 net: aquantia: Limit number of MSIX irqs to the number of cpus 93d87b8 net: aquantia: Fixed transient link up/down/up notification 5d8d84e net: aquantia: Add queue restarts stats counter 65e665e net: aquantia: Reset nic statistics on interface up/down And to avoid conflict, cherry pick 2 more commits 3aec641 aquantia: Fix Tx queue hangups 65e665e net: aquantia: Reset nic statistics on interface up/down To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1730544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727228] Re: ath9k can't connect to wifi AP
** Patch added: "0001-ath9k-add-MSI-support.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727228/+attachment/5034864/+files/0001-ath9k-add-MSI-support.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/1727228 Title: ath9k can't connect to wifi AP Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: iwlist scan can search the available wifi APs, but can't get connected. On new Intel platforms like ApolloLake, legacy interrupt mechanism (INTx) is not supported, so WLAN modules are not working because interrupts are missing. The affected and listed platforms are Dell Inspiron 24-3460 Dell Inspiron 14-3473 Dell Inspiron 3472 Dell Inspiron 3576 Dell Vostro 3262 Dell Vostro 15-3572 Dell Vostro 3578 There should not be any regression potential. These are newly enabled machines and quirks are applied based on DMI_PRODUCT_NAME to only use MSI on such machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1727228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727228] Re: ath9k can't connect to wifi AP
The patches are in git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git pending ** Patch added: "0002-ath9k-add-a-quirk-to-set-use_msi-automatically.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727228/+attachment/5034865/+files/0002-ath9k-add-a-quirk-to-set-use_msi-automatically.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/1727228 Title: ath9k can't connect to wifi AP Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: iwlist scan can search the available wifi APs, but can't get connected. On new Intel platforms like ApolloLake, legacy interrupt mechanism (INTx) is not supported, so WLAN modules are not working because interrupts are missing. The affected and listed platforms are Dell Inspiron 24-3460 Dell Inspiron 14-3473 Dell Inspiron 3472 Dell Inspiron 3576 Dell Vostro 3262 Dell Vostro 15-3572 Dell Vostro 3578 There should not be any regression potential. These are newly enabled machines and quirks are applied based on DMI_PRODUCT_NAME to only use MSI on such machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1727228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
This bug is also occurring for me when installing nvidia-387 off Nvidia's 16.04 repository when using 4.13.0-26-generic. Attached is /var/lib/dkms/nvidia-387/387.26/build/make.log. ** Attachment added: "make.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+attachment/5034844/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in linux package in Ubuntu: Incomplete Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. 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/1742302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
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-rc7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-key pti -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://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 1692538] Re: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA
Hi Frank, Yes, that is how I see it - these changes can go through, but we need good docs to point people to as there is an incredibly high likelihood of misconfiguration at various points. Regards, Daniel On Tue, Dec 19, 2017 at 3:46 AM, Frank Heimes <1692...@bugs.launchpad.net> wrote: > Siva and Daniel, may I just ask where we are on this? > Well it looks to me that Siva/IBM sees this more as a miss-configuration, so > that the changes in comment #18 are _not_ needed. Daniel, do you see it now > the same way? > But in this case this needs to be documented somewhere, so that we can point > customers, too it - right? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1692538 > > Title: > Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA > > Status in The Ubuntu-power-systems project: > In Progress > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Xenial: > In Progress > Status in linux source package in Zesty: > Fix Released > Status in linux source package in Artful: > Fix Released > > Bug description: > > == SRU Justification == > Commit 66aa0678ef is request to fix four issues with the ibmveth driver. > The issues are as follows: > - Issue 1: ibmveth doesn't support largesend and checksum offload features > when configured as "Trunk". > - Issue 2: SYN packet drops seen at destination VM. When the packet > originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to IO > server's inbound Trunk ibmveth, on validating "checksum good" bits in > ibmveth > receive routine, SKB's ip_summed field is set with CHECKSUM_UNNECESSARY > flag. > - Issue 3: First packet of a TCP connection will be dropped, if there is > no OVS flow cached in datapath. > - Issue 4: ibmveth driver doesn't have support for SKB's with frag_list. > > The details for the fixes to these issues are described in the commits > git log. > > > > == Comment: #0 - BRYANT G. LY - 2017-05-22 08:40:16 == > ---Problem Description--- > >- Issue 1: ibmveth doesn't support largesend and checksum offload features > when configured as "Trunk". Driver has explicit checks to prevent > enabling these offloads. > >- Issue 2: SYN packet drops seen at destination VM. When the packet > originates, it has CHECKSUM_PARTIAL flag set and as it gets delivered to > IO server's inbound Trunk ibmveth, on validating "checksum good" bits > in ibmveth receive routine, SKB's ip_summed field is set with > CHECKSUM_UNNECESSARY flag. This packet is then bridged by OVS (or Linux > Bridge) and delivered to outbound Trunk ibmveth. At this point the > outbound ibmveth transmit routine will not set "no checksum" and > "checksum good" bits in transmit buffer descriptor, as it does so only > when the ip_summed field is CHECKSUM_PARTIAL. When this packet gets > delivered to destination VM, TCP layer receives the packet with checksum > value of 0 and with no checksum related flags in ip_summed field. This > leads to packet drops. So, TCP connections never goes through fine. > >- Issue 3: First packet of a TCP connection will be dropped, if there is > no OVS flow cached in datapath. OVS while trying to identify the flow, > computes the checksum. The computed checksum will be invalid at the > receiving end, as ibmveth transmit routine zeroes out the pseudo > checksum value in the packet. This leads to packet drop. > >- Issue 4: ibmveth driver doesn't have support for SKB's with frag_list. > When Physical NIC has GRO enabled and when OVS bridges these packets, > OVS vport send code will end up calling dev_queue_xmit, which in turn > calls validate_xmit_skb. > In validate_xmit_skb routine, the larger packets will get segmented into > MSS sized segments, if SKB has a frag_list and if the driver to which > they are delivered to doesn't support NETIF_F_FRAGLIST feature. > > Contact Information = Bryant G. Ly/b...@us.ibm.com > > ---uname output--- > 4.8.0-51.54 > > Machine Type = p8 > > ---Debugger--- > A debugger is not configured > > ---Steps to Reproduce--- >Increases performance greatly > > The patch has been accepted upstream: > https://patchwork.ozlabs.org/patch/764533/ > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu-power-systems/+bug/1692538/+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/1692538 Title: Ubuntu 16.04.02: ibmveth: Support to enable LSO/CSO for Trunk VEA Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Fix Released St
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe (Ubuntu Artful) 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/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: Confirmed Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: Confirmed Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 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 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe (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/1733662 Title: System hang with Linux kernel 4.13, not with 4.10 Status in linux package in Ubuntu: In Progress Status in linux-hwe package in Ubuntu: Confirmed Status in linux source package in Artful: In Progress Status in linux-hwe source package in Artful: Confirmed Status in linux source package in Bionic: In Progress Status in linux-hwe source package in Bionic: Confirmed Bug description: In doing Ubuntu 17.10 regression testing, we've encountered one computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in four times when running our cpu_offlining test. This test attempts to take all the CPU cores offline except one, then brings them back online again. This test ran successfully on boldore with previous releases, but with 17.10, the system sometimes (about one in four runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but when I upgraded the 16.04.3 installation to linux- image-4.13.0-16-generic, the problem appeared again, so I'm confident this is a problem with the kernel. I'm attaching two files, dmesg- output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output that appears when running the cpu_offlining test with 4.10.0-38 and 4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I was running "dmesg -w" in a second SSH login; the files are cut-and- pasted from that.) I initiated this bug report from an Ubuntu 16.04.3 installation running a 4.10 kernel; but as I said, this applies to the 4.13 kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: User Name 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 Date: Tue Nov 21 17:36:06 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742576] Re: Update inte-microcodes with fixes for spectre
*** This bug is a duplicate of bug 1742364 *** https://bugs.launchpad.net/bugs/1742364 ** This bug has been marked a duplicate of bug 1742364 Updated microcode for Spectre fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1742576 Title: Update inte-microcodes with fixes for spectre Status in linux-firmware package in Ubuntu: New Bug description: Debian already included new microcodes inside new version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886367 They've been released at https://downloadcenter.intel.com/download/27431/Linux-Processor- Microcode-Data-File?product=122139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1742576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 995743] Re: 197b:2394 [Dell XPS 17 L502X] Internal SD card reader is not working
dmesg on inserting card [Thu Jan 11 13:18:28 2018] mmc0: Timeout waiting for hardware interrupt. [Thu Jan 11 13:18:28 2018] mmc0: sdhci: SDHCI REGISTER DUMP === [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Sys addr: 0x | Version: 0x1502 [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Blk size: 0x7008 | Blk cnt: 0x0001 [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Argument: 0x | Trn mode: 0x0013 [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Present: 0x1fff0202 | Host ctl: 0x0019 [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Power: 0x000f | Blk gap: 0x [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Wake-up: 0x | Clock: 0xfa07 [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Timeout: 0x000a | Int stat: 0x [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b [Thu Jan 11 13:18:28 2018] mmc0: sdhci: AC12 err: 0x | Slot int: 0x [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Caps: 0x176ec8b0 | Caps_1: 0x03002177 [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Cmd: 0x333a | Max curr: 0x [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Resp[0]: 0x0920 | Resp[1]: 0x [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Resp[2]: 0x | Resp[3]: 0x [Thu Jan 11 13:18:28 2018] mmc0: sdhci: Host ctl2: 0x0008 [Thu Jan 11 13:18:28 2018] mmc0: sdhci: ADMA Err: 0x0001 | ADMA Ptr: 0x000432665200 [Thu Jan 11 13:18:28 2018] mmc0: sdhci: [Thu Jan 11 13:18:28 2018] mmc0: error -110 whilst initialising SD card [Thu Jan 11 13:18:34 2018] mmc0: Skipping voltage switch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/995743 Title: 197b:2394 [Dell XPS 17 L502X] Internal SD card reader is not working Status in linux package in Ubuntu: Invalid Bug description: If I start up the computer with no SD card in the reader, it will not recognise SD cards inserted. WORKAROUND: If you start up the computer with an SD card inserted, all is good. WORKAROUND: The following rescan will find the SD card. sudo su -l echo 1 > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic 3.2.0-24.37 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC665 Analog [ALC665 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lee 20624 F pulseaudio CRDA: country AU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (3, 23) (5250 - 5330 @ 40), (3, 23), DFS (5735 - 5835 @ 40), (3, 30) Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf3c0 irq 55' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0665,10280571,0013 HDA:80862805,80860101,0010' Controls : 31 Simple ctrls : 13 Date: Mon May 7 13:52:09 2012 HibernationDevice: RESUME=UUID=131e7674-2f9b-4de3-b917-8d79a5a64e28 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. Dell System XPS L702X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=157174fa-f17e-471d-9008-353e4499b5f8 ro RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic N/A linux-backports-modules-3.2.0-24-generic N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: Upgraded to precise on 2012-04-29 (7 days ago) dmi.bios.date: 01/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0XN71K dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd01/10/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L702X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 995743] Re: 197b:2394 [Dell XPS 17 L502X] Internal SD card reader is not working
This is effecting me (or something similar) on: ~$ cat /etc/issue Ubuntu Bionic Beaver (development branch) But # echo 1 > /sys/bus/pci/rescan has no effect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/995743 Title: 197b:2394 [Dell XPS 17 L502X] Internal SD card reader is not working Status in linux package in Ubuntu: Invalid Bug description: If I start up the computer with no SD card in the reader, it will not recognise SD cards inserted. WORKAROUND: If you start up the computer with an SD card inserted, all is good. WORKAROUND: The following rescan will find the SD card. sudo su -l echo 1 > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-24-generic 3.2.0-24.37 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC665 Analog [ALC665 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lee 20624 F pulseaudio CRDA: country AU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (3, 23) (5250 - 5330 @ 40), (3, 23), DFS (5735 - 5835 @ 40), (3, 30) Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf3c0 irq 55' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:10ec0665,10280571,0013 HDA:80862805,80860101,0010' Controls : 31 Simple ctrls : 13 Date: Mon May 7 13:52:09 2012 HibernationDevice: RESUME=UUID=131e7674-2f9b-4de3-b917-8d79a5a64e28 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Dell Inc. Dell System XPS L702X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=157174fa-f17e-471d-9008-353e4499b5f8 ro RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic N/A linux-backports-modules-3.2.0-24-generic N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: Upgraded to precise on 2012-04-29 (7 days ago) dmi.bios.date: 01/10/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0XN71K dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd01/10/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L702X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742576] [NEW] Update inte-microcodes with fixes for spectre
*** This bug is a security vulnerability *** Public security bug reported: Debian already included new microcodes inside new version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886367 They've been released at https://downloadcenter.intel.com/download/27431 /Linux-Processor-Microcode-Data-File?product=122139 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1742576 Title: Update inte-microcodes with fixes for spectre Status in linux-firmware package in Ubuntu: New Bug description: Debian already included new microcodes inside new version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886367 They've been released at https://downloadcenter.intel.com/download/27431/Linux-Processor- Microcode-Data-File?product=122139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1742576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742572] 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/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: Confirmed Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741934] Re: Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix)
Kernel 4.4.0-10--generic fixed the problem also on Dell Inspiron i5-5000 Processor Intel i7-7500U 2.7Ghz 8 Mb RAM. Thank you very much for the quick response. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741934 Title: Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI fix) Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: ### HOW TO BOOT INTO PREVIOUS KERNEL IF UNABLE TO BOOT ### If you hit this bug and are unable to boot, you can boot back into the last working kernel. To do that, select that version(Probably 4.4.0-104) from the GRUB menu. The GRUB menu can be accessed by holding the 'Shift' key after powering on the system(Some systems require the 'ESC' key to be held instead of Shift). Detailed information about GRUB can be found here: https://help.ubuntu.com/community/Grub2 [Description] When using PPA https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/pti/ to fetch the candidate kernels for CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same kernel trace shown in many different pre-installed Ubuntu images of different platform. So far these platform are known to reproduce this issue: CID 201606-22340 (Dell Vostro 5468) CID 201606-22349 (Dell Inspiron 7560) CID 201606-22365 (Dell Inspiron 5767) [Steps to Reproduce] 1. Install the target pre-installed image (Xenial 4.4-based stack) for the platform. 2. Fetch the kernel 4.4.0-108.131 from this PPA https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/ 3. Update the system by "sudo apt-get dist-upgrade" 4. After the system update, reboot it. 5. Check the syslog after the system is ready to use again. [Expected Result] No kernel trace message. [Actual Result] Kernel trace message as: Jan 9 00:33:33 201606-22365 kernel: [ 37.701226] [ cut here ] Jan 9 00:33:33 201606-22365 kernel: [ 37.701243] kernel BUG at /build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627! Jan 9 00:33:33 201606-22365 kernel: [ 37.701261] invalid opcode: [#1] SMP Jan 9 00:33:33 201606-22365 kernel: [ 37.701273] Modules linked in: nvram msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Jan 9 00:33:33 201606-22365 kernel: [ 37.701735] CPU: 3 PID: 21 Comm: watchdog/3 Tainted: G OE 4.4.0-108-generic #131-Ubuntu Jan 9 00:33:33 201606-22365 kernel: [ 37.701756] Hardware name: Dell Inc. Inspiron 5767/ , BIOS 1.0.0 07/14/2016 Jan 9 00:33:33 201606-22365 kernel: [ 37.701774] task: 880169df6900 ti: 880169a1c000 task.ti: 880169a1c000 Jan 9 00:33:33 201606-22365 kernel: [ 37.701792] RIP: 0010:[] [] kfree+0x147/0x150 Jan 9 00:33:33 201606-22365 kernel: [ 37.701814] RSP: 0018:880169a1fd58 EFLAGS: 00010246 Jan 9 00:33:33 201606-22365 kernel: [ 37.701827] RAX: ea0005bd0120 RBX: 88016f404840 RCX: 88016f7fa220 Jan 9 00:33:33 201606-22365 kernel: [ 37.701843] RDX: ea0005a64420 RSI: ea0005a64820 RDI: ea0005bd0100 Jan 9 00:33:33 201606-22365 kernel: [ 37.701860] RBP: 880169a1fd70 R08: 0009 R09: ff80003f Jan 9 00:33:33 201606-22365 kernel: [ 37.701877] R10: ea0005bd0100 R11: 0001 R12: 0
[Kernel-packages] [Bug 1742572] Re: System Hangs and General Protection Fault Occurs following NFS Access
Please note that I ran 'ubuntu-bug' from my most recent working kernel (from Zesty): 4.10.0-42-generic, so some of this log output may be inaccurate as a result. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742572 Title: System Hangs and General Protection Fault Occurs following NFS Access Status in linux package in Ubuntu: New Bug description: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742572] [NEW] System Hangs and General Protection Fault Occurs following NFS Access
Public bug reported: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. Attached is the console log (obtained via netconsole) which includes the kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: mvastola 4661 F pulseaudio /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IwConfig: lono wireless extensions. mike no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic root=/dev/mapper/VastDesk-RootOS ro apparmor=0 netconsole=@10.12.1.55/mike,@10.12.1.1/8c:ae:4c:f4:83:1a crashkernel=384M-:128M crashkernel=384M-:128M RelatedPackageVersions: linux-restricted-modules-4.10.0-42-generic N/A linux-backports-modules-4.10.0-42-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2014-12-03 (1134 days ago) dmi.bios.date: 09/09/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14e dmi.board.name: GA-990XA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14e:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-990XA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990XA-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990XA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1742572/+attachment/5034766/+files/dmesg.log ** Description changed: Last night, in an attempt to secure my system against Meltdown/Spectre, I upgraded from Zesty to Artful. Upon booting into the latest kernel, my system would immediately hang and fail to respond (including to SysRq commands). Both this (my primary) system and an Intel NUC (which were both upgraded from Zesty to Artful at the same time) export NFS shares to one other. The NUC appears to be error-free, but my primary system seems to crash whenever I attempt to access the NFS share of NUC. As I have not tried any other kernel releases in either system other than 4.13.0-25.29, it's impossible for me to say if this is an issue regarding the recent security patch, or if it is some other issue. - Attached is the console log (obtained via netconsole), lspci (with - -vnvn), and the output from lsb_release -a. + Attached is the console log (obtained via netconsole) which includes the + kernel trace of the error. Please let me know if further information is required or if I can help further in troubleshooting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: mvastola 4661 F pulseaudio - /dev/snd/controlC1: mvastola 4661 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: mvastola 4661 F pulseaudio + /dev/snd/controlC1: mvastola 4661 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 18:18:52 2018 InstallationDate: Installed on 2012-01-06 (2196 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
[Kernel-packages] [Bug 1697450] Re: Whole machine freezes at startup using kernels after 4.8
No, everything is frozen, if I ssh in the machine before starting the session, ssh is frozen too -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697450 Title: Whole machine freezes at startup using kernels after 4.8 Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to install from the daily Artful desktop image (20170612). After boot, the gnome session hangs at startup, while the "zoom" animation is being shown. I have an intel card: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f780 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915 I'm not sure how to debug this further, but I had similar issues with the installer from Zesty as well (see https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846) With Artful, at least it gets past the splash screen but then it hangs. Note that the system is currently running Yakkety with no issue. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-07-30 (71 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Tags: artful wayland-session Uname: Linux 4.8.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: corrupted BIOS due to Intel SPI bug in kernel
#519 no, I did not compile the kernel yet. So far only used the one provided in the fix description. As for repairing -like with the fix kernel- this won't help, right? It would just be an option to go away from the repository kernels and compile my own one until the commit is included in the repository 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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: 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!! To manage notifications about this bug go to: https://bugs.launchpad.net/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 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
I am also having this issue. Won't start working unless I shut computer off and on. So frustrating. My version is 5.37-0ubuntu5.1. I'm using 16.04 on a new Dell XPS13. -- 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/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742418] Re: Stuck attempting to acess "/proc/sys/kernel/nmi_watchdog" file
*** This bug is a duplicate of bug 1741934 *** https://bugs.launchpad.net/bugs/1741934 ** This bug has been marked a duplicate of bug 1741934 Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI 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/1742418 Title: Stuck attempting to acess "/proc/sys/kernel/nmi_watchdog" file Status in linux package in Ubuntu: Incomplete Bug description: I has always been able to both read and write "/proc/sys/kernel/nmi_watchdog" file. After the recent kernel update (4.4.0-108-generic, updated on 10-Jan-2018) the computer merely gets stuck on these commands. Ctrl-C cannot interrupt. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-108-generic 4.4.0-108.131 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-108-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/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' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Wed Jan 10 12:30:37 2018 HibernationDevice: RESUME=UUID=a0f49bd7-5ec0-414e-8183-41221652c849 InstallationDate: Installed on 2016-08-17 (510 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 003: ID 04b4:6570 Cypress Semiconductor Corp. Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: CompuLab Ltd. SBC-iBT ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed root=UUID=1ee7c5d5-a843-43d4-a90d-0c484d09d041 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-108-generic N/A linux-backports-modules-4.4.0-108-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: CompuLab Ltd. dmi.bios.version: SBC-iBT_3.1.0.314 X64 dmi.board.asset.tag: None dmi.board.name: SBC-iBT dmi.board.vendor: CompuLab Ltd. dmi.board.version: 1.x dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 11 dmi.chassis.vendor: CompuLab Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnCompuLabLtd.:bvrSBC-iBT_3.1.0.314X64:bd02/24/2015:svnCompuLabLtd.:pnSBC-iBT:pvr1.x:rvnCompuLabLtd.:rnSBC-iBT:rvr1.x:cvnCompuLabLtd.:ct11:cvr1.0: dmi.product.name: SBC-iBT dmi.product.version: 1.x dmi.sys.vendor: CompuLab Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742418/+subscriptions -- Mailing list: https://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 1742418] Re: Stuck attempting to acess "/proc/sys/kernel/nmi_watchdog" file
Hi ! Indeed this fixes the issue: -- # cat /proc/sys/kernel/nmi_watchdog 0 -- Thank you ! Andrey Gelman On Wed, Jan 10, 2018 at 11:15 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > This may be a duplicate of bug 1741934, which was fixed by the 4.4.0-109 > kernel. Can you upgrade to 4.4.0-109 and see if this bug still exists? > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > ** Tags added: pti > > ** Changed in: linux (Ubuntu) > Assignee: (unassigned) => Joseph Salisbury (jsalisbury) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1742418 > > Title: > Stuck attempting to acess "/proc/sys/kernel/nmi_watchdog" file > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I has always been able to both read and write > "/proc/sys/kernel/nmi_watchdog" > file. > After the recent kernel update (4.4.0-108-generic, updated on > 10-Jan-2018) the computer merely gets stuck on these commands. Ctrl-C > cannot interrupt. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-108-generic 4.4.0-108.131 > ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 > Uname: Linux 4.4.0-108-generic x86_64 > AlsaVersion: Advanced Linux Sound Architecture Driver Version > k4.4.0-108-generic. > AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', > '/dev/snd/pcmC0D0c', '/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' > Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' > Date: Wed Jan 10 12:30:37 2018 > HibernationDevice: RESUME=UUID=a0f49bd7-5ec0-414e-8183-41221652c849 > InstallationDate: Installed on 2016-08-17 (510 days ago) > InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release > amd64 (20160719) > IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' > Lsusb: >Bus 001 Device 003: ID 04b4:6570 Cypress Semiconductor Corp. >Bus 001 Device 002: ID 8087:07e6 Intel Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: CompuLab Ltd. SBC-iBT > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed > root=UUID=1ee7c5d5-a843-43d4-a90d-0c484d09d041 ro > RelatedPackageVersions: >linux-restricted-modules-4.4.0-108-generic N/A >linux-backports-modules-4.4.0-108-generic N/A >linux-firmware 1.157.14 > RfKill: Error: [Errno 2] No such file or directory: 'rfkill' > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 02/24/2015 > dmi.bios.vendor: CompuLab Ltd. > dmi.bios.version: SBC-iBT_3.1.0.314 X64 > dmi.board.asset.tag: None > dmi.board.name: SBC-iBT > dmi.board.vendor: CompuLab Ltd. > dmi.board.version: 1.x > dmi.chassis.asset.tag: Asset Tag > dmi.chassis.type: 11 > dmi.chassis.vendor: CompuLab Ltd. > dmi.chassis.version: 1.0 > dmi.modalias: dmi:bvnCompuLabLtd.:bvrSBC-iBT_3.1.0.314X64:bd02/24/2015: > svnCompuLabLtd.:pnSBC-iBT:pvr1.x:rvnCompuLabLtd.:rnSBC- > iBT:rvr1.x:cvnCompuLabLtd.:ct11:cvr1.0: > dmi.product.name: SBC-iBT > dmi.product.version: 1.x > dmi.sys.vendor: CompuLab Ltd. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1742418/+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/1742418 Title: Stuck attempting to acess "/proc/sys/kernel/nmi_watchdog" file Status in linux package in Ubuntu: Incomplete Bug description: I has always been able to both read and write "/proc/sys/kernel/nmi_watchdog" file. After the recent kernel update (4.4.0-108-generic, updated on 10-Jan-2018) the computer merely gets stuck on these commands. Ctrl-C cannot interrupt. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-108-generic 4.4.0-108.131 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-108-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
[Kernel-packages] [Bug 1742560] [NEW] zfsutils-linux recommends dkms when it's not needed
Public bug reported: 1. $ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 2. $ apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.6.5.6-0ubuntu18 Candidate: 0.6.5.6-0ubuntu18 Version table: *** 0.6.5.6-0ubuntu18 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.6.5.6-0ubuntu8 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 3. apt install zfsutils-linux does not install dkms,spl-dkms and dependencies since 16.04 kernel already contains zfs.ko 4. apt install zfsutils-linux installs all of the following: dkms fakeroot gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libfakeroot libfreetype6 libgcc-5-dev libgomp1 libitm1 liblsan0 libmpx0 libquadmath0 libtsan0 libubsan0 linux-libc-dev manpages-dev spl spl-dkms and then any kernel install/update then attempts to dkms rebuild zfs and spl even though the modules are already provided. % dpkg -S /lib/modules/4.13.0-19-generic/kernel/zfs/zfs/zfs.ko linux-image-4.13.0-19-generic: /lib/modules/4.13.0-19-generic/kernel/zfs/zfs/zfs.ko % dpkg -S /lib/modules/4.13.0-19-generic/kernel/zfs/spl/spl.ko linux-image-4.13.0-19-generic: /lib/modules/4.13.0-19-generic/kernel/zfs/spl/spl.ko We can see from the package requirements, that it Recommends zfs-dkms, but only on Xenial. Releases newer than Xenial do not have this package requirement. % apt-cache show zfsutils-linux Package: zfsutils-linux Architecture: amd64 Version: 0.6.5.6-0ubuntu18 Priority: extra Section: admin Source: zfs-linux Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Darik Horn Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 779 Provides: zfs Depends: init-system-helpers (>= 1.18~), zfs-doc (= 0.6.5.6-0ubuntu18), libblkid1 (>= 2.16), libc6 (>= 2.14), libnvpair1linux, libuuid1 (>= 2.16), libuutil1linux, libzfs2linux, libzpool2linux, python3:any (>= 3.3.2-2~), python3 Recommends: zfs-dkms, zfs-zed Suggests: samba-common-bin (>= 3.0.23), nfs-kernel-server, zfs-initramfs Conflicts: zfs, zfs-fuse Replaces: zfs Filename: pool/main/z/zfs-linux/zfsutils-linux_0.6.5.6-0ubuntu18_amd64.deb Size: 275970 MD5sum: 02ead25f1fed812980d70865da916468 SHA1: e6736c223c3b2198bba8777153836bb8d4789518 SHA256: c4ad2b81ee13072cb3f4e31fd3aed93cf66c7c50872fc542cc2425120b222eed Homepage: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.5.6 Description-en: Native OpenZFS management utilities for Linux This package provides the zpool and zfs commands that are used to manage OpenZFS filesystems. Description-md5: 7b0f98269f6c33505790717cd478736c Supported: 5y Here's Artful ~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 $ apt-cache show zfsutils-linux Package: zfsutils-linux Architecture: amd64 Version: 0.6.5.11-1ubuntu3 Priority: extra Section: admin Source: zfs-linux Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian ZFS on Linux maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1100 Provides: zfsutils Depends: init-system-helpers (>= 1.18~), libblkid1 (>= 2.16), libc6 (>= 2.14), libnvpair1linux, libuuid1 (>= 2.16), libuutil1linux, libzfs2linux, libzpool2linux, python3:any, python3 Recommends: lsb-base, zfs-zed Suggests: nfs-kernel-server, samba-common-bin (>= 3.0.23), zfs-initramfs | zfs-dracut Conflicts: zfs, zfs-fuse, zutils Filename: pool/main/z/zfs-linux/zfsutils-linux_0.6.5.11-1ubuntu3_amd64.deb Size: 328574 MD5sum: d1ce7f5ffa75c9b46e7d5285430efff3 SHA1: 8a8ab05186b83c3f25e07d4e8fe04e60ec314640 SHA256: c462a555dda50ed12424a51158666bd3cbe1befb93a34ac81f03548051fa0b50 Homepage: http://www.zfsonlinux.org/ Description-en: command-line tools to manage OpenZFS filesystems The Z file system is a pooled filesystem designed for maximum data integrity, supporting data snapshots, multiple copies, and data checksums. . This package provides the zfs and zpool commands to create and administer OpenZFS filesystems. Description-md5: 3b2c00b92882937cb7252c01e41d8975 Supported: 9m ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu18 ProcVersionSignature: User Name 4.13.0-19.22~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Jan 10 22:26:33 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [deleted] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug curtin uec-images xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1742560 Title: zfsutils-linux recommends dkms
[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working
Unfortunatly the same problem: [6.201796] [ cut here ] [6.201799] kernel BUG at /home/kernel/COD/linux/drivers/media/common/saa7146/saa7146_core.c:163! [6.201812] invalid opcode: [#1] SMP [6.201814] Modules linked in: snd_hda_codec_generic snd_hda_intel budget_av(+) snd_hda_codec saa7146_vv snd_hda_core budget_core ttpci_eeprom snd_hwdep saa7146 snd_pcm intel_powerclamp videobuf_dma_sg videobuf_core dvb_core v4l2_common snd_timer videodev snd input_leds joydev lpc_ich media soundcore shpchp mac_hid nct6775 hwmon_vid coretemp ip_tables x_tables autofs4 uas usb_storage hid_generic usbhid hid gma500_gfx i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt r8169 fb_sys_fops ahci drm libahci mii video [6.201882] CPU: 3 PID: 293 Comm: systemd-udevd Not tainted 4.15.0-041500rc7-generic #201801072330 [6.201884] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./AD2700-ITX, BIOS P1.60 04/19/2013 [6.201895] EIP: saa7146_vmalloc_build_pgtable+0x140/0x1020 [saa7146] [6.201897] EFLAGS: 00010246 CPU: 3 [6.201900] EAX: f24b8908 EBX: f478b800 ECX: 0002 EDX: fff1c000 [6.201903] ESI: EDI: f864a000 EBP: f4b65c44 ESP: f4b65c24 [6.201906] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [6.201910] CR0: 80050033 CR2: 00587024 CR3: 310b72a0 CR4: 06f0 [6.201912] Call Trace: [6.201925] ttpci_budget_init+0x26c/0x530 [budget_core] [6.201935] ? budget_av_attach+0x3e/0x4e8 [budget_av] [6.201944] budget_av_attach+0x75/0x4e8 [budget_av] [6.201954] ? vprintk_func+0x29/0x70 [6.201959] ? printk+0x13/0x15 [6.201965] ? saa7146_init_one+0x69f/0x770 [saa7146] [6.201971] saa7146_init_one+0x70b/0x770 [saa7146] [6.201979] ? __pm_runtime_resume+0x51/0x80 [6.201985] pci_device_probe+0xc2/0x160 [6.201991] driver_probe_device+0x2d9/0x450 [6.201996] __driver_attach+0x99/0xe0 [6.202000] ? driver_probe_device+0x450/0x450 [6.202005] bus_for_each_dev+0x57/0x90 [6.202010] driver_attach+0x19/0x20 [6.202014] ? driver_probe_device+0x450/0x450 [6.202018] bus_add_driver+0x187/0x230 [6.202022] ? 0xf8334000 [6.202026] driver_register+0x56/0xd0 [6.202030] ? 0xf8334000 [6.202035] __pci_register_driver+0x3a/0x40 [6.202041] saa7146_register_extension+0x50/0x80 [saa7146] [6.202050] budget_av_init+0x12/0x1000 [budget_av] [6.202055] do_one_initcall+0x46/0x170 [6.202061] ? vunmap_page_range+0x13e/0x280 [6.202067] ? _cond_resched+0x17/0x40 [6.202073] ? kmem_cache_alloc_trace+0x165/0x1d0 [6.202078] ? do_init_module+0x21/0x1ec [6.202082] ? do_init_module+0x21/0x1ec [6.202087] do_init_module+0x50/0x1ec [6.202092] load_module+0x1565/0x1a80 [6.202102] SyS_finit_module+0x8a/0xe0 [6.202110] do_fast_syscall_32+0x71/0x1d0 [6.202116] entry_SYSENTER_32+0x4e/0x7c [6.202119] EIP: 0xb7eeccf9 [6.202121] EFLAGS: 0292 CPU: 3 [6.202124] EAX: ffda EBX: 0018 ECX: b7cdda71 EDX: [6.202127] ESI: 01547e30 EDI: 0154a2f0 EBP: ESP: bfb3355c [6.202129] DS: 007b ES: 007b FS: GS: 0033 SS: 007b [6.202133] Code: 50 8b 45 e4 e8 02 ec ff ff 85 c0 59 75 60 8b 45 ec 8d 65 f4 5b 5e 5f 5d c3 66 90 83 3d 2c 1d e7 c5 02 0f 85 4c ff ff ff 8d 76 00 <0f> 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 31 ff 8b 1d b0 [6.202209] EIP: saa7146_vmalloc_build_pgtable+0x140/0x1020 [saa7146] SS:ESP: 0068:f4b65c24 [6.202214] ---[ end trace 3619646989f934cf ]--- ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742316 Title: DVB Card with SAA7146 chipset not working Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore. There is a kernel bug message while booting and no /dev/dvb device is created. Tried also with newest mainline 4.14 kernel - same error. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-25-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/se
[Kernel-packages] [Bug 1742323] Re: Meltdown Update Kernel doesnt boot
*** This bug is a duplicate of bug 1741934 *** https://bugs.launchpad.net/bugs/1741934 @Carter Braxton, Can you open a new bug for the issue you are seeing? Also, please add the tag 'pti' to the bug. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742323 Title: Meltdown Update Kernel doesnt boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Using a Dell Poweredge T20 and Ubuntu 16.04 with the 4.4 Kernel. Just got the Meltdown update to kernel linux-image-4.4.0-108-generic but this doesnt boot at all. It just hangs after grub. There is no logs from syslog or such. SysReq Keys dont work neither. The last kernel linux-image-4.4.0-104-generic still boots fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-104-generic 4.4.0-104.127 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-104-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/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' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Wed Jan 10 01:36:01 2018 HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99 InstallationDate: Installed on 2017-05-17 (237 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge T20 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic.efi.signed root=UUID=9edb2ffb-791e-4988-b3a9-7ce73227802c ro RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0VD5HY dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/11/2017:svnDellInc.:pnPowerEdgeT20:pvr00:rvnDellInc.:rn0VD5HY:rvrA07:cvnDellInc.:ct6:cvr: dmi.product.name: PowerEdge T20 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742318] Re: USB-Storage Quirk for 174c:1356
Another, more specific source code would be unusual_devs.h. Manually specified ASMedia devices: /* Reported by Oliver Neukum */ UNUSUAL_DEV( 0x174c, 0x55aa, 0x0100, 0x0100, "ASMedia", "AS2105", USB_SC_DEVICE, USB_PR_DEVICE, NULL, US_FL_NEEDS_CAP16)... It may be more appropriate to add this device in either or both places. At the moment, I have only tested quirk US_FL_IGNORE_UAS (u) (which worked for an install). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742318 Title: USB-Storage Quirk for 174c:1356 Status in linux package in Ubuntu: Incomplete Bug description: A usb-storage quirk is needed for the Mediasonic ProRaid 2 Bay 2.5' SATA HDD / SSD Enclosure - USB 3.1 Gen-II Type-C (HUR6-SU31) for reliable use in Ubuntu/Kubuntu 14-17.10. Using quirk 'u' appears to have fixed disconnect issues during install and use. Linux Version: Ubuntu 4.13.0-16.19-generic 4.13.4 Device ID:174c:1356 ASMedia Technology Inc. usb 9-1: new SuperSpeed USB device number 2 using xhci_hcd usb 9-1: New USB device found, idVendor=174c, idProduct=1356 usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 usb 9-1: Product: ASM1352R-Fast usb 9-1: Manufacturer: ASMT usb 9-1: SerialNumber: 0001 usb 9-1: UAS is blacklisted for this device, using usb-storage instead Note: With/without UAS the issue persisted. I disabled UAS to prevent devices sleeping to eliminate that as a possibility. Symptoms: Before using the quirk, the enclosure would completely stop responding during an install attempt, and the usb host would eventually be disabled. The device's LEDs would continue to blink as if being accessed. Fix: I specified the quirk by appending "usb- storage.quirks=174c:1356:u" to the linux line in Grub. Hopefully others can verify this (if I'm not insane) and include a patch for this upstream in the Kernel. Note: For those who install to a device such as this, you may need to modify your installation before booting it, by creating a file "/etc/modprobe.d/asm1352r-usb-quirk.conf" with contents "options usb- storage quirks=0x174c:0x1356:u". I have seen others (through Google) issuing the same "u" quirk for several ASMedia devices...Perhaps their chipsets need this? This is my first bug report. If any more information is needed, please inform me. I'd like to thank a TJ- in Ubuntu's IRC for helping nail this down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742318] Re: USB-Storage Quirk for 174c:1356
I checked the usb/core/quirks.c and other various source code under
driver/usb/storage, but only one file sticks out as targeting the
vendor, and it doesn't have code related to this device.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/storage/uas-detect.h?h=v4.15-rc7
/*
* ASMedia has a number of usb3 to sata bridge chips, at the time of
* this writing the following versions exist:
* ASM1051 - no uas support version
* ASM1051 - with broken (*) uas support
* ASM1053 - with working uas support, but problems with large xfers
* ASM1153 - with working uas support
*
* Devices with these chips re-use a number of device-ids over the
* entire line, so the device-id is useless to determine if we're
* dealing with an ASM1051 (which we want to avoid).
*
* The ASM1153 can be identified by config.MaxPower == 0,
* where as the ASM105x models have config.MaxPower == 36.
*
* Differentiating between the ASM1053 and ASM1051 is trickier, when
* connected over USB-3 we can look at the number of streams supported,
* ASM1051 supports 32 streams, where as early ASM1053 versions support
* 16 streams, newer ASM1053-s also support 32 streams, but have a
* different prod-id.
*
* (*) ASM1051 chips do work with UAS with some disks (with the
* US_FL_NO_REPORT_OPCODES quirk), but are broken with other disks
*/
if (le16_to_cpu(udev->descriptor.idVendor) == 0x174c &&
(le16_to_cpu(udev->descriptor.idProduct) == 0x5106 ||
le16_to_cpu(udev->descriptor.idProduct) == 0x55aa)) {
if (udev->actconfig->desc.bMaxPower == 0) {
/* ASM1153, do nothing */
} else if (udev->speed < USB_SPEED_SUPER) {
/* No streams info, assume ASM1051 */
flags |= US_FL_IGNORE_UAS;
} else if (usb_ss_max_streams(&eps[1]->ss_ep_comp) == 32) {
/* Possibly an ASM1051, disable uas */
flags |= US_FL_IGNORE_UAS;
} else {
/* ASM1053, these have issues with large transfers */
flags |= US_FL_MAX_SECTORS_240;
}
}
It seems to be a case of simply adding this device into the routine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1742318
Title:
USB-Storage Quirk for 174c:1356
Status in linux package in Ubuntu:
Incomplete
Bug description:
A usb-storage quirk is needed for the Mediasonic ProRaid 2 Bay 2.5'
SATA HDD / SSD Enclosure - USB 3.1 Gen-II Type-C (HUR6-SU31) for
reliable use in Ubuntu/Kubuntu 14-17.10. Using quirk 'u' appears to
have fixed disconnect issues during install and use.
Linux Version: Ubuntu 4.13.0-16.19-generic 4.13.4
Device ID:174c:1356 ASMedia Technology Inc.
usb 9-1: new SuperSpeed USB device number 2 using xhci_hcd
usb 9-1: New USB device found, idVendor=174c, idProduct=1356
usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
usb 9-1: Product: ASM1352R-Fast
usb 9-1: Manufacturer: ASMT
usb 9-1: SerialNumber: 0001
usb 9-1: UAS is blacklisted for this device, using usb-storage instead
Note: With/without UAS the issue persisted. I disabled UAS to prevent
devices sleeping to eliminate that as a possibility.
Symptoms: Before using the quirk, the enclosure would completely stop
responding during an install attempt, and the usb host would
eventually be disabled. The device's LEDs would continue to blink as
if being accessed.
Fix: I specified the quirk by appending "usb-
storage.quirks=174c:1356:u" to the linux line in Grub. Hopefully
others can verify this (if I'm not insane) and include a patch for
this upstream in the Kernel.
Note: For those who install to a device such as this, you may need to
modify your installation before booting it, by creating a file
"/etc/modprobe.d/asm1352r-usb-quirk.conf" with contents "options usb-
storage quirks=0x174c:0x1356:u". I have seen others (through Google)
issuing the same "u" quirk for several ASMedia devices...Perhaps their
chipsets need this?
This is my first bug report. If any more information is needed, please
inform me. I'd like to thank a TJ- in Ubuntu's IRC for helping nail
this down.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742318] Re: USB-Storage Quirk for 174c:1356
I am not aware of any method to use an upstream kernel during a Live CD/DVD/USB to install Ubuntu/Kubuntu. I have only noticed it happening during an install. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742318 Title: USB-Storage Quirk for 174c:1356 Status in linux package in Ubuntu: Incomplete Bug description: A usb-storage quirk is needed for the Mediasonic ProRaid 2 Bay 2.5' SATA HDD / SSD Enclosure - USB 3.1 Gen-II Type-C (HUR6-SU31) for reliable use in Ubuntu/Kubuntu 14-17.10. Using quirk 'u' appears to have fixed disconnect issues during install and use. Linux Version: Ubuntu 4.13.0-16.19-generic 4.13.4 Device ID:174c:1356 ASMedia Technology Inc. usb 9-1: new SuperSpeed USB device number 2 using xhci_hcd usb 9-1: New USB device found, idVendor=174c, idProduct=1356 usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 usb 9-1: Product: ASM1352R-Fast usb 9-1: Manufacturer: ASMT usb 9-1: SerialNumber: 0001 usb 9-1: UAS is blacklisted for this device, using usb-storage instead Note: With/without UAS the issue persisted. I disabled UAS to prevent devices sleeping to eliminate that as a possibility. Symptoms: Before using the quirk, the enclosure would completely stop responding during an install attempt, and the usb host would eventually be disabled. The device's LEDs would continue to blink as if being accessed. Fix: I specified the quirk by appending "usb- storage.quirks=174c:1356:u" to the linux line in Grub. Hopefully others can verify this (if I'm not insane) and include a patch for this upstream in the Kernel. Note: For those who install to a device such as this, you may need to modify your installation before booting it, by creating a file "/etc/modprobe.d/asm1352r-usb-quirk.conf" with contents "options usb- storage quirks=0x174c:0x1356:u". I have seen others (through Google) issuing the same "u" quirk for several ASMedia devices...Perhaps their chipsets need this? This is my first bug report. If any more information is needed, please inform me. I'd like to thank a TJ- in Ubuntu's IRC for helping nail this down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742323] Re: Meltdown Update Kernel doesnt boot
*** This bug is a duplicate of bug 1741934 *** https://bugs.launchpad.net/bugs/1741934 I'm still having problems even with 4.4.0-109. This is running Ubuntu Mate 16.04 on an Intel Core i5-3570K with onboard graphics and luks disk encryption. Although the system gets a little farther than it did with 4.4.0-108, the password screen comes up in low resolution mode and does not respond to keyboard input, apparently crashed. So for now I'm back to running 4.4.0-104. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742323 Title: Meltdown Update Kernel doesnt boot Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Using a Dell Poweredge T20 and Ubuntu 16.04 with the 4.4 Kernel. Just got the Meltdown update to kernel linux-image-4.4.0-108-generic but this doesnt boot at all. It just hangs after grub. There is no logs from syslog or such. SysReq Keys dont work neither. The last kernel linux-image-4.4.0-104-generic still boots fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-104-generic 4.4.0-104.127 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-104-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/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' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Wed Jan 10 01:36:01 2018 HibernationDevice: RESUME=UUID=9b654b0f-96ef-49f0-bfd8-ad7907cb7b99 InstallationDate: Installed on 2017-05-17 (237 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge T20 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic.efi.signed root=UUID=9edb2ffb-791e-4988-b3a9-7ce73227802c ro RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0VD5HY dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/11/2017:svnDellInc.:pnPowerEdgeT20:pvr00:rvnDellInc.:rn0VD5HY:rvrA07:cvnDellInc.:ct6:cvr: dmi.product.name: PowerEdge T20 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742315] Re: corrupted BIOS due to Intel SPI bug in kernel but in ubuntu gnome 16.04
*** This bug is a duplicate of bug 1734147 *** https://bugs.launchpad.net/bugs/1734147 ** This bug has been marked a duplicate of bug 1734147 corrupted BIOS due to Intel SPI bug in 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/1742315 Title: corrupted BIOS due to Intel SPI bug in kernel but in ubuntu gnome 16.04 Status in linux package in Ubuntu: Incomplete Bug description: same bug as Bug #1734147 but for lenovo yoga 3 11 cannot save any BIOS settings cannot boot from USB sorry i do not know the kernel version as i wiped ubuntu but i do know my device is bricked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742293] Re: Kernel Upgrade Error
this bug is a duplicate of #1705345 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742293 Title: Kernel Upgrade Error Status in linux package in Ubuntu: Incomplete Bug description: Installation frozen on this and even after a dpkg --configure -a: Setting up linux-image-4.13.0-25-generic (4.13.0-25.29) ... Running depmod. update-initramfs: deferring update (hook will be called later) The link /initrd.img is a dangling linkto /boot/initrd.img-4.13.0-25-generic vmlinuz(/boot/vmlinuz-4.13.0-25-generic ) points to /boot/vmlinuz-4.13.0-25-generic (/boot/vmlinuz-4.13.0-25-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.13.0-25-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-25-generic /boot/vmlinuz-4.13.0-25-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-25-generic /boot/vmlinuz-4.13.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741655] Re: Regression: KVM no longer supports Intel CPUs without Virtual NMI
** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1741655 Title: Regression: KVM no longer supports Intel CPUs without Virtual NMI Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Bug description: Since upgrading from zesty to artful, I'm not longer able to use KVM on my server: # modprobe kvm-intel modprobe: ERROR: could not insert 'kvm_intel': Input/output error Searching tells me this is caused by requiring Virtual NMI support[1] Running the script provided on the mailing list[1] to check virtualization features confirms my CPU (Xeon E5345) doesn't support Virtual NMIs: # python features.py | grep NMI NMI exiting yes Virtual NMIs no NMI-window exiting no Virtual NMI support was required in v4.12[1] and later reverted in v4.14.3[2] as some models (including Xeons) don't support it, even if others with the same core do. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1490803 [2] https://lkml.org/lkml/2017/8/7/231 [3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.13.y&id=2c82878b0cb38fd516fd612c67852a6bbf282003 [4] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/x86/kvm/vmx.c?h=linux-4.14.y&id=a77360e989f3dc06e4f177a0837d533d13a20d91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742537] Re: Kernel 3.2.0-132 stack trace on boot
@jsalisbury I believe it doesn't, it shows up on the kernels we were upgrading from (-124, I think) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742537 Title: Kernel 3.2.0-132 stack trace on boot Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 27 pages/cpu @8803ace0 s81216 r8192 d21184 u524288 [0.00] pcpu-alloc: s81216 r8192 d21184 u524288 alloc=1*2097152 [0.00] pcpu-alloc: [0] 0 1 2 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3794217 [0.00] Policy zone: Normal [0.00] Kernel command line: root=LABEL=cloudimg-rootf
[Kernel-packages] [Bug 1742537] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1742537/+attachment/5034721/+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/1742537 Title: Kernel 3.2.0-132 stack trace on boot Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 27 pages/cpu @8803ace0 s81216 r8192 d21184 u524288 [0.00] pcpu-alloc: s81216 r8192 d21184 u524288 alloc=1*2097152 [0.00] pcpu-alloc: [0] 0 1 2 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3794217 [0.00] Policy zone: Normal [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro console=hvc0
[Kernel-packages] [Bug 1742537] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1742537/+attachment/5034723/+files/UdevLog.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/1742537 Title: Kernel 3.2.0-132 stack trace on boot Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 27 pages/cpu @8803ace0 s81216 r8192 d21184 u524288 [0.00] pcpu-alloc: s81216 r8192 d21184 u524288 alloc=1*2097152 [0.00] pcpu-alloc: [0] 0 1 2 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3794217 [0.00] Policy zone: Normal [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00
[Kernel-packages] [Bug 1742537] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1742537/+attachment/5034719/+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/1742537 Title: Kernel 3.2.0-132 stack trace on boot Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 27 pages/cpu @8803ace0 s81216 r8192 d21184 u524288 [0.00] pcpu-alloc: s81216 r8192 d21184 u524288 alloc=1*2097152 [0.00] pcpu-alloc: [0] 0 1 2 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3794217 [0.00] Policy zone: Normal [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [
[Kernel-packages] [Bug 1742537] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1742537/+attachment/5034722/+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/1742537 Title: Kernel 3.2.0-132 stack trace on boot Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 27 pages/cpu @8803ace0 s81216 r8192 d21184 u524288 [0.00] pcpu-alloc: s81216 r8192 d21184 u524288 alloc=1*2097152 [0.00] pcpu-alloc: [0] 0 1 2 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3794217 [0.00] Policy zone: Normal [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] P
[Kernel-packages] [Bug 1742537] Re: Kernel 3.2.0-132 stack trace on boot
apport information ** Tags added: apport-collected ec2-images ** Description changed: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 27 pages/cpu @8803ace0 s81216 r8192 d21184 u524288 [0.00] pcpu-alloc: s81216 r8192 d21184 u524288 alloc=1*2097152 [0.00] pcpu-alloc: [0] 0 1 2 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3794217 [0.00] Policy zone: Normal [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Checking aperture... [0.00] No AGP bridge found [0.00] Calgary: detecting Calgary via BIOS EBDA area [0.00] Calgary: Unable to locate Rio Grande table in EBDA - bailing! [0.00] Memory: 15019976k/15426412k availabl
[Kernel-packages] [Bug 1742537] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1742537/+attachment/5034720/+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/1742537 Title: Kernel 3.2.0-132 stack trace on boot Status in linux package in Ubuntu: Confirmed Bug description: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 27 pages/cpu @8803ace0 s81216 r8192 d21184 u524288 [0.00] pcpu-alloc: s81216 r8192 d21184 u524288 alloc=1*2097152 [0.00] pcpu-alloc: [0] 0 1 2 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3794217 [0.00] Policy zone: Normal [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [
[Kernel-packages] [Bug 1742535] Re: 4.4.0-108: stuck loading initial ramdisk
This may be a duplicate of bug 1741934, which was fixed by the 4.4.0-109 kernel. Can you upgrade to 4.4.0-109 and see if this bug still exists? ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: pti -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742535 Title: 4.4.0-108: stuck loading initial ramdisk Status in linux package in Ubuntu: Incomplete Bug description: This kernel does not boot on my machine: it stops at loading the ramdisk. The only information displayed is: > Loading Linux 4.4.0-108-generic ... > Loading initial ramdisk ... I'd like to provide more information about what is happening (or not happening), but I don't know how to debug kernel boot. Any suggestions are welcome. :) The previous kernel 4.4.0-104 works fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-108-generic 4.4.0-108.131 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: edysli 1873 F pulseaudio /dev/snd/controlC2: edysli 1873 F pulseaudio /dev/snd/controlC0: edysli 1873 F pulseaudio CurrentDesktop: MATE Date: Wed Jan 10 21:23:53 2018 HibernationDevice: RESUME=UUID=bf48c561-02f1-4545-8006-2ff0c00bd708 InstallationDate: Installed on 2016-08-09 (518 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic root=/dev/mapper/hostname-root ro verbose RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1905 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-V 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.:bvr1905:bd10/27/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-V:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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/1742535/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742318] Re: USB-Storage Quirk for 174c:1356
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-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key ** 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/1742318 Title: USB-Storage Quirk for 174c:1356 Status in linux package in Ubuntu: Incomplete Bug description: A usb-storage quirk is needed for the Mediasonic ProRaid 2 Bay 2.5' SATA HDD / SSD Enclosure - USB 3.1 Gen-II Type-C (HUR6-SU31) for reliable use in Ubuntu/Kubuntu 14-17.10. Using quirk 'u' appears to have fixed disconnect issues during install and use. Linux Version: Ubuntu 4.13.0-16.19-generic 4.13.4 Device ID:174c:1356 ASMedia Technology Inc. usb 9-1: new SuperSpeed USB device number 2 using xhci_hcd usb 9-1: New USB device found, idVendor=174c, idProduct=1356 usb 9-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 usb 9-1: Product: ASM1352R-Fast usb 9-1: Manufacturer: ASMT usb 9-1: SerialNumber: 0001 usb 9-1: UAS is blacklisted for this device, using usb-storage instead Note: With/without UAS the issue persisted. I disabled UAS to prevent devices sleeping to eliminate that as a possibility. Symptoms: Before using the quirk, the enclosure would completely stop responding during an install attempt, and the usb host would eventually be disabled. The device's LEDs would continue to blink as if being accessed. Fix: I specified the quirk by appending "usb- storage.quirks=174c:1356:u" to the linux line in Grub. Hopefully others can verify this (if I'm not insane) and include a patch for this upstream in the Kernel. Note: For those who install to a device such as this, you may need to modify your installation before booting it, by creating a file "/etc/modprobe.d/asm1352r-usb-quirk.conf" with contents "options usb- storage quirks=0x174c:0x1356:u". I have seen others (through Google) issuing the same "u" quirk for several ASMedia devices...Perhaps their chipsets need this? This is my first bug report. If any more information is needed, please inform me. I'd like to thank a TJ- in Ubuntu's IRC for helping nail this down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742316] Re: DVB Card with SAA7146 chipset not working
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-rc7 ** 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/1742316 Title: DVB Card with SAA7146 chipset not working Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to 17.10 (from 16.04 with 4.4 kernel) my PCI DVB card Terratec Cinergy DVB-1200 with SAA7146 chipset is not working anymore. There is a kernel bug message while booting and no /dev/dvb device is created. Tried also with newest mainline 4.14 kernel - same error. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-25-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/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' Date: Wed Jan 10 00:42:24 2018 HibernationDevice: RESUME=UUID=342e30a6-d71f-47c0-b65a-5ba657a80456 InstallationDate: Installed on 2016-02-13 (696 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release i386 (20151021) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 psbdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=97ea5186-d18d-4c06-a8b2-2dd1417477be ro splash quiet acpi=force video=LVDS-1:d vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2016-07-07 (551 days ago) dmi.bios.date: 04/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: AD2700-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd04/19/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAD2700-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742530] Re: Crash on boot
*** This bug is a duplicate of bug 1741934 *** https://bugs.launchpad.net/bugs/1741934 ** This bug has been marked a duplicate of bug 1741934 Kernel trace with xenial 4.4 (4.4.0-108.131, Candidate kernels for PTI 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/1742530 Title: Crash on boot Status in linux package in Ubuntu: Confirmed Bug description: After an unattended upgrade today my system would no longer boot. Presumably the kernel panic and stack trace info is attached. This is on an HP ProLiant MicroServer Gen8 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-104-generic 4.4.0-104.127 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 19:43 seq crw-rw 1 root audio 116, 33 Jan 10 19:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jan 10 19:50:06 2018 HibernationDevice: RESUME=/dev/mapper/honk--vg-swap_1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic root=/dev/mapper/hostname--vg-root ro noquiet nomodeset radeon.modeset=0 systemd.recover_state=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2015 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ06:bd11/02/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742474] Re: Bad return status for module build on kernel: 4.13.0-26-generic (i686)
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-rc7 ** Changed in: linux-hwe (Ubuntu) Importance: Undecided => Medium ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** 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/1742474 Title: Bad return status for module build on kernel: 4.13.0-26-generic (i686) Status in linux package in Ubuntu: Incomplete Bug description: Distributor ID: LinuxMint Description: Linux Mint 18.3 Sylvia Release: 18.3 Codename: sylvia Linux Asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux Linux Mint 18.3 with HWE Kernel (sudo apt install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04) I've upgraded linux kernel from 4.10.0-4.10.0-42.46~16.04.1 to 4.13.0-26.29~16.04.2. I've got errors while upgrade kernel. And, After rebooting, my linux login screen has been broken. I cannot log in and my linux screen has gone black. Restroing kernel 4.10, then works well. run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-26-generic /boot/vmlinuz-4.13.0-26-generic Error! Bad return status for module build on kernel: 4.13.0-26-generic (i686) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. Belows are /var/lib/dkms/ndiswrapper/1.60/build/make.log. DKMS make.log for ndiswrapper-1.60 for kernel 4.13.0-26-generic (i686) 2018. 01. 11. (목) 00:16:20 KST make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 들어감 AR /var/lib/dkms/ndiswrapper/1.60/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o In file included from /var/lib/dkms/ndiswrapper/1.60/build/ndis.h:19:0, from /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:16: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMAllocateSharedMemory’: /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: error: ‘__GFP_REPEAT’ undeclared (first use in this function) GFP_KERNEL | __GFP_REPEAT) ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of macro ‘PCI_DMA_ALLOC_COHERENT’ *virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, &dma_addr); ^ /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: note: each undeclared identifier is reported only once for each function it appears in GFP_KERNEL | __GFP_REPEAT) ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of macro ‘PCI_DMA_ALLOC_COHERENT’ *virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, &dma_addr); ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMIndicateReceivePacket’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2261:15: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘EthRxIndicateHandler’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2349:14: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMTransferDataComplete’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2464:14: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ scripts/Makefile.build:308: '/var/lib/dkms/ndiswrapper/1.60/build/ndis.o' 타겟에 대한 명령이 실패했습니다 make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/ndis.o] 오류 1 Makefile:1550: '_module_/var/lib/dkms/ndiswrapper/1.60/build' 타겟에 대한 명령이 실패했습니다 make: *** [_module_/var/lib/dk
[Kernel-packages] [Bug 1742413] Re: freezing
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? 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-rc7 ** 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/1742413 Title: freezing Status in linux package in Ubuntu: Incomplete Bug description: freezing issue ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-21-generic 4.13.0-21.24 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhav 1312 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 15:43:28 2018 InstallationDate: Installed on 2017-10-25 (76 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=79a18857-747d-4825-8f82-112c0123d466 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.21 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.32 dmi.chassis.asset.tag: 0297070 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.21:bd03/28/2012:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.32:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742418] Re: Stuck attempting to acess "/proc/sys/kernel/nmi_watchdog" file
This may be a duplicate of bug 1741934, which was fixed by the 4.4.0-109 kernel. Can you upgrade to 4.4.0-109 and see if this bug still exists? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: pti ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742418 Title: Stuck attempting to acess "/proc/sys/kernel/nmi_watchdog" file Status in linux package in Ubuntu: Incomplete Bug description: I has always been able to both read and write "/proc/sys/kernel/nmi_watchdog" file. After the recent kernel update (4.4.0-108-generic, updated on 10-Jan-2018) the computer merely gets stuck on these commands. Ctrl-C cannot interrupt. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-108-generic 4.4.0-108.131 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-108-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/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' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Date: Wed Jan 10 12:30:37 2018 HibernationDevice: RESUME=UUID=a0f49bd7-5ec0-414e-8183-41221652c849 InstallationDate: Installed on 2016-08-17 (510 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 003: ID 04b4:6570 Cypress Semiconductor Corp. Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: CompuLab Ltd. SBC-iBT ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed root=UUID=1ee7c5d5-a843-43d4-a90d-0c484d09d041 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-108-generic N/A linux-backports-modules-4.4.0-108-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: CompuLab Ltd. dmi.bios.version: SBC-iBT_3.1.0.314 X64 dmi.board.asset.tag: None dmi.board.name: SBC-iBT dmi.board.vendor: CompuLab Ltd. dmi.board.version: 1.x dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 11 dmi.chassis.vendor: CompuLab Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnCompuLabLtd.:bvrSBC-iBT_3.1.0.314X64:bd02/24/2015:svnCompuLabLtd.:pnSBC-iBT:pvr1.x:rvnCompuLabLtd.:rnSBC-iBT:rvr1.x:cvnCompuLabLtd.:ct11:cvr1.0: dmi.product.name: SBC-iBT dmi.product.version: 1.x dmi.sys.vendor: CompuLab Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742472] Re: 3.13.0-139.188 build fails with CONFIG_PARAVIRT_CLOCK but not CONFIG_KVM_GUEST
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1742472
Title:
3.13.0-139.188 build fails with CONFIG_PARAVIRT_CLOCK but not
CONFIG_KVM_GUEST
Status in linux package in Ubuntu:
Triaged
Bug description:
Attempting to build the 3.13.0-139.188 kernel with
CONFIG_PARAVIRT_CLOCK=y but with CONFIG_KVM_GUEST unset fails.
arch/x86/built-in.o: In function `kaiser_init':
(.init.text+0x14a84): undefined reference to `kvm_clock'
This appears to be because kvmclock.o is included based on
CONFIG_KVM_GUEST, but the code in arch/x86/mm/kaiser.c referencing
kvm_clock is included based only on CONFIG_PARAVIRT_CLOCK:
#ifdef CONFIG_PARAVIRT_CLOCK
for (idx = 0; kvm_clock.archdata.vclock_mode == VCLOCK_PVCLOCK &&
idx <= (PVCLOCK_FIXMAP_END-PVCLOCK_FIXMAP_BEGIN); idx++)
{
kaiser_add_user_map_early((void
*)__fix_to_virt(PVCLOCK_FIXMAP_BEGIN + idx),
PAGE_SIZE,
__PAGE_KERNEL_VVAR | _PAGE_GLOBAL);
}
#endif
I found this cross-compiling, so the output of ubuntu-bug, cat
version_signature and lspci are not correct for the target system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742472/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.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-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** 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/1742302 Title: Kernel 4.13.0-25 broke nvidia driver Status in linux package in Ubuntu: Incomplete Bug description: After updating to linux-image-4.13.0-25-generic the binary nvidia driver 387.22 cannot be built. As a result the system does not boot into the desktop environment (in my case, KDE). I've attached the driver build log. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lastique 3049 F pulseaudio /dev/snd/controlC2: lastique 3049 F pulseaudio /dev/snd/controlC3: lastique 3049 F pulseaudio /dev/snd/controlC1: lastique 3049 F pulseaudio CurrentDesktop: KDE Date: Wed Jan 10 02:00:46 2018 InstallationDate: Installed on 2015-05-01 (984 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.13.0-21-generic N/A linux-backports-modules-4.13.0-21-generic N/A linux-firmware 1.169.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. 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/1742302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742530] Re: Crash on boot
*** This bug is a duplicate of bug 1741934 *** https://bugs.launchpad.net/bugs/1741934 It is indeed not happening after upgrading to 4.4.0-109. Many thanks for the lightning-quick response! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742530 Title: Crash on boot Status in linux package in Ubuntu: Confirmed Bug description: After an unattended upgrade today my system would no longer boot. Presumably the kernel panic and stack trace info is attached. This is on an HP ProLiant MicroServer Gen8 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-104-generic 4.4.0-104.127 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 19:43 seq crw-rw 1 root audio 116, 33 Jan 10 19:43 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jan 10 19:50:06 2018 HibernationDevice: RESUME=/dev/mapper/honk--vg-swap_1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant MicroServer Gen8 PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic root=/dev/mapper/hostname--vg-root ro noquiet nomodeset radeon.modeset=0 systemd.recover_state=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-104-generic N/A linux-backports-modules-4.4.0-104-generic N/A linux-firmware 1.157.14 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2015 dmi.bios.vendor: HP dmi.bios.version: J06 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrJ06:bd11/02/2015:svnHP:pnProLiantMicroServerGen8:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer Gen8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742537] Re: Kernel 3.2.0-132 stack trace on boot
Does this bug go away if you boot back into the prior kernel? ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742537 Title: Kernel 3.2.0-132 stack trace on boot Status in linux package in Ubuntu: Incomplete Bug description: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 27 pages/cpu @8803ace0 s81216 r8192 d21184 u524288 [0.00] pcpu-alloc: s81216 r8192 d21184 u524288 alloc=1*2097152 [0.00] pcpu-alloc: [0] 0 1 2 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3794217 [0.00] Policy zone: Normal [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro console
[Kernel-packages] [Bug 1742474] [NEW] Bad return status for module build on kernel: 4.13.0-26-generic (i686)
You have been subscribed to a public bug: Distributor ID: LinuxMint Description: Linux Mint 18.3 Sylvia Release: 18.3 Codename: sylvia Linux Asus-1000HE 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux Linux Mint 18.3 with HWE Kernel (sudo apt install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04) I've upgraded linux kernel from 4.10.0-4.10.0-42.46~16.04.1 to 4.13.0-26.29~16.04.2. I've got errors while upgrade kernel. And, After rebooting, my linux login screen has been broken. I cannot log in and my linux screen has gone black. Restroing kernel 4.10, then works well. run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-26-generic /boot/vmlinuz-4.13.0-26-generic Error! Bad return status for module build on kernel: 4.13.0-26-generic (i686) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. Belows are /var/lib/dkms/ndiswrapper/1.60/build/make.log. DKMS make.log for ndiswrapper-1.60 for kernel 4.13.0-26-generic (i686) 2018. 01. 11. (목) 00:16:20 KST make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 들어감 AR /var/lib/dkms/ndiswrapper/1.60/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o In file included from /var/lib/dkms/ndiswrapper/1.60/build/ndis.h:19:0, from /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:16: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMAllocateSharedMemory’: /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: error: ‘__GFP_REPEAT’ undeclared (first use in this function) GFP_KERNEL | __GFP_REPEAT) ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of macro ‘PCI_DMA_ALLOC_COHERENT’ *virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, &dma_addr); ^ /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.h:122:20: note: each undeclared identifier is reported only once for each function it appears in GFP_KERNEL | __GFP_REPEAT) ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:1095:10: note: in expansion of macro ‘PCI_DMA_ALLOC_COHERENT’ *virt = PCI_DMA_ALLOC_COHERENT(wd->pci.pdev, size, &dma_addr); ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMIndicateReceivePacket’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2261:15: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘EthRxIndicateHandler’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2349:14: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ /var/lib/dkms/ndiswrapper/1.60/build/ndis.c: In function ‘NdisMTransferDataComplete’: /var/lib/dkms/ndiswrapper/1.60/build/ndis.c:2464:14: error: ‘struct net_device’ has no member named ‘last_rx’ wnd->net_dev->last_rx = jiffies; ^ scripts/Makefile.build:308: '/var/lib/dkms/ndiswrapper/1.60/build/ndis.o' 타겟에 대한 명령이 실패했습니다 make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/ndis.o] 오류 1 Makefile:1550: '_module_/var/lib/dkms/ndiswrapper/1.60/build' 타겟에 대한 명령이 실패했습니다 make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] 오류 2 make: 디렉터리 '/usr/src/linux-headers-4.13.0-26-generic' 나감 ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete -- Bad return status for module build on kernel: 4.13.0-26-generic (i686) https://bugs.launchpad.net/bugs/1742474 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1741992] Re: kpatch - Add livepatch hook support for ppc64le
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged ** 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/1741992 Title: kpatch - Add livepatch hook support for ppc64le Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: kpatch is a Linux dynamic kernel patching infrastructure which allows you to patch a running kernel without rebooting or restarting any processes. It enables sysadmins to apply critical security patches to the kernel immediately, without having to wait for long-running tasks to complete, for users to log off, or for scheduled reboot windows. It gives more control over uptime without sacrificing security or stability. kpatch is upstream hosted at https://github.com/dynup/kpatch https://github.com/dynup/kpatch/releases Add support for livepatch infrastructure on ppc64le https://github.com/dynup/kpatch/pull/650 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742537] 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 1742537 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742537 Title: Kernel 3.2.0-132 stack trace on boot Status in linux package in Ubuntu: Incomplete Bug description: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR
[Kernel-packages] [Bug 1663555] Re: Repeated suspend and splash screen freeze after upgrading to 16.04
** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1663555 Title: Repeated suspend and splash screen freeze after upgrading to 16.04 Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Previously using nvidia-367 with Ubuntu 14.04. Now Ubuntu 16.04 with nvidia-367.57-0ubuntu0.16.04.1 After upgrade two problems have occurred. 1) Splash screen at startup that prompts for LUKS passphrase has really low resolution and does not accept input to decrypt the filesystem. Booting is currently only possible with the 'nomodeset' option. Kernel version does not affect this. This affects at least * nvidia-367.57 * nvidia-375.26 (from PPA) Older version nvidia-340.101 is NOT affected. 2) When booting with two monitors & extended desktop the computer will go to suspend mode. Sometimes it will go into suspend repeatedly. This happens 'most of the time' when the laptops lid is closed and with all driver versions. Probably unrelated to graphics driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Feb 10 12:48:59 2017 DistUpgraded: 2017-02-08 10:35:37,423 DEBUG got a conffile-prompt from dpkg for file: '/etc/gnome/defaults.list' DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 3.13.0-108-generic, x86_64: installed bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed nvidia-367, 367.57, 4.4.0-62-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK106GLM [Quadro K2100M] [1028:05cc] InstallationDate: Installed on 2014-09-24 (870 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Precision M4800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic root=/dev/mapper/vgcrypt-lvcryptoroot ro cryptopts=target=cryptvol,source=/dev/disk/by-uuid/31fbd5c5-dcfb-4904-aec8-1c69025870a0,lvm=vgcrypt nomodeset SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-02-08 (2 days ago) dmi.bios.date: 05/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 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.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Feb 10 12:44:57 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1663555/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : http
[Kernel-packages] [Bug 1742537] Re: Kernel 3.2.0-132 stack trace on boot
I believe this is unrelated to the KPTI patches as the same stack trace is appearing in our non-updated machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742537 Title: Kernel 3.2.0-132 stack trace on boot Status in linux package in Ubuntu: Incomplete Bug description: Upgrading to 3.2.0-132 (Ubuntu 12.04 EMS) shows a stack trace on boot. This is in a paravirtualized instance running in AWS. $ dmesg [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-132-virtual (buildd@lgw01-amd64-036) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #178-Ubuntu SMP Sat Jan 6 11:20:35 UTC 2018 (Ubuntu 3.2.0-132.178-virtual 3.2.79) [0.00] Command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Centaur CentaurHauls [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 0003ad8db000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] e820 update range: - 0001 (usable) ==> (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x3ad8db max_arch_pfn = 0x4 [0.00] last_pfn = 0x10 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 02cee000 [0.00] Base memory trampoline at [8809b000] 9b000 size 20480 [0.00] init_memory_mapping: -0001 [0.00] 00 - 01 page 4k [0.00] kernel direct mapping tables up to 1 @ 7fb000-100 [0.00] xen: setting RW the range fd4000 - 100 [0.00] init_memory_mapping: 0001-0003ad8db000 [0.00] 01 - 03ad8db000 page 4k [0.00] kernel direct mapping tables up to 3ad8db000 @ fea87000-1 [0.00] xen: setting RW the range f000 - 1 [0.00] RAMDISK: 0206 - 02cee000 [0.00] NUMA turned off [0.00] Faking a node at -0003ad8db000 [0.00] Initmem setup node 0 -0003ad8db000 [0.00] NODE_DATA [0003ad0d6000 - 0003ad0dafff] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal 0x0010 -> 0x003ad8db [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 -> 0x00a0 [0.00] 0: 0x0100 -> 0x003ad8db [0.00] On node 0 totalpages: 3856491 [0.00] DMA zone: 64 pages used for memmap [0.00] DMA zone: 2014 pages reserved [0.00] DMA zone: 1906 pages, LIFO batch:0 [0.00] DMA32 zone: 16320 pages used for memmap [0.00] DMA32 zone: 1028160 pages, LIFO batch:31 [0.00] Normal zone: 43876 pages used for memmap [0.00] Normal zone: 2764151 pages, LIFO batch:31 [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] SMP: Allowing 4 CPUs, 0 hotplug CPUs [0.00] No local APIC present [0.00] APIC: disable apic facility [0.00] APIC: switched to apic NOOP [0.00] nr_irqs_gsi: 16 [0.00] PM: Registered nosave memory: 000a - 0010 [0.00] PCI: Warning: Cannot find a gap in the 32bit address range [0.00] PCI: Unassigned devices with 32bit resource registers may break! [0.00] Allocating PCI resources starting at 3ad9db000 (gap: 3ad9db000:40) [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.2.amazon (preserve-AD) [0.00] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 [0.00] PERCPU: Embedded 27 pages/cpu @8803ace0 s81216 r8192 d21184 u524288 [0.00] pcpu-alloc: s81216 r8192 d21184 u524288 alloc=1*2097152 [0.00] pcpu-alloc: [0] 0 1 2 3 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3794217 [0.00] Policy zone: Normal [0.00] Kernel command line: root=LABEL=cloudimg-rootfs ro console=hvc0 [0.00] PID hash table entrie
[Kernel-packages] [Bug 1739649] Re: Touchpad does not work, "lost sync at byte 6"
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-rc7 ** 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/1739649 Title: Touchpad does not work, "lost sync at byte 6" Status in linux package in Ubuntu: Incomplete Bug description: Touchpad does not work most of the time. I think it randomly started working once, but on several other tries/reboots, it does not work. The device in question: cat /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=000e Version= N: Name="ETPS/2 Elantech Touchpad" P: Phys=isa0060/serio2/input0 S: Sysfs=/devices/platform/i8042/serio2/input/input9 U: Uniq= H: Handlers=mouse0 event4 B: PROP=1 B: EV=b B: KEY=e420 3 0 0 0 0 B: ABS=66180001103 Log messages: dmesg |grep mouse | tail [ 3573.938741] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 [ 3573.946967] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 [ 3573.955131] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 [ 3573.955133] psmouse serio2: issuing reconnect request [ 3574.292050] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 [ 3574.300438] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 [ 3574.308767] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 [ 3574.317016] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 [ 3574.327805] psmouse serio2: Touchpad at isa0060/serio2/input0 lost sync at byte 6 [ 3574.327813] psmouse serio2: issuing reconnect request Using the following workaround I can get it to work, but with limited functionality: https://askubuntu.com/questions/922092/lifebook-e546-touchpad-on-ubuntu-16-04 sudo modprobe -r psmouse sudo modprobe psmouse proto=imps The problem with this fix is that two finger scrolling is no longer possible with the touchpad and the laptop has no other way to scroll. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3 Uname: Linux 4.10.14-041014-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 21 19:30:24 2017 DistUpgraded: 2017-06-29 13:53:24,058 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-22 (944 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: FUJITSU LIFEBOOK E557 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.14-041014-generic root=UUID=f173708e-0a98-4b15-ad20-cc642244842f ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to xenial on 2017-06-29 (175 days ago) dmi.bios.date: 08/23/2017 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.08 dmi.board.name: FJNB2A2 dmi.board.vendor: FUJITSU dmi.board.version: B1 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E557 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.08:bd08/23/2017:svnFUJITSU:pnLIFEBOOKE557:pvr10601736746:rvnFUJITSU:rnFJNB2A2:rvrB1:cvnFUJITSU:ct10:cvrLIFEBOOKE557: dmi.product.name: LIFEBOOK E557 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU 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 2:1.18.4-0ubuntu0.7 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Dec 21 18:32:13 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Kernel-packages] [Bug 1742090] Re: Redpine: Wifi/BT not functioning after s3 resume
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1742090 Title: Redpine: Wifi/BT not functioning after s3 resume Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: System cannot be waked by wowlan, but sometimes works. When the wowlan not works and system waked by other wakeup sources, after resume the wifi and BT would not functioning until reload driver. The driver/FW info: [ 395.217187] ven_rsi_91x: RSI Version Info == [ 395.217188] ven_rsi_91x: [ 395.217192] ven_rsi_91x: FW Version : 1.5.4 [ 395.217198] ven_rsi_91x: Driver Version : RS9113.NB0.NL.GNU.LNX.1.2 [ 395.217200] ven_rsi_91x: Operating mode : 13 [Wi-Fi STA + BT DUAL] [ 395.217201] ven_rsi_91x: Firmware file : RS9113_WLAN_BT_DUAL_MODE.rps [ 395.217202] ven_rsi_91x: Kernel version: 4.4.0-98-generic Kernel snap: caracalla-kernel version:4.4.0-98.121-1 revision:58 BIOS version: 01.00.05 (Also tested with 01.00.03) Tested SKU: T, Media, GPA The reproduce steps: 1. Enable Wowlan and Wol in BIOS 2. Boot up Ubuntu core 3. Connect to Wifi AP $ nmcli d wifi connect password 4. Enable wowlan $ sudo iw phy phy0 wowlan enable magic-packet 5. Enter suspend or hibernate $ sudo systemctl suspend or $ sudo systemctl hibernate 6. Send wake signal from another machine # wakeonlan or # sudo etherwake 7. If system not waked, try to wol or other wake source # wakeonlan 8. After resume, check the wifi/BT function, but not functioning. $ nmcli dev DEVICE TYPE STATE CONNECTION eth0 ethernet connected Wired connection 1 wlan0 wifi disconnected -- eth1 ethernet unavailable -- cdc-wdm0 gsm unavailable -- lo loopback unmanaged -- $ nmcli dev wifi rescan $ nmcli dev wfii list No wifi APs found $ sudo bluetoothctl [NEW] Controller 00:23:A7:EA:65:64 0225399 [default] [bluetooth]# power on Failed to set power on: org.bluez.Error.Failed The not functioning issue can be fixed by reload driver. Also hibernate wakeup fails, and wake by other wake source. The Wifi/BT still functioning which could be the FW is reloaded by driver. This bug is only for tracking purporse, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1742090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1742094] Re: [16.04][classic] Redpine: wowlan feature doesn't work
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1742094
Title:
[16.04][classic] Redpine: wowlan feature doesn't work
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Bug description:
Steps to reproduce:
1. Ensure WoWLAN is enabled in BIOS.
2. Initiate connection to an AP (using nmcli)
3. Configure the device for WoWLAN, run the command:
$ sudo iw phy phy0 wowlan enable magic-packet
4. Enter S5/S4/S3 (using poweroff, etc.)
5. From another computer on the same network run the following command:
$ wakeonlan {mac} (in my case `wakeonlan 00:23:a7:ec:b4:04`)
Expected result: the device starts/resume
This bug is only for tracking purporse, please do not triage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1742094/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
