[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 wont boot as Xen-DomU with PVH

2019-06-12 Thread David Kowis
Also does not boot for linux-image-4.15.0-51-generic

>From the xl console output trying to boot that kernel. Previous kernels
have no problem.

libxl: error: libxl_xshelp.c:201:libxl__xs_read_mandatory: xenstore read 
failed: `/libxl/45/type': No such file or directory
libxl: warning: libxl_dom.c:52:libxl__domain_type: unable to get domain type 
for domid=45, assuming HVM
xenconsole: Could not read tty from store: No such file or directory
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: console child 
[3420] exited with error status 2
root@nosgoth:/etc/xen/conf#

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

Title:
  Kernel 4.15.0-50 wont boot as Xen-DomU with PVH

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New

Bug description:
  After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel 
crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works).
  Kernel 4.15.0-48 and prior did boot without any problems as PVH.

  We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50.
  Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH-
  DomU.

  See also https://lists.xenproject.org/archives/html/xen-
  users/2019-05/msg00010.html

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

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


[Kernel-packages] [Bug 1829378] Re: Kernel 4.15.0-50 wont boot as Xen-DomU with PVH

2019-06-12 Thread David Kowis
https://lists.xenproject.org/archives/html/xen-
users/2019-05/txtiEUldDuKY9.txt

This is the stacktrace/log that was originally captured by the filer.

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

Title:
  Kernel 4.15.0-50 wont boot as Xen-DomU with PVH

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New

Bug description:
  After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel 
crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works).
  Kernel 4.15.0-48 and prior did boot without any problems as PVH.

  We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50.
  Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH-
  DomU.

  See also https://lists.xenproject.org/archives/html/xen-
  users/2019-05/msg00010.html

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

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


[Kernel-packages] [Bug 1807974] Re: Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic on Dell XPS 13 9370

2020-11-09 Thread David Kowis
This happens for me quite often on 20.10:

02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)

I can barely stay attached to wifi.

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

Title:
  Qualcomm Atheros QCA617 [168c:003e] Subsystem [1a56:143a] Wireless
  regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
  on Dell XPS 13 9370

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
  Cosmic. A handful of times per day, my wireless stops working ("?"
  appears in the icon in Network Manager). Turning wireless off and then
  on again, or suspending and waking the machine up, makes the wireless
  work again.

  dmesg output is as follows:

  $ dmesg | grep ath10k

  [ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid 
6317c652-4817-4fdd-b6d7-c7b8336e493f)
  [ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [ 6646.270369] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
  [ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800  29  29 106 107
  [ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00  20  19  18  19
  [ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000   8   8  10   8
  [ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
  [ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0   6   6
  [ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
  [ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
  [ 6647.239340] ath10k_pci :02:00.0: device successfully recovered

  
  [17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid 
03393f2f-0ce1-4017-b711-40dd14f2ec11)
  [17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [17641.848065] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
  [17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800   6   6 243 244
  [17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00  53  52  51  52
  [17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000   5   5   7   5
  [17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
  [17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0  30  30
  [17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
  [17642.835601] ath10k_pci :02:00.0: device successfully recovered
  [17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118

  I do not recall having any wireless issues before I upgraded (when
  this machine was running Bionic).

  Bug #1730331 - ath10k_pci: firmware crashed!
  Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
  could be related, but appear to be related to earlier releases, whereas my 
issue has appeared/become much worse on Cosmic.

  

[Kernel-packages] [Bug 1698616] [NEW] 4.10.0-22 No longer suspends on Dell XPS 9560

2017-06-17 Thread David Kowis
Public bug reported:

I have to roll back to -21 to be able to suspend.

Linux XPS 4.10.0-21-lowlatency #23~16.04.1-Ubuntu SMP PREEMPT Tue May 2
14:25:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

With -22, it doesn't suspend, and has lots of trouble with it.

I expect to be able to suspend when I close the laptop lid, or when I go
to suspend from the power menu. Instead the OS acts like it suspends,
but the laptop doesn't power down anything. The display remains on, the
fans continue to spin. It acts like it has, because it takes a bit for
the keyboard to respond, and the mouse to move again, and the wifi was
disconnected. It's just that the hardware doesn't power down at all.

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

Title:
  4.10.0-22 No longer suspends on Dell XPS 9560

Status in linux package in Ubuntu:
  New

Bug description:
  I have to roll back to -21 to be able to suspend.

  Linux XPS 4.10.0-21-lowlatency #23~16.04.1-Ubuntu SMP PREEMPT Tue May
  2 14:25:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  With -22, it doesn't suspend, and has lots of trouble with it.

  I expect to be able to suspend when I close the laptop lid, or when I
  go to suspend from the power menu. Instead the OS acts like it
  suspends, but the laptop doesn't power down anything. The display
  remains on, the fans continue to spin. It acts like it has, because it
  takes a bit for the keyboard to respond, and the mouse to move again,
  and the wifi was disconnected. It's just that the hardware doesn't
  power down at all.

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

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


[Kernel-packages] [Bug 1698616] Re: 4.10.0-22 No longer suspends on Dell XPS 9560

2017-06-17 Thread David Kowis
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698508

mentions the same symptoms, but it also talks about failures during
install. I don't have these failures, only the suspend problem.

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

Title:
  4.10.0-22 No longer suspends on Dell XPS 9560

Status in linux package in Ubuntu:
  New

Bug description:
  I have to roll back to -21 to be able to suspend.

  Linux XPS 4.10.0-21-lowlatency #23~16.04.1-Ubuntu SMP PREEMPT Tue May
  2 14:25:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  With -22, it doesn't suspend, and has lots of trouble with it.

  I expect to be able to suspend when I close the laptop lid, or when I
  go to suspend from the power menu. Instead the OS acts like it
  suspends, but the laptop doesn't power down anything. The display
  remains on, the fans continue to spin. It acts like it has, because it
  takes a bit for the keyboard to respond, and the mouse to move again,
  and the wifi was disconnected. It's just that the hardware doesn't
  power down at all.

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

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


[Kernel-packages] [Bug 1698616] Re: 4.10.0-22 No longer suspends on Dell XPS 9560

2017-06-29 Thread David Kowis
~ > uname -a
Linux XPS 4.12.0-041200rc5-lowlatency #201706112031 SMP PREEMPT Mon Jun 12 
00:38:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


Suspends just fine, so i'll tag it with "kernel-fixed-upstream"

** Tags added: kernel-fixed-upstream

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

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

Title:
  4.10.0-22 No longer suspends on Dell XPS 9560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have to roll back to -21 to be able to suspend.

  Linux XPS 4.10.0-21-lowlatency #23~16.04.1-Ubuntu SMP PREEMPT Tue May
  2 14:25:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  With -22, it doesn't suspend, and has lots of trouble with it.

  I expect to be able to suspend when I close the laptop lid, or when I
  go to suspend from the power menu. Instead the OS acts like it
  suspends, but the laptop doesn't power down anything. The display
  remains on, the fans continue to spin. It acts like it has, because it
  takes a bit for the keyboard to respond, and the mouse to move again,
  and the wifi was disconnected. It's just that the hardware doesn't
  power down at all.

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

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


[Kernel-packages] [Bug 1698616] Re: 4.10.0-22 No longer suspends on Dell XPS 9560

2017-07-15 Thread David Kowis
Still present in -26

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

Title:
  4.10.0-22 No longer suspends on Dell XPS 9560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have to roll back to -21 to be able to suspend.

  Linux XPS 4.10.0-21-lowlatency #23~16.04.1-Ubuntu SMP PREEMPT Tue May
  2 14:25:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  With -22, it doesn't suspend, and has lots of trouble with it.

  I expect to be able to suspend when I close the laptop lid, or when I
  go to suspend from the power menu. Instead the OS acts like it
  suspends, but the laptop doesn't power down anything. The display
  remains on, the fans continue to spin. It acts like it has, because it
  takes a bit for the keyboard to respond, and the mouse to move again,
  and the wifi was disconnected. It's just that the hardware doesn't
  power down at all.

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

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


[Kernel-packages] [Bug 1698616] Re: 4.10.0-22 No longer suspends on Dell XPS 9560

2017-07-20 Thread David Kowis
> I guess it's pretty similar to LP: #1697556. Try blacklisting nouveau.

Good guess, it is indeed. Blacklisting nouveau and things suspend just
fine.

of note, I'm using the intel graphics adaptor exclusively, and don't
even have the nvidia drivers installed at the moment.

But this gets me to an up-to-date (at least with ubuntu) kernel! 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/1698616

Title:
  4.10.0-22 No longer suspends on Dell XPS 9560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have to roll back to -21 to be able to suspend.

  Linux XPS 4.10.0-21-lowlatency #23~16.04.1-Ubuntu SMP PREEMPT Tue May
  2 14:25:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  With -22, it doesn't suspend, and has lots of trouble with it.

  I expect to be able to suspend when I close the laptop lid, or when I
  go to suspend from the power menu. Instead the OS acts like it
  suspends, but the laptop doesn't power down anything. The display
  remains on, the fans continue to spin. It acts like it has, because it
  takes a bit for the keyboard to respond, and the mouse to move again,
  and the wifi was disconnected. It's just that the hardware doesn't
  power down at all.

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

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