[Kernel-packages] [Bug 1799988] Re: Missing wifi and bluetooth after sleep on XPS 9370

2019-02-08 Thread Raphael Kimmig
I'm now running the patches against 4.20.7 with
firmware=RM.4.4.1.c2-00057-QCARMSWP-1 and I'm seeing some issues in the
log after resume, however the wifi does work fine.

Feb 09 08:13:21 hostname kernel: ACPI: Waking up from system sleep state S3
Feb 09 08:13:21 hostname kernel: ACPI: EC: interrupt unblocked
Feb 09 08:13:21 hostname kernel: ACPI: EC: event unblocked
Feb 09 08:13:21 hostname kernel: ath10k_pci :02:00.0: unsupported HTC 
service id: 1536
Feb 09 08:13:21 hostname kernel: ath10k_pci :02:00.0: Unknown eventid: 
118809
Feb 09 08:13:21 hostname kernel: WARNING: CPU: 2 PID: 26770 at 
drivers/net/wireless/ath/ath10k/mac.c:5650 ath10k_bss_info_changed+0xe8e/0xfd0 
[ath10k_core]
Feb 09 08:13:21 hostname kernel: Modules linked in: cmac rfcomm bnep btusb 
btrtl btbcm btintel bluetooth ecdh_generic ath10k_pci ath10k_core mac80211 ath 
cfg80211 thunderbolt fuse ccm xt_CHECKSUM ipt_MASQUERADE tun bridge stp llc 
devlink nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter 
ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ip6table_nat nf_nat_ipv6 
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat_ipv4 nf_nat 
iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables 
ip6table_filter ip6_tables sunrpc vfat fat arc4 hid_multitouch 
snd_hda_codec_hdmi snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match 
snd_soc_acpi snd_soc_core snd_hda_codec_realtek intel_rapl 
snd_hda_codec_generic snd_compress x86_pkg_temp_thermal intel_powerclamp 
ac97_bus iTCO_wdt coretemp snd_pcm_dmaengine dell_laptop iTCO_vendor_support 
mei_wdt kvm_intel
Feb 09 08:13:21 hostname kernel:  snd_hda_intel intel_cstate snd_hda_codec 
snd_hda_core snd_hwdep intel_uncore snd_seq intel_rapl_perf snd_seq_device 
snd_pcm dell_wmi uvcvideo dell_smbios joydev videobuf2_vmalloc dcdbas snd_timer 
videobuf2_memops videobuf2_v4l2 snd videobuf2_common wmi_bmof 
dell_wmi_descriptor intel_wmi_thunderbolt videodev soundcore rtsx_pci_ms mei_me 
cdc_acm memstick i2c_i801 media idma64 mei rfkill processor_thermal_device 
intel_lpss_pci ucsi_acpi typec_ucsi intel_lpss intel_soc_dts_iosf 
intel_pch_thermal typec intel_hid sparse_keymap int3403_thermal int3400_thermal 
int340x_thermal_zone acpi_thermal_rel pcc_cpufreq acpi_pad dm_crypt 
hid_logitech_hidpp hid_logitech_dj i915 r8152 mii kvmgt mdev vfio kvm 
rtsx_pci_sdmmc irqbypass mmc_core i2c_algo_bit drm_kms_helper crct10dif_pclmul 
crc32_pclmul crc32c_intel drm nvme ghash_clmulni_intel serio_raw rtsx_pci wmi 
i2c_hid nvme_core video pinctrl_sunrisepoint pinctrl_intel [last unloaded: 
cfg80211]
Feb 09 08:13:21 hostname kernel: CPU: 2 PID: 26770 Comm: kworker/u16:1 Tainted: 
GW 
4.20.7-201.0001_fix_ath10k_sleep_wake_issue.patch.fc29.x86_64 #1
Feb 09 08:13:21 hostname kernel: Hardware name: Dell Inc. XPS 13 9370/0F6P3V, 
BIOS 1.6.3 11/04/2018
Feb 09 08:13:21 hostname kernel: Workqueue: events_unbound async_run_entry_fn
Feb 09 08:13:21 hostname kernel: RIP: 0010:ath10k_bss_info_changed+0xe8e/0xfd0 
[ath10k_core]
Feb 09 08:13:21 hostname kernel: Code: 89 c1 89 f2 4c 89 d7 48 c7 c6 80 ae 04 
c1 4c 89 4c 24 10 89 44 24 08 e8 c0 36 00 00 8b 44 24 08 4c 8b 4c 24 10 e9 22 
f8 ff ff <0f> 0b e9 7a f4 ff ff 8b b3 70 01 00 00 89 f2 89 c1 48 c7 c6 40 ae
Feb 09 08:13:21 hostname kernel: RSP: :abdd422dfcc0 EFLAGS: 00010246
Feb 09 08:13:21 hostname kernel: RAX:  RBX: 95eaec7cf3a0 
RCX: 
Feb 09 08:13:21 hostname kernel: RDX: 95eadd4718f8 RSI: 0216 
RDI: 0216
Feb 09 08:13:21 hostname kernel: RBP: 020674ff R08: 0020 
R09: 001b
Feb 09 08:13:21 hostname kernel: R10: 95eadd471580 R11: 00035000 
R12: 95eaec7cf3a8
Feb 09 08:13:21 hostname kernel: R13: 95eadd471580 R14: 95eadd471580 
R15: 95eaec7cf500
Feb 09 08:13:21 hostname kernel: FS:  () 
GS:95eb1e48() knlGS:
Feb 09 08:13:21 hostname kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Feb 09 08:13:21 hostname kernel: CR2:  CR3: 00040320a001 
CR4: 003606e0
Feb 09 08:13:21 hostname kernel: Call Trace:
Feb 09 08:13:21 hostname kernel:  ? ath10k_conf_tx+0x7d/0x4b0 [ath10k_core]
Feb 09 08:13:21 hostname kernel:  ieee80211_bss_info_change_notify+0xab/0x1a0 
[mac80211]
Feb 09 08:13:21 hostname kernel:  ieee80211_reconfig+0x661/0x1310 [mac80211]
Feb 09 08:13:21 hostname kernel:  ? __switch_to_asm+0x40/0x70
Feb 09 08:13:21 hostname kernel:  ? __switch_to_asm+0x40/0x70
Feb 09 08:13:21 hostname kernel:  ? __switch_to_asm+0x34/0x70
Feb 09 08:13:21 hostname kernel:  wiphy_resume+0x7f/0x120 [cfg80211]
Feb 09 08:13:21 hostname kernel:  ? wiphy_suspend+0x270/0x270 [cfg80211]
Feb 09 08:13:21 hostname kernel:  dpm_run_callback+0x59/0x150
Feb 09 08:13:21 hostname kernel:  

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

2019-02-08 Thread 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 1815268

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

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

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

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

** Tags added: bionic

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  

[Kernel-packages] [Bug 1815268] [NEW] hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy

2019-02-08 Thread Si-Wei Liu
Public bug reported:

Host has a QEMU/KVM setup with standby virtio-net [1]:

# qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on -machine
pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp
4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

Guest is loaded with Xenial Xerus (16.04.5),

vsbalakr@ubuntu-16:~$ uname -a
Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
vsbalakr@ubuntu-16:~$ cat /proc/version_signature
Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
vsbalakr@ubuntu-16:~$ cat /etc/os*release
NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
vsbalakr@ubuntu-16:~$ 

ens3 is the master interface of net_failover, while ens3nsby is its
standby slave [2]:

vsbalakr@ubuntu-16:~$ ip a sh
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
   valid_lft forever preferred_lft forever
inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
valid_lft forever preferred_lft forever
3: ens3nsby:  mtu 1500 qdisc pfifo_fast master 
ens3 state UP group default qlen 1000
link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
   valid_lft 2154sec preferred_lft 2154sec
inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
valid_lft forever preferred_lft forever

Now we hot plug a Virtual Function (with MAC set to same address
d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

(qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
(qemu)

VF now shows up in guest as "eth0" instead of the expected "ens4":

vsbalakr@ubuntu-16:~$ ip a sh
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
   valid_lft forever preferred_lft forever
inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
   valid_lft forever preferred_lft forever
3: ens3nsby:  mtu 1500 qdisc pfifo_fast master 
ens3 state UP group default qlen 1000
link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
   valid_lft 2072sec preferred_lft 2072sec
inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
   valid_lft forever preferred_lft forever
6: eth0:  mtu 1500 qdisc mq master ens3 state 
UP group default qlen 1000
link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
vsbalakr@ubuntu-16:~$

/var/log/syslog shows that renaming to "ens4" had failed because of
"Device or resource busy",

Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC Link 
is Up 10 Gbps
Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id' 
/lib/udev/rules.d/80-net-setup-link.rules:5
Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'net_setup_link' 
/lib/udev/rules.d/80-net-setup-link.rules:9
Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: Config file 
/lib/systemd/network/99-default.link applies to device eth0
Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: NAME 'ens4' 
/lib/udev/rules.d/80-net-setup-link.rules:11
Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN '/lib/systemd/systemd-sysctl 
--prefix=/net/ipv4/conf/$name --prefix=/net/ipv4/neigh/$name 
--prefix=/net/ipv6/conf/$name --prefix=/net/ipv6/neigh/$name' 
/lib/udev/rules.d/99-systemd.rules:51

[Kernel-packages] [Bug 1815258] Re: 4.18.0-14-generic unbootable on Toshiba

2019-02-08 Thread Brad Figg
** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  4.18.0-14-generic unbootable on Toshiba

Status in linux package in Ubuntu:
  Triaged

Bug description:
  After the update for the 4.18.0-14-generic kernel the machine freezes
  on booting. Machine still books under the 0-13 kernel. Booting in
  Recovery Mode seems go normally to the Recovery Menu. At that point it
  reports "Starting Avahi mDNS-SD Stack" and gets an OK response. That
  is repeated with another OK. Then it says "Starting Daily apt upgrade
  and clean activities" followed by an OK. Next is a second attempt for
  the same "apt upgrade" and it appears to be frozen. No OK ever
  received and no further progress towards booting.

  Not sure how additional details can be acquired.

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

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


[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2019-02-08 Thread Mercury
Alright, I have a little more detail, but it's still largely a puzzle.

My current machine state (expected to remain this way until the next
reboot), is that any time I plug a USB device into a port under the xHCI
controller in the TB18DC dock, the xHCI controller dies a horrible
death.

This is 100% reproducible right now.

Unbinding the xHCI driver and rebinding works, as does something firmer
to the entire thunderbolt PCI chain and rescanning.

Doing so results in every USB device plugged in at the time of the
rebind/rescan working perfectly, until such time as I next plug a USB
device in.

That device can be on a port on the dock, or on a port on any hub
connected to a port on the dock.

I can remove the thunderbolt PCI devices software wise, unplug the dock
from the laptop, unplug the dock from power, then reconnect the dock to
power, plug it back into the laptop, and once everything comes back up I
am again in a temporarily working state...  Until I plug a USB device
into the system.

At which point it fails again, in exactly the same way.

Given that a reboot will solve the problem for some time, this is
starting to make me think that either A, there is something very wonky
going on in Dell SMBIOS land, or B, there is something wonky going on
somewhere in the kernel space.

It being an issue with the dock itself seems difficult to support, given
that the dock is getting a full power cycle and it's not changing
anything, and yet a reboot of the laptop without a full power cycle of
the dock seems to resolve the issue for a little while.

Here are some more kernel messages of the death, this time with more
debugging enabled:

Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: // Ding dong!
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Slot 3 output ctx = 
0xaa5a13000 (dma)
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Slot 3 input ctx = 
0xacd98c000 (dma)
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Set slot id 3 dcbaa 
entry 6f1f9598 to 0xaa5a13000
Feb 08 20:03:46 chimera kernel: usb 3-1.4: new full-speed USB device number 7 
using xhci_hcd
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Set root hub portnum to 3
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Set fake root hub 
portnum to 1
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: udev->tt = 
8fd0cd08
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: udev->ttport = 0x4
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: // Ding dong!
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Successful setup context 
command
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Op regs DCBAA ptr = 
0x0acbcc6000
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Slot ID 3 dcbaa entry 
@6f1f9598 = 0x0aa5a13000
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Output Context DMA 
address = 0xaa5a13000
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Internal device address 
= 0
Feb 08 20:03:46 chimera kernel: xhci_hcd :0c:00.0: Waiting for status stage 
event
Feb 08 20:03:47 chimera kernel: xhci_hcd :0c:00.0: Cancel URB 
b99abcb2, dev 1, ep 0x0, starting at offset 0xaa6cbddc0
Feb 08 20:03:47 chimera kernel: xhci_hcd :0c:00.0: // Ding dong!
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: xHCI host not responding 
to stop endpoint command.
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: // Halt the HC
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Host halt failed, -110
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: xHCI host controller not 
responding, assume dead
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
1, ep index 0
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
1, ep index 2
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
2, ep index 0
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
2, ep index 2
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
3, ep index 0
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
4, ep index 0
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
4, ep index 2
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
4, ep index 3
Feb 08 20:03:52 chimera kernel: r8152 4-1.2:1.0 eth0: Tx status -108
Feb 08 20:03:52 chimera kernel: r8152 4-1.2:1.0 eth0: Tx status -108
Feb 08 20:03:52 chimera kernel: r8152 4-1.2:1.0 eth0: Tx status -108
Feb 08 20:03:52 chimera kernel: r8152 4-1.2:1.0 eth0: Tx status -108
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
4, ep index 6
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
5, ep index 0
Feb 08 20:03:52 chimera kernel: xhci_hcd :0c:00.0: Killing URBs for slot ID 
5, ep index 2
Feb 08 20:03:52 chimera kernel: 

[Kernel-packages] [Bug 1805188] Re: Installmedia; Failing boot: "ACPI Error: Method parse/execution failed"

2019-02-08 Thread 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/1805188

Title:
  Installmedia; Failing boot: "ACPI Error: Method parse/execution
  failed"

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hardware: Thinkpad X1 Extreme (20MF000TGE)
  State: Initial Win10 installation.

  Trying to install *any* recent desktop version of ubuntu, but also
  live image fails brutally, due to (PCIO) ACPI errors:

  [0.452142] ACPI Error: Method parse/execution failed 
\_SB.PCIO.SPI1.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20180531/psparse-516)
  [0.452168] ACPI Error: Method execution failed \_SB.PCIO.SPI1.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20180531/uteval-69)
  [0.455124] ACPI Error: Method parse/execution failed 
\_SB.PCIO.SPI2.FPNT._CRS, AE_AML_INVALID_RESOURCE_TYPE (20180531/psparse-516)
  [0.455146] ACPI Error: Method execution failed \_SB.PCIO.SPI2.FPNT._CRS, 
AE_AML_INVALID_RESOURCE_TYPE (20180531/uteval-69)

  The error occurs on 18.10. desktop usb installation media: It doesn't matter 
which USB stick on the right side is used. I was neither able to boot the live 
system of this version in efi mode nor in legacy bios mode. Medium check 
completed successfully. SHA256-sum of the install media is 
"818affdaea8d38bbbe620009bfa788a7cbc583c7c61c2d278f61dd3c43e030a0" (which is 
correct!).
  Directly choosing installation in the boot menu does just show a black screen.

  I also tried 18.04.1 LTS to double check: This install image does not
  boot either, but the error is just shown briefly, so I cannot tell if
  this is indeed the same error. Selfchecking this media freezes the
  system at some point during the process. Also this media produces the
  correct sha256-sum.

  I can confirm this for two different USB sticks: SanDisk Ultra USB3.0
  (16GB) and some unknown TOSHIBA  model.

  Update:
  Okay. A BIOS update fixed something: at least it boots now into live...

  Please ask questions, if something is unclear or if you want me to
  test/do something...

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

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


[Kernel-packages] [Bug 1803752] Re: HID inputs (mouse buttons and keyboard) stop responding when plug in DP monitor

2019-02-08 Thread 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/1803752

Title:
  HID inputs (mouse buttons and keyboard) stop responding when plug in
  DP monitor

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ever since upgrading to 18.10 plugging in external monitors has been
  buggy.

  Device Lenovo T460s. Ubuntu-Mate 18.10.

  Plugging in External monitor using mini-display port causes keyboard
  to be unresponsive. Mouse buttons as well. though can still move mouse
  on screen. Plugging in and out using arndr sometimes resolves this.
  Notwithstanding, no smooth transition to multi-monitor mode.

  
  EDIT: 2018-11-22 // The problems are not observed when using HDMI instead of 
mini display-port. Moreover, if one can regain control of HID devices when mini 
DP plugged in, the resolution of the monitor plugged in is completely wrong. 

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins:
   (gconftool-2:31954): GConf-WARNING **: 21:41:20.841: Client failed to 
connect to the D-BUS daemon:
   Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: 2018-10-17 21:42:48,989 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroRelease: Ubuntu 18.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233]
  InstallationDate: Installed on 2016-07-23 (848 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  LightdmDisplayLog:
   (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
   (II) AIGLX: Suspending AIGLX clients for VT switch
   (II) AIGLX: Suspending AIGLX clients for VT switch
   (II) AIGLX: Suspending AIGLX clients for VT switch
  MachineType: LENOVO 20F9004FUS
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=074ff7b7-c074-4137-8cf7-d46cdd7dd723 ro quiet nosplash
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Tags:  cosmic ubuntu
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (32 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F9004FUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20F9004FUS:pvrThinkPadT460s:rvnLENOVO:rn20F9004FUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20F9004FUS
  dmi.product.sku: LENOVO_MT_20F9_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  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 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  ---
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: 2018-10-17 21:42:48,989 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroRelease: Ubuntu 18.10
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-10-generic, x86_64: installed
   acpi-call, 1.1.0, 4.18.0-11-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
   wireguard, 0.0.20181119, 4.18.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 

[Kernel-packages] [Bug 1805527] Re: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted (as of a few weeks ago)

2019-02-08 Thread 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/1805527

Title:
  [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is
  distorted (as of a few weeks ago)

Status in linux package in Ubuntu:
  Expired

Bug description:
  I use audio via DisplayPort.  Until a few weeks ago, I got good
  quality audio.

  Now, I get really bad 8-bit-ish distorted audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mikel  2276 F pulseaudio
   /dev/snd/pcmC1D3p:   mikel  2276 F...m pulseaudio
   /dev/snd/controlC1:  mikel  2276 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue Nov 27 17:18:56 2018
  InstallationDate: Installed on 2015-10-05 (1149 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - 
HDA ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  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.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX: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/1805527/+subscriptions

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


[Kernel-packages] [Bug 1805655] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008

2019-02-08 Thread 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/1805655

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0008

Status in linux package in Ubuntu:
  Expired

Bug description:
  [77211.421509] BUG: unable to handle kernel NULL pointer dereference at 
0008
  [77211.422467] IP: process_one_work+0x2e/0x410
  [77211.422970] PGD 0 P4D 0 
  [77211.423278] Oops:  [#1] SMP PTI
  [77211.423699] Modules linked in: binfmt_misc dccp_diag dccp udp_diag 
unix_diag af_packet_diag netlink_diag tcp_diag inet_diag xt_multiport 
iptable_filter ip_tables 8021q garp mrp stp llc bonding ip6t_REJECT 
nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt intel_rapl skx_edac 
x86_pkg_temp_thermal coretemp kvm_intel kvm irqbypass nf_conntrack_ipv6 
nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 ipmi_si nf_log_ipv4 nf_log_common 
xt_LOG intel_cstate xt_limit input_leds joydev xt_tcpudp ipmi_devintf 
intel_rapl_perf xt_addrtype ipmi_msghandler shpchp lpc_ich mei_me mei ioatdma 
dca mac_hid acpi_power_meter nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack 
ip6table_filter ib_iser rdma_cm iw_cm ib_cm ib_core ip6_tables iscsi_tcp 
libiscsi_tcp libiscsi nf_conntrack_netbios_ns nf_conntrack_broadcast 
scsi_transport_iscsi nf_nat_ftp
  [77211.432146]  nf_nat nf_conntrack_ftp toa(OE) nf_conntrack lp parport 
x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic crct10dif_pclmul crc32_pclmul hibmc_drm 
ghash_clmulni_intel ttm usbhid pcbc drm_kms_helper hid syscopyarea ses 
aesni_intel sysfillrect enclosure aes_x86_64 sysimgblt i40e crypto_simd 
scsi_transport_sas fb_sys_fops glue_helper ptp megaraid_sas cryptd drm ahci 
pps_core libahci [last unloaded: ip_tables]
  [77211.437829] CPU: 78 PID: 481 Comm: kworker/78:0 Tainted: G   OE
4.15.0-21-shopee-generic #22~16.04.1+3
  [77211.439038] Hardware name: Huawei 2288H V5/BC11SPSCB0, BIOS 0.62 03/26/2018
  [77211.439865] RIP: 0010:process_one_work+0x2e/0x410
  [77211.440417] RSP: :a81d0d7e3e88 EFLAGS: 00010046
  [77211.441032] RAX:  RBX: 8a2ebf5a2180 RCX: 
8a2ebf5a8a60
  [77211.441869] RDX: 8a2ebf5a8a60 RSI: a81d2f38bb08 RDI: 
8a2eb71a35c0
  [77211.442710] RBP: a81d0d7e3ec0 R08: fffc R09: 
0003
  [77211.443547] R10:  R11:  R12: 
8a2ebf5a2180
  [77211.444383] R13: 8a2ebf5a2180 R14:  R15: 
8a2eb71a35c0
  [77211.445222] FS:  () GS:8a2ebf58() 
knlGS:
  [77211.446175] CS:  0010 DS:  ES:  CR0: 80050033
  [77211.446850] CR2: 00b0 CR3: 003eb220a003 CR4: 
007606e0
  [77211.447688] DR0:  DR1:  DR2: 

  [77211.448525] DR3:  DR6: fffe0ff0 DR7: 
0400
  [77211.475504] PKRU: 5554
  [77211.502040] Call Trace:
  [77211.528218]  worker_thread+0x253/0x410
  [77211.554162]  kthread+0x121/0x140
  [77211.579749]  ? process_one_work+0x410/0x410
  [77211.605690]  ? kthread_create_worker_on_cpu+0x70/0x70
  [77211.631715]  ret_from_fork+0x35/0x40
  [77211.657159] Code: 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 10 
48 8b 06 4c 8b 6f 48 49 89 c6 45 30 f6 a8 04 b8 00 00 00 00 4c 0f 44 f0 <49> 8b 
46 08 44 8b b8 00 01 00 00 41 83 e7 20 41 f6 45 10 04 75 
  [77211.733169] RIP: process_one_work+0x2e/0x410 RSP: a81d0d7e3e88
  [77211.758179] CR2: 0008
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 28 20:27 seq
   crw-rw 1 root audio 116, 33 Nov 28 20:27 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=c153c4f5-1fb0-4da5-9bb4-c04f794dc70c
  InstallationDate: Installed on 2018-08-23 (97 days ago)
  InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 12d1:0003 Huawei Technologies Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Huawei 2288H V5
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   0 VESA VGA
   1 hibmcdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-21-shopee-generic 

[Kernel-packages] [Bug 1807429] Re: 4.15.0-42-generic intel_iommu=on crash on boot

2019-02-08 Thread 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/1807429

Title:
  4.15.0-42-generic intel_iommu=on crash on boot

Status in linux package in Ubuntu:
  Expired

Bug description:
  New Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-42-generic x86_64) installation
  dist-upgraded as of Fri Dec  7 17:49:07 GMT 2018
  running Dell R440 with Dell Boss card as boot drive

  nano /etc/default/grub
  ->GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on"

  update-grub
  reboot

  Error on boot:

  gave up waiting for root file system
  missing modules
  Alert UUID= does not exist dropping to shell

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

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


[Kernel-packages] [Bug 1815258] Re: 4.18.0-14-generic unbootable on Toshiba

2019-02-08 Thread shanen (Shannon Jacobs)
** Description changed:

  After the update for the 4.18.0-14-generic kernel the machine freezes on
  booting. Machine still books under the 0-13 kernel. Booting in Recovery
  Mode seems go normally to the Recovery Menu. At that point it reports
- "Starting Avahi mDNS-SD Stack" and gets and OK. That is repeated with
- another OK. Then it says "Starting Daily apt upgrade and clean
+ "Starting Avahi mDNS-SD Stack" and gets an OK response. That is repeated
+ with another OK. Then it says "Starting Daily apt upgrade and clean
  activities" followed by an OK. Next is a second attempt and it appears
  to be frozen. No OK ever received and no further progress towards
  booting.
  
  Not sure how additional details can be acquired.

** Description changed:

  After the update for the 4.18.0-14-generic kernel the machine freezes on
  booting. Machine still books under the 0-13 kernel. Booting in Recovery
  Mode seems go normally to the Recovery Menu. At that point it reports
  "Starting Avahi mDNS-SD Stack" and gets an OK response. That is repeated
  with another OK. Then it says "Starting Daily apt upgrade and clean
- activities" followed by an OK. Next is a second attempt and it appears
- to be frozen. No OK ever received and no further progress towards
- booting.
+ activities" followed by an OK. Next is a second attempt for the same
+ "apt upgrade" and it appears to be frozen. No OK ever received and no
+ further progress towards booting.
  
  Not sure how additional details can be acquired.

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

Title:
  4.18.0-14-generic unbootable on Toshiba

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the update for the 4.18.0-14-generic kernel the machine freezes
  on booting. Machine still books under the 0-13 kernel. Booting in
  Recovery Mode seems go normally to the Recovery Menu. At that point it
  reports "Starting Avahi mDNS-SD Stack" and gets an OK response. That
  is repeated with another OK. Then it says "Starting Daily apt upgrade
  and clean activities" followed by an OK. Next is a second attempt for
  the same "apt upgrade" and it appears to be frozen. No OK ever
  received and no further progress towards booting.

  Not sure how additional details can be acquired.

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

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


[Kernel-packages] [Bug 1815259] [NEW] BPF: kernel pointer leak to unprivileged userspace

2019-02-08 Thread Tyler Hicks
*** This bug is a security vulnerability ***

Public security bug reported:

[Impact]

Per Jann Horn, "Upstream commit dd066823db2ac4e22f721ec85190817b58059a54
("bpf/verifier: disallow pointer subtraction") fixes a security bug
(kernel pointer leak to unprivileged userspace)."

https://lore.kernel.org/netdev/CAG48ez1=zogmdsue38hkg73ea4en+5qotltmzme+pgcthhw...@mail.gmail.com/

[Test Case]

Run the "check subtraction on pointers for unpriv" test from
tools/testing/selftests/bpf/test_verifier.c. The test should pass if the
bug is fixed, fail otherwise.

[Regression Potential]

The change could cause a regression in an unprivileged process that is
using eBPF. I suspect that this is unlikely. The alternative is to leave
a potential security hole open.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Tyler Hicks (tyhicks)
 Status: Fix Released

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Assignee: Tyler Hicks (tyhicks)
 Status: In Progress

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  BPF: kernel pointer leak to unprivileged userspace

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

Bug description:
  [Impact]

  Per Jann Horn, "Upstream commit dd066823db2ac4e22f721ec85190817b58059a54
  ("bpf/verifier: disallow pointer subtraction") fixes a security bug
  (kernel pointer leak to unprivileged userspace)."

  
https://lore.kernel.org/netdev/CAG48ez1=zogmdsue38hkg73ea4en+5qotltmzme+pgcthhw...@mail.gmail.com/

  [Test Case]

  Run the "check subtraction on pointers for unpriv" test from
  tools/testing/selftests/bpf/test_verifier.c. The test should pass if
  the bug is fixed, fail otherwise.

  [Regression Potential]

  The change could cause a regression in an unprivileged process that is
  using eBPF. I suspect that this is unlikely. The alternative is to
  leave a potential security hole open.

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

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


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

2019-02-08 Thread 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 1815258

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

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

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

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

** Tags added: 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/1815258

Title:
  4.18.0-14-generic unbootable on Toshiba

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the update for the 4.18.0-14-generic kernel the machine freezes
  on booting. Machine still books under the 0-13 kernel. Booting in
  Recovery Mode seems go normally to the Recovery Menu. At that point it
  reports "Starting Avahi mDNS-SD Stack" and gets and OK. That is
  repeated with another OK. Then it says "Starting Daily apt upgrade and
  clean activities" followed by an OK. Next is a second attempt and it
  appears to be frozen. No OK ever received and no further progress
  towards booting.

  Not sure how additional details can be acquired.

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

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


[Kernel-packages] [Bug 1815258] [NEW] 4.18.0-14-generic unbootable on Toshiba

2019-02-08 Thread shanen (Shannon Jacobs)
Public bug reported:

After the update for the 4.18.0-14-generic kernel the machine freezes on
booting. Machine still books under the 0-13 kernel. Booting in Recovery
Mode seems go normally to the Recovery Menu. At that point it reports
"Starting Avahi mDNS-SD Stack" and gets and OK. That is repeated with
another OK. Then it says "Starting Daily apt upgrade and clean
activities" followed by an OK. Next is a second attempt and it appears
to be frozen. No OK ever received and no further progress towards
booting.

Not sure how additional details can be acquired.

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

Title:
  4.18.0-14-generic unbootable on Toshiba

Status in linux package in Ubuntu:
  New

Bug description:
  After the update for the 4.18.0-14-generic kernel the machine freezes
  on booting. Machine still books under the 0-13 kernel. Booting in
  Recovery Mode seems go normally to the Recovery Menu. At that point it
  reports "Starting Avahi mDNS-SD Stack" and gets and OK. That is
  repeated with another OK. Then it says "Starting Daily apt upgrade and
  clean activities" followed by an OK. Next is a second attempt and it
  appears to be frozen. No OK ever received and no further progress
  towards booting.

  Not sure how additional details can be acquired.

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

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


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

2019-02-08 Thread 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/1815255

Title:
  ubuntu 18.04 freezes randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  unable to do anything,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  godzill22   1619 F pulseaudio
   /dev/snd/controlC0:  godzill22   1619 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  8 23:28:34 2019
  InstallationDate: Installed on 2018-12-22 (48 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUS Laptop X505ZA_K505ZA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=45dac615-9bbf-4809-8615-e47376e42226 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X505ZA
  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.:bvrX505ZA.305:bd06/01/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX505ZA_K505ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUS Laptop X505ZA_K505ZA
  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/1815255/+subscriptions

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


[Kernel-packages] [Bug 1815255] [NEW] ubuntu 18.04 freezes randomly

2019-02-08 Thread Mariusz Bronowicki
Public bug reported:

unable to do anything,

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  godzill22   1619 F pulseaudio
 /dev/snd/controlC0:  godzill22   1619 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  8 23:28:34 2019
InstallationDate: Installed on 2018-12-22 (48 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUS Laptop X505ZA_K505ZA
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=45dac615-9bbf-4809-8615-e47376e42226 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/01/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X505ZA.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X505ZA
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.:bvrX505ZA.305:bd06/01/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX505ZA_K505ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUS Laptop X505ZA_K505ZA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug bionic

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

Title:
  ubuntu 18.04 freezes randomly

Status in linux package in Ubuntu:
  New

Bug description:
  unable to do anything,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  godzill22   1619 F pulseaudio
   /dev/snd/controlC0:  godzill22   1619 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  8 23:28:34 2019
  InstallationDate: Installed on 2018-12-22 (48 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUS Laptop X505ZA_K505ZA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=45dac615-9bbf-4809-8615-e47376e42226 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X505ZA
  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.:bvrX505ZA.305:bd06/01/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX505ZA_K505ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUS Laptop X505ZA_K505ZA
  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/1815255/+subscriptions

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


[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-02-08 Thread Steve Langasek
This SRU claims for regression-potential:

> Low. The quirk uses strict DMI to match affected systems.

This doesn't appear to be true for the changes to upower, which include
no DMI quirking whatsoever.  Please clarify this.

** Changed in: upower (Ubuntu Bionic)
   Status: Fix Committed => 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  In Progress
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  New
Status in upower source package in Bionic:
  Incomplete
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  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/gnome-control-center/+bug/1745032/+subscriptions

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


[Kernel-packages] [Bug 1815225] Re: Ubuntu System on USB Drive Breaks with Updates Requiring Restarts

2019-02-08 Thread Wade
I remembered some additional information I should have put in the
original post:

First: Just to be sure, I wanted to reiterate that the 128 GB USB drive
was not just a "boot drive". It was an exact duplicate of the entire
Ubuntu system from my laptop, and worked the exact same way (Trash
function and all).

Second: As noted, the update from Software Updater that required a
restart broke both (1) the GRUB 2 bootloader on the (booted) USB drive,
AND (2) the GRUB 2 bootloader on the (unmounted) laptop's hard drive.

When I said they were broken to the point where neither was bootable,
taking me to the dreaded "grub_rescue" command line when trying to boot
either one, I should have added the following regarding the errors
given:

1) When trying to boot from the USB drive (during the restart), the
error was similar to "trying to read outside hd0" (hd0 = the hard drive,
I believe), before I was put at grub_rescue command line. (To note, I
have seen that same error at other *unrelated* times, but at those
times, it acted more like a warning pause before simply continuing to
the login screen.)

2) Then removing the USB drive and attempting to simply boot up from the
hard drive instead, I got an error similar to "cannot find (or locate)
device such-and-such" before being put at grub_rescue. I believe the
"such-and-such" was the UUID of the USB drive that was being run from
when the update that required a restart came up. So even though trying
to boot up from the hard drive at that point, it still knew something
about the previously-booted USB drive that was active during the
restart-requiring-update; and it didn't like that it couldn't find that
USB drive, so grub_rescue ensued.

That's it. Thank you again!

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

Title:
  Ubuntu System on USB Drive Breaks with Updates Requiring Restarts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First, please forgive me if I do not report this issue correctly. I'm
  new here and don't generally live in the Launchpad world. (I've tried
  this at askUbuntu.com, and it was suggested I come here.)

  In brief: I have a 2006 Dell Inspiron (32 bit) with a (slow) 40 GB
  hard drive running Ubuntu 14.04 LTS. Having the system exactly the way
  I want it, I used the application "Systemback" to install the system
  on a (fast) 128 GB USB drive, which, being bootable, worked exactly
  the same as if I booted from the hard drive. So I started using the
  faster 128 USB drive exclusively.

  Now typically, Software Updater, if not requiring a restart, updated the 
running USB drive just fine. But one day, after Software Updater did an update 
that required a restart, this happened:
  the GRUB 2 bootloader the USB drive that was booted from, AND ALSO the GRUB 2 
bootloader on the laptop's hard drive got broken, to the point where neither 
was bootable, taking me to the dreaded "grub rescue" command line when trying 
to boot either one. (Thankfully, I had a second USB drive with my Ubuntu system 
on it, and was able to install it from there to both the laptop's hard drive 
and the other now-ruined USB drive to bring them back to a pre-broken, normal 
existence.)

  With that background, I ask: Can Ubuntu's updates that require
  restarts merely work with the drive that was booted from, and not any
  affect any others (including an unmounted hard drive that was not
  booted from) ?

  If so, then anyone could get a Linux the way they want that they can
  take anywhere, bootable from any computer, AND update-able from any
  computer, bypassing all need for hard drives of any sort. No longer
  would people need to even buy laptops with hard drives or even
  operating systems. They could simply buy a smaller, cheaper, hard-
  drive-less and OS-less device that runs merely by plugging an Ubuntu
  Linux USB drive into it as "the system".

  Thank you very much for your time!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-165-generic 3.13.0-165.215
  ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-165-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  noname 2014 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  8 12:12:35 2019
  HibernationDevice: RESUME=UUID=230fdc83-e7b8-40a5-8731-075b72792c69
  InstallationDate: Installed on 2018-12-31 (39 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Dell Inc. ME051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-165-generic 
root=UUID=7cfb23c6-b380-495e-9e1c-813436961fef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-165-generic N/A
   

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-02-08 Thread Steve Langasek
I think the test and regression potential templates on this bug are not
up to the normal SRU standard.  There are a number of firmware blobs
updated, what is the set of chips that make use of these firmware blobs
that could potentially be affected by this update?  Why is this complete
range of firmware blobs being updated, if there is a bug being reported
with only a single chip?

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: Fix Committed => Incomplete

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  New
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in The Cosmic Cuttlefish:
  New
Status in linux-firmware source package in Cosmic:
  Incomplete

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 

[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-02-08 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 18.2.2-0ubuntu1~18.04.2

---
mesa (18.2.2-0ubuntu1~18.04.2) bionic; urgency=medium

  * i965-revert-enabling-softpin.diff: Don't enable softpin, causes
issues on 32bit installs. (LP: #1815172)

 -- Timo Aaltonen   Fri, 08 Feb 2019 19:12:58 +0200

** Changed in: mesa (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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


[Kernel-packages] [Bug 1815172] Update Released

2019-02-08 Thread Adam Conrad
The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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


[Kernel-packages] [Bug 1814655] Re: linux-raspi2: 4.4.0-1104.112 -proposed tracker

2019-02-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1814647
- phase: Holding before Promote to Proposed
- phase-changed: Friday, 08. February 2019 18:03 UTC
+ phase: Promote to Proposed
+ phase-changed: Friday, 08. February 2019 21:34 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux-raspi2: 4.4.0-1104.112 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Promote to Proposed
  phase-changed: Friday, 08. February 2019 21:34 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814655/+subscriptions

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-02-08 Thread Alkis Georgopoulos
I verify that the bionic-proposed package addresses the issue.

Tested in:
# lspci -nn -k | grep -A 2 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 
[8086:5912] (rev 04)
Subsystem: Gigabyte Technology Co., Ltd HD Graphics 630 [1458:d000]
Kernel driver in use: i915


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

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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


[Kernel-packages] [Bug 1396654] Re: C++ demangling support missing from perf

2019-02-08 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  C++ demangling support missing from perf

Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete
Status in linux-hwe source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux-hwe source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Triaged
Status in linux-hwe source package in Disco:
  Confirmed

Bug description:
  Hi,
  It appears that C++ demangling support is missing from linux-tools-3.16.0-24, 
on Utopic on arm64.

  Could the following please be added to the build dependencies for that 
package:
  libiberty-dev
  binutils-dev

  Installing the above and rebuilding the package fixed the problem for
  me.

  Cheers,
  --
  Steve
  --- 
  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
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  DistroRelease: Ubuntu 14.10
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-24-generic aarch64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-08 Thread P.D.
Confirmed fixed even in 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/1814555

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2019-02-08 Thread bugproxy
--- Comment From leona...@ibm.com 2019-02-08 14:05 EDT---
In a meeting with lagarcia, I was informed this patch is very important, and 
that it is already on kernel 4.18-15 onwards.

In fact, including this one. there are two important patches on this
subject:

https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=6579804c431712d56956a63b1a01509441cc6800

As I said before, for 18.10 onwards (kernel >= 4.18), the patch is
available from kernel upstream source, but for Ubuntu 18.04 they may not
be so easily applied.

So I will work on backporting them to v4.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/1788098

Title:
  Avoid migration issues with aligned 2MB THB

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

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 this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions

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


[Kernel-packages] [Bug 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

2019-02-08 Thread Seth Forshee
** Description changed:

+ SRU Justification
+ 
+ Impact: Missing firmware for nouveau is causing errors to appear in
+ dmesg.
+ 
+ Fix: Add missing firmware files from upstream linux-firmware.
+ 
+ Test Case: Confirm that errors in dmesg are gone once new firmware files
+ are present.
+ 
+ Regression Potential: New and updated firmware always has potential to
+ cause regressions, however this firmware has been in disco for several
+ months with no reported issues.
+ 
+ ---
+ 
  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
- [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors 
-  
- Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com 
-  
+ [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors
+ 
+ Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com
+ 
  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
-  
- Machine Type = Witherspoon DD2.2 LC 
-  
+ 
+ Machine Type = Witherspoon DD2.2 LC
+ 
  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.
  
-   [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
- Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
- Ubuntu, with Linux 4.18.0-7-generic
- Ubuntu
-   [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
- Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
-  *  Ubuntu, with Linux 4.18.0-7-generic   
 
- Ubuntu
- 
-   System information
-   System configuration
-   System status log
-   Language
-   Rescan devices
-   Retrieve config from URL
-   Plugins (0)
-   Exit to shell
-  
??
-  Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
+   [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
+ Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
+ Ubuntu, with Linux 4.18.0-7-generic
+ Ubuntu
+   [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
+ Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
+  *  Ubuntu, with Linux 4.18.0-7-generic
+ Ubuntu
+ 
+   System information
+   System configuration
+   System status log
+   Language
+   Rescan devices
+   Retrieve config from URL
+   Plugins (0)
+   Exit to shell
+  
??
+  Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM]
  [   64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx
  [   65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22
  
  [   80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx
  [   80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22
  [   95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM]
  /dev/nvme0n1p2: recovering journal
  /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks
  -.mount
  kmod-static-nodes.service
  dev-hugepages.mount
  dev-mqueue.mount
  sys-kernel-debug.mount
  ufw.service
  lvm2-lvmetad.service
  systemd-remount-fs.service
  systemd-random-seed.service
  systemd-sysusers.service
  keyboard-setup.service
  systemd-tmpfiles-setup-dev.service
  lvm2-monitor.service
  finalrd.service
  

[Kernel-packages] [Bug 1815234] [NEW] Bionic update: upstream stable patchset 2019-02-08

2019-02-08 Thread Kamal Mostafa
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2019-02-08 (ported from v4.14.60 and v4.17.12)
   from git://git.kernel.org/

fork: unconditionally clear stack on fork
spi: spi-s3c64xx: Fix system resume support
Input: elan_i2c - add ACPI ID for lenovo ideapad 330
Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
kvm, mm: account shadow page tables to kmemcg
delayacct: fix crash in delayacct_blkio_end() after delayacct init failure
tracing: Fix double free of event_trigger_data
tracing: Fix possible double free in event_enable_trigger_func()
kthread, tracing: Don't expose half-written comm when creating kthreads
tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure
tracing: Quiet gcc warning about maybe unused link variable
arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups
mlxsw: spectrum_switchdev: Fix port_vlan refcounting
kcov: ensure irq code sees a valid area
xen/netfront: raise max number of slots in xennet_get_responses()
skip LAYOUTRETURN if layout is invalid
ALSA: emu10k1: add error handling for snd_ctl_add
ALSA: fm801: add error handling for snd_ctl_add
NFSv4.1: Fix the client behaviour on NFS4ERR_SEQ_FALSE_RETRY
nfsd: fix potential use-after-free in nfsd4_decode_getdeviceinfo
vfio: platform: Fix reset module leak in error path
vfio/mdev: Check globally for duplicate devices
vfio/type1: Fix task tracking for QEMU vCPU hotplug
kernel/hung_task.c: show all hung tasks before panic
mm: /proc/pid/pagemap: hide swap entries from unprivileged users
mm: vmalloc: avoid racy handling of debugobjects in vunmap
mm/slub.c: add __printf verification to slab_err()
rtc: ensure rtc_set_alarm fails when alarms are not supported
perf tools: Fix pmu events parsing rule
netfilter: ipset: forbid family for hash:mac sets
netfilter: ipset: List timing out entries with "timeout 1" instead of zero
irqchip/ls-scfg-msi: Map MSIs in the iommu
watchdog: da9063: Fix updating timeout value
printk: drop in_nmi check from printk_safe_flush_on_panic()
bpf, arm32: fix inconsistent naming about emit_a32_lsr_{r64,i64}
ceph: fix alignment of rasize
e1000e: Ignore TSYNCRXCTL when getting I219 clock attributes
powerpc/lib: Adjust .balign inside string functions for PPC32
powerpc/64s: Add barrier_nospec
powerpc/eeh: Fix use-after-release of EEH driver
hvc_opal: don't set tb_ticks_per_usec in udbg_init_opal_common()
powerpc/64s: Fix compiler store ordering to SLB shadow area
RDMA/mad: Convert BUG_ONs to error flows
lightnvm: pblk: warn in case of corrupted write buffer
netfilter: nf_tables: check msg_type before nft_trans_set(trans)
pnfs: Don't release the sequence slot until we've processed layoutget on open
disable loading f2fs module on PAGE_SIZE > 4KB
f2fs: fix error path of move_data_page
f2fs: fix to don't trigger writeback during recovery
f2fs: fix to wait page writeback during revoking atomic write
f2fs: Fix deadlock in shutdown ioctl
f2fs: fix to detect failure of dquot_initialize
f2fs: fix race in between GC and atomic open
block, bfq: remove wrong lock in bfq_requests_merged
usbip: usbip_detach: Fix memory, udev context and udev leak
usbip: dynamically allocate idev by nports found in sysfs
perf/x86/intel/uncore: Correct fixed counter index check in generic code
perf/x86/intel/uncore: Correct fixed counter index check for NHM
selftests/intel_pstate: Improve test, minor fixes
selftests: memfd: return Kselftest Skip code for skipped tests
selftests: intel_pstate: return Kselftest Skip code for skipped tests
PCI: Fix devm_pci_alloc_host_bridge() memory leak
iwlwifi: pcie: fix race in Rx buffer allocator
Bluetooth: hci_qca: Fix "Sleep inside atomic section" warning
Bluetooth: btusb: Add a new Realtek 8723DE ID 2ff8:b011
ASoC: dpcm: fix BE dai not hw_free and shutdown
mfd: cros_ec: Fail early if we cannot identify the EC
mwifiex: handle race during mwifiex_usb_disconnect
wlcore: sdio: check for valid platform device data before suspend
media: tw686x: Fix incorrect vb2_mem_ops GFP flags
media: videobuf2-core: don't call memop 'finish' when queueing
Btrfs: don't return ino to ino cache if inode item removal fails
Btrfs: don't BUG_ON() in btrfs_truncate_inode_items()
btrfs: add barriers to btrfs_sync_log before log_commit_wait wakeups
btrfs: qgroup: Finish rescan when hit the last leaf of extent tree
x86/microcode: Make the late update update_lock a raw lock for RT
PM / wakeup: Make s2idle_lock a RAW_SPINLOCK
PCI: Prevent sysfs disable of device while driver is attached
nvme-rdma: 

[Kernel-packages] [Bug 1396654] Re: C++ demangling support missing from perf

2019-02-08 Thread Ignat Loskutov
There seems to be a mistype in the build flags; haven't checked whether
it fixes the bug though.

** Patch added: "0001-UBUNTU-Packaging-fix-a-mistype.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396654/+attachment/5237067/+files/0001-UBUNTU-Packaging-fix-a-mistype.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/1396654

Title:
  C++ demangling support missing from perf

Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete
Status in linux-hwe source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux-hwe source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Triaged
Status in linux-hwe source package in Disco:
  Confirmed

Bug description:
  Hi,
  It appears that C++ demangling support is missing from linux-tools-3.16.0-24, 
on Utopic on arm64.

  Could the following please be added to the build dependencies for that 
package:
  libiberty-dev
  binutils-dev

  Installing the above and rebuilding the package fixed the problem for
  me.

  Cheers,
  --
  Steve
  --- 
  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
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  DistroRelease: Ubuntu 14.10
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-24-generic aarch64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

2019-02-08 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu)
   Status: New => Fix Released

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Witherspoon DD2.2 LC

  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

    [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
    [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu

    System information
    System configuration
    System status log
    Language
    Rescan devices
    Retrieve config from URL
    Plugins (0)
    Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM]
  [   64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx
  [   65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22

  [   80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx
  [   80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22
  [   95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM]
  /dev/nvme0n1p2: recovering journal
  /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks
  -.mount
  kmod-static-nodes.service
  dev-hugepages.mount
  dev-mqueue.mount
  sys-kernel-debug.mount
  ufw.service
  lvm2-lvmetad.service
  systemd-remount-fs.service
  systemd-random-seed.service
  systemd-sysusers.service
  keyboard-setup.service
  systemd-tmpfiles-setup-dev.service
  lvm2-monitor.service
  finalrd.service
  

[Kernel-packages] [Bug 1815176] Re: Out-of-tree kernel modules can't be built

2019-02-08 Thread Brad Figg
** Tags added: bjf-tracking

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

Title:
  Out-of-tree kernel modules can't be built

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to build an external module with gcc 7.3.0 fails with an error
  similar to:

   CC [M]  /home/user/../ApiFunc.o
  In file included from ./include/linux/mmdebug.h:5:0,
  from ./include/linux/gfp.h:5,
  from ./include/linux/slab.h:15,
  from /home/user/.../ApiFunc.c:51:
  ./include/linux/bug.h:5:10: fatal error: asm/bug.h: No such file or directory
  #include 
   ^~~
  compilation terminated.

  This problem is already fixed in the linux kernel starting from version 4.17
  We need to backport the following patch to Ubuntu kernel:
  https://patchwork.kernel.org/patch/10309291/

  Tested by me that it helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julia  1360 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  8 12:17:00 2019
  InstallationDate: Installed on 2018-12-28 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20M5003QRT
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=4384c2b9-39c0-41fe-a898-ef2c212df2e3 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0RET31W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20M5003QRT
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0RET31W(1.14):bd08/03/2018:svnLENOVO:pn20M5003QRT:pvrThinkPadL380:rvnLENOVO:rn20M5003QRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L380
  dmi.product.name: 20M5003QRT
  dmi.product.version: ThinkPad L380
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1815178] Re: 18.04: Raid5 performances on kernel 4.15 are suboptimal

2019-02-08 Thread Brad Figg
** Tags added: bjf-tracking

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

Title:
  18.04: Raid5 performances on kernel 4.15 are suboptimal

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  We have been running multiple tests using the md driver to build various type 
of RAID devices. Performances on RAID5 are particularly disappointing so we 
would like to know if there are any known issue with the md driver on Bionic 
kernels. Here are some of our results :

  Test (Threads)QCT JBODQCT RAID5 (8 threads)   QCT RAID10
  read(1)   838751 (-10%)   572 (-32%)
  read(2)   1226   1172 (-4%)   1057 (-14%)
  read(4)   1129   2006 (+78%)  1760 (+56%)
  write(1)  804382 (-52%)   398 (-50%)
  write(2)  1047   175 (-83%)   667 (-36%)
  write(4)  883415 (-53%)   871 (-1%)
  randread(1)   863749 (-13%)   619 (-28%)
  randread(2)   1346   1067 (-21%)  1020 (-24%)
  randread(4)   1648   1785 (+8%)   1650 (=)
  randwrite(1)  766287 (-63%)   391 (-50%)
  randwrite(2)  1044   313 (-70%)   664 (-36%)
  randwrite(4)  916282 (-69%)   885 (-3%)

  We are preparing tests with one of the latest mainline kernel.

  TIA,

  ...Louis

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

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-02-08 Thread Brad Figg
** Tags added: bjf-tracking

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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


[Kernel-packages] [Bug 1815225] Re: Ubuntu System on USB Drive Breaks with Updates Requiring Restarts

2019-02-08 Thread Brad Figg
** Tags added: bjf-tracking

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

Title:
  Ubuntu System on USB Drive Breaks with Updates Requiring Restarts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First, please forgive me if I do not report this issue correctly. I'm
  new here and don't generally live in the Launchpad world. (I've tried
  this at askUbuntu.com, and it was suggested I come here.)

  In brief: I have a 2006 Dell Inspiron (32 bit) with a (slow) 40 GB
  hard drive running Ubuntu 14.04 LTS. Having the system exactly the way
  I want it, I used the application "Systemback" to install the system
  on a (fast) 128 GB USB drive, which, being bootable, worked exactly
  the same as if I booted from the hard drive. So I started using the
  faster 128 USB drive exclusively.

  Now typically, Software Updater, if not requiring a restart, updated the 
running USB drive just fine. But one day, after Software Updater did an update 
that required a restart, this happened:
  the GRUB 2 bootloader the USB drive that was booted from, AND ALSO the GRUB 2 
bootloader on the laptop's hard drive got broken, to the point where neither 
was bootable, taking me to the dreaded "grub rescue" command line when trying 
to boot either one. (Thankfully, I had a second USB drive with my Ubuntu system 
on it, and was able to install it from there to both the laptop's hard drive 
and the other now-ruined USB drive to bring them back to a pre-broken, normal 
existence.)

  With that background, I ask: Can Ubuntu's updates that require
  restarts merely work with the drive that was booted from, and not any
  affect any others (including an unmounted hard drive that was not
  booted from) ?

  If so, then anyone could get a Linux the way they want that they can
  take anywhere, bootable from any computer, AND update-able from any
  computer, bypassing all need for hard drives of any sort. No longer
  would people need to even buy laptops with hard drives or even
  operating systems. They could simply buy a smaller, cheaper, hard-
  drive-less and OS-less device that runs merely by plugging an Ubuntu
  Linux USB drive into it as "the system".

  Thank you very much for your time!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-165-generic 3.13.0-165.215
  ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-165-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  noname 2014 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  8 12:12:35 2019
  HibernationDevice: RESUME=UUID=230fdc83-e7b8-40a5-8731-075b72792c69
  InstallationDate: Installed on 2018-12-31 (39 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Dell Inc. ME051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-165-generic 
root=UUID=7cfb23c6-b380-495e-9e1c-813436961fef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-165-generic N/A
   linux-backports-modules-3.13.0-165-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2018-12-31 (39 days ago)
  WifiSyslog:
   
  dmi.bios.date: 12/22/2005
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TD535
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd12/22/2005:svnDellInc.:pnME051:pvr:rvnDellInc.:rn0TD535:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: ME051
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1815214] Re: Lenovo T480: throttling CPU issue

2019-02-08 Thread Brad Figg
** Tags added: bjf-tracking

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

Title:
  Lenovo T480: throttling CPU issue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Linux OS the CPU package power limit (PL1/2) is set wrong reducing
  drastically CPU performance under load.

  Apparently many Lenovo laptops (certified for Ubuntu) are affected.
  The problem is described in details here: 
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  There is "hacky" workaround (not compatible with SecureBoot, a Python
  script writing MSR registers periodically) :
  https://github.com/erpalma/throttled

  There is also a thread on Lenovo forum: https://forums.lenovo.com/t5
  /Linux-Discussion/X1C6-T480s-low-cTDP-and-trip-temperature-in-
  Linux/td-p/4028489

  I confirm the issue affect my machine running the latest kernel
  (4.15.0-45-generic, although bug affects previous releases as well)
  and using the latest firmware from Lenovo (1.19).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   4050 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   4050 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   4050 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb  8 17:14:17 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (309 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (170 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's

2019-02-08 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted mesa into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-cosmic
** Tags added: verification-needed-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/1789924

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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


[Kernel-packages] [Bug 1815172] Please test proposed package

2019-02-08 Thread Adam Conrad
Hello Alkis, or anyone else affected,

Accepted mesa into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.10.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-02-08 Thread Adam Conrad
Hello Alkis, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.2-0ubuntu1~18.04.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: mesa (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

** Changed in: mesa (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed-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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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


[Kernel-packages] [Bug 1815103] Re: linux: 4.19.0-13.14 -proposed tracker

2019-02-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 
  derivatives:
  -- swm properties --
- phase: Promote to Proposed
- phase-changed: Friday, 08. February 2019 17:03 UTC
+ phase: Testing
+ phase-changed: Friday, 08. February 2019 18:37 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   regression-testing: Ongoing -- testing 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/1815103

Title:
  linux: 4.19.0-13.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 
  derivatives:
  -- swm properties --
  phase: Testing
  phase-changed: Friday, 08. February 2019 18:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1815103/+subscriptions

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


[Kernel-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04

2019-02-08 Thread Gilbert Standen
#8 from Kai-Heng Feng (kaihengfeng) fixed the issue for me on Lenovo P72
Intel® Core™ i7-8750H running Ubuntu 18.10 kernel 4.18.0-15-generic
#16-Ubuntu SMP. I added the following line to my /etc/default/grub

GRUB_CMDLINE_LINUX="psmouse.elantech_smbus=0"

then ran "sudo update-grub" in the usual way and track pad and buttons
work now.

-- 
You 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: 
dmi:bvnLENOVO:bvrR0QET37W(1.14):bd02/09/2018:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LS001AGE
  dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.4-0~b~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.4-0~b~padoka0
  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: 

[Kernel-packages] [Bug 1815122] Re: Unable to login via tty

2019-02-08 Thread Vlad D.
*** This bug is a duplicate of bug 1813873 ***
https://bugs.launchpad.net/bugs/1813873

** This bug has been marked a duplicate of bug 1813873
   Userspace break as a result of missing patch backport

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

Title:
  Unable to login via tty

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 16.04.

  After upgrading the kernel from 4.4.0-141.167-generic to
  4.4.0-142.168-generic I am experiencing problem logging in via the
  tty. I am able to provide my username, but the terminal automatically
  submit password before I am able to type it. If I start the computer
  with the previous kernel (4.4.0-141.167) it works as expected.

  
  I have done strace on the tty in both scenarios while performing the login 
with the following command:

  "sudo strace -p 1572 -s 1024 -vff -o tty-login-issue/login"

  4.4.0-141.167-generic (works):
  https://gist.github.com/ivarconr/b022d2b4cadfc654031e8a930bf4408b

  4.4.0-142.168-generic (fails): 
  https://gist.github.com/ivarconr/603409ad1f0a3343a7f44a854283befc

  
  Let me know if you need me to provide any additional details.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivaosthu   3706 F pulseaudio
   /dev/snd/controlC1:  ivaosthu   3706 F pulseaudio
  CurrentDesktop: i3
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=08d4aeb0-e54b-475e-8a26-b9e8b488a314
  InstallationDate: Installed on 2016-08-12 (909 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EQS2HW00
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic.efi.signed 
root=UUID=a0472864-d2ab-4f9d-8b4c-e89db4dbd51b ro quiet nomodeset splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.4.0-142-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS2HW00
  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: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS2HW00:pvrThinkPadP50:rvnLENOVO:rn20EQS2HW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EQS2HW00
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivaosthu   3706 F pulseaudio
   /dev/snd/controlC1:  ivaosthu   3706 F pulseaudio
  CurrentDesktop: i3
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=08d4aeb0-e54b-475e-8a26-b9e8b488a314
  InstallationDate: Installed on 2016-08-12 (909 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EQS2HW00
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic.efi.signed 
root=UUID=a0472864-d2ab-4f9d-8b4c-e89db4dbd51b ro quiet nomodeset splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.4.0-142-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS2HW00
  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: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS2HW00:pvrThinkPadP50:rvnLENOVO:rn20EQS2HW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EQS2HW00
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

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

2019-02-08 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

-- 
You 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 1814655] Re: linux-raspi2: 4.4.0-1104.112 -proposed tracker

2019-02-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814647
- phase: Packaging
- phase-changed: Thursday, 07. February 2019 08:04 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Friday, 08. February 2019 18:03 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete

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

Title:
  linux-raspi2: 4.4.0-1104.112 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1814647
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 08. February 2019 18:03 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814655/+subscriptions

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


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

2019-02-08 Thread 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/1815225

Title:
  Ubuntu System on USB Drive Breaks with Updates Requiring Restarts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First, please forgive me if I do not report this issue correctly. I'm
  new here and don't generally live in the Launchpad world. (I've tried
  this at askUbuntu.com, and it was suggested I come here.)

  In brief: I have a 2006 Dell Inspiron (32 bit) with a (slow) 40 GB
  hard drive running Ubuntu 14.04 LTS. Having the system exactly the way
  I want it, I used the application "Systemback" to install the system
  on a (fast) 128 GB USB drive, which, being bootable, worked exactly
  the same as if I booted from the hard drive. So I started using the
  faster 128 USB drive exclusively.

  Now typically, Software Updater, if not requiring a restart, updated the 
running USB drive just fine. But one day, after Software Updater did an update 
that required a restart, this happened:
  the GRUB 2 bootloader the USB drive that was booted from, AND ALSO the GRUB 2 
bootloader on the laptop's hard drive got broken, to the point where neither 
was bootable, taking me to the dreaded "grub rescue" command line when trying 
to boot either one. (Thankfully, I had a second USB drive with my Ubuntu system 
on it, and was able to install it from there to both the laptop's hard drive 
and the other now-ruined USB drive to bring them back to a pre-broken, normal 
existence.)

  With that background, I ask: Can Ubuntu's updates that require
  restarts merely work with the drive that was booted from, and not any
  affect any others (including an unmounted hard drive that was not
  booted from) ?

  If so, then anyone could get a Linux the way they want that they can
  take anywhere, bootable from any computer, AND update-able from any
  computer, bypassing all need for hard drives of any sort. No longer
  would people need to even buy laptops with hard drives or even
  operating systems. They could simply buy a smaller, cheaper, hard-
  drive-less and OS-less device that runs merely by plugging an Ubuntu
  Linux USB drive into it as "the system".

  Thank you very much for your time!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-165-generic 3.13.0-165.215
  ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-165-generic i686
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  noname 2014 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  8 12:12:35 2019
  HibernationDevice: RESUME=UUID=230fdc83-e7b8-40a5-8731-075b72792c69
  InstallationDate: Installed on 2018-12-31 (39 days ago)
  InstallationMedia:
   
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Dell Inc. ME051
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-165-generic 
root=UUID=7cfb23c6-b380-495e-9e1c-813436961fef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-165-generic N/A
   linux-backports-modules-3.13.0-165-generic  N/A
   linux-firmware  1.127.24
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2018-12-31 (39 days ago)
  WifiSyslog:
   
  dmi.bios.date: 12/22/2005
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TD535
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd12/22/2005:svnDellInc.:pnME051:pvr:rvnDellInc.:rn0TD535:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: ME051
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1815225] [NEW] Ubuntu System on USB Drive Breaks with Updates Requiring Restarts

2019-02-08 Thread Kerry Reinhart
Public bug reported:

First, please forgive me if I do not report this issue correctly. I'm
new here and don't generally live in the Launchpad world. (I've tried
this at askUbuntu.com, and it was suggested I come here.)

In brief: I have a 2006 Dell Inspiron (32 bit) with a (slow) 40 GB hard
drive running Ubuntu 14.04 LTS. Having the system exactly the way I want
it, I used the application "Systemback" to install the system on a
(fast) 128 GB USB drive, which, being bootable, worked exactly the same
as if I booted from the hard drive. So I started using the faster 128
USB drive exclusively.

Now typically, Software Updater, if not requiring a restart, updated the 
running USB drive just fine. But one day, after Software Updater did an update 
that required a restart, this happened:
the GRUB 2 bootloader the USB drive that was booted from, AND ALSO the GRUB 2 
bootloader on the laptop's hard drive got broken, to the point where neither 
was bootable, taking me to the dreaded "grub rescue" command line when trying 
to boot either one. (Thankfully, I had a second USB drive with my Ubuntu system 
on it, and was able to install it from there to both the laptop's hard drive 
and the other now-ruined USB drive to bring them back to a pre-broken, normal 
existence.)

With that background, I ask: Can Ubuntu's updates that require restarts
merely work with the drive that was booted from, and not any affect any
others (including an unmounted hard drive that was not booted from) ?

If so, then anyone could get a Linux the way they want that they can
take anywhere, bootable from any computer, AND update-able from any
computer, bypassing all need for hard drives of any sort. No longer
would people need to even buy laptops with hard drives or even operating
systems. They could simply buy a smaller, cheaper, hard-drive-less and
OS-less device that runs merely by plugging an Ubuntu Linux USB drive
into it as "the system".

Thank you very much for your time!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-165-generic 3.13.0-165.215
ProcVersionSignature: Ubuntu 3.13.0-165.215-generic 3.13.11-ckt39
Uname: Linux 3.13.0-165-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  noname 2014 F pulseaudio
CurrentDesktop: Unity
Date: Fri Feb  8 12:12:35 2019
HibernationDevice: RESUME=UUID=230fdc83-e7b8-40a5-8731-075b72792c69
InstallationDate: Installed on 2018-12-31 (39 days ago)
InstallationMedia:
 
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: Dell Inc. ME051
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-165-generic 
root=UUID=7cfb23c6-b380-495e-9e1c-813436961fef ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-165-generic N/A
 linux-backports-modules-3.13.0-165-generic  N/A
 linux-firmware  1.127.24
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2018-12-31 (39 days ago)
WifiSyslog:
 
dmi.bios.date: 12/22/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0TD535
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd12/22/2005:svnDellInc.:pnME051:pvr:rvnDellInc.:rn0TD535:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: ME051
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug i386 trusty

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

Title:
  Ubuntu System on USB Drive Breaks with Updates Requiring Restarts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First, please forgive me if I do not report this issue correctly. I'm
  new here and don't generally live in the Launchpad world. (I've tried
  this at askUbuntu.com, and it was suggested I come here.)

  In brief: I have a 2006 Dell Inspiron (32 bit) with a (slow) 40 GB
  hard drive running Ubuntu 14.04 LTS. Having the system exactly the way
  I want it, I used the application "Systemback" to install the system
  on a (fast) 128 GB USB drive, which, being bootable, worked exactly
  the same as if I booted from the hard drive. So I started using the
  faster 128 USB drive exclusively.

  Now typically, Software Updater, if not requiring a restart, updated the 
running USB drive just fine. But one day, after Software Updater did an update 
that required a restart, this happened:
  the GRUB 2 bootloader the USB drive that was booted from, AND ALSO the GRUB 2 
bootloader on the laptop's hard drive got broken, to the point where neither 
was bootable, taking me to the dreaded "grub rescue" command line when trying 
to boot either one. (Thankfully, I had a second USB drive with my Ubuntu system 
on it, and was able to 

[Kernel-packages] [Bug 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

2019-02-08 Thread Seth Forshee
Added bionic nomination too since the 18.10 kernel is available there in
the hwe packages.

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

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

** Changed in: linux-firmware (Ubuntu Bionic)
   Importance: Undecided => Medium

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

** Changed in: linux-firmware (Ubuntu Bionic)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux-firmware (Ubuntu Cosmic)
   Status: Confirmed => In Progress

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

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  Confirmed
Status in linux-firmware source package in Cosmic:
  In Progress

Bug description:
  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors 
   
  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com 
   
  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Witherspoon DD2.2 LC 
   
  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

[Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
[Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic   
 
  Ubuntu

System information
System configuration
System status log
Language
Rescan devices
Retrieve config from URL
Plugins (0)
Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM]
  [   64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx
  [   65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22

  [   80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx
  [   80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22
  [   95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM]
  /dev/nvme0n1p2: recovering journal
  /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks
  -.mount
  kmod-static-nodes.service
  dev-hugepages.mount
  dev-mqueue.mount
  sys-kernel-debug.mount
  ufw.service
  lvm2-lvmetad.service
  systemd-remount-fs.service
  systemd-random-seed.service
  systemd-sysusers.service
  keyboard-setup.service
  systemd-tmpfiles-setup-dev.service
  lvm2-monitor.service
  finalrd.service
  console-setup.service
  swapfile.swap
  

[Kernel-packages] [Bug 1815103] Re: linux: 4.19.0-13.14 -proposed tracker

2019-02-08 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 
  derivatives:
  -- swm properties --
  phase: Promote to Proposed
  phase-changed: Friday, 08. February 2019 17:03 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

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

Title:
  linux: 4.19.0-13.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 
  derivatives:
  -- swm properties --
  phase: Promote to Proposed
  phase-changed: Friday, 08. February 2019 17:03 UTC
  reason:
promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1815103/+subscriptions

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


[Kernel-packages] [Bug 1756824] Re: Intel wifi bluetooth coexistence issue in 18.04

2019-02-08 Thread Seth Forshee
I built a package with the bluetooth firmware files from the bug updated
from the tip of linux-firmware. Can you please give this a try and
confirm it fixes your issue? Thanks!

http://people.canonical.com/~sforshee/lp1756824/linux-
firmware_1.173.3+lp1756824v201902081042_all.deb

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

** Changed in: linux-firmware (Ubuntu Bionic)
   Importance: Undecided => Medium

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

** Changed in: linux-firmware (Ubuntu Bionic)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Intel wifi bluetooth coexistence issue in 18.04

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Incomplete

Bug description:
  (Intel wifi/bluetooth 8260 and 8265)

  Bluetooth does not work (bluetooth keyboard and mouse do not connect)
  when wifi enabled.

  Upstream bug seems to be fixing this, copying intel firmware from this bug 
fixes the issue:
  https://bugzilla.kernel.org/show_bug.cgi?id=197147

  Ubuntu firmware package update from last couple of days still comes
  with broken intel firmware.

  Other way to get bluetooth working with intel firmware from ubuntu
  package is to add following parameter in modprobe:

  options iwlwifi bt_coex_active=0
  to /etc/modprobe-d/iwlwifi.conf
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Dependencies:
   
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-10-24 (1241 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  NonfreeKernelModules: wl
  Package: linux-firmware 1.173 [modified: lib/firmware/intel/ibt-12-16.ddc 
lib/firmware/intel/ibt-12-16.sfi]
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd netdev plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1815103] Re: linux: 4.19.0-13.14 -proposed tracker

2019-02-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Fix Committed

** Tags added: block-proposed-disco

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 
  derivatives:
  -- swm properties --
- phase: Packaging
- phase-changed: Thursday, 07. February 2019 18:37 UTC
+ phase: Promote to Proposed
+ phase-changed: Friday, 08. February 2019 17:03 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

Title:
  linux: 4.19.0-13.14 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 
  derivatives:
  -- swm properties --
  phase: Promote to Proposed
  phase-changed: Friday, 08. February 2019 17:03 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1815103/+subscriptions

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


[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-02-08 Thread Timo Aaltonen
this is caused by enabling softpin in mesa, which is supported in kernel
4.5 and up but is still somewhat buggy as seen here.. we need these
commits backported to the kernel:

9125963a9494253fa5a29cc1b4169885d2be7042 drm/i915: Mark up GTT sizes as u64
6fc4e48f9ed46e9adff236a0c350074aafa3b7fa drm/i915: Compare user's 64b GTT 
offset even on 32b

but since 18.04.2 is about to be released, it's best to revert enabling
softpin in mesa, and enable it again for 18.04.3.

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

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  New

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions

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


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

2019-02-08 Thread 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/1815214

Title:
  Lenovo T480: throttling CPU issue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Linux OS the CPU package power limit (PL1/2) is set wrong reducing
  drastically CPU performance under load.

  Apparently many Lenovo laptops (certified for Ubuntu) are affected.
  The problem is described in details here: 
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  There is "hacky" workaround (not compatible with SecureBoot, a Python
  script writing MSR registers periodically) :
  https://github.com/erpalma/throttled

  There is also a thread on Lenovo forum: https://forums.lenovo.com/t5
  /Linux-Discussion/X1C6-T480s-low-cTDP-and-trip-temperature-in-
  Linux/td-p/4028489

  I confirm the issue affect my machine running the latest kernel
  (4.15.0-45-generic, although bug affects previous releases as well)
  and using the latest firmware from Lenovo (1.19).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   4050 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   4050 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   4050 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb  8 17:14:17 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (309 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (170 days ago)
  dmi.bios.date: 11/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET44W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L6S04200
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L6S04200
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1815214] [NEW] Lenovo T480: throttling CPU issue

2019-02-08 Thread Adrian
Public bug reported:

On Linux OS the CPU package power limit (PL1/2) is set wrong reducing
drastically CPU performance under load.

Apparently many Lenovo laptops (certified for Ubuntu) are affected.
The problem is described in details here: 
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

There is "hacky" workaround (not compatible with SecureBoot, a Python
script writing MSR registers periodically) :
https://github.com/erpalma/throttled

There is also a thread on Lenovo forum: https://forums.lenovo.com/t5
/Linux-Discussion/X1C6-T480s-low-cTDP-and-trip-temperature-in-
Linux/td-p/4028489

I confirm the issue affect my machine running the latest kernel
(4.15.0-45-generic, although bug affects previous releases as well) and
using the latest firmware from Lenovo (1.19).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  afiergol   4050 F pulseaudio
 /dev/snd/pcmC0D0p:   afiergol   4050 F...m pulseaudio
 /dev/snd/controlC0:  afiergol   4050 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Feb  8 17:14:17 2019
HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
InstallationDate: Installed on 2018-04-05 (309 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: LENOVO 20L6S04200
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-08-22 (170 days ago)
dmi.bios.date: 11/07/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET44W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L6S04200
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET44W(1.19):bd11/07/2018:svnLENOVO:pn20L6S04200:pvrThinkPadT480:rvnLENOVO:rn20L6S04200:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L6S04200
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  Lenovo T480: throttling CPU issue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Linux OS the CPU package power limit (PL1/2) is set wrong reducing
  drastically CPU performance under load.

  Apparently many Lenovo laptops (certified for Ubuntu) are affected.
  The problem is described in details here: 
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/

  There is "hacky" workaround (not compatible with SecureBoot, a Python
  script writing MSR registers periodically) :
  https://github.com/erpalma/throttled

  There is also a thread on Lenovo forum: https://forums.lenovo.com/t5
  /Linux-Discussion/X1C6-T480s-low-cTDP-and-trip-temperature-in-
  Linux/td-p/4028489

  I confirm the issue affect my machine running the latest kernel
  (4.15.0-45-generic, although bug affects previous releases as well)
  and using the latest firmware from Lenovo (1.19).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  afiergol   4050 F pulseaudio
   /dev/snd/pcmC0D0p:   afiergol   4050 F...m pulseaudio
   /dev/snd/controlC0:  afiergol   4050 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb  8 17:14:17 2019
  HibernationDevice: RESUME=UUID=7b4a9d17-f6d7-42ed-8f12-34f46c41cc6c
  InstallationDate: Installed on 2018-04-05 (309 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 20L6S04200
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nogpumanager 
intel_iommu=on,igfx_off iommu=pt kvm.ignore_msrs=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1814982] Re: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted

2019-02-08 Thread mahmoh
** Tags added: arm64

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

Title:
  efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted

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

Bug description:
  [Impact]
  The Ubuntu kernel is not currently bootable on various arm64 laptops (HP Envy 
x2, Asus NovaGo, Lenovo Miix 630, Lenovo Yoga C630, Samsung ...) because of EFI 
memory permissions/restrictions. The reason is explained in the commit supplied 
below. 

  [Test Case]
  Install and boot Ubuntu on one of the above arm64 laptops.

  [Fix]
  Committed upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e46c2a956215482418d7b315749fb1b6c6bc224

  [Regression Risk]
  This commit adds support for an optional kernel command line parameter so 
there is minimal to no risk.

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

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


[Kernel-packages] [Bug 1814982] Re: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted

2019-02-08 Thread 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1814982

Title:
  efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted

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

Bug description:
  [Impact]
  The Ubuntu kernel is not currently bootable on various arm64 laptops (HP Envy 
x2, Asus NovaGo, Lenovo Miix 630, Lenovo Yoga C630, Samsung ...) because of EFI 
memory permissions/restrictions. The reason is explained in the commit supplied 
below. 

  [Test Case]
  Install and boot Ubuntu on one of the above arm64 laptops.

  [Fix]
  Committed upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e46c2a956215482418d7b315749fb1b6c6bc224

  [Regression Risk]
  This commit adds support for an optional kernel command line parameter so 
there is minimal to no risk.

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

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


[Kernel-packages] [Bug 1814749] Re: linux: 4.18.0-16.17 -proposed tracker

2019-02-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
- phase: Packaging
- phase-changed: Tuesday, 05. February 2019 13:01 UTC
+ boot-testing-requested: true
+ phase: Promote to Proposed
+ phase-changed: Friday, 08. February 2019 16:03 UTC
  reason:
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Pending -- ready for review

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

Title:
  linux: 4.18.0-16.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1814750 (linux-hwe), bug 1814751 (linux-hwe-edge), bug 1814752 
(linux-aws-edge), bug 1814753 (linux-azure-edge), bug 1814754 (linux-gcp-edge), 
bug 1814761 (linux-azure-edge)
  derivatives: bug 1814755 (linux-raspi2), bug 1814757 (linux-aws), bug 1814758 
(linux-azure), bug 1814759 (linux-gcp), bug 1814760 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  phase: Promote to Proposed
  phase-changed: Friday, 08. February 2019 16:03 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814749/+subscriptions

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


[Kernel-packages] [Bug 1814982] Re: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted

2019-02-08 Thread Dimitri John Ledkov
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

** Tags added: ubuntu-on-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/1814982

Title:
  efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted

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

Bug description:
  [Impact]
  The Ubuntu kernel is not currently bootable on various arm64 laptops (HP Envy 
x2, Asus NovaGo, Lenovo Miix 630, Lenovo Yoga C630, Samsung ...) because of EFI 
memory permissions/restrictions. The reason is explained in the commit supplied 
below. 

  [Test Case]
  Install and boot Ubuntu on one of the above arm64 laptops.

  [Fix]
  Committed upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e46c2a956215482418d7b315749fb1b6c6bc224

  [Regression Risk]
  This commit adds support for an optional kernel command line parameter so 
there is minimal to no risk.

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

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


[Kernel-packages] [Bug 1814982] Re: efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted

2019-02-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu Cosmic)
   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/1814982

Title:
  efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted

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

Bug description:
  [Impact]
  The Ubuntu kernel is not currently bootable on various arm64 laptops (HP Envy 
x2, Asus NovaGo, Lenovo Miix 630, Lenovo Yoga C630, Samsung ...) because of EFI 
memory permissions/restrictions. The reason is explained in the commit supplied 
below. 

  [Test Case]
  Install and boot Ubuntu on one of the above arm64 laptops.

  [Fix]
  Committed upstream: 
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=4e46c2a956215482418d7b315749fb1b6c6bc224

  [Regression Risk]
  This commit adds support for an optional kernel command line parameter so 
there is minimal to no risk.

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

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


[Kernel-packages] [Bug 1774443] Re: wireless hardblocked and wireless enable button not functional

2019-02-08 Thread Kai-Heng Feng
Does this still happen on latest mainline kernel?

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

Title:
  wireless hardblocked and wireless enable button not functional

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and
  ubuntu. In Windows, system boots with wireless disabled and then
  pressing the wireless enable button twice enables WiFi.

  In ubuntu, system boots with wireless disabled and wireless enable
  button has no functionality either directly or in combination with the
  fn-key.

  Module hp_wmi may be the culprit? But disabling this has no effect on
  hardblock.

  reference forum post for more detailed info:
  https://ubuntuforums.org/showthread.php?t=2392934=13772159#post13772159

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 31 10:32:38 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-19 (11 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IpRoute:
   default via 172.16.96.1 dev eno1  proto static  metric 100 
   169.254.0.0/16 dev eno1  scope link  metric 1000 
   172.16.96.0/19 dev eno1  proto kernel  scope link  src 172.16.119.109  
metric 100 
   192.17.90.180 via 172.16.96.1 dev eno1  proto dhcp  metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  0357c159-f43c-38f9-8b6f-91bb641d1712  802-3-ethernet  
1527780471  Thu 31 May 2018 10:27:51 AM CDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eno1ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  0357c159-f43c-38f9-8b6f-91bb641d1712  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp8s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
disabled  enabled  enabled
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  naww   1928 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=96f5e2e6-1a22-453e-84c5-21cb7094a381
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-19 (32 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IpRoute:
   default via 192.168.42.129 dev enp0s20u3  proto static  metric 100 
   169.254.0.0/16 dev enp0s20u3  scope link  metric 1000 
   192.168.42.0/24 dev enp0s20u3  proto kernel  scope link  src 192.168.42.168  
metric 100
  MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=753230c7-6c88-415a-93f2-c133b9a161b1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 

[Kernel-packages] [Bug 1795453] Re: [SRU] IO's are issued with incorrect Scatter Gather Buffer

2019-02-08 Thread Michael Reed
This landed in the 4.15 kernel so it should picked up in 16.04.5

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

Title:
  [SRU] IO's are issued with incorrect Scatter Gather Buffer

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

Bug description:
  [Impact]
  We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect 
Scatter Gather Buffer address .

  i.e

   OS is sending the IO with 64 bit Scatter Gather Buffer address , such
  that if we add the length with buffer address then it causes the roll
  over .

  Here is the data we captured in our driver (Printed the SGE details
  which was sent by OS)

  sgl_ptr->Address = f000
  [14547.313240]
  sgl_ptr->Length = 1000
  [14547.313241]
  sge_count = 18
  [14547.313242]
  cmd->index = 9d9

  Note : This issue is observed only when virtualization is enabled

  Product : Broadcom (LSI) Megaraid H840 controller

  
  [Test Case]
  Steps found in comment #60
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/60

  
  [Regression Potential]

  The patches in Comment #59 have been accepted upstream.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/comments/59


  [Other Info]

  Product : Broadcom (LSI) Megaraid H840 controller
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.2:bd09/07/2018:svnDellInc.:pnPowerEdgeR7415:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr:
  dmi.product.family: PowerEdge
  dmi.product.name: PowerEdge R7415
  dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R7415
  dmi.sys.vendor: Dell Inc.
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Oct 12 16:35 seq
   crw-rw+ 1 root audio 116, 33 Oct 12 16:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R7415
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=43e89410-c7ff-11e8-9229-d094661013d8 ro
  ProcVersionSignature: Ubuntu 4.18.0-8.9~18.04.1-generic 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.18.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  

[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

2019-02-08 Thread Seth Forshee
We have a fix applied for bug 1808389, and if that's the same issue then
it should help when running the 4.18 hwe kernel in bionic. I plan to
upload new packages today.

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-08 Thread fyo
Changed to works for me. I had installed 4.18.0-15.16 from the -proposed
repo prior to #19, but a search of kern.log shows that I apparently
failed to select it on boot for some inexplicable reason.

So, yes, fix works. Great. 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/1814555

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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


[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

2019-02-08 Thread Mauricio Faria de Oliveira
Hi Marcelo (@mhcerri),

We have another user who confirmed the 2 patches submitted for linux-
azure also fix the problem on linux(-generic).

  srcu: Prohibit call_srcu() use under raw spinlocks 
  srcu: Lock srcu_data structure in srcu_gp_start()

Could they be submitted for linux as well?

Thank you very much,
Mauricio

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes srcu_gp_start() acquire the srcu_data
  structure's ->lock across the calls to rcu_segcblist_advance() and
  rcu_segcblist_accelerate(), thus preventing this corruption.

  Please investigate this issue and evaluate the proposed fix.

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

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

[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-08 Thread Greg Ward
Fix works for me (I opened duplicate #1815152): I apt upgraded to linux-
modules-4.18.0-15-generic   4.18.0-15.16, and now my system boots
just fine. 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/1814555

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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


[Kernel-packages] [Bug 1815152] Re: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"

2019-02-08 Thread Greg Ward
*** This bug is a duplicate of bug 1814555 ***
https://bugs.launchpad.net/bugs/1814555

Bug fixed! I apt upgraded to linux-image-4.18.0-15-generic 4.18.0-15.16
as usual, and my system boots happily again.

Thank you ~smb for the quick followup.

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

Title:
  kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few days ago, I let update-manager upgrade my kernel from 4.18.0-13
  to 4.18.0-14. Since then, my system is unable to boot. It freezes
  after printing

fb: switching to inteldrmfb from VESA VGA

  but before it gets around to asking me the passphrase for my encrypted
  main partition. (At first I thought it was a problem with cryptsetup
  because it never got to that prompt, but now I'm pretty sure it's
  something to do with changing video mode.)

  However, if I use the grub menu to select the older 4.18.0-13, the
  system boots just fine. It looks very much like a bug introduced
  between 4.18.0-13 and 4.18.0-14.

  Additionally, if I boot 4.18.0-14 in maintenance mode, the kernel
  modesetting does not happen, and the system boots just fine. (Except
  for the 1980s-style low-res video, that is.) This seems like good
  evidence that it's a problem with setting the video mode.

  I'll test with some mainline builds, but I want to get this bug report opened 
before I start rebooting.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=UUID=fb24f9f1-0e89-4ef6-a88a-fb9fc5d776c7
  InstallationDate: Installed on 2018-09-05 (155 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/lubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-14-generic N/A
   linux-backports-modules-4.18.0-14-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-14-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2019-01-23 (16 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7H55-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1604:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  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/1815152/+subscriptions

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


[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-08 Thread fyo
4.18.0-15.16 is available in -proposed and does not boot.

Bader's test kernel above works.

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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


[Kernel-packages] [Bug 1804841] Re: iwlwifi Microcode SW error detected. Restarting 0x2000000.

2019-02-08 Thread Jalon Funk
It may be the same as this issue reported upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=202513

** Bug watch added: Linux Kernel Bug Tracker #202513
   https://bugzilla.kernel.org/show_bug.cgi?id=202513

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

Title:
  iwlwifi Microcode SW error detected.  Restarting 0x200.

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  This seems to be a return of an existing bug, in newer hardware and
  microcode versions.

  Wireless card: Intel Corporation Wireless 8265 / 8275 [8086:24fd] (rev 78)
  Firmware version: 34.0.1
  Description:Ubuntu 18.04.1 LTS

  Frequent errors as soon as I connect to wifi:
  Microcode SW error detected.  Restarting 0x200.

  Expected to happen: Great and stable wifi like a couple of weeks ago
  What happens: very slow, intermittent internet access, lots of ping loss

  Found a suggestion of a workaround: adding these lines to
  /etc/NetworkManager/NetworkManager.conf

  [device]
  wifi.scan-rand-mac-address=no

  These lines were already there, not added by me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.2 [modified: lib/firmware/iwlwifi-8265-36.ucode]
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 15:23:54 2018
  Dependencies:

  InstallationDate: Installed on 2018-09-03 (81 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport

2019-02-08 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-15.16

---
linux (4.18.0-15.16) cosmic; urgency=medium

  * Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555)
- Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5"

  * Userspace break as a result of missing patch backport (LP: #1813873)
- tty: Don't hold ldisc lock in tty_reopen() if ldisc present

 -- Stefan Bader   Thu, 07 Feb 2019 11:24:34
+0100

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

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


[Kernel-packages] [Bug 1813873] Re: Userspace break as a result of missing patch backport

2019-02-08 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-15.16

---
linux (4.18.0-15.16) cosmic; urgency=medium

  * Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555)
- Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5"

  * Userspace break as a result of missing patch backport (LP: #1813873)
- tty: Don't hold ldisc lock in tty_reopen() if ldisc present

 -- Stefan Bader   Thu, 07 Feb 2019 11:24:34
+0100

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  Userspace break as a result of missing patch backport

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Hi,

  The most recent set of Ubuntu kernels applied a variety of tty patches
  including:
  
https://github.com/torvalds/linux/commit/c96cf923a98d1b094df9f0cf97a83e118817e31b

  But have not applied the more recent
  
https://github.com/torvalds/linux/commit/d3736d82e8169768218ee0ef68718875918091a0
  patch.

  This second patch is required to prevent a rather serious regression
  where userspace applications reading from stdin can receive EAGAIN
  when they should not.

  I will try to link correspondence from the mailing list archives once
  they are available, but for now if you have access to the linux-
  console mailing list you can find discussion under the thread
  "Userspace break? read from STDIN returns EAGAIN if tty is "touched"".

  I would appreciate it if this could be examined soon as it is a
  regression on userspace.

  Thanks
  Michael

  
  Good:
  4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018

  
  Bad:
  4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019

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

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


[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-08 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.18.0-15.16

---
linux (4.18.0-15.16) cosmic; urgency=medium

  * Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555)
- Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5"

  * Userspace break as a result of missing patch backport (LP: #1813873)
- tty: Don't hold ldisc lock in tty_reopen() if ldisc present

 -- Stefan Bader   Thu, 07 Feb 2019 11:24:34
+0100

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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


[Kernel-packages] [Bug 1800702] Re: upgrading from 4.4.0-116-generic to latest linux-azure automatically adds an additional ethernet interface

2019-02-08 Thread zaed
** Changed in: linux-azure (Ubuntu)
   Status: New => 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/1800702

Title:
  upgrading from 4.4.0-116-generic to latest linux-azure automatically
  adds an additional ethernet interface

Status in linux-azure package in Ubuntu:
  Fix Released

Bug description:
  This behavior is reproducible:
  * Create a VM running a generic 16.04 kernel
  * update to the linux-azure package
  * run ip addr too see the additional interface

  This behavior is problematic for azure users wanting to use OMPI
  because eth0 and eth1 use the same network card but have different IP
  which will cause OpenMPI job to fail: https://github.com/open-
  mpi/ompi/issues/5818

  Furthermore, it is not expected for a new ethernet interface to be
  created when installing a kernel.

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

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


[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker

2019-02-08 Thread zaed
thanks please fix it for me , good job.

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

Title:
  linux-azure: 4.18.0-1008.8 -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-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
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: 1811406
  phase: Release
  phase-changed: Wednesday, 06. February 2019 16: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/1811415/+subscriptions

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


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

2019-02-08 Thread Oleg Nechiporuk
Same freezing error.
Clean 18.10 Ubuntu instal. 
Processor: Ryzen
Nvidia drivers installed from nvidia homepage. 

More frequently freezing when working with video inside kdenlive. But
had freezes also when only chrome was playing music.

-- 
You 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:
  New
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/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 1815176] Status changed to Confirmed

2019-02-08 Thread 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/1815176

Title:
  Out-of-tree kernel modules can't be built

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to build an external module with gcc 7.3.0 fails with an error
  similar to:

   CC [M]  /home/user/../ApiFunc.o
  In file included from ./include/linux/mmdebug.h:5:0,
  from ./include/linux/gfp.h:5,
  from ./include/linux/slab.h:15,
  from /home/user/.../ApiFunc.c:51:
  ./include/linux/bug.h:5:10: fatal error: asm/bug.h: No such file or directory
  #include 
   ^~~
  compilation terminated.

  This problem is already fixed in the linux kernel starting from version 4.17
  We need to backport the following patch to Ubuntu kernel:
  https://patchwork.kernel.org/patch/10309291/

  Tested by me that it helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julia  1360 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  8 12:17:00 2019
  InstallationDate: Installed on 2018-12-28 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20M5003QRT
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=4384c2b9-39c0-41fe-a898-ef2c212df2e3 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0RET31W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20M5003QRT
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0RET31W(1.14):bd08/03/2018:svnLENOVO:pn20M5003QRT:pvrThinkPadL380:rvnLENOVO:rn20M5003QRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L380
  dmi.product.name: 20M5003QRT
  dmi.product.version: ThinkPad L380
  dmi.sys.vendor: LENOVO

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

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


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

2019-02-08 Thread 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 1815178

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

Title:
  18.04: Raid5 performances on kernel 4.15 are suboptimal

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  We have been running multiple tests using the md driver to build various type 
of RAID devices. Performances on RAID5 are particularly disappointing so we 
would like to know if there are any known issue with the md driver on Bionic 
kernels. Here are some of our results :

  Test (Threads)QCT JBODQCT RAID5 (8 threads)   QCT RAID10
  read(1)   838751 (-10%)   572 (-32%)
  read(2)   1226   1172 (-4%)   1057 (-14%)
  read(4)   1129   2006 (+78%)  1760 (+56%)
  write(1)  804382 (-52%)   398 (-50%)
  write(2)  1047   175 (-83%)   667 (-36%)
  write(4)  883415 (-53%)   871 (-1%)
  randread(1)   863749 (-13%)   619 (-28%)
  randread(2)   1346   1067 (-21%)  1020 (-24%)
  randread(4)   1648   1785 (+8%)   1650 (=)
  randwrite(1)  766287 (-63%)   391 (-50%)
  randwrite(2)  1044   313 (-70%)   664 (-36%)
  randwrite(4)  916282 (-69%)   885 (-3%)

  We are preparing tests with one of the latest mainline kernel.

  TIA,

  ...Louis

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

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


[Kernel-packages] [Bug 1815178] [NEW] 18.04: Raid5 performances on kernel 4.15 are suboptimal

2019-02-08 Thread Louis Bouchard
Public bug reported:

Hello,
We have been running multiple tests using the md driver to build various type 
of RAID devices. Performances on RAID5 are particularly disappointing so we 
would like to know if there are any known issue with the md driver on Bionic 
kernels. Here are some of our results :

Test (Threads)  QCT JBODQCT RAID5 (8 threads)   QCT RAID10
read(1) 838751 (-10%)   572 (-32%)
read(2) 1226   1172 (-4%)   1057 (-14%)
read(4) 1129   2006 (+78%)  1760 (+56%)
write(1)804382 (-52%)   398 (-50%)
write(2)1047   175 (-83%)   667 (-36%)
write(4)883415 (-53%)   871 (-1%)
randread(1) 863749 (-13%)   619 (-28%)
randread(2) 1346   1067 (-21%)  1020 (-24%)
randread(4) 1648   1785 (+8%)   1650 (=)
randwrite(1)766287 (-63%)   391 (-50%)
randwrite(2)1044   313 (-70%)   664 (-36%)
randwrite(4)916282 (-69%)   885 (-3%)

We are preparing tests with one of the latest mainline kernel.

TIA,

...Louis

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1815178

Title:
  18.04: Raid5 performances on kernel 4.15 are suboptimal

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  We have been running multiple tests using the md driver to build various type 
of RAID devices. Performances on RAID5 are particularly disappointing so we 
would like to know if there are any known issue with the md driver on Bionic 
kernels. Here are some of our results :

  Test (Threads)QCT JBODQCT RAID5 (8 threads)   QCT RAID10
  read(1)   838751 (-10%)   572 (-32%)
  read(2)   1226   1172 (-4%)   1057 (-14%)
  read(4)   1129   2006 (+78%)  1760 (+56%)
  write(1)  804382 (-52%)   398 (-50%)
  write(2)  1047   175 (-83%)   667 (-36%)
  write(4)  883415 (-53%)   871 (-1%)
  randread(1)   863749 (-13%)   619 (-28%)
  randread(2)   1346   1067 (-21%)  1020 (-24%)
  randread(4)   1648   1785 (+8%)   1650 (=)
  randwrite(1)  766287 (-63%)   391 (-50%)
  randwrite(2)  1044   313 (-70%)   664 (-36%)
  randwrite(4)  916282 (-69%)   885 (-3%)

  We are preparing tests with one of the latest mainline kernel.

  TIA,

  ...Louis

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

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


[Kernel-packages] [Bug 1815122] Re: Unable to login via tty

2019-02-08 Thread James Stocker
Looks like someone had already reported this issue:

https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095

On there they identify a potential fix:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873

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

Title:
  Unable to login via tty

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 16.04.

  After upgrading the kernel from 4.4.0-141.167-generic to
  4.4.0-142.168-generic I am experiencing problem logging in via the
  tty. I am able to provide my username, but the terminal automatically
  submit password before I am able to type it. If I start the computer
  with the previous kernel (4.4.0-141.167) it works as expected.

  
  I have done strace on the tty in both scenarios while performing the login 
with the following command:

  "sudo strace -p 1572 -s 1024 -vff -o tty-login-issue/login"

  4.4.0-141.167-generic (works):
  https://gist.github.com/ivarconr/b022d2b4cadfc654031e8a930bf4408b

  4.4.0-142.168-generic (fails): 
  https://gist.github.com/ivarconr/603409ad1f0a3343a7f44a854283befc

  
  Let me know if you need me to provide any additional details.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivaosthu   3706 F pulseaudio
   /dev/snd/controlC1:  ivaosthu   3706 F pulseaudio
  CurrentDesktop: i3
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=08d4aeb0-e54b-475e-8a26-b9e8b488a314
  InstallationDate: Installed on 2016-08-12 (909 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EQS2HW00
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic.efi.signed 
root=UUID=a0472864-d2ab-4f9d-8b4c-e89db4dbd51b ro quiet nomodeset splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.4.0-142-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS2HW00
  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: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS2HW00:pvrThinkPadP50:rvnLENOVO:rn20EQS2HW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EQS2HW00
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivaosthu   3706 F pulseaudio
   /dev/snd/controlC1:  ivaosthu   3706 F pulseaudio
  CurrentDesktop: i3
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=08d4aeb0-e54b-475e-8a26-b9e8b488a314
  InstallationDate: Installed on 2016-08-12 (909 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EQS2HW00
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic.efi.signed 
root=UUID=a0472864-d2ab-4f9d-8b4c-e89db4dbd51b ro quiet nomodeset splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.4.0-142-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS2HW00
  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: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS2HW00:pvrThinkPadP50:rvnLENOVO:rn20EQS2HW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EQS2HW00
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1815176] [NEW] Out-of-tree kernel modules can't be built

2019-02-08 Thread Alexander Fomichev
Public bug reported:

Trying to build an external module with gcc 7.3.0 fails with an error
similar to:

 CC [M]  /home/user/../ApiFunc.o
In file included from ./include/linux/mmdebug.h:5:0,
from ./include/linux/gfp.h:5,
from ./include/linux/slab.h:15,
from /home/user/.../ApiFunc.c:51:
./include/linux/bug.h:5:10: fatal error: asm/bug.h: No such file or directory
#include 
 ^~~
compilation terminated.

This problem is already fixed in the linux kernel starting from version 4.17
We need to backport the following patch to Ubuntu kernel:
https://patchwork.kernel.org/patch/10309291/

Tested by me that it helps.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  julia  1360 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb  8 12:17:00 2019
InstallationDate: Installed on 2018-12-28 (41 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20M5003QRT
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=4384c2b9-39c0-41fe-a898-ef2c212df2e3 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: R0RET31W (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20M5003QRT
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0RET31W(1.14):bd08/03/2018:svnLENOVO:pn20M5003QRT:pvrThinkPadL380:rvnLENOVO:rn20M5003QRT:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L380
dmi.product.name: 20M5003QRT
dmi.product.version: ThinkPad L380
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  Out-of-tree kernel modules can't be built

Status in linux package in Ubuntu:
  New

Bug description:
  Trying to build an external module with gcc 7.3.0 fails with an error
  similar to:

   CC [M]  /home/user/../ApiFunc.o
  In file included from ./include/linux/mmdebug.h:5:0,
  from ./include/linux/gfp.h:5,
  from ./include/linux/slab.h:15,
  from /home/user/.../ApiFunc.c:51:
  ./include/linux/bug.h:5:10: fatal error: asm/bug.h: No such file or directory
  #include 
   ^~~
  compilation terminated.

  This problem is already fixed in the linux kernel starting from version 4.17
  We need to backport the following patch to Ubuntu kernel:
  https://patchwork.kernel.org/patch/10309291/

  Tested by me that it helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julia  1360 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  8 12:17:00 2019
  InstallationDate: Installed on 2018-12-28 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20M5003QRT
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=4384c2b9-39c0-41fe-a898-ef2c212df2e3 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0RET31W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20M5003QRT
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1815122] Re: Unable to login via tty

2019-02-08 Thread James Stocker
I just experienced the same issue on 18.04, after upgrading to
4.15.0-45-generic and rebooting, gdm hung after logging in, I had this
issue when trying to log in to tty as described here. I found if I
didn't type a username, the cursor returned and i could type again, if I
entered a username it continually entered newlines until I did a ctrl-c.

I had to revert back to 4.15.0-43-generic in order to log in to either
gdm or tty (when I tried 4.15.0-44-generic it just hung before gdm
finished loading)

I am using a Lenovo P51s

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

Title:
  Unable to login via tty

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 16.04.

  After upgrading the kernel from 4.4.0-141.167-generic to
  4.4.0-142.168-generic I am experiencing problem logging in via the
  tty. I am able to provide my username, but the terminal automatically
  submit password before I am able to type it. If I start the computer
  with the previous kernel (4.4.0-141.167) it works as expected.

  
  I have done strace on the tty in both scenarios while performing the login 
with the following command:

  "sudo strace -p 1572 -s 1024 -vff -o tty-login-issue/login"

  4.4.0-141.167-generic (works):
  https://gist.github.com/ivarconr/b022d2b4cadfc654031e8a930bf4408b

  4.4.0-142.168-generic (fails): 
  https://gist.github.com/ivarconr/603409ad1f0a3343a7f44a854283befc

  
  Let me know if you need me to provide any additional details.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivaosthu   3706 F pulseaudio
   /dev/snd/controlC1:  ivaosthu   3706 F pulseaudio
  CurrentDesktop: i3
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=08d4aeb0-e54b-475e-8a26-b9e8b488a314
  InstallationDate: Installed on 2016-08-12 (909 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EQS2HW00
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic.efi.signed 
root=UUID=a0472864-d2ab-4f9d-8b4c-e89db4dbd51b ro quiet nomodeset splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.4.0-142-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS2HW00
  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: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS2HW00:pvrThinkPadP50:rvnLENOVO:rn20EQS2HW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EQS2HW00
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ivaosthu   3706 F pulseaudio
   /dev/snd/controlC1:  ivaosthu   3706 F pulseaudio
  CurrentDesktop: i3
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=08d4aeb0-e54b-475e-8a26-b9e8b488a314
  InstallationDate: Installed on 2016-08-12 (909 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EQS2HW00
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic.efi.signed 
root=UUID=a0472864-d2ab-4f9d-8b4c-e89db4dbd51b ro quiet nomodeset splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-142-generic N/A
   linux-backports-modules-4.4.0-142-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.4.0-142-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS2HW00
  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 1815152] Re: kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"

2019-02-08 Thread Stefan Bader
*** This bug is a duplicate of bug 1814555 ***
https://bugs.launchpad.net/bugs/1814555

I am rather sure this one is a variation of bug #1814555 for which an
update should be available soon. Marking as duplicate now but if the
4.18.0-15.16 does not help, you can revert that.

** This bug has been marked a duplicate of bug 1814555
   Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

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

Title:
  kernel hangs on boot after "fb: switching to inteldrmfb from VESA VGA"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few days ago, I let update-manager upgrade my kernel from 4.18.0-13
  to 4.18.0-14. Since then, my system is unable to boot. It freezes
  after printing

fb: switching to inteldrmfb from VESA VGA

  but before it gets around to asking me the passphrase for my encrypted
  main partition. (At first I thought it was a problem with cryptsetup
  because it never got to that prompt, but now I'm pretty sure it's
  something to do with changing video mode.)

  However, if I use the grub menu to select the older 4.18.0-13, the
  system boots just fine. It looks very much like a bug introduced
  between 4.18.0-13 and 4.18.0-14.

  Additionally, if I boot 4.18.0-14 in maintenance mode, the kernel
  modesetting does not happen, and the system boots just fine. (Except
  for the 1980s-style low-res video, that is.) This seems like good
  evidence that it's a problem with setting the video mode.

  I'll test with some mainline builds, but I want to get this bug report opened 
before I start rebooting.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=UUID=fb24f9f1-0e89-4ef6-a88a-fb9fc5d776c7
  InstallationDate: Installed on 2018-09-05 (155 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-14-generic 
root=/dev/mapper/lubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-14-generic N/A
   linux-backports-modules-4.18.0-14-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-14-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2019-01-23 (16 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7H55-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1604:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  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/1815152/+subscriptions

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


[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04

2019-02-08 Thread latimerio
I cannot confirm that 4.15.18-041518-generic works stable.
It did work for a while though..
Since a few days my boot is slow again and yesterday and today the system again 
got stuck in emergency mode because of too slow boot.
Thus I think there is more to it than just the kernel.
The only explanation I do have is that there is some dependency between the 
kernel and other packages which get updated when I run apt dist-upgrade.
I am also puzzled that my system boots very fast when I do a CTRL-ALT-DELETE 
when it is stuck in emergency mode. 
So there is a difference between a warm start and a cold boot.
I suppose that there is some hardware initialization which is done too late 
during cold boot but makes the following warm start fast.

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

Title:
  ASPEED server console output extremely slow after upgrade to 18.04

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Server console is extremely slow on ast, after the upgrade from 16.04 to
  18.04.

  [Fix]
  Remove firmware/bootloader configured framebuffer device before probing.

  [Test]
  User confirmed the patch fixes the issue.

  [Regression Potential]
  Low. The fix is in stable tree, limits to one specific device, and other
  DRM drivers already do this for a while.

  ===Original Bug Report===
  After the upgrade from 16.04 to 18.04 my server console is extremely slow.
  It looks similar to the youtube clips mentioned in the problem described 
here: https://ubuntuforums.org/showthread.php?t=2399941
  My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD.
  It runs on an ASUS P9D-X board.
  Before the upgrade everything was fine.
  Now it is so slow that it sometimes even hangs during boot and goes into an 
emergency console where I just can do a ctrl-alt-delete as described in bug 
1802469

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Dec 12 17:07:48 2018
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago)
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 15 07:22 seq
   crw-rw 1 root audio 116, 33 Dec 15 07:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=99dd75dc-dc37-4970-be5a-79d9244a3bcc
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: ASUSTeK COMPUTER INC. P9D-X Series
  Package: linux (not installed)
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=0fa1f208-3a7b-44ca-9f85-e7349a3b1844 ro nosplash
  ProcVersionSignature: Ubuntu 4.15.0-42.45-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.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (64 days ago)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9D-X Series
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd10/13/2014:svnASUSTeKCOMPUTERINC.:pnP9D-XSeries:pvrRev1.xx:rvnASUSTeKCOMPUTERINC.:rnP9D-XSeries:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: P9D-X Series
  dmi.product.version: Rev 1.xx
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1814628] Re: divide error: 0000 with Ubuntu 18.04

2019-02-08 Thread Tony
We are running MAAS here and that server is one that was deployed a
month ago approximately.

1a)
[0.00] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 
2019 (Ubuntu 4.15.0-45.48-generic 4.15.18)
[0.00] Command line: 
BOOT_IMAGE=ubuntu/amd64/generic/bionic/daily/boot-kernel nomodeset ro 
root=squash:http://10.223.0.5:5248/images/ubuntu/amd64/generic/bionic/daily/squashfs
 ip=finer-panda:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{'datasource_list': ['MAAS']}end_cc 
cloud-config-url=http://10.223.0.5:5240/MAAS/metadata/latest/by-id/yx6d6w/?op=get_preseed
 apparmor=0 log_host=10.223.0.5 log_port=514 --- elevator=noop console=tty1 
console=ttyS0,115200 initrd=ubuntu/amd64/generic/bionic/daily/boot-initrd 
BOOTIF=01-f4-e9-d4-b6-5d-70

1b) Last check for them was a couple of months ago
1c) iDRAC says no.
2a) Say what? I tried starting it up and I got the shell appearing in the 
console. Then it just shut itself down again before I had time to react to log 
in. Could be a MAAS thing shutting it down?
2b) And what's that?
2c) Don't see any failures. First it boots up:
Ubuntu 18.04.1 LTS finer-panda ttyS0

finer-panda login: [   50.049021] cloud-init[2188]: Cloud-init v. 
18.4-0ubuntu1~18.04.1 running 'modules:config' at Fri, 08 Feb 2019 07:21:19 
+. Up 48.36 seconds.
[   51.015952] cloud-init[2270]: Powering node off.
ci-info: no authorized ssh keys fingerprints found for user ubuntu.


Then promptly after that:
[   51.169438] cloud-init[2270]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 
'modules:final' at Fri, 08 Feb 2019 07:21:22 +. Up 50.67 seconds.
[   51.169580] cloud-init[2270]: ci-info: no authorized ssh keys fingerprints 
found for user ubuntu.
[   51.169694] cloud-init[2270]: Cloud-init v. 18.4-0ubuntu1~18.04.1 finished 
at Fri, 08 Feb 2019 07:21:23 +. Datasource DataSourceMAAS 
[http://10.223.0.5:5240/MAs
 Stopping Authorization Manager...
[  OK  ] Stopped target Timers.
[  OK  ] Stopped Daily apt upgrade and clean activ Stopping Accounts 
Service...
[  OK  ] Stopped target Host and Network Name Lookups.
 Stopping Read required files in advance...
 Stopping OpenBSD Secure Shell server...
 Stopping LVM2 PV scan on device 8:2...
[  OK  ] Unmounted /var/lib/lxcfs.
etc..

2d) This is the host running the dozens of virtual machines popping up
and shut down daily. Until this day and all the 32 exactly identical
hosts are still up and running...and have been for a month.

I'll try to dig out the info what causes it to shut down instead of
staying up.

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

Title:
  divide error:  with Ubuntu 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Got a host running lots of virtual machines crashing today with the
  following terminal output (if that's to any help):

  [3430458.298979] divide error:  [#1] SMP PTI
  [3430458.304484] Modules linked in: cpuid vhost_net vhost tap 
nf_conntrack_ipv6 nf_defrag_ipv6 xt_physdev br_netfilter ip_set nfnetlink 
kvm_intel kvm irqbypass rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace 
sunrpc cachefiles fscache xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge ebtable_filter ebtables ip6table_filter ip6_tables devlink 
iptable_filter 8021q garp mrp stp llc bonding ipmi_ssif intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp dcdbas intel_cstate 
intel_rapl_perf ipmi_si mei_me ipmi_devintf lpc_ich mei shpchp ipmi_msghandler 
acpi_power_meter mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi
  [3430458.389747]  scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq raid1 raid0 multipath linear crct10dif_pclmul mgag200 
crc32_pclmul i2c_algo_bit ghash_clmulni_intel ttm pcbc mxm_wmi drm_kms_helper 
bnx2x aesni_intel syscopyarea sysfillrect aes_x86_64 sysimgblt fb_sys_fops 
crypto_simd glue_helper ptp cryptd drm pps_core ahci mdio libahci libcrc32c wmi 
[last unloaded: irqbypass]
  [3430458.440756] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [3430458.450411] Hardware name: Dell Inc. PowerEdge R430/0CN7X8, BIOS 2.7.1 
01/26/2018
  [3430458.460008] RIP: 0010:update_group_capacity+0x19d/0x1f0
  [3430458.467098] RSP: 0018:91043ec03bd8 EFLAGS: 00010247
  [3430458.474207] RAX: 006314d6 RBX: 0001 RCX: 
024d
  [3430458.483490] RDX:  RSI:  RDI: 
00022880
  [3430458.492769] RBP: 91043ec03c00 R08: