[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[MURAOKA Taro]

I tried Kernel/MainlineBuilds (https://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D) with my Dell XPS13 (9343).


* v4.16 is OK
* v4.16.1 is NG
* v4.17.19, v4.19.x are NG

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1530405] IwConfig.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224253/+files/IwConfig.txt

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] ProcModules.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224259/+files/ProcModules.txt

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[Elvis de Freitas Souza]

ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  typer  2994 F pulseaudio
 /dev/snd/pcmC0D0p:   typer  2994 F...m pulseaudio
CurrentDesktop: LXQt
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-20 (2 days ago)
InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
 Bus 001 Device 002: ID 046d:c083 Logitech, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. B360M-D3H
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic 
root=UUID=ba2e86e4-48ce-47f3-a413-98536fe6febd ro quiet splash 
resume=UUID=5b571422-2d63-4044-88be-ecd5e66732d8 vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-12-generic N/A
 linux-backports-modules-4.18.0-12-generic  N/A
 linux-firmware 1.175.1
RfKill:
 
Tags:  cosmic
Uname: Linux 4.18.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo
_MarkForUpload: True
dmi.bios.date: 04/19/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: B360M D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/19/2018:svnGigabyteTechnologyCo.,Ltd.:pnB360M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B360M-D3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.


** Tags added: apport-collected cosmic

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 

[Kernel-packages] [Bug 1530405] ProcCpuinfo.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224255/+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/1530405

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] WifiSyslog.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224262/+files/WifiSyslog.txt

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] CurrentDmesg.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224252/+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/1530405

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] AlsaInfo.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224250/+files/AlsaInfo.txt

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] UdevDb.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1530405/+attachment/5224261/+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/1530405

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] ProcInterrupts.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224258/+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/1530405

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] CRDA.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1530405/+attachment/5224251/+files/CRDA.txt

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] Lspci.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1530405/+attachment/5224254/+files/Lspci.txt

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] ProcEnviron.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224257/+files/ProcEnviron.txt

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] PulseList.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224260/+files/PulseList.txt

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112247]  [] 

[Kernel-packages] [Bug 1530405] ProcCpuinfoMinimal.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1530405/+attachment/5224256/+files/ProcCpuinfoMinimal.txt

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112243]  [] ? 
do_nanosleep+0x5a/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112245]  [] 
SyS_nanosleep+0x7a/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   

[Kernel-packages] [Bug 1797538] CurrentDmesg.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224239/+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/1797538

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] ProcModules.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224246/+files/ProcModules.txt

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] ProcCpuinfo.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224242/+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/1797538

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] WifiSyslog.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224249/+files/WifiSyslog.txt

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] ProcEnviron.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224244/+files/ProcEnviron.txt

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

[Elvis de Freitas Souza]

ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  typer  2994 F pulseaudio
 /dev/snd/pcmC0D0p:   typer  2994 F...m pulseaudio
CurrentDesktop: LXQt
DistroRelease: Ubuntu 18.10
InstallationDate: Installed on 2018-12-20 (2 days ago)
InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
 Bus 001 Device 002: ID 046d:c083 Logitech, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. B360M-D3H
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic 
root=UUID=ba2e86e4-48ce-47f3-a413-98536fe6febd ro quiet splash 
resume=UUID=5b571422-2d63-4044-88be-ecd5e66732d8 vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-12-generic N/A
 linux-backports-modules-4.18.0-12-generic  N/A
 linux-firmware 1.175.1
RfKill:
 
Tags:  cosmic
Uname: Linux 4.18.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo
_MarkForUpload: True
dmi.bios.date: 04/19/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: Default string
dmi.board.name: B360M D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/19/2018:svnGigabyteTechnologyCo.,Ltd.:pnB360M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B360M-D3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.


** Tags added: apport-collected

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] Lspci.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1797538/+attachment/5224241/+files/Lspci.txt

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] ProcInterrupts.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224245/+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/1797538

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] CRDA.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1797538/+attachment/5224238/+files/CRDA.txt

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] PulseList.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224247/+files/PulseList.txt

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] UdevDb.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1797538/+attachment/5224248/+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/1797538

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] IwConfig.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224240/+files/IwConfig.txt

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] ProcCpuinfoMinimal.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224243/+files/ProcCpuinfoMinimal.txt

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1797538] AlsaInfo.txt

[Elvis de Freitas Souza]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1797538/+attachment/5224237/+files/AlsaInfo.txt

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1767098] Re: Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

[Launchpad Bug Tracker]

[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/1767098

Title:
  Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

Status in linux package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  On a fresh installation of Ubuntu 18.04, both DVI outputs on the back
  of the card function as expected but it is not possible to enable the
  HDMI output.

  I can reliably reproduce the issue under both X and Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 26 11:22:57 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Tonga PRO [Radeon R9 
285/380] [1462:2015]
  InstallationDate: Installed on 2018-04-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1767098] Re: Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

[Launchpad Bug Tracker]

[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

** Changed in: xorg-server (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/1767098

Title:
  Tonga PRO [Radeon R9 285/380] HDMI output always "disconnected"

Status in linux package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  On a fresh installation of Ubuntu 18.04, both DVI outputs on the back
  of the card function as expected but it is not possible to enable the
  HDMI output.

  I can reliably reproduce the issue under both X and Wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 26 11:22:57 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Tonga PRO [Radeon R9 
285/380] [1462:2015]
  InstallationDate: Installed on 2018-04-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1799035] Re: [SKL] My ubuntu doesn't show resolution above 1024x768

[Launchpad Bug Tracker]

[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/1799035

Title:
  [SKL] My ubuntu doesn't show resolution above 1024x768

Status in linux package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  my ubuntu doesn't show resolution above 1024X800

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog:
   
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 14:35:55 2018
  DistUpgraded: 2018-05-13 17:09:57,832 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000]
  InstallationDate: Installed on 2017-05-01 (537 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=b3c39627-09f9-42d5-ad90-40cd98527af9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (160 days ago)
  dmi.bios.date: 03/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H110M-S2-CF
  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:bd03/15/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2-CF:rvrx.x: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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1797538] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

[Elvis de Freitas Souza]

For me the issue is happening on ubuntu 16.04, 18.04 and 18.10 I also
tried kernel 4.19, no success

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rob2250 F pulseaudio
  Date: Fri Oct 12 08:54:08 2018
  Failure: oops
  InstallationDate: Installed on 2018-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=b1c8d7c6-d9ec-495c-9770-18e7120e87d5 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85]
  UpgradeStatus: Upgraded to cosmic on 2018-10-12 (0 days ago)
  dmi.bios.date: 09/03/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1796466] Re: Graphical login problems after upgrade to linux-image-4.15.0-36

[Launchpad Bug Tracker]

[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/1796466

Title:
  Graphical login problems after upgrade to linux-image-4.15.0-36

Status in linux package in Ubuntu:
  Expired

Bug description:
  Today, I performed the following upgrade:
  Start-Date: 2018-10-06  06:52:59
  Commandline: aptdaemon role='role-commit-packages' sender=':1.121'
  Install: linux-headers-4.15.0-36-generic:i386 (4.15.0-36.39, automatic), 
linux-modules-extra-4.15.0-36-generic:i386 (4.15.0-36.39, automatic), 
linux-modules-4.15.0-36-generic:i386 (4.15.0-36.39, automatic), 
linux-headers-4.15.0-36:i386 (4.15.0-36.39, automatic), 
linux-image-4.15.0-36-generic:i386 (4.15.0-36.39, automatic)
  Upgrade: linux-headers-generic:i386 (4.15.0.34.36, 4.15.0.36.38), 
linux-libc-dev:i386 (4.15.0-34.37, 4.15.0-36.39), libbrotli1:i386 
(1.0.3-1ubuntu1, 1.0.3-1ubuntu1.2), linux-image-generic:i386 (4.15.0.34.36, 
4.15.0.36.38), libgs9:i386 (9.22~dfsg+1-0ubuntu1.2, 
9.25~dfsg+1-0ubuntu0.18.04.1), libwoff1:i386 (1.0.2-1, 1.0.2-1build0.1), 
liblouis14:i386 (3.5.0-1ubuntu0.2, 3.5.0-1ubuntu0.3), plymouth-label:i386 
(0.9.3-1ubuntu7, 0.9.3-1ubuntu7.18.04.1), python3-louis:i386 (3.5.0-1ubuntu0.2, 
3.5.0-1ubuntu0.3), plymouth-theme-ubuntu-text:i386 (0.9.3-1ubuntu7, 
0.9.3-1ubuntu7.18.04.1), libplymouth4:i386 (0.9.3-1ubuntu7, 
0.9.3-1ubuntu7.18.04.1), firefox-locale-de:i386 (62.0+build2-0ubuntu0.18.04.5, 
62.0.3+build1-0ubuntu0.18.04.1), firefox-locale-en:i386 
(62.0+build2-0ubuntu0.18.04.5, 62.0.3+build1-0ubuntu0.18.04.1), 
firefox-globalmenu:i386 (62.0+build2-0ubuntu0.18.04.5, 
62.0.3+build1-0ubuntu0.18.04.1), ghostscript:i386 (9.22~dfsg+1-0ubuntu1.2, 
9.25~dfsg+1-0ubuntu0.18.04.1), libwebkit2gtk-4.0-37:i386 
(2.20.5-0ubuntu0.18.04.1, 2.22.2-0ubuntu0.18.04.1), ghostscript-x:i386 
(9.22~dfsg+1-0ubuntu1.2, 9.25~dfsg+1-0ubuntu0.18.04.1), libgs9-common:i386 
(9.22~dfsg+1-0ubuntu1.2, 9.25~dfsg+1-0ubuntu0.18.04.1), plymouth:i386 
(0.9.3-1ubuntu7, 0.9.3-1ubuntu7.18.04.1), gir1.2-webkit2-4.0:i386 
(2.20.5-0ubuntu0.18.04.1, 2.22.2-0ubuntu0.18.04.1), apache2-bin:i386 
(2.4.29-1ubuntu4.3, 2.4.29-1ubuntu4.4), liblouis-data:i386 (3.5.0-1ubuntu0.2, 
3.5.0-1ubuntu0.3), firefox:i386 (62.0+build2-0ubuntu0.18.04.5, 
62.0.3+build1-0ubuntu0.18.04.1), plymouth-theme-ubuntu-logo:i386 
(0.9.3-1ubuntu7, 0.9.3-1ubuntu7.18.04.1), python-louis:i386 (3.5.0-1ubuntu0.2, 
3.5.0-1ubuntu0.3), apache2-utils:i386 (2.4.29-1ubuntu4.3, 2.4.29-1ubuntu4.4), 
libjavascriptcoregtk-4.0-18:i386 (2.20.5-0ubuntu0.18.04.1, 
2.22.2-0ubuntu0.18.04.1), linux-generic:i386 (4.15.0.34.36, 4.15.0.36.38), 
gir1.2-javascriptcoregtk-4.0:i386 (2.20.5-0ubuntu0.18.04.1, 
2.22.2-0ubuntu0.18.04.1)
  End-Date: 2018-10-06  06:55:43

  After the linux restart, the graphical login (via GDM3) was no longer
  reliable:

   * in one trial, the desktop remained empty; mouse still following;
  keyboard strokes not recognized (this has also happened once before
  after the Ununtu 18.04 upgrade)

   * in one trial, the desktop switched from the initial background to
  an irregular black and white pattern

   * in a third trial, I first perform a console login (to collect
  "ubuntu-bug" error information) and then performed the GDM3-login.
  This time, it has been successful.

  Booting the previous linux version gave a successful graphical login
  (but up to now, I have tried this only once).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic i686
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   dieter 2258 F...m pulseaudio
   /dev/snd/pcmC0D0p:   dieter 2258 F...m pulseaudio
   /dev/snd/controlC0:  dieter 2258 F pulseaudio
  Date: Sat Oct  6 10:43:34 2018
  HibernationDevice:
   # dist value
   #RESUME=UUID=e1161a34-098d-4ba1-ac46-c281e2d5967f
   RESUME=UUID=d1371bc2-640b-484e-aab8-58d2a2640201
  InstallationDate: Installed on 2013-01-21 (2084 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=9c03cebc-9cba-47bc-9974-5c236a34906e ro
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1799218] Re: brightness controller missing after installing nvidia-390

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  brightness controller missing after installing nvidia-390

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Expired

Bug description:
  brightness controller gone after installing nvidia drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.77  Tue Jul 10 18:28:52 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 18:26:31 2018
  DistUpgraded: 2018-09-13 00:30:24,004 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [GeForce 410M] [10de:1055] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF119M [GeForce 410M] [104d:908b]
  InstallationDate: Installed on 2018-08-16 (66 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Sony Corporation VPCEH3AEN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fd7306d2-c2eb-414c-bf34-7e6c72a1fe79 ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (39 days ago)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0190Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH3AEN:pvrC1074QWS:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEH3AEN
  dmi.product.version: C1074QWS
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Oct 22 17:22:30 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799218/+subscriptions

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

[Kernel-packages] [Bug 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

[spm2011]

`apport-bug linux` uploads WifiSyslog.txt, so this also affects apport
hook for the linux package.

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

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

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

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

[Kernel-packages] [Bug 1809510] Re: ubuntu minimal 1804 image published to GCE has the wrong family name

[Sherry Li]

Hi, to clarify, this is a not package related issue but an issue that
the new ubuntu image released to GCP (google cloud platform) on 12/20,
where it broke the contract for image family name.  If you think this
bug should be re-routed, please do so.

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

Title:
  ubuntu minimal 1804 image published to GCE has the wrong family name

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Image ubuntu-minimal-1804-bionic-v20181220 published to Google Compute
  Engine had the wrong Family name.  The name published was 'minimal'.
  This broke customer applications which depends on the family name.

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

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

[Kernel-packages] [Bug 1804593] Re: thermal thermal_zone0: failed to read out thermal zone

[Reinhard Katzmann]

If you need those newer vega firmware for your hardware you need to
update linux-firmware. Best would be to get the src deb from debian sid
or Ubuntu development (19.04) repo and recompile it on your system. I
have not checked if it was backported.

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

Title:
  thermal thermal_zone0: failed to read out thermal zone

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  thermal thermal_zone0: failed to read out thermal zone (-61)

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

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

[Kernel-packages] [Bug 1809510] Missing required logs.

[Ubuntu Kernel Bot]

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 1809510

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  ubuntu minimal 1804 image published to GCE has the wrong family name

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Image ubuntu-minimal-1804-bionic-v20181220 published to Google Compute
  Engine had the wrong Family name.  The name published was 'minimal'.
  This broke customer applications which depends on the family name.

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

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

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

[DH]

I am having a similar issue with Intel 8260. Wifi and BT works correctly
after cold boot. Wifi works correctly after suspend, but BT was showing
no adapters available in KDE plasma widget. dmesg would report "[
150.064149] Bluetooth: hci0: Failed to send firmware data (-38)" after
each resume.

My 8260 was not listed in lsusb, but is listed in lspci.

Fix in #47 did not work for me. However, adding a systemd service to
rmmod and modprobe btusb after each resume seems to have the BT adapter
working correctly now.

uname -a:
Linux uranus 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred was 4.17.0-6-generic.  Before 
that, I used 4.15.0-25-generic which works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USER   

[Kernel-packages] [Bug 1809510] [NEW] ubuntu minimal 1804 image published to GCE has the wrong family name

[Sherry Li]

Public bug reported:

Image ubuntu-minimal-1804-bionic-v20181220 published to Google Compute
Engine had the wrong Family name.  The name published was 'minimal'.
This broke customer applications which depends on the family name.

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

Title:
  ubuntu minimal 1804 image published to GCE has the wrong family name

Status in linux package in Ubuntu:
  New

Bug description:
  Image ubuntu-minimal-1804-bionic-v20181220 published to Google Compute
  Engine had the wrong Family name.  The name published was 'minimal'.
  This broke customer applications which depends on the family name.

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

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

[Kernel-packages] [Bug 1802821] Re: Serious design flaw using large external drives.

[Robert Pearson]

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

Title:
  Serious design flaw using large external drives.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am trying to recover data from an HFS+ files system on a 4TB
  external USB 3 drive. Copying 3TB from the 4TB HFS+ drive to a 4TB
  NTFS drive using MATE Terminal cp -anR from to took 2 days.

  When I try to copy the same data to a 6TB NTFS USB 3 drive the results
  are glacial. 750GB has taken over 6 days. Obviously there is a problem
  of scale drive in Ubuntu MATE. I invite the developers to plug in a
  12TB drive and see just how glacial (no - not glacial, more on the
  order of plate techtonics) slow their design is.

  Robert Pearson

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  robert 2102 F pulseaudio
   /dev/snd/controlC0:  robert 2102 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Nov 11 23:50:13 2018
  HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb
  InstallationDate: Installed on 2018-10-25 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  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.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x: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/1802821/+subscriptions

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

[Kernel-packages] [Bug 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[Matt C]

The same for me, 4.4.0-141 does not help.

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

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[bmaupin]

I'm not sure if this helps, but I removed noapic and added
earlyprintk=efi,keep in an attempt to show some logs. I took a video and
extracted the frames. I've gone through them briefly but I don't see any
errors or warnings:

https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot1.png
https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot2.png
https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot3.png
https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot4.png
https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot5.png
https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot6.png
https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot7.png

Thanks!

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

-- 
Mailing 

[Kernel-packages] [Bug 1806488] Re: Support non-strict iommu mode on arm64

[dann frazier]

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  Support non-strict iommu mode on arm64

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  The Intel IOMMU driver provides an option for strict mode. When disabled, 
batching of IOTLB flush operations is permitted, allowing the user to trade-off 
isolation for improved performance. Ubuntu's kernel currently lacks a parity 
for this feature for ARM.

  There's a significant performance gain to be had by removing the need
  to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25%
  performance gain w/ fio reads on a single NVMe device.

  This mode of operation is available for x86 via the
  "intel_iommu=strict" parameter. Upstream now exposes an equivalent
  feature for ARM platforms via the "iommu.strict=[0|1]" parameter,
  while retaining the default strict-enabled mode.

  [Test Case]
  $ cat fio.rc
  [global]
  rw=read
  direct=1
  ioengine=libaio
  iodepth=2048
  numjobs=10
  bs=4k
  group_reporting=1
  group_reporting=1
  cpumask=0xff
  runtime=100
  loops = 1

  [job1]
  filename=/dev/nvme0n1

  [Fix]
  44f6876a00e83 iommu/arm-smmu: Support non-strict mode
  b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode
  9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode
  b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode
  68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  2da274cdf998a iommu/dma: Add support for non-strict mode
  07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook
  85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()

  [Regression Risk]
  Most of these patches are specific to ARM, and have been regression tested on 
both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)"

  2 patches do touch arch-indep code however:

  > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  Adds a new command line option and sets an attribute that iommu drivers can 
optionally react to. Doesn't change default behavior.

  > 2da274cdf998a iommu/dma: Add support for non-strict mode
  This driver is only built for arm64 and ppc64el (determined by looking at the 
build logs). Most of this patch only changes behavior in the non-default (and 
new) iommu.strict=0 case. The exception, which is called out in the commit 
message, is this hunk:

  -   WARN_ON(iommu_unmap(domain, dma_addr, size) != size);
  +   WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size);
  +   if (!cookie->fq_domain)
  +   iommu_tlb_sync(domain);

  
  In the default case, where fq_domain will be NULl, we are now factoring 
iommu_unmap() into:
iommu_unmap_fast()
iommu_tlb_sync()

  Looking at the source to iommu_unmap() confirms that this is
  functionally equivalent.

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

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

[Kernel-packages] [Bug 1809496] [NEW] kernel RIP when I was cloning a virtual machine in virtualbox5.2

[enri]

Public bug reported:

when cloning a virtual machine (full clone) PCmanFM was frozen and the spootify 
song that was sounding lost a part (advancing the song, the sound returned, but 
half of the song was silent).
At the end of the cloning and when starting the virtual machine, after a little 
use (win7) the machine was completely frozen.
With 3 more starts, the machine had an erratic behaviour (Firefox could not 
boot)
At 4 start I was able to regain control (now I write this)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-43-generic.
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   enrique1269 F...m pulseaudio
 /dev/snd/controlC0:  enrique1189 F lxpanel
  enrique1269 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xdf12 irq 130'
   Mixer name   : 'Realtek ALC887-VD'
   Components   : 'HDA:10ec0887,1849d887,00100302 
HDA:8086280b,80860101,0010'
   Controls  : 78
   Simple ctrls  : 27
CurrentDesktop: LXDE
Date: Fri Dec 21 16:57:53 2018
HibernationDevice: RESUME=UUID=1a5c1bae-cc12-487b-9be1-ca1728d13835
InstallationDate: Installed on 2018-08-08 (135 days ago)
InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
IwConfig:
 enp2s0no wireless extensions.
 
 enp1s0no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04d9:a06b Holtek Semiconductor, Inc. 
 Bus 001 Device 004: ID 0951:1665 Kingston Technology Digital DataTraveler SE9 
64GB
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=482b2391-ee3e-4c27-819c-12edf3894cff ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-43-generic N/A
 linux-backports-modules-4.15.0-43-generic  N/A
 linux-firmware 1.173.2
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.40
dmi.board.name: H110M-HDV R3.0
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.:bvrP7.40:bd02/26/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDVR3.0: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.

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


** Tags: amd64 apport-bug bionic

** Attachment added: "msg.log"
   https://bugs.launchpad.net/bugs/1809496/+attachment/5224164/+files/msg.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/1809496

Title:
  kernel RIP when I was cloning a virtual machine in virtualbox5.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  when cloning a virtual machine (full clone) PCmanFM was frozen and the 
spootify song that was sounding lost a part (advancing the song, the sound 
returned, but half of the song was silent).
  At the end of the cloning and when starting the virtual machine, after a 
little use (win7) the machine was completely frozen.
  With 3 more starts, the machine had an erratic behaviour (Firefox could not 
boot)
  At 4 start I was able to regain control (now I write this)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-43-generic.
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   enrique1269 F...m pulseaudio
   /dev/snd/controlC0:  enrique1189 F lxpanel
enrique1269 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xdf12 irq 130'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,1849d887,00100302 
HDA:8086280b,80860101,0010'
 Controls  : 78
 Simple ctrls  : 27
  CurrentDesktop: LXDE
  Date: Fri Dec 21 16:57:53 2018
  HibernationDevice: 

[Kernel-packages] [Bug 1809496] Status changed to Confirmed

[Ubuntu Kernel Bot]

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

Title:
  kernel RIP when I was cloning a virtual machine in virtualbox5.2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  when cloning a virtual machine (full clone) PCmanFM was frozen and the 
spootify song that was sounding lost a part (advancing the song, the sound 
returned, but half of the song was silent).
  At the end of the cloning and when starting the virtual machine, after a 
little use (win7) the machine was completely frozen.
  With 3 more starts, the machine had an erratic behaviour (Firefox could not 
boot)
  At 4 start I was able to regain control (now I write this)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-43-generic.
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   enrique1269 F...m pulseaudio
   /dev/snd/controlC0:  enrique1189 F lxpanel
enrique1269 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xdf12 irq 130'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,1849d887,00100302 
HDA:8086280b,80860101,0010'
 Controls  : 78
 Simple ctrls  : 27
  CurrentDesktop: LXDE
  Date: Fri Dec 21 16:57:53 2018
  HibernationDevice: RESUME=UUID=1a5c1bae-cc12-487b-9be1-ca1728d13835
  InstallationDate: Installed on 2018-08-08 (135 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp2s0no wireless extensions.
   
   enp1s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04d9:a06b Holtek Semiconductor, Inc. 
   Bus 001 Device 004: ID 0951:1665 Kingston Technology Digital DataTraveler 
SE9 64GB
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=482b2391-ee3e-4c27-819c-12edf3894cff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.40
  dmi.board.name: H110M-HDV R3.0
  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.:bvrP7.40:bd02/26/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-HDVR3.0: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/1809496/+subscriptions

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

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

[Brian Murray]

** Description changed:

+ Impact
+ --
+ Users who have manually configured and xorg.conf file with nvidia enabled as 
a driver will be surprised to have disabled on upgrade to a new release of 
Ubuntu and won't have a graphical display.
+ 
+ Test Case
+ -
+ If you don't have a system with nvidia hardware to upgrade this is a bit 
convoluted but still works.
+ 
+ 1) Run do-release-upgrade (use -d if upgrading to disco)
+ 2) Cancel the upgrade
+ 3) Create an /etc/X11/xorg.conf file with a Device section listed in the 
original description using the nvidia driver.
+ 4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME
+ 5) run ./$target-release-name --frontend DistUpgradeViewText
+ 6) Observe the Driver line is commented out of xorg.conf
+ 
+ When testing the release-upgrader from -proposed you'll need to use the
+ -p switch to get the right tarball. Additionally, you'll want to add a
+ step 4.5 where you modify xorg_fix_proprietary.py so nvidia defaults to
+ True instead of False (line 106) this'll simulate the nvidia driver
+ being loaded.
+ 
+ Regression Potential
+ 
+ This just changes how xorg_fix_proprietary check for nvidia being in use and 
it only affects people who have an /etc/X11/xorg.conf so the impact of a 
regression is rather small. Additionally, the logic used to determine if nvidia 
in use is the same logic used in the apport package hook for all xorg packages 
so is well tested.
+ 
+ Original Description
+ 
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:
  
  Section "Device"
- Identifier "nvidia"
+ Identifier "nvidia"
  #Driver "nvidia"
- BusID "PCI:10@0:0:0"
- Option "ConstrainCursor" "off"
+ BusID "PCI:10@0:0:0"
+ Option "ConstrainCursor" "off"
  EndSection
  
  As the installtion routine backuped my xorg.conf I could verify that the
  line hadn't been commented out before upgrading. Removing the "#" solved
  the problem.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
+ ProblemType: BugDistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
-  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
+  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
-  bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
-  bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
-  nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
-  nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
+  bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
+  bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
+  nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
+  nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
-Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
-Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
+  Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
+    Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
+    Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
- SourcePackage: xorg
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash 
vt.handoff=1SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 

[Kernel-packages] [Bug 1809168] Re: FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root device not found

[Nivedita Singhvi]

This issue is not any of the above mentioned bugs,
after some checking.

This is possibly enablement of new HW as BradF
suggested might be the case, and Dan Streetman 
identified the driver/device in question. 

Driver: megaraid_sas
PCI dev id: 0016
#define PCI_DEVICE_ID_LSI_HARPOON  0x0016

All of the following commits went in into v4.11-rc1.

The following is the commit that enables 
the PCI dev id:

45f4f2eb3da3cbff02c3d77c784c81320c733056 scsi: megaraid_sas: Add new pci
device Ids for SAS3.5 Generic Megaraid Controllers


Set of patches related to this (there might be others):
223e4b93e61f7538681632bfb19edd4f27a0c319 scsi: megaraid_sas: driver version 
upgrade
ede7c3ce82dc4001bbab33dddebab8c089f309e0 scsi: megaraid_sas: Implement the PD 
Map support for SAS3.5 Generic Megaraid Controllers
b71b49c209facf8fec3778142ae5e45bb6ca4afc scsi: megaraid_sas: ldio_outstanding 
variable is not decremented in completion path
3e5eadb1a881bea2e3fa41f5ae7cdbfa36222d37 scsi: megaraid_sas: Enable or Disable 
Fast path based on the PCI Threshold Bandwidth
9581ebebbe351d99579e8701e238c2771ccdae93 scsi: megaraid_sas: Add the Support 
for SAS3.5 Generic Megaraid Controllers Capabilities
d889344e4e59eb962894ab3b64042dc37a2d8b39 scsi: megaraid_sas: Dynamic Raid Map 
Changes for SAS3.5 Generic Megaraid Controllers
69c337c0f8d74d71e085efa8869be9fc51e5962b scsi: megaraid_sas: SAS3.5 Generic 
Megaraid Controllers Fast Path for RAID 1/10 Writes
fdd84e2514b0157219720cf8f3f55757938a39cd scsi: megaraid_sas: SAS3.5 Generic 
Megaraid Controllers Stream Detection and IO Coalescing
45d446038c7b93c40b2fe5ba0e95380f19e0493e scsi: megaraid_sas: EEDP Escape Mode 
Support for SAS3.5 Generic Megaraid Controllers
2493c67e518c772a573c3b1ad02e7ced5b53f6ca scsi: megaraid_sas: 128 MSIX Support
45f4f2eb3da3cbff02c3d77c784c81320c733056 scsi: megaraid_sas: Add new pci device 
Ids for SAS3.5 Generic Megaraid Controllers <---


I will try and confirm that it is the above case,
in which case we likely will not backport to 
4.4/Xenial or FIPS, as it is new HW enablement.

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

Title:
  FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root
  device not found

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  [IMPACT]

  Booting of the Xenial-based FIPS kernel packages
  failed with disk not found errors on amd64.
  This was also observed on standard Ubuntu
  kernels prior to 4.11.0.

  FIPS
  --
  1. linux-image-4.4.0-1002-fips <-- FAIL
  2. linux-image-4.4.0-1006-fips <-- FAIL

  UBUNTU
  

  1. Bionic kernels all WORK

  2. Artful kernels:

     Ubuntu-4.11.0-1.6 <-- WORKS
     Ubuntu-4.10.0-26.30 <-- FAILS

  3. Xenial kernels:

     Ubuntu-hwe-4.11.0-12.17_16.04.1 <--- WORKS
     Ubuntu-hwe-4.10.0-43.47_16.04.1 <--- FAILS

     Ubuntu-lts-* <--- ALL FAIL
     Ubuntu-4.4.0-* <--- ALL FAIL

  We have narrowed down the window to be:

  4.11.0-1.6 (custom build) <--- WORKS
  4.10.0-43.47~16.04.1   <-- FAILS

  Also works:
  
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb

  Symptoms
  -
  System cannot find the root disk and drops into
  an initramfs shell:

  mdadm script local-block "CREATE group disk not found"
  "Gave up waiting for root device. Common problems:
   - Boot args (cat /proc/cmdline)
     - Check rootdelay=...
     - Check root= ...
   - Missing modules (cat /proc/modules; ls/dev)
  ALERT! UUID=... does not exist. Dropping to a shell!

  ...
  (initramfs)_

  There does not appear to be any workaround so far.
  The disks are encrypted SSDs.

  Attaching commit list between the last known
  failing Artful kernel and earliest known
  working kernel (adjacent tags) and other info.

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

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

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

[matyas]

After updating to the latest kernel (the update before was on
2018-12-06) the issue in operational mode did get fixed. I can boot
without the acpi=off parameter

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

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

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1809488] [NEW] armhf guests fail to boot in EFI mode

[dann frazier]

Public bug reported:

[Impact]
The fix for bug 1786878 introduced a regression that causes armhf guest booted 
in EFI mode to panic.

[Test Case]
Boot an armhf guest in EFI mode. Here's how I do that on an arm64 box that 
supports AArch32:

sudo qemu-system-aarch64 -enable-kvm -M virt,gic_version=host -smp 7 -m
2048 -cpu host,aarch64=off -nographic -pflash AAVMF32_CODE.fd -pflash
AAVMF32_VARS.fd -drive if=none,file=bionic-server-cloudimg-
armhf.img,id=hd0 -device virtio-blk-device,drive=hd0 -drive if=none,file
=my-seed.img,id=hd1  -device virtio-blk-device,drive=hd1 -drive
if=none,file=debian.img,id=hd3 -device virtio-blk-device,drive=hd3
-netdev type=tap,id=net0  -device virtio-net-
device,netdev=net0,mac=

[Fix]
33412b8673135 efi/arm: Revert deferred unmap of early memmap mapping

[Regression Risk]
This change is specific to efi/arm, which currently doesn't boot. The reverted 
change was to allow for ACPI BGRT code, which isn't supported on 32-bit ARM.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Status: Fix Released

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: dann frazier (dannf)
   Status: In Progress

** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Disco)
   Status: In Progress => Fix Released

** Changed in: linux (Ubuntu Disco)
 Assignee: dann frazier (dannf) => (unassigned)

** Changed in: linux (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => dann frazier (dannf)

** Description changed:

  [Impact]
- Booting an armhf guest in EFI mode results in a panic.
+ The fix for bug 1786878 introduced a regression that causes armhf guest 
booted in EFI mode to panic.
  
  [Test Case]
  Boot an armhf guest in EFI mode. Here's how I do that on an arm64 box that 
supports AArch32:
  
  sudo qemu-system-aarch64 -enable-kvm -M virt,gic_version=host -smp 7 -m
  2048 -cpu host,aarch64=off -nographic -pflash AAVMF32_CODE.fd -pflash
  AAVMF32_VARS.fd -drive if=none,file=bionic-server-cloudimg-
  armhf.img,id=hd0 -device virtio-blk-device,drive=hd0 -drive if=none,file
  =my-seed.img,id=hd1  -device virtio-blk-device,drive=hd1 -drive
  if=none,file=debian.img,id=hd3 -device virtio-blk-device,drive=hd3
  -netdev type=tap,id=net0  -device virtio-net-
  device,netdev=net0,mac=
  
  [Fix]
  33412b8673135 efi/arm: Revert deferred unmap of early memmap mapping
  
  [Regression Risk]
- This is a regression fix.
+ This change is specific to efi/arm, which currently doesn't boot. The 
reverted change was to allow for ACPI BGRT code, which isn't supported on 
32-bit ARM.

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

Title:
  armhf guests fail to boot in EFI mode

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The fix for bug 1786878 introduced a regression that causes armhf guest 
booted in EFI mode to panic.

  [Test Case]
  Boot an armhf guest in EFI mode. Here's how I do that on an arm64 box that 
supports AArch32:

  sudo qemu-system-aarch64 -enable-kvm -M virt,gic_version=host -smp 7
  -m 2048 -cpu host,aarch64=off -nographic -pflash AAVMF32_CODE.fd
  -pflash AAVMF32_VARS.fd -drive if=none,file=bionic-server-cloudimg-
  armhf.img,id=hd0 -device virtio-blk-device,drive=hd0 -drive
  if=none,file=my-seed.img,id=hd1  -device virtio-blk-
  device,drive=hd1 -drive if=none,file=debian.img,id=hd3 -device virtio-
  blk-device,drive=hd3 -netdev type=tap,id=net0  -device virtio-
  net-device,netdev=net0,mac=

  [Fix]
  33412b8673135 efi/arm: Revert deferred unmap of early memmap mapping

  [Regression Risk]
  This change is specific to efi/arm, which currently doesn't boot. The 
reverted change was to allow for ACPI BGRT code, which isn't supported on 
32-bit ARM.

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

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

Re: [Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Terry Rudd]

Hi Thadeu,

So it feels like we're "done" on this bug; fix released on the kernels
that make sense and not doing anything on the kernels that don't.  Is
that correct?

Thanks in advance,

Terry


On 12/21/2018 10:43 AM, Thadeu Lima de Souza Cascardo wrote:
> I have just marked this as Invalid for Bionic, as the crash version on
> Bionic is capable of analyzing 4.15 kernels (and older 4.13 kernels,
> even though no one should be using such kernels on Bionic).
> 
> If there are any bugs about specific functionalities on that Bionic
> crash version, please report it as a different bug. See, for example,
> https://bugs.launchpad.net/ubuntu-power-systems/+bug/1765660.
> 
> Cascardo.
> 
> ** Changed in: crash (Ubuntu Bionic)
>Status: In Progress => Invalid
>

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Invalid

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1802813] Re: Fix "incomplete report" noise after S3

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  Fix "incomplete report" noise after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  I2C HID devices may keep spewing out error "i2c_hid_get_input:
  incomplete report (30/2)" after system S3.

  [Fix]
  It a regression caused by commit ac75a041048b, backport commmit
  ef6eaf27274c to fix it. Input report length 2 is a valid length.

  [Test]
  With the fix the issue can no longer be observed on Alps touchpads.

  [Regression Potential]
  None. Input report lenght 2 is valid per spec.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1802813/+subscriptions

-- 
Mailing list: https://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 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Terry Rudd]

On 12/21/2018 10:40 AM, Thadeu Lima de Souza Cascardo wrote:
> So, the SRU team asked for more detail on the tests. I will post it
> after January 15th.
> 

Thank you Thadeu! Have a great holiday break!

Terry

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Confirmed
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels. In this case, ipcs command 
could not be used with the bionic GA kernel on ppc64le.

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.
  More tests will be done with the version of the package from -proposed on 
amd64 and ppc64el, including memory commands, and bt.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing is desirable.

  In case of regressions, analysis of kernel dumps will require that the
  crash file be moved to a system where crash doesn't have the
  regression. But live analysis won't be possible in that case.

  -

  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: 

[Kernel-packages] [Bug 1772038] Re: ubuntu/xubuntu 18.04 kernel crash during install.

[matyas]

This is also affecting the 3 Lenovo Thinkpad T420s I have tried in all
live/install and normal modes. I can only operate them with the acpi=off
parameter, but in this case Standby/Restart/Volume controls don't work.
Note: All 3 models have a dedicated nvidia card, which is switched off
in the BIOS Menu.

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

Title:
  ubuntu/xubuntu 18.04 kernel crash during install.

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

Bug description:
  I've been trying to install ubuntu 18.04, but the system crashes with a 
kernel panic and thus won't run. So how do I report this bug?
  The system passes all memory tests and runs 17.10 with no problems, but will 
not run 18.04

  There is very little data gathering that I can do, as the system will
  not boot, not even into text mode.

  PS. This back door way of creating a bug report is very poor when
  dealing with systems that don't run.

  The steps required to reproduce this bug are:
  1) download Ubuntu and/or Xubuntu
  2) burn the installation image to a dvd
  3) insert dvd into target computer
  4) power on target computer
  5) wait a couple of seconds
  6) Stare at frozen screen saying Kernel panic
  7) Go back to step 1

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

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

[Kernel-packages] [Bug 1809185] Re: KMail is crashing

[Stephen Smith]

Don't know if this is related, but this morning I can't start  anakondi
and syslog has the following:

Dec 21 10:39:35 localhost kernel: [  383.890318] audit: type=1400 
audit(1545413975.060:31): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" 
name="/sys/devices/system/node/" pid=3772 comm="mysqld" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
Dec 21 10:39:35 localhost kernel: [  383.890803] audit: type=1400 
audit(1545413975.060:32): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" 
name="/etc/mysql/my.cnf.fallback" pid=3772 comm="mysqld" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
Dec 21 10:39:35 localhost kernel: [  383.895160] audit: type=1400 
audit(1545413975.064:33): apparmor="DENIED" operation="open" 
profile="/usr/sbin/mysqld-akonadi///usr/sbin/mysqld" 
name="/sys/devices/system/node/" pid=3773 comm="mysqld" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0

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

Title:
  KMail is crashing

Status in kmail package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have an Kubuntu 18.10 install where kmail, which I use as my primary
  email client, constantly crashes.

  If I open kmail is sometimes crashes before I've had a chance to click
  anywhere.  Other times it will crash when I open an email.

  I can't read more than ten email before it crashes.

  Where should I look to get data to find out why kmail is crashing.

  Is this the correct forum to report the error?
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steves 3303 F pulseaudio
   /dev/snd/controlC1:  steves 3303 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-19 (0 days ago)
  InstallationMedia:
   
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07b2 Microsoft Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=052c09a3-429e-445b-9312-c949176e9e74 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-12-generic N/A
   linux-backports-modules-4.18.0-12-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/20/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4023
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4023:bd08/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Thadeu Lima de Souza Cascardo]

I have just marked this as Invalid for Bionic, as the crash version on
Bionic is capable of analyzing 4.15 kernels (and older 4.13 kernels,
even though no one should be using such kernels on Bionic).

If there are any bugs about specific functionalities on that Bionic
crash version, please report it as a different bug. See, for example,
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1765660.

Cascardo.

** Changed in: crash (Ubuntu Bionic)
   Status: In Progress => Invalid

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Invalid

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+subscriptions

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

[Kernel-packages] [Bug 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Thadeu Lima de Souza Cascardo]

So, the SRU team asked for more detail on the tests. I will post it
after January 15th.

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Confirmed
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels. In this case, ipcs command 
could not be used with the bionic GA kernel on ppc64le.

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.
  More tests will be done with the version of the package from -proposed on 
amd64 and ppc64el, including memory commands, and bt.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing is desirable.

  In case of regressions, analysis of kernel dumps will require that the
  crash file be moved to a system where crash doesn't have the
  regression. But live analysis won't be possible in that case.

  -

  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (SYSRQ)

  crash> ?

  *  

[Kernel-packages] [Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out

[Brian Murray]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Cosmic)
   Status: New => Won't Fix

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

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  Won't Fix
Status in ubuntu-release-upgrader source package in Cosmic:
  New

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 11:43:16 2018
  DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
  InstallationDate: Installed on 2017-11-02 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 229D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 097312405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773637/+subscriptions

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

[Kernel-packages] [Bug 1806343] Re: FN+F3/F4 does not modify keyboard backlight brightness.

[David]

Whoops, forgot about that, I was attempting to use that to fix some
things (trying things from internet searches,) didn't work before that.

I could load up a Live CD and give the defaults from that, doesn't work
on those.

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

Title:
  FN+F3/F4 does not modify keyboard backlight brightness.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  acpi_listen does not output anything to terminal when pressing key
  combination.

  Keyboard backlight has worked on older versions (I believe 18.04 or
  earlier.)

  I can manually toggle with:

  echo 0 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 1 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 2 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 3 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness

  for varying degrees of brightness.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  disco
  Uname: Linux 4.19.6-041906-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  duck   3632 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (22 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/vg0-root ro quiet splash acpi_osi= acpi_backlight=native 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  Tags:  disco
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VMK.305:bd07/03/2017:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  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/1806343/+subscriptions

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

[Kernel-packages] [Bug 1761379] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From grom...@br.ibm.com 2018-12-21 12:13 EDT---
Hi Frank,

Thanks for the update.

Looking forward for the final resolution :)

Happy Holidays.

Regards,
Gustavo

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

Title:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods
   
  ---uname output---
  inux-image-4.13.0-36-generic
   
  Machine Type = not relevant 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being packaged in any .deb file?

  Thanks. 
   

   
  Userspace tool common name: perf 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions

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

[Kernel-packages] [Bug 1788098] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From leona...@ibm.com 2018-12-21 12:10 EDT---
Hello,

I have been trying to reproduce this bug over this week, but I couldn't
do so on Ubuntu.

Could anyone verify what I have been doing wrong?

#

## QEMU

I have built version Qemu 3.1.0 and made sure the patch that enables THP was 
included:
../configure 
--target-list=ppc-linux-user,ppc64-linux-user,ppc64le-linux-user,ppc-softmmu,ppc64-softmmu
 --enable-debug-info --enable-trace-backends=log --python=/usr/bin/python3 && 
make -j $(nproc)'

./ppc-softmmu/qemu-system-ppc -version
QEMU emulator version 3.1.0 (v3.1.0-dirty)

## Kernel

uname -a
Linux NAME 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

cat /sys/kernel/mm/transparent_hugepage/enabled
[always] madvise never

## CLI command

Both commands were sent on the same host,  (1) is the "migrating from"
instance and (2) is the "migrate to" instance.

(1)
MALLOC_PERTURB_=1 /home/leonardo/qemu/build/ppc64-softmmu/qemu-system-ppc64 \
-nographic \
-serial mon:stdio \
-S  \
-name 'avocado-vt-vm1'  \
-machine pseries  \
-nodefaults  \
-vga std \
-device pci-bridge,id=pci_bridge,bus=pci.0,addr=0x3,chassis_nr=1  \
-device virtio-serial-pci,id=virtio_serial_pci0,bus=pci.0,addr=0x4 \
-object rng-random,filename=/dev/random,id=passthrough-RHq4nIpF \
-device 
virtio-rng-pci,id=virtio-rng-pci-aXCni2OX,rng=passthrough-RHq4nIpF,bus=pci.0,addr=0x5
 \
-device nec-usb-xhci,id=usb1,bus=pci.0,addr=0x6 \
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=0x7 \
-drive 
id=drive_image1,if=none,snapshot=off,aio=native,cache=none,format=qcow2,file=/home/leonardo/images/ubuntu-18.04-ppc64le.qcow2
 \
-device scsi-hd,id=image1,drive=drive_image1 \
-m 8192  \
-smp 4,maxcpus=4,cores=2,threads=1,sockets=2 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
-vnc :0  \
-rtc base=utc,clock=host  \
-boot order=cdn,once=c,menu=off,strict=off \
-enable-kvm  \
-watchdog i6300esb \
-watchdog-action reset \
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9

(2) Same as above. Changes only a few stuff:
- -name 'avocado-vt-vm1'  \
+ -name 'avocado-vt-vm2'  \
- -vnc :0  \
+ -vnc :1  \
+ -incoming tcp:0:5801 \

## Testing and Results

(1) On guest :
# stress --io 5 --cpu 4
stress: info: [812] dispatching hogs: 4 cpu, 5 io, 0 vm, 0 hdd

(1) on Qemu Terminal:
(qemu) migrate_set_speed 256
(qemu) migrate -d tcp:0:5801
(qemu) info migrate
globals:
store-global-state: on
only-migratable: off
send-configuration: on
send-section-footer: on
capabilities: xbzrle: off rdma-pin-all: off auto-converge: off zero-blocks: off 
compress: off events: off postcopy-ram: off x-colo: off release-ram: off block: 
off return-path: off pause-before-switchover: off x
-multifd: off dirty-bitmaps: off
Migration status: completed
total time: 1776 milliseconds
downtime: 61 milliseconds
setup: 9 milliseconds
transferred ram: 422571 kbytes
throughput: 1964.89 mbps
remaining ram: 0 kbytes
total ram: 8405056 kbytes
duplicate: 2006371 pages
skipped: 0 pages
normal: 101037 pages
normal bytes: 404148 kbytes
dirty sync count: 3
page size: 4 kbytes
(qemu) info status
VM status: paused (postmigrate)

It's all over on ~2 seconds, no issues. Stress stay running on the new
machine. (after cont)

###

Other Qemu tested, with the same result:
v2.12 git
v3.0.0 git
Debian 1:2.12+dfsg-3ubuntu8)

Other Host Kernel tested, with the same result:
4.18.0 - Vanilla, no patch
4.15.0-42-generic
4.15.0-42-generic + patch
4.15.0-32-generic (provided by jsalisbury)
4.15.0-20-generic
4.15.0 - Vanilla, no 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/1788098

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about 

[Kernel-packages] [Bug 1801305] Re: Restore request-based mode to xen-blkfront for AWS kernels

[Kamal Mostafa]

** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu)

** Changed in: linux-aws (Ubuntu Trusty)
   Status: New => Fix Released

** Changed in: linux-aws (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: linux-aws (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: linux-aws (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: linux-aws (Ubuntu Disco)
   Status: New => 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/1801305

Title:
  Restore request-based mode to xen-blkfront for AWS kernels

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-aws source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux-aws source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-aws source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Triaged
Status in linux-aws source package in Disco:
  Fix Released

Bug description:
  In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by
  default and cannot use the old I/O scheduler.

  [Impact]
  blk-mq is not as fast as the old request-based scheduler for some workloads 
on HDD disks.

  [Fix]
  Amazon Linux has a commit which reintroduces the request-based mode. It 
disables blk-mq by default but allows it to be switched back on with a kernel 
parameter.

  For X this needs a small patch from upstream for error handling.

  For B/C this patchset is bigger as it includes the suspend/resume
  patches already in X, and a new fixup. These are desirable as the
  request mode patch assumes their presence.

  [Regression Potential]
  Could potentially break xen based disks on AWS.

  For B/C, the patches also add some code to the xen core around suspend
  and resume, this code is much smaller and also mirrors code already in
  Xenial.

  [Tests]
  Tested by AWS for Xenial, and their kernel engineers vetted the patches. I 
tested the Bionic and Cosmic patchsets with fio, the system appears stable and 
the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did 
an apt update/upgrade and everything worked (no hash-sum mismatches).

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

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

[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu

[Frank Heimes]

quick update:
Looks like a way was found (by apw) to modify the dependencies to become able 
to finally ship libperf-jvmti.so, but this needs to be discussed with the 
Ubuntu archive team first - which is the next step 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/1761379

Title:
  [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
  deb on Ubuntu

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  In Progress

Bug description:
  ---Problem Description---
  File libperf-jvmti.so is missing in linux-tools-common deb making it 
impossible to use perf for the JVM JITed methods
   
  ---uname output---
  inux-image-4.13.0-36-generic
   
  Machine Type = not relevant 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   File libperf-jvmti.so is missing in linux-tools-common deb provided for 
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also 
checked if the file is available on launchpad 
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) 
at it's also absent there:

  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
  gromero@ltc-wspoon3:~/download$ dpkg -c 
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm

  I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
  apparently it's no being packaged in any .deb file?

  Thanks. 
   

   
  Userspace tool common name: perf 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace tool obtained from project website:  na

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions

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

[Kernel-packages] [Bug 1809477] Status changed to Confirmed

[Ubuntu Kernel Bot]

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

Title:
  package linux-cloud-tools-common 4.4.0-128.154 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Unable to uninstall this package. Get same error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-cloud-tools-common 4.4.0-128.154
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   linux-cloud-tools-common: Install
   linux-cloud-tools-common: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Dec 21 06:48:31 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 5
  HibernationDevice: RESUME=UUID=6e79004e-a8a4-47c1-87b8-b3c7b9c90916
  InstallationDate: Installed on 2016-10-31 (781 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-45-generic 
root=/dev/mapper/rootvg-root ro ipv6.disable=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  Title: package linux-cloud-tools-common 4.4.0-128.154 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785T-M
  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.:bvr2301:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785T-M:rvrRevX.0x: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
  modified.conffile..etc.init.hv-fcopy-daemon.conf: [deleted]
  modified.conffile..etc.init.hv-kvp-daemon.conf: [deleted]
  modified.conffile..etc.init.hv-vss-daemon.conf: [deleted]

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

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

[Kernel-packages] [Bug 1808743] Re: [Ubuntu 1810] Kdump fails to dump vmcore and enters initramfs inside Power9 KVM guest

[Joseph Salisbury]

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu)
   Status: New => Triaged

** Changed in: makedumpfile (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Kernel Team (canonical-kernel-team)

** Tags added: kernel-da-key

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

Title:
  [Ubuntu 1810] Kdump fails to dump vmcore and enters initramfs inside
  Power9 KVM guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  Triaged

Bug description:
  Kdump fails to dump vmcore even with workaround suggested

  This issue is submitted to
  track on Power9 Guest where it uses file type qcow2 disk (virtio-scsi)

  
  Boot Log: (Attached full console log)

  [3.754031]32regs: 19616.000 MB/sec
  [3.794031]32regs_prefetch: 17280.000 MB/sec
  [3.834030]altivec   : 22480.000 MB/sec
  [3.834063] xor: using function: altivec (22480.000 MB/sec)
  done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... 
done.
  Begin: Running /scripts/local-premount ... done.
  Begin: Waiting for root file system ... Begin: Running /scripts/local-block 
... mdadm: No devices listed in conf file were found.
  done.
  mdadm: No devices listed in conf file were found.
  mdadm: No devices listed in conf file were found.
  mdadm: No devices listed in conf file were found.
  done.
  Gave up waiting for root file system device.  Common problems:
   - Boot args (cat /proc/cmdline)
 - Check rootdelay= (did the system wait long enough?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  UUID=5e1fe9e9-cf03-4c73-adce-0e57676f98e0 does not exist.  Dropping 
to a shell!

  
  BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs)

  Contact Information = Balamuruhan S / balamuruh...@in.ibm.com 
   
  ---uname output---

  Guest Kernel: 4.18.0-11-generic
  Host Kernel:  4.18.0-11-generic
   
  Machine Type = Boston 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Have a healthy KVM guest with Ubuntu 1810 with kernel 4.18.0-11-generic
  2. Install kdump, kexec and crash tools in the guest,
  # dpkg -l | grep crash
  ii  apport2.20.10-0ubuntu13.1 
 all  automatically generate crash reports for debugging
  ii  crash 7.2.3+real-1
 ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools   1:1.6.4-2ubuntu1
 ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  linux-crashdump   4.18.0.11.12
 ppc64el  Linux kernel crashdump setup for the latest generic kernel
  ii  python3-apport2.20.10-0ubuntu13.1 
 all  Python 3 library for Apport crash report handling

  3. Ensure workaround suggested in Bug 172389 is followed by uncomment the 
`KDUMP_CMDLINE_APPEND`
  and change nr_cpus to maxcpus in /etc/default/kdump-tools config file,
   
  # cat /etc/default/kdump-tools | grep -i cmdline
  # KDUMP_CMDLINE - The default is to use the contents of /proc/cmdline.  
  # Set this variable to override /proc/cmdline.
  # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line 
  #KDUMP_CMDLINE=""
  KDUMP_CMDLINE_APPEND="1 maxcpus=1 systemd.unit=kdump-tools.service irqpoll 
noirqdistrib nousb reset_devices"

  4. restart the kdump tools service,
  # service kdump-tools restart
  # service kdump-tools status
  ? kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: active (exited) since Mon 2018-12-03 02:34:03 CST; 1 weeks 3 days 
ago
Process: 1560 ExecStart=/etc/init.d/kdump-tools start (code=exited, 
status=0/S
   Main PID: 1560 (code=exited, status=0/SUCCESS)

  Dec 03 02:34:02 ubuntu1810 systemd[1]: Starting Kernel crash dump capture 
servic
  Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]: Starting kdump-tools:  * 
Creating 
  Dec 03 02:34:02 ubuntu1810 kdump-tools[1560]:  * Creating symlink 
/var/lib/kdump
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]: Modified 
cmdline:BOOT_IMAGE=/boot/
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1560]:  * loaded kdump kernel
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1678]: /sbin/kexec -p 
--command-line="BOO
  Dec 03 02:34:03 ubuntu1810 kdump-tools[1679]: loaded kdump kernel
  Dec 03 02:34:03 ubuntu1810 systemd[1]: Started Kernel crash dump capture 
service

  5. check kdump-config is state is ready to dump,
  # 

[Kernel-packages] [Bug 1809477] Re: package linux-cloud-tools-common 4.4.0-128.154 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-cloud-tools-common 4.4.0-128.154 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Unable to uninstall this package. Get same error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-cloud-tools-common 4.4.0-128.154
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   linux-cloud-tools-common: Install
   linux-cloud-tools-common: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Dec 21 06:48:31 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 5
  HibernationDevice: RESUME=UUID=6e79004e-a8a4-47c1-87b8-b3c7b9c90916
  InstallationDate: Installed on 2016-10-31 (781 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-45-generic 
root=/dev/mapper/rootvg-root ro ipv6.disable=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  Title: package linux-cloud-tools-common 4.4.0-128.154 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785T-M
  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.:bvr2301:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785T-M:rvrRevX.0x: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
  modified.conffile..etc.init.hv-fcopy-daemon.conf: [deleted]
  modified.conffile..etc.init.hv-kvp-daemon.conf: [deleted]
  modified.conffile..etc.init.hv-vss-daemon.conf: [deleted]

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

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

[Kernel-packages] [Bug 1809477] [NEW] package linux-cloud-tools-common 4.4.0-128.154 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

[Mike Halliday]

Public bug reported:

Unable to uninstall this package. Get same error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-cloud-tools-common 4.4.0-128.154
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 linux-cloud-tools-common: Install
 linux-cloud-tools-common: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Dec 21 06:48:31 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 5
HibernationDevice: RESUME=UUID=6e79004e-a8a4-47c1-87b8-b3c7b9c90916
InstallationDate: Installed on 2016-10-31 (781 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: System manufacturer System Product Name
PackageArchitecture: all
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-45-generic 
root=/dev/mapper/rootvg-root ro ipv6.disable=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19
RfKill:
 0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
Title: package linux-cloud-tools-common 4.4.0-128.154 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A785T-M
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.:bvr2301:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785T-M:rvrRevX.0x: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
modified.conffile..etc.init.hv-fcopy-daemon.conf: [deleted]
modified.conffile..etc.init.hv-kvp-daemon.conf: [deleted]
modified.conffile..etc.init.hv-vss-daemon.conf: [deleted]

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-cloud-tools-common 4.4.0-128.154 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Unable to uninstall this package. Get same error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-cloud-tools-common 4.4.0-128.154
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   linux-cloud-tools-common: Install
   linux-cloud-tools-common: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Dec 21 06:48:31 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 5
  HibernationDevice: RESUME=UUID=6e79004e-a8a4-47c1-87b8-b3c7b9c90916
  InstallationDate: Installed on 2016-10-31 (781 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-45-generic 
root=/dev/mapper/rootvg-root ro ipv6.disable=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.19
  RfKill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  Title: package linux-cloud-tools-common 4.4.0-128.154 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785T-M
  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.:bvr2301:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785T-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By 

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[bmaupin]

I just tried kernel v4.20-rc7 and without noapic my computer hangs at a
blank screen. With noapic it boots fine.

Thanks!

** Description changed:

  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot, hanging
  at various screens:
  
  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked
  
  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
+ - 4.20.0-rc7
  
  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:
  
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"
  
  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.
  
  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401
  
  I'll attach screenshots of various times I've encountered this bug over
  the last year.
  
  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  
  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered 

[Kernel-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

[Jarno Suni]

Verified unattended-upgrades 1.1ubuntu1.18.04.7~16.04.1

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-notifier source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  [Impact]

  The rationale behind the SRU to Xenial is that with latest unattended-
  upgrades SRU it starts removing unused kernels, but all older kernels
  are not removed in a single run. With update-notifier and u-u not
  fixed they place /var/run/reboot-required asking for a reboot when it
  is not needed.

  
  [Test Case]

  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  [ Regression Potential ]

  If the check for skipping placing the /var/run/reboot-required file is too 
broad it may make kernel upgrades fail to ask for reboot. The fix changes a 
hook called by maintainer scripts and a failure in the hook can make kernel 
package installations fail.
  The fix is simple and was tested in several releases thus regressing in these 
ways is unlikely.

  [ Original Bug Text ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  ---
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx: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/unattended-upgrades/+bug/1458204/+subscriptions

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

[Kernel-packages] [Bug 1808412] Re: 4.15.0 memory allocation issue

[Marc Gariépy]

** Also affects: qemu (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/1808412

Title:
  4.15.0 memory allocation issue

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  New

Bug description:
  My server is : 
  PowerEdge T630
  2x Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz
  128G of ram
  4x VGA compatible controller [0300]: NVIDIA Corporation GP102 [TITAN X] 
[10de:1b00] (rev a1)

  Starting 116G ram 16vcpus + 4 pci passthrough allocating memory stops
  after about half of the memory.

  When upgrading from kernel 4.13.0 to 4.15.0 starting a vm takes a long
  time.

  I tested kernel : 
  linux-image-4.13.0-37 not affected
  linux-image-4.13.0-45 not affected
  linux-image-4.15.0-34 affected
  linux-image-4.15.0-42 affected

  After disabling transparent_hugepage on 4.15 everything seems to work
  correctly.

  cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID= ro 
intel_iommu=on transparent_hugepage=never splash quiet vt.handoff=7
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 18 20:02 seq
   crw-rw 1 root audio 116, 33 Dec 18 20:02 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d1a63627-71f0-4d12-90cb-025ed3aa8439
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Supermicro X8DTH-i/6/iF/6F
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=UUID=7d5fdcc6-37a6-4b95-bf01-4f5c9637720b ro biosdevname=0 net.ifnames=0 
splash intel_iommu=on quiet audit=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 05/04/12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.1b
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X8DTH
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.1b:bd05/04/12:svnSupermicro:pnX8DTH-i/6/iF/6F:pvr1234567890:rvnSupermicro:rnX8DTH:rvr1234567890:cvnSupermicro:ct17:cvr1234567890:
  dmi.product.family: Server
  dmi.product.name: X8DTH-i/6/iF/6F
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro

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

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

[Kernel-packages] [Bug 1807342] Re: Add support for Dell DW5821e WWAN/GPS module

[Kleber Sacilotto de Souza]

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  Add support for Dell DW5821e WWAN/GPS module

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  == Impact ==
  DW5821e doesn't work in Bionic.

  == Fix ==
  Three commits are required to support it. All of them are already in the 
mainline kernel.

  == Test Case ==
  With the command
  $ sudo mmcli -L
  the device should be listed as a modem.

  == Risk of Regression ==
  Very low. it only adds the device ID to the right driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1807342/+subscriptions

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

[Kernel-packages] [Bug 1806850] Re: Fix Terminus USB hub that may breaks connected USB devices after S3

[Kleber Sacilotto de Souza]

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  Fix Terminus USB hub that may breaks connected USB devices after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  New

Bug description:
  [Impact]
  USB devices connected to Terminus USB hub stop working after S3.

  [Fix]
  The Terminus hub seems to have a rather slow reset command, so we need to 
wait for extra time before doing any further action.

  [Test]
  After applying the fix, USB devices connected to the HUB no longer stop 
functioning after S3.

  [Regression Potential]
  Low. Although the fix affects all devices connect to the HUB, it has no 
functional change other than imposes longer delay time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806850/+subscriptions

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

[Kernel-packages] [Bug 1806335] Re: Enable new Realtek card reader

[Kleber Sacilotto de Souza]

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux-oem (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: Incomplete

** Also affects: linux-oem (Ubuntu Disco)
   Importance: Undecided
   Status: Fix Released

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  Enable new Realtek card reader

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  New
Status in linux source package in Disco:
  In Progress
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  USB Storage based Realtek card reader doesn't work, because the usb-storage 
module tries to use it in UAS mode instead of using "ums-realtek".

  [Fix]
  Add new IDs to ums-realtek driver.
  In addition to that, we add a new module knob, "enable_mmc=", to 
enable/disable MMC, as vendors may not pay MMC royalties. "enable_mmc" defaults 
to 1.

  [Test]
  After applying the patch, the card reader works, and verified "enable_mmc=" 
can enable/disable MMC support.

  [Regression Potential]
  Minimal. This SRU enables two specific card readers that don't work as UAS, 
the new module knob only introduces new behavior when enable_mmc=0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806335/+subscriptions

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

[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[shaju]

shaju@678:~$ dmesg | grep i915
[2.088602] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[2.103420] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0
[2.264884] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[10947.862266] WARNING: CPU: 1 PID: 1174 at 
/build/linux-hwe-O570pP/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_display.c:1247
 assert_plane+0x98/0xa0 [i915]
[10947.862307]  nf_nat_ftp nf_nat binfmt_misc nf_conntrack_ftp nf_conntrack 
libcrc32c iptable_filter parport_pc ppdev ip_tables x_tables lp parport autofs4 
ums_realtek hid_generic usbhid hid uas usb_storage i915 i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops wmi sky2 
drm video
[10947.862365] RIP: 0010:assert_plane+0x98/0xa0 [i915]
[10947.862417]  assert_planes_disabled.isra.96+0x4d/0x70 [i915]
[10947.862453]  intel_disable_pipe+0x58/0x190 [i915]
[10947.862512]  i9xx_crtc_disable+0x7e/0x410 [i915]
[10947.862549]  intel_atomic_commit_tail+0x1f4/0xd90 [i915]
[10947.862585]  intel_atomic_commit+0x282/0x2b0 [i915]
[10947.862673]  intel_fbdev_set_par+0x1a/0x70 [i915]
[10947.880823] WARNING: CPU: 0 PID: 1174 at 
/build/linux-hwe-O570pP/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_display.c:1247
 assert_plane+0x98/0xa0 [i915]
[10947.880864]  nf_nat_ftp nf_nat binfmt_misc nf_conntrack_ftp nf_conntrack 
libcrc32c iptable_filter parport_pc ppdev ip_tables x_tables lp parport autofs4 
ums_realtek hid_generic usbhid hid uas usb_storage i915 i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops wmi sky2 
drm video
[10947.880921] RIP: 0010:assert_plane+0x98/0xa0 [i915]
[10947.880973]  assert_planes_disabled.isra.96+0x4d/0x70 [i915]
[10947.881009]  intel_enable_pipe+0x58/0x200 [i915]
[10947.881045]  i9xx_crtc_enable+0x373/0x480 [i915]
[10947.881082]  intel_update_crtc+0x47/0xa0 [i915]
[10947.881117]  intel_update_crtcs+0x5d/0x70 [i915]
[10947.881153]  intel_atomic_commit_tail+0x3ad/0xd90 [i915]
[10947.881189]  intel_atomic_commit+0x282/0x2b0 [i915]
[10947.881288]  intel_fbdev_set_par+0x1a/0x70 [i915]
[10947.900888] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
[11015.563288] WARNING: CPU: 0 PID: 997 at 
/build/linux-hwe-O570pP/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_display.c:1247
 assert_plane+0x98/0xa0 [i915]
[11015.563353]  nf_nat_ftp nf_nat binfmt_misc nf_conntrack_ftp nf_conntrack 
libcrc32c iptable_filter parport_pc ppdev ip_tables x_tables lp parport autofs4 
ums_realtek hid_generic usbhid hid uas usb_storage i915 i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops wmi sky2 
drm video
[11015.563430] RIP: 0010:assert_plane+0x98/0xa0 [i915]
[11015.563497]  assert_planes_disabled.isra.96+0x4d/0x70 [i915]
[11015.563542]  intel_disable_pipe+0x58/0x190 [i915]
[11015.563613]  i9xx_crtc_disable+0x7e/0x410 [i915]
[11015.563659]  intel_atomic_commit_tail+0x1f4/0xd90 [i915]
[11015.563704]  intel_atomic_commit+0x282/0x2b0 [i915]
[11015.588602] WARNING: CPU: 0 PID: 997 at 
/build/linux-hwe-O570pP/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_display.c:1247
 assert_plane+0x98/0xa0 [i915]
[11015.588684]  nf_nat_ftp nf_nat binfmt_misc nf_conntrack_ftp nf_conntrack 
libcrc32c iptable_filter parport_pc ppdev ip_tables x_tables lp parport autofs4 
ums_realtek hid_generic usbhid hid uas usb_storage i915 i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops wmi sky2 
drm video
[11015.588785] RIP: 0010:assert_plane+0x98/0xa0 [i915]
[11015.588874]  assert_planes_disabled.isra.96+0x4d/0x70 [i915]
[11015.588934]  intel_enable_pipe+0x58/0x200 [i915]
[11015.588993]  i9xx_crtc_enable+0x373/0x480 [i915]
[11015.589054]  intel_update_crtc+0x47/0xa0 [i915]
[11015.589114]  intel_update_crtcs+0x5d/0x70 [i915]
[11015.589174]  intel_atomic_commit_tail+0x3ad/0xd90 [i915]
[11015.589234]  intel_atomic_commit+0x282/0x2b0 [i915]
[11015.606386] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame 

[Kernel-packages] [Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[shaju]

shaju@678:~$ dmesg | grep i915
[2.088602] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[2.103420] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0
[2.264884] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[10947.862266] WARNING: CPU: 1 PID: 1174 at 
/build/linux-hwe-O570pP/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_display.c:1247
 assert_plane+0x98/0xa0 [i915]
[10947.862307]  nf_nat_ftp nf_nat binfmt_misc nf_conntrack_ftp nf_conntrack 
libcrc32c iptable_filter parport_pc ppdev ip_tables x_tables lp parport autofs4 
ums_realtek hid_generic usbhid hid uas usb_storage i915 i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops wmi sky2 
drm video
[10947.862365] RIP: 0010:assert_plane+0x98/0xa0 [i915]
[10947.862417]  assert_planes_disabled.isra.96+0x4d/0x70 [i915]
[10947.862453]  intel_disable_pipe+0x58/0x190 [i915]
[10947.862512]  i9xx_crtc_disable+0x7e/0x410 [i915]
[10947.862549]  intel_atomic_commit_tail+0x1f4/0xd90 [i915]
[10947.862585]  intel_atomic_commit+0x282/0x2b0 [i915]
[10947.862673]  intel_fbdev_set_par+0x1a/0x70 [i915]
[10947.880823] WARNING: CPU: 0 PID: 1174 at 
/build/linux-hwe-O570pP/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_display.c:1247
 assert_plane+0x98/0xa0 [i915]
[10947.880864]  nf_nat_ftp nf_nat binfmt_misc nf_conntrack_ftp nf_conntrack 
libcrc32c iptable_filter parport_pc ppdev ip_tables x_tables lp parport autofs4 
ums_realtek hid_generic usbhid hid uas usb_storage i915 i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops wmi sky2 
drm video
[10947.880921] RIP: 0010:assert_plane+0x98/0xa0 [i915]
[10947.880973]  assert_planes_disabled.isra.96+0x4d/0x70 [i915]
[10947.881009]  intel_enable_pipe+0x58/0x200 [i915]
[10947.881045]  i9xx_crtc_enable+0x373/0x480 [i915]
[10947.881082]  intel_update_crtc+0x47/0xa0 [i915]
[10947.881117]  intel_update_crtcs+0x5d/0x70 [i915]
[10947.881153]  intel_atomic_commit_tail+0x3ad/0xd90 [i915]
[10947.881189]  intel_atomic_commit+0x282/0x2b0 [i915]
[10947.881288]  intel_fbdev_set_par+0x1a/0x70 [i915]
[10947.900888] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
[11015.563288] WARNING: CPU: 0 PID: 997 at 
/build/linux-hwe-O570pP/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_display.c:1247
 assert_plane+0x98/0xa0 [i915]
[11015.563353]  nf_nat_ftp nf_nat binfmt_misc nf_conntrack_ftp nf_conntrack 
libcrc32c iptable_filter parport_pc ppdev ip_tables x_tables lp parport autofs4 
ums_realtek hid_generic usbhid hid uas usb_storage i915 i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops wmi sky2 
drm video
[11015.563430] RIP: 0010:assert_plane+0x98/0xa0 [i915]
[11015.563497]  assert_planes_disabled.isra.96+0x4d/0x70 [i915]
[11015.563542]  intel_disable_pipe+0x58/0x190 [i915]
[11015.563613]  i9xx_crtc_disable+0x7e/0x410 [i915]
[11015.563659]  intel_atomic_commit_tail+0x1f4/0xd90 [i915]
[11015.563704]  intel_atomic_commit+0x282/0x2b0 [i915]
[11015.588602] WARNING: CPU: 0 PID: 997 at 
/build/linux-hwe-O570pP/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_display.c:1247
 assert_plane+0x98/0xa0 [i915]
[11015.588684]  nf_nat_ftp nf_nat binfmt_misc nf_conntrack_ftp nf_conntrack 
libcrc32c iptable_filter parport_pc ppdev ip_tables x_tables lp parport autofs4 
ums_realtek hid_generic usbhid hid uas usb_storage i915 i2c_algo_bit 
drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt fb_sys_fops wmi sky2 
drm video
[11015.588785] RIP: 0010:assert_plane+0x98/0xa0 [i915]
[11015.588874]  assert_planes_disabled.isra.96+0x4d/0x70 [i915]
[11015.588934]  intel_enable_pipe+0x58/0x200 [i915]
[11015.588993]  i9xx_crtc_enable+0x373/0x480 [i915]
[11015.589054]  intel_update_crtc+0x47/0xa0 [i915]
[11015.589114]  intel_update_crtcs+0x5d/0x70 [i915]
[11015.589174]  intel_atomic_commit_tail+0x3ad/0xd90 [i915]
[11015.589234]  intel_atomic_commit+0x282/0x2b0 [i915]
[11015.606386] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun


** Attachment added: "shaju personal.ods"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+attachment/5224082/+files/shaju%20personal.ods

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

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  

[Kernel-packages] [Bug 1781904] Re: ThinkPad T460P Ultra Dock Can't dock it while running

[Martin Dünkelmann]

Linux Mint 19.1 Cinnamon
Installed the Linux Kernel HWE-18.04 stuff.
Now running 4.18.0-13-generic

Works fine.
But the standard kernel is still 4.15

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

Title:
  ThinkPad T460P Ultra Dock Can't dock it while running

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux deus-ex-machina 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13
  08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   LinuxMint
  Description:  Linux Mint 19 Tara
  Release:  19
  Codename: tara

  Ubuntu 18.04
  ThinkPad T460p

  I reject the dock and want to use the dock again.
  System hang, usb doesn't work, displays doesn't work.
  Nothing but the ethernet connection at the dock is working.

  The ThinkPad is working again, if I reject the dock.
  But to use the dock again, I need to restart the laptop.

  But I can reject the dock and plugin it again, while running the ThinkPad in 
Standby.
  Weird.

  I attached the dmesg log.

  I use the normal nvidia drivers from the repo (v390).
  Here is my lspci log (can only attach ONE file):

  00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers 
(rev 07)
   Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: skl_uncore

  00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:01.2 PCI bridge: Intel Corporation Skylake PCIe Controller (x4) (rev 07) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
   Capabilities: 
   Kernel driver in use: pcieport
   Kernel modules: shpchp

  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 530
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31) (prog-if 30 [XHCI])
   Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: xhci_hcd

  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
   Subsystem: Lenovo Sunrise Point-H Thermal subsystem
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: intel_pch_thermal
   Kernel modules: intel_pch_thermal

  00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI 
#1 (rev 31)
   Subsystem: Lenovo Sunrise Point-H CSME HECI
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: mei_me
   Kernel modules: mei_me

  00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller 
[AHCI mode] (rev 31) (prog-if 01 [AHCI 1.0])
   Subsystem: Lenovo Sunrise Point-H SATA Controller [AHCI mode]
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Kernel driver in use: ahci
   Kernel modules: ahci

  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port 
#1 (rev f1) (prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
    PriDiscTmr- SecDiscTmr- DiscTmrStat- 

[Kernel-packages] [Bug 1806343] Re: FN+F3/F4 does not modify keyboard backlight brightness.

[Kai-Heng Feng]

Not sure why "acpi_osi=" is uses in your kernel parameter, but please
remove it and see if it starts working.

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

Title:
  FN+F3/F4 does not modify keyboard backlight brightness.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  acpi_listen does not output anything to terminal when pressing key
  combination.

  Keyboard backlight has worked on older versions (I believe 18.04 or
  earlier.)

  I can manually toggle with:

  echo 0 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 1 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 2 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness
  echo 3 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness

  for varying degrees of brightness.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  disco
  Uname: Linux 4.19.6-041906-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  duck   3632 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2018-11-28 (22 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128)
  MachineType: ASUSTeK COMPUTER INC. GL502VMK
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/vg0-root ro quiet splash acpi_osi= acpi_backlight=native 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  Tags:  disco
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL502VMK.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL502VMK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL502VMK.305:bd07/03/2017:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL502VMK
  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/1806343/+subscriptions

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

[Kernel-packages] [Bug 1718761] Re: It's not possible to use OverlayFS (mount -t overlay) to stack directories on a ZFS volume

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: zfs-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  It's not possible to use OverlayFS (mount -t overlay) to stack
  directories on a ZFS volume

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  -- Configuration
  # echo -e $(grep VERSION= /etc/os-release)\\nSIGNATURE=\"$(cat 
/proc/version_signature)\"
  VERSION="16.04.3 LTS (Xenial Xerus)"
  SIGNATURE="Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17"
  # dpkg --list | grep zfs
  ii  libzfs2linux0.6.5.6-0ubuntu18
  ii  zfs-doc 0.6.5.6-0ubuntu18
  ii  zfs-initramfs   0.6.5.6-0ubuntu18
  ii  zfs-zed 0.6.5.6-0ubuntu18
  ii  zfsutils-linux  0.6.5.6-0ubuntu18

  -- Fault: Creating an overlay of multiple directories on a ZFS volume 
does not work
  # df /var/tmp
  Filesystem Type 1K-blocks  Used Available Use% Mounted on
  tank07/var/tmp zfs  129916288   128 129916160   1% /var/tmp
  # mkdir /var/tmp/{lower,middle,upper,workdir,overlay}
  # mount -t overlay overlay 
-olowerdir=/var/tmp/middle:/var/tmp/lower,upperdir=/var/tmp/upper,workdir=/var/tmp/workdir
 /var/tmp/overlay
  mount: wrong fs type, bad option, bad superblock on overlay,
 missing codepage or helper program, or other error

 In some cases useful info is found in syslog - try
 dmesg | tail or so.
  # dmesg|tail -1
  [276328.438284] overlayfs: filesystem on '/var/tmp/upper' not supported as 
upperdir

  -- Control test 1: Creating an overlay of multiple directories on 
another filesystem works
  # df /tmp
  Filesystem Type  1K-blocks   Used Available Use% Mounted on
  tmpfs  tmpfs   1048576 133492915084  13% /tmp
  # mkdir /tmp/{lower,middle,upper,workdir,overlay}
  # mount -t overlay overlay 
-olowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir 
/tmp/overlay
  # mount | grep overlay
  overlay on /tmp/overlay type overlay 
(rw,relatime,lowerdir=/tmp/middle:/tmp/lower,upperdir=/tmp/upper,workdir=/tmp/workdir)

  -- Control test 2: Creating an overlay using AuFS works on ZFS volume 
and elsewhere
  # mount -t aufs -obr=/tmp/lower:/tmp/middle:/tmp/upper:/tmp/workdir none 
/tmp/overlay
  # mount -t aufs 
-obr=/var/tmp/lower:/var/tmp/middle:/var/tmp/upper:/var/tmp/workdir none 
/var/tmp/overlay
  # mount | grep aufs
  none on /var/tmp/overlay type aufs (rw,relatime,si=9ead1ecae778b250)
  none on /tmp/overlay type aufs (rw,relatime,si=9ead1ec9257d1250)

  -- Remark
  While the use of AuFS can be used as a workaround in the above scenario, AuFS 
in turn will not work with [fuse.]glusterfs mounts (this has been documented 
elsewhere). Given that OverlayFS is part of the (upstream) kernel and Ubuntu 
now officially supports ZFS, the above should be fixed.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 18 16:12 seq
   crw-rw 1 root audio 116, 33 Sep 18 16:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci: Error: [Errno 2] No such file or directory
  Lsusb: Error: [Errno 2] No such file or directory
  MachineType: Red Hat KVM
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: 
BOOT_IMAGE=/ROOT/ubuntu1604@/boot/vmlinuz-4.10.0-35-generic 
root=ZFS=tank07/ROOT/ubuntu1604 ro
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.157.12
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.10.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.9.1-5.el7_3.3
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.chassis.version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.9.1-5.el7_3.3:bd04/01/2014:svnRedHat:pnKVM:pvrRHEL7.3.0PC(i440FX+PIIX,1996):cvnRedHat:ct1:cvrRHEL7.3.0PC(i440FX+PIIX,1996):
  dmi.product.name: KVM
  dmi.product.version: RHEL 7.3.0 PC (i440FX + PIIX, 1996)
  dmi.sys.vendor: Red Hat
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 18 16:12 seq
   crw-rw 1 root audio 116, 33 Sep 18 16:12 

[Kernel-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04

[LGB [Gábor Lénárt]]

Lenovo ThinkPad L580:

$ cat /sys/bus/serio/devices/serio1/firmware_id
PNP: LEN2037 PNP0f13

$ dmesg | fgrep -i elan
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8ee3c188-2063-45de-b270-2db3df928e18 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=1
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=8ee3c188-2063-45de-b270-2db3df928e18 ro psmouse.elantech_smbus=0 
quiet splash vt.handoff=1
[2.432975] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x5f3001)
[2.449022] psmouse serio1: elantech: Synaptics capabilities query result 
0x90, 0x18, 0x10.
[2.464414] psmouse serio1: elantech: Elan sample query result 00, 22, c8
[2.526860] input: ETPS/2 Elantech TrackPoint as 
/devices/platform/i8042/serio1/input/input6
[2.545342] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input5

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

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Confirmed affected laptops:
  ThinkPad: 
  L480
  L580
  P72
  P52

  
  When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech touchpad 
stopped working. This means it is not recognized at all. This problem occured 
after the first boot in 18.10

  `dmesg | grep -i elantech` shows the following errors:

  [3.409043] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [3.427372] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8
  [3.464905] psmouse serio1: elantech: Trying to set up SMBus access
  [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy 
regulator
  [5.586505] elan_i2c 0-0015: failed to get resolution: -71
  [5.586527] elan_i2c: probe of 0-0015 failed with error -71

  uname:

  $ uname -a
  Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  I found the following thread which solves the problem temporarly (and reports 
the same problem in Arch):
  https://bugs.archlinux.org/task/59714

  Running the following command enables it again for the current
  session:

  sudo sh -c 'echo -n "elantech">
  /sys/bus/serio/devices/serio1/protocol'

  dmesg afterwards:

  [  569.522490] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [  569.544584] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [  569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8

  Before running the fix:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETSMBus

  and after:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETPS/2

  After reboot the command has to be run again, of course.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Nov 15 20:59:36 2018
  DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2018-08-06 (101 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LS001AGE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago)
  dmi.bios.date: 02/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET37W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LS001AGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1803929] Re: Summary: Kernel bug (unhandled paging request) on "udisksctl power-off"

[mintbug]

Hi there, the problem persists in the same way in kernel 4.4.0-141 :-(

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

Title:
  Summary: Kernel bug (unhandled paging request) on "udisksctl power-
  off"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04

  uname -a
  Linux metabox 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Steps (1) to reproduce:
  1) Plug in a USB3 hard drive.
  2) Right click on launcher icon.
  3) Select "Safely Remove".

  After finding this: https://askubuntu.com/a/532691
  ...the following steps also reproduce the problem.

  Steps (2) to reproduce:
  1) Plugin in a USB3 hard drive.
  2) udisksctl unmount -b /dev/sdXY
  3) udisksctl power-off -b /dev/sdX

  System completely locks and becomes unresponsive, such that even the Magic 
SysRq key combination does nothing.
  Most of the time the fans on my laptop go crazy (so the CPU must get stuck in 
some loop), but once they did not and the system was just locked (without the 
fans going nuts).

  I can't get a textual copy of the kernel bug log (because I have to do a hard 
reset to regain control of the system and the output doesn't get flushed to 
disk), but I did manage to get a photo of some of it (please refer to 
attachment).
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   matt   2754 F...m pulseaudio
   /dev/snd/controlC1:  matt   2754 F pulseaudio
   /dev/snd/controlC0:  matt   2754 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f00235c0-ba8a-4403-91b1-64e9d87b76e0
  InstallationDate: Installed on 2016-04-23 (940 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook N150SD/N155SD
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-139-generic 
root=UUID=beb9b9ce-39a7-464a-978c-ac4fb82a5a81 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.4.0-139-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/31/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150SD/N155SD
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd03/31/2015:svnNotebook:pnN150SD/N155SD:pvrNotApplicable:rvnNotebook:rnN150SD/N155SD:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: N150SD/N155SD
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Yingfang]

@ian-x88 Hi Ian, nothing changed, so no solution for now. I am
considering to buy a new laptop. The problem makes me feel so confused
and upset. The SSD is Samsung 250 GB 860 EVO Sata III 64L V NAND Solid
State Drive. The infinite loop for ext4 fs error occur irregularly,
might be twice an hour or whole night works well.

I post my issue on below link:
https://askubuntu.com/questions/1100838/ext4-fs-error-device-sda2-ext4-find-entry1436-ubuntu-18-04

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1809439] Re: cpu_hot_plug test in ubuntu_kernel_selftest failed on B s390x KVM

[Po-Hsu Lin]

This issue looks like a bug for s390x in the kernel.

There are only two processors listed on this Bionic s390x KVM, not sure
why it will report CPU 0-1 are in online state, 2 in offline state:

$ cat /proc/cpuinfo 
vendor_id   : IBM/S390
# processors: 2
bogomips per cpu: 3033.00
max thread id   : 0
features: esan3 zarch stfle msa ldisp eimm dfp edat etf3eh highgprs te 
vx 
facilities  : 0 1 2 3 4 6 7 8 9 10 13 14 16 17 18 19 20 21 22 23 24 25 26 
27 28 30 31 32 33 34 35 36 37 40 41 42 43 44 45 47 48 49 50 51 52 53 57 64 69 
71 73 74 75 76 77 78 80 81 82 129 131 138
cache0  : level=1 type=Data scope=Private size=128K line_size=256 
associativity=8
cache1  : level=1 type=Instruction scope=Private size=96K line_size=256 
associativity=6
cache2  : level=2 type=Data scope=Private size=2048K line_size=256 
associativity=8
cache3  : level=2 type=Instruction scope=Private size=2048K 
line_size=256 associativity=8
cache4  : level=3 type=Unified scope=Shared size=65536K line_size=256 
associativity=16
cache5  : level=4 type=Unified scope=Shared size=491520K line_size=256 
associativity=30
processor 0: version = FF,  identification = 268F67,  machine = 2964
processor 1: version = FF,  identification = 268F67,  machine = 2964

cpu number  : 0
cpu MHz dynamic : 5000
cpu MHz static  : 5000

cpu number  : 1
cpu MHz dynamic : 5000
cpu MHz static  : 5000

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

Title:
  cpu_hot_plug test in ubuntu_kernel_selftest failed on B s390x KVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests
  make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  TAP version 13
  selftests: cpu-on-off-test.sh
  
  pid 18238's current affinity mask: 3
  pid 18238's new affinity mask: 1
  CPU online/offline summary:
 Cpus in online state: 0-1
 Cpus in offline state: 2
  Limited scope test: one hotplug cpu
 (leaves cpu in the original state):
 online to offline to online: cpu 1
 offline to online to offline: cpu 2
  ./cpu-on-off-test.sh: line 85: /sys/devices/system/cpu/cpu2/online: No such 
file or directory
  online_cpu_expect_success 2: unexpected fail
  not ok 1..1 selftests:  cpu-on-off-test.sh [FAIL]
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Fri Dec 21 10:38:05 2018
  HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809439/+subscriptions

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

[Kernel-packages] [Bug 1806422] Re: linux-azure: 4.18.0-1007.7 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 4.18.0-1007.7

---
linux-azure (4.18.0-1007.7) cosmic; urgency=medium

  * linux-azure: 4.18.0-1007.7 -proposed tracker (LP: #1806422)

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- [Packaging] update update.conf

  [ Ubuntu: 4.18.0-13.14 ]

  * linux: 4.18.0-13.14 -proposed tracker (LP: #1806409)
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * Regression: hinic performance degrades over time (LP: #1805248)
- Revert "net-next/hinic: add checksum offload and TSO support"
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.

 -- Marcelo Henrique Cerri   Thu, 06 Dec
2018 18:04:26 +

** Changed in: linux-azure (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  linux-azure: 4.18.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Released
  phase-changed: Thursday, 20. December 2018 06:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806422/+subscriptions

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

[Kernel-packages] [Bug 1806838] Re: Workaround CSS timeout on AMD SNPS 3.0 xHC

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

** Changed in: linux-oem (Ubuntu Disco)
   Status: New => Fix Released

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

Title:
  Workaround CSS timeout on AMD SNPS 3.0 xHC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Raven Ridge xHC may fail to suspend, causes the USB stops working, and blocks 
the system entering system-wide suspend.

  [Fix]
  It's a hardware/firmware bug, workarounded by bailing out suspend function if 
it ever fails, and reset the xHC in next resume function.

  [Test]
  After applying the patch, the USB works, and the system can enter S3 
consecutively.

  [Regression Potential]
  Minimal. This workaround only applies to AMD Raven Ridge xHC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806838/+subscriptions

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

[Kernel-packages] [Bug 1809439] Missing required logs.

[Ubuntu Kernel Bot]

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 1809439

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  cpu_hot_plug test in ubuntu_kernel_selftest failed on B s390x KVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests
  make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  TAP version 13
  selftests: cpu-on-off-test.sh
  
  pid 18238's current affinity mask: 3
  pid 18238's new affinity mask: 1
  CPU online/offline summary:
 Cpus in online state: 0-1
 Cpus in offline state: 2
  Limited scope test: one hotplug cpu
 (leaves cpu in the original state):
 online to offline to online: cpu 1
 offline to online to offline: cpu 2
  ./cpu-on-off-test.sh: line 85: /sys/devices/system/cpu/cpu2/online: No such 
file or directory
  online_cpu_expect_success 2: unexpected fail
  not ok 1..1 selftests:  cpu-on-off-test.sh [FAIL]
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Fri Dec 21 10:38:05 2018
  HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809439/+subscriptions

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

[Kernel-packages] [Bug 1806424] Re: linux-kvm: 4.18.0-1006.6 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-kvm - 4.18.0-1006.6

---
linux-kvm (4.18.0-1006.6) cosmic; urgency=medium

  * linux-kvm: 4.18.0-1006.6 -proposed tracker (LP: #1806424)

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- [Packaging] update update.conf

  [ Ubuntu: 4.18.0-13.14 ]

  * linux: 4.18.0-13.14 -proposed tracker (LP: #1806409)
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * Regression: hinic performance degrades over time (LP: #1805248)
- Revert "net-next/hinic: add checksum offload and TSO support"
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.

 -- Stefan Bader   Wed, 05 Dec 2018 16:45:55
+0100

** Changed in: linux-kvm (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  linux-kvm: 4.18.0-1006.6 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Cosmic:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Released
  phase-changed: Thursday, 20. December 2018 06:09 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806424/+subscriptions

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

[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

** Changed in: linux-oem (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads to other devices not getting there during long idle or s2idle. And 
it also prevents the system from entering deeper PC state other than PC3.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1781533/+subscriptions

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

[Kernel-packages] [Bug 1806420] Re: linux-aws: 4.18.0-1007.9 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 4.18.0-1007.9

---
linux-aws (4.18.0-1007.9) cosmic; urgency=medium

  * linux-aws: 4.18.0-1007.9 -proposed tracker (LP: #1806420)

  [ Ubuntu: 4.18.0-13.14 ]

  * linux: 4.18.0-13.14 -proposed tracker (LP: #1806409)
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * Regression: hinic performance degrades over time (LP: #1805248)
- Revert "net-next/hinic: add checksum offload and TSO support"
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.

 -- Khalid Elmously   Thu, 06 Dec 2018
18:17:37 +

** Changed in: linux-aws (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  linux-aws: 4.18.0-1007.9 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Cosmic:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Released
  phase-changed: Thursday, 20. December 2018 06:13 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806420/+subscriptions

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

[Kernel-packages] [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector

[TJ]

daftykins:

Your issue is there is no handler so you won't find anything in
debug/irg for it:

[ 167.279809] do_IRQ: 1.35 No irq handler for vector

HOWEVER, you should be able to find which target device is responsible
by searching for matching Target: value, e.g. something like:

$ grep -l 'Target: 1' /sys/kernel/debug/irq/irqs/*

Examine/report the matching targets which should help identify the PCI
bus *device* id (e.g. "device: :00:16.0" in the report for
irqs/126). Correlate that to the output of:

$ lspci -nnk

>From our previous IRC discussions you already know I believe it is the
NIC since these reports only start once the NIC interface moves to UP
state.

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

Title:
  Slow flood of do_IRQ: No irq for vector

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Every few seconds I get something like this in my dmesg:

  [44984.933221] do_IRQ: 1.34 No irq handler for vector
  [44986.933976] do_IRQ: 1.34 No irq handler for vector
  [44991.935614] do_IRQ: 1.34 No irq handler for vector
  [45004.938590] do_IRQ: 1.34 No irq handler for vector
  [45005.939002] do_IRQ: 4.34 No irq handler for vector
  [45034.949161] do_IRQ: 4.34 No irq handler for vector
  [45051.954569] do_IRQ: 4.34 No irq handler for vector
  [45058.956019] do_IRQ: 4.34 No irq handler for vector
  [45062.957727] do_IRQ: 4.34 No irq handler for vector
  [45063.958204] do_IRQ: 4.34 No irq handler for vector
  [45073.961103] do_IRQ: 4.34 No irq handler for vector

  The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34,
  7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log
  is just messages like above with varying #.## numbers.

  I researched it and tried disabling irqbalance. It had no effect, the
  messages continued.

  The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS.
  I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2
  NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never
  occurred before installing 18.03 on the same hardware. No overclocking
  whatsoever has ever been done to this machine.

  Also, I had to disable selective suspend on USB in this version to
  prevent major USB issues, which was not required in 17.10, that might
  be related.

  My system seems stable, but spurious IRQs can't be good. I'd like to
  resolve this if possible.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-26-generic 4.15.0-26.28
  ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18
  Uname: Linux 4.15.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
   /dev/snd/controlC1:  gdm2145 F pulseaudio
doug   3736 F pulseaudio
  Date: Tue Jul 10 12:49:00 2018
  HibernationDevice:
   
  InstallationDate: Installed on 2017-06-26 (379 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic 
root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal 
video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-26-generic N/A
   linux-backports-modules-4.15.0-26-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4011
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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:

[Kernel-packages] [Bug 1809423] Re: General Performance Is "slow" including stuttering when dragging windows around etc (nvidia-390 is installed but modesetting in use)

[Nicholas Davis]

Hi,

So far I have been unable to find out how to enable the drivers as you
suggested I will continue searching.

Thanks

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

Title:
  General Performance Is "slow" including stuttering when dragging
  windows around etc (nvidia-390 is installed but modesetting in use)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  System information included in debug log.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 21 19:43:06 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.87, 4.18.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1080] 
[1458:3717]
  InstallationDate: Installed on 2018-12-21 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-AR:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1809423/+subscriptions

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

[Kernel-packages] [Bug 1809439] [NEW] cpu_hot_plug test in ubuntu_kernel_selftest failed on B s390x KVM

[Po-Hsu Lin]

Public bug reported:

$ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests
make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests'
make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
TAP version 13
selftests: cpu-on-off-test.sh

pid 18238's current affinity mask: 3
pid 18238's new affinity mask: 1
CPU online/offline summary:
 Cpus in online state: 0-1
 Cpus in offline state: 2
Limited scope test: one hotplug cpu
 (leaves cpu in the original state):
 online to offline to online: cpu 1
 offline to online to offline: cpu 2
./cpu-on-off-test.sh: line 85: /sys/devices/system/cpu/cpu2/online: No such 
file or directory
online_cpu_expect_success 2: unexpected fail
not ok 1..1 selftests:  cpu-on-off-test.sh [FAIL]
make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic s390x
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
CurrentDmesg:
 
Date: Fri Dec 21 10:38:05 2018
HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lspci:
 
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
 
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 
crashkernel=196M
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-43-generic N/A
 linux-backports-modules-4.15.0-43-generic  N/A
 linux-firmware 1.173.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: apport-bug bionic s390x

** Also affects: ubuntu-kernel-tests
   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/1809439

Title:
  cpu_hot_plug test in ubuntu_kernel_selftest failed on B s390x KVM

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests
  make: Entering directory '/home/ubuntu/src/linux/tools/testing/selftests'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Nothing to be done for 'all'.
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make[1]: Entering directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  TAP version 13
  selftests: cpu-on-off-test.sh
  
  pid 18238's current affinity mask: 3
  pid 18238's new affinity mask: 1
  CPU online/offline summary:
 Cpus in online state: 0-1
 Cpus in offline state: 2
  Limited scope test: one hotplug cpu
 (leaves cpu in the original state):
 online to offline to online: cpu 1
 offline to online to offline: cpu 2
  ./cpu-on-off-test.sh: line 85: /sys/devices/system/cpu/cpu2/online: No such 
file or directory
  online_cpu_expect_success 2: unexpected fail
  not ok 1..1 selftests:  cpu-on-off-test.sh [FAIL]
  make[1]: Leaving directory 
'/home/ubuntu/src/linux/tools/testing/selftests/cpu-hotplug'
  make: Leaving directory '/home/ubuntu/src/linux/tools/testing/selftests'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic s390x
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: 

[Kernel-packages] [Bug 1805617] Re: linux-oem: 4.15.0-1029.34 -proposed tracker

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 1806663 ***
https://bugs.launchpad.net/bugs/1806663

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

** Changed in: linux-oem (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  linux-oem: 4.15.0-1029.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1803592
  phase: Promoted to proposed
  phase-changed: Tuesday, 04. December 2018 11:38 UTC
  proposed-announcement-sent: true
  

[Kernel-packages] [Bug 1805088] Re: iwlwifi fails to work on 16 or more logical CPUs machines

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

** Changed in: linux-oem (Ubuntu)
   Status: New => Fix Released

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

Title:
  iwlwifi fails to work on 16 or more logical CPUs machines

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Got dmesg kernel BUG while loading iwlwifi driver on machines which has 16 or 
more logical CPUs
 kernel: RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi]
  And it leads to wifi can't scan any APs, and leads to system hangs while 
suspending.

  [Fix]
  Below commit contained in v4.17 fix the issue.
 ab1068d6866e iwlwifi: pcie: compare with number of IRQs requested for, not 
number of CPUs

  [Regression Potential]
  Low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805088/+subscriptions

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

[Kernel-packages] [Bug 1805607] Re: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

** Changed in: linux-oem (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless
  Network Adapter

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  It drains power more than 0.5 Watt after power off(S5) the machine with 
QCA9377 wifi card. The power consumption should be lower than 0.5 Watt, or it 
won't pass E-star 7.

  [Fix]
  Qualcomm provides this fix, and the power consumption becomes 0.23 Watt at 
S5. This fix doesn't submit to upstream yet, Qualcomm is still working on it.

  [Test]
  Verified on Dell machines, it works.

  [Regression Potential]
  Low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1805607/+subscriptions

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

[Kernel-packages] [Bug 1802813] Re: Fix "incomplete report" noise after S3

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

** Changed in: linux-oem (Ubuntu)
   Status: New => Fix Released

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

Title:
  Fix "incomplete report" noise after S3

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  I2C HID devices may keep spewing out error "i2c_hid_get_input:
  incomplete report (30/2)" after system S3.

  [Fix]
  It a regression caused by commit ac75a041048b, backport commmit
  ef6eaf27274c to fix it. Input report length 2 is a valid length.

  [Test]
  With the fix the issue can no longer be observed on Alps touchpads.

  [Regression Potential]
  None. Input report lenght 2 is valid per spec.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1802813/+subscriptions

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

[Kernel-packages] [Bug 1806838] Re: Workaround CSS timeout on AMD SNPS 3.0 xHC

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

** Changed in: linux-oem (Ubuntu Cosmic)
   Status: New => Fix Released

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

Title:
  Workaround CSS timeout on AMD SNPS 3.0 xHC

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Committed
Status in linux-oem source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  New

Bug description:
  [Impact]
  Raven Ridge xHC may fail to suspend, causes the USB stops working, and blocks 
the system entering system-wide suspend.

  [Fix]
  It's a hardware/firmware bug, workarounded by bailing out suspend function if 
it ever fails, and reset the xHC in next resume function.

  [Test]
  After applying the patch, the USB works, and the system can enter S3 
consecutively.

  [Regression Potential]
  Minimal. This workaround only applies to AMD Raven Ridge xHC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806838/+subscriptions

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

[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

** Changed in: linux-oem (Ubuntu Cosmic)
   Status: Invalid => Fix Released

** Changed in: linux-oem (Ubuntu Cosmic)
   Status: Invalid => Fix Released

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

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads to other devices not getting there during long idle or s2idle. And 
it also prevents the system from entering deeper PC state other than PC3.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1781533/+subscriptions

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

[Kernel-packages] [Bug 1806663] Re: linux-oem: 4.15.0-1030.35 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

** Changed in: linux-oem (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  linux-oem: 4.15.0-1030.35 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Released
  phase-changed: Thursday, 20. December 2018 06:15 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1781533] Re: SATA device is not going to DEVSLP

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem - 4.15.0-1030.35

---
linux-oem (4.15.0-1030.35) bionic; urgency=medium

  * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663)

  * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339)
- SAUCE: (no-up) add IXXAT USB-to-CAN driver

  * Add support for 0cf3:535b QCA_ROME device (LP: #1807333)
- Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device

  * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342)
- qmi_wwan: add support for the Dell Wireless 5821e module
- qmi_wwan: fix interface number for DW5821e production firmware
- USB: option: add support for DW5821e

  * Fix Terminus USB hub that may breaks connected USB devices after S3
(LP: #1806850)
- USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub

  * The line-out on the Dell Dock station can't work (LP: #1806532)
- ALSA: usb-audio: Allow to override the longname string
- ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock
- ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock

  * Enable new Realtek card reader (LP: #1806335)
- USB: usb-storage: Add new IDs to ums-realtek
- SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek

  [ Ubuntu: 4.15.0-43.46 ]

  * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659)
  * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942)
- SAUCE: base/dd: limit release function changes to vfio driver only
  * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838)
- xhci: Allow more than 32 quirks
- xhci: workaround CSS timeout on AMD SNPS 3.0 xHC
  * linux-buildinfo: pull out ABI information into its own package
(LP: #1806380)
- [Packaging] limit preparation to linux-libc-dev in headers
- [Packaging] commonise debhelper invocation
- [Packaging] ABI -- accumulate abi information at the end of the build
- [Packaging] buildinfo -- add basic build information
- [Packaging] buildinfo -- add firmware information to the flavour ABI
- [Packaging] buildinfo -- add compiler information to the flavour ABI
- [Packaging] buildinfo -- add buildinfo support to getabis
- [Config] buildinfo -- add retpoline version markers
  * linux packages should own /usr/lib/linux/triggers (LP: #1770256)
- [Packaging] own /usr/lib/linux/triggers
  * CVE-2018-12896
- posix-timers: Sanitize overrun handling
  * CVE-2018-16276
- USB: yurex: fix out-of-bounds uaccess in read handler
  * CVE-2018-10902
- ALSA: rawmidi: Change resized buffers atomically
  * CVE-2018-18710
- cdrom: fix improper type cast, which can leat to information leak.
  * CVE-2018-18690
- xfs: don't fail when converting shortform attr to long form during
  ATTR_REPLACE
  * CVE-2018-14734
- infiniband: fix a possible use-after-free bug
  * CVE-2018-18445
- bpf: 32-bit RSH verification must truncate input before the ALU op
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts

 -- Chia-Lin Kao (AceLan)   Sat, 08 Dec 2018
11:02:54 +0800

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

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads to other devices not getting there during long idle or s2idle. And 
it also prevents the system from entering deeper PC state other than PC3.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1781533/+subscriptions

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