[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

2017-10-19 Thread Kai-Heng Feng
Please try kernel here:

http://people.canonical.com/~khfeng/lp1722478/

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-19 Thread Steve Langasek
** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1716332] Re: HP Thunderbolt 3 Dock (90W): USB does not work

2017-10-19 Thread Matthias Lohr
Patch accepted, should be in the next kernel release.

https://marc.info/?l=linux-usb&m=150824989207482&w=2

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

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

Title:
  HP Thunderbolt 3 Dock (90W): USB does not work

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Hello,

  i'm using a Lenovo Carbon x1 (5th generation) with a HP Thunderbolt 3
  dock (90W version). All ports are working, except USB Ports - for ~30
  minutes. After ~30 minutes, also the USB ports get activated.

  While waiting for that, dmesg shows something like a "loop" through
  usb devices:

  [...]
  [  389.023845] usb 3-1: new high-speed USB device number 55 using xhci_hcd
  [  389.491841] usb 3-1: new high-speed USB device number 56 using xhci_hcd
  [  389.959928] usb 3-1: new high-speed USB device number 57 using xhci_hcd
  [  390.427925] usb 3-1: new high-speed USB device number 58 using xhci_hcd
  [  390.895832] usb 3-1: new high-speed USB device number 59 using xhci_hcd
  [  391.363817] usb 3-1: new high-speed USB device number 60 using xhci_hcd
  [  391.831818] usb 3-1: new high-speed USB device number 61 using xhci_hcd
  [  392.299759] usb 3-1: new high-speed USB device number 62 using xhci_hcd
  [  392.771813] usb 3-1: new high-speed USB device number 63 using xhci_hcd
  [  393.239765] usb 3-1: new high-speed USB device number 64 using xhci_hcd
  [...]

  Some lines which might be interesting:
  [   13.908506] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.058807] usb 3-2: 2:1: cannot get freq at ep 0x1
  [   14.210694] usb 3-2: 2:1: cannot get freq at ep 0x1

  Best regards
  Matthias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic 4.10.0-33.37
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mlohr  5068 F pulseaudio
   /dev/snd/controlC0:  mlohr  5068 F pulseaudio
   /dev/snd/seq:timidity   1311 F timidity
  Date: Mon Sep 11 09:34:54 2017
  HibernationDevice: RESUME=UUID=50da97f8-11c6-4a09-979a-313bba30057d
  InstallationDate: Installed on 2017-04-12 (151 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 20HRCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed 
root=UUID=6216746e-6b05-4609-9464-e4322637d512 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  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:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1715581] Re: seccomp test suite failed to build on s390x zKVM

2017-10-19 Thread Po-Hsu Lin
seccomp test will now be tested in ubuntu_kernel_selftests test suite.
The old ubuntu_seccomp test will be only tested on Trusty (which does not have 
the seccomp in selftest)

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

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

Title:
  seccomp test suite failed to build on s390x zKVM

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Maybe we should find a new repo, the one we use wasn't updated for two
  years.

  Source: git clone https://github.com/redpig/seccomp.git

  $ make
  cc resumption.c test_harness.h -o resumption -Wall   -ggdb3
  resumption.c: In function ‘TRAP_action’:
  resumption.c:156:42: error: ‘REG_ARG0’ undeclared (first use in this function)
  (unsigned long)ctx->uc_mcontext.gregs[REG_ARG0],
^
  resumption.c:156:42: note: each undeclared identifier is reported only once 
for each function it appears in
  resumption.c:157:42: error: ‘REG_ARG1’ undeclared (first use in this function)
  (unsigned long)ctx->uc_mcontext.gregs[REG_ARG1],
^
  resumption.c:158:42: error: ‘REG_ARG2’ undeclared (first use in this function)
  (unsigned long)ctx->uc_mcontext.gregs[REG_ARG2],
^
  resumption.c:159:42: error: ‘REG_ARG3’ undeclared (first use in this function)
  (unsigned long)ctx->uc_mcontext.gregs[REG_ARG3],
^
  resumption.c:160:42: error: ‘REG_ARG4’ undeclared (first use in this function)
  (unsigned long)ctx->uc_mcontext.gregs[REG_ARG4],
^
  resumption.c:161:42: error: ‘REG_ARG5’ undeclared (first use in this function)
  (unsigned long)ctx->uc_mcontext.gregs[REG_ARG5]);
^
  resumption.c:164:29: error: ‘REG_IP’ undeclared (first use in this function)
if (ctx->uc_mcontext.gregs[REG_IP] >= 0xff60ULL &&
   ^
  resumption.c:169:26: error: ‘REG_SP’ undeclared (first use in this function)
 ctx->uc_mcontext.gregs[REG_SP] -= sizeof(unsigned long);
^
  Makefile:13: recipe for target 'resumption' failed
  make: *** [resumption] Error 1

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

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


[Kernel-packages] [Bug 1723112] Re: Stpped printer. Ubuntu 16.04 upgrade 2

2017-10-19 Thread Paul Garff
Re-installed HPLIP 3.15.2.run  on my desktop pc and configured my
printer via 123.hp.com.  My hp 8710 office jet now works again.
Problem solved!

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

Title:
  Stpped printer.  Ubuntu 16.04  upgrade 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed an new hp 8710 office jet on 10/5/2017 and downloaded
  third party hp drivers from 123.hp.com.  Every thing worked just fine.
  I unfortunately upgraded 16.04 to stay current and my printer quit
  printing with a status of stopped - missing cups filter.  I've
  unplugged, rebooted, deleted printer, tried to re-download printer
  drivers - nothing works.  The only printer settings status is printer
  is not configured.

  I think this is also related to: Sorry Ubuntu 16.04 has experienced
  internal errors, that keeps appearing. HP filters have been deleted
  out of /usr/lib/cups due to an 16.04 upgrade. Now third partly
  printer drivers can't be downloaded and installed. Need help!

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

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


Re: [Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

2017-10-19 Thread Mario Limonciello
There was a problem I found a little while back with hooking up dock to
artful where gnome would crash. That was fixed recently, but I haven't seen
anything else either (both wd15 and tb16 with XPS 9350)

On Thu, Oct 19, 2017, 23:15 Kai-Heng Feng 
wrote:

> Uh, I meant "I cannot reproduce the issue".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1701499
>
> Title:
>   System often freezes or panics if I log in with Dell Dock WD15
>   connected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701499/+subscriptions
>

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10

[Kernel-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

2017-10-19 Thread Olivier Doriath
The firmware updates have no effect on this issue, Daniel! (It would've
been nice though...)

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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


[Kernel-packages] [Bug 1723772] Re: Hibernation

2017-10-19 Thread Kai-Heng Feng
It sounds like a gnome-shell bug instead.

** Also affects: gnome-shell (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/1723772

Title:
  Hibernation

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When the monitor in the modus hibernation gets, it works until then
  ok, even if I'm listenig to music, the music plays further. When I try
  to come back to use the computer the music stops and when I insert my
  password all the programs are closed, as if I had started the OS.
  Every windows are closed and you need to open eveything again. Just to
  inform: I use a Monitor Samsung 4K 28" through DisplayPort. On a
  desktop, not a laptop.

  If you need some more information that I may forgot, I try to answer
  as soon as possible.

  Thank you very much,
  Thiago Benites

  PS: I use the german version of Artful Aardvark
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   thiago 1032 F...m pulseaudio
   /dev/snd/controlC0:  thiago 1032 F pulseaudio
   /dev/snd/controlC1:  thiago 1032 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-02 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 32272R4
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=49009627-59f0-42b5-a403-7fd1a9dfc065 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT67AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT67AUS:bd04/27/2013:svnLENOVO:pn32272R4:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrWin8STDDPKTPG:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 32272R4
  dmi.product.version: ThinkCentre M92p
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   thiago 6664 F...m pulseaudio
   /dev/snd/controlC0:  thiago 6664 F pulseaudio
   /dev/snd/controlC1:  thiago 6664 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-02 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: LENOVO 32272R4
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=49009627-59f0-42b5-a403-7fd1a9dfc065 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT67AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT67AUS:bd04/27/2013:svnLENOVO:pn32272R4:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrWin8STDDPKTPG:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.pro

[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-19 Thread Kai-Heng Feng
SurfaceBook has a nvidia chip, right?
Can you try "blacklist=nouveau modprobe.blacklist=nouveau" kernel parameter?

Also, give this kernel a try:
http://people.canonical.com/~khfeng/lp1723619-revert/

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

Title:
  Boot freeze with Ubuntu 17.10-beta2 on Surface Book

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to boot 17.10-beta2 from USB key on a Surface Book the
  system freezes immediately after "boot" in grub. Not even a
  uncompressing message. Something similar happens even with Fedora 27:
  https://bugzilla.redhat.com/show_bug.cgi?id=1500057

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  Date: Wed Oct 18 20:42:20 2017
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1597961] Re: [Acer Aspire E5-573] Qualcomm Atheros Bluetooth 4.0 not working on [Ubuntu 16.04

2017-10-19 Thread Kai-Heng Feng
Please file an upstream bug at https://bugzilla.kernel.org

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

Title:
  [Acer Aspire E5-573] Qualcomm Atheros Bluetooth 4.0 not working on
  [Ubuntu 16.04

Status in linux package in Ubuntu:
  Expired

Bug description:
  While using Windows with my Acer Aspire E5-573, I'm able to use the Bluetooth:
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: Lite-On Communications Inc QCA9565 / AR9565 Wireless Network 
Adapter [11ad:0803]

  I've installed Ubuntu 16.04 in dual boot. While using Ubuntu, the
  Bluetooth adapter is the only piece of hardware that does not work.

  $ dmesg | grep -i bluetooth
  [   20.905534] Bluetooth: Core ver 2.21
  [   20.905548] Bluetooth: HCI device and connection manager initialized
  [   20.905551] Bluetooth: HCI socket layer initialized
  [   20.905553] Bluetooth: L2CAP socket layer initialized
  [   20.905557] Bluetooth: SCO socket layer initialized
  [   21.477624] Bluetooth: Can't change to loading configuration err
  [   21.477654] Bluetooth: Loading patch file failed
  [  124.347977] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [  124.347980] Bluetooth: BNEP filters: protocol multicast
  [  124.347985] Bluetooth: BNEP socket layer initialized

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinicius   1913 F pulseaudio
   /dev/snd/controlC1:  vinicius   1913 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 30 22:27:24 2016
  HibernationDevice: RESUME=UUID=8ab51bc9-dd7d-4e30-9c74-696b6bb851ef
  InstallationDate: Installed on 2016-06-23 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=216c2bbc-7194-46dc-929e-2a02be497343 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1725086] Re: Spam of dmesg messages, Wi-Fi related

2017-10-19 Thread Leonardo Müller
Now I have rebooted and I am using the kernel version 4.10.0-37-generic
and there is no error. The problem appears to be with the kernel.

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

Title:
  Spam of dmesg messages, Wi-Fi related

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hi

  After I upgraded from Xubuntu 17.04 to 17.10, a message is repeating
  every two minutes: https://pastebin.com/7FA69dme

  I am reporting against linux-firmware because it appears to be Wi-Fi
  related. The system looks like it's working fine, but this message is
  repeating.

  The notebook is a Lenovo Ideapad 310 and it has a QCA9377 wireless +
  bluetooth card.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-firmware 1.169
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 19 23:39:23 2017
  Dependencies:
   
  InstallationDate: Installed on 2017-06-13 (128 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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


[Kernel-packages] [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

2017-10-19 Thread Kai-Heng Feng
Uh, I meant "I cannot reproduce the issue".

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

Title:
  System often freezes or panics if I log in with Dell Dock WD15
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Dell Precision 5520 with Ubuntu 17.04.

  If I first start a Unity session and then connect Dell WD15 USB-C dock
  with an external diplay plugged in, the system detects it properly and
  all the things work flawlessly (ethernet, external keyboard, external
  display, external storage connected to USB on the dock). I can plug-in
  and plug-out the dock multiple times and it just works.

  However if I boot the laptop with the dock already plugged in, first I
  get to the login screen and initially all is ok. Both screens are
  activated, and I can log in using the keyboard connected to the dock.

  When I hit "Enter", both screens go blank for a while, then they turn
  back on and I can see the desktop. A second or maybe two seconds later
  things start falling apart. When I move the mouse pointer a second
  after logging, it is kinda "jumpy", the movement is not smooth. The
  move freezes for a few times. I observed this behaviour only when
  moving the wireless mouse connected to the USB of the laptop. The
  builtin touchpad works smoothly.

  If it was the only issue, this would be a very minor annoyance.
  Sometimes, after a few short mouse pointer freezes the system starts
  working smoothly and all is rock stable from that point. However quite
  often I noticed much worse things happen:

  1. The mouse pointer and everything freezes totally after a few
  seconds from displaying the desktop. It is not possible to switch to
  the console with Ctrl-Alt-F1. This happens in >50% of logins.

  2. Kernel panic.

  I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well
  as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more
  stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

  Even if everything goes fine, I noticed the following errors printed
  in syslog. I'm not sure if they are related, but they look very iffy
  to me:

  Jun 30 10:46:23 p5520 kernel: [   38.391971] DMAR: DRHD: handling fault 
status reg 2
  Jun 30 10:46:23 p5520 kernel: [   38.391977] DMAR: [INTR-REMAP] Request 
device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request 
due to source-id verification failure
  Jun 30 10:46:23 p5520 kernel: [   38.472490] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.472496] usb usb4: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.472497] usb 4-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.472498] usb 4-1.2: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7510] device 
(eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
  Jun 30 10:46:23 p5520 ModemManager[1076]:   (net/eth0): released by 
modem 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2
  Jun 30 10:46:23 p5520 NetworkManager[1129]:   [1498812383.7537] devices 
removed (path: 
/sys/devices/pci:00/:00:1d.6/:06:00.0/:07:02.0/:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
  Jun 30 10:46:23 p5520 kernel: [   38.552718] xhci_hcd :0a:00.0: Host halt 
failed, -19
  Jun 30 10:46:23 p5520 kernel: [   38.552721] xhci_hcd :0a:00.0: Host not 
accessible, reset failed.
  Jun 30 10:46:23 p5520 kernel: [   38.552722] xhci_hcd :0a:00.0: USB bus 4 
deregistered
  Jun 30 10:46:23 p5520 kernel: [   38.552728] xhci_hcd :0a:00.0: remove, 
state 1
  Jun 30 10:46:23 p5520 kernel: [   38.552731] usb usb3: USB disconnect, device 
number 1
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1: USB disconnect, device 
number 2
  Jun 30 10:46:23 p5520 kernel: [   38.552732] usb 3-1.5: USB disconnect, 
device number 3
  Jun 30 10:46:23 p5520 kernel: [   38.553322] usb 3-1.7: USB disconnect, 
device number 4
  Jun 30 10:46:23 p5520 kernel: [   38.556064] BUG: unable to handle kernel 
paging request at 002018387ad8
  Jun 30 10:46:23 p5520 kernel: [   38.556173] IP: __radix_tree_lookup+0x10/0xf0
  Jun 30 10:46:23 p5520 kernel: [   38.556230] PGD 0 
  Jun 30 10:46:23 p5520 kernel: [   38.556232] 
  Jun 30 10:46:24 p5520 kernel: [   38.556280] Oops:  [#1] SMP
  Jun 30 10:46:24 p5520 kernel: [   38.556320] Modules linked in: ccm rfcomm 
cdc_ether usbnet snd_usb_audio snd_usbmidi_lib r8152 mii snd_hda_codec_hdmi 
cmac msr uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev media btusb btrtl joydev hid_multitouch ipmi_devintf 
ipmi_msghandler bnep nls_iso8859_1 arc4 dell_led snd_hda_codec_realtek 
snd_hda_codec_generic i2c_designware_platform i2c_designware_core dell_wmi 
snd_hd

[Kernel-packages] [Bug 1725102] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate()

2017-10-19 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1689446 ***
https://bugs.launchpad.net/bugs/1689446

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1689446, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1689446
   bluetoothd crashed with SIGSEGV in malloc_consolidate from _int_malloc from 
_int_realloc from __GI___libc_realloc from dbus_realloc

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

Title:
  bluetoothd crashed with SIGSEGV in malloc_consolidate()

Status in bluez package in Ubuntu:
  New

Bug description:
  Trying to connect NES30Pro from 8bitdo

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: bluez 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 19 22:27:42 2017
  ExecutablePath: /usr/lib/bluetooth/bluetoothd
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: HP HP EliteBook 850 G3
  ProcCmdline: /usr/lib/bluetooth/bluetoothd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a65dd27b-ea3c-438f-9194-1fe13412160c ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f5920c97108 :   mov
0x8(%rbx),%rax
   PC (0x7f5920c97108) ok
   source "0x8(%rbx)" (0x10007) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f5920fe8c20 ) at malloc.c:4489
   _int_malloc (av=av@entry=0x7f5920fe8c20 , 
bytes=bytes@entry=1265) at malloc.c:3705
   _int_realloc (av=av@entry=0x7f5920fe8c20 , 
oldp=oldp@entry=0x559f492c60e0, oldsize=oldsize@entry=640, nb=nb@entry=1280) at 
malloc.c:4626
   __GI___libc_realloc (oldmem=0x559f492c60f0, bytes=1264) at malloc.c:3245
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  Title: bluetoothd crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.16
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.16:bd06/08/2017:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.76:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A4:71:DD:E5:04  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:828 acl:0 sco:0 events:36 errors:0
TX bytes:392 acl:0 sco:0 commands:35 errors:0

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

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


[Kernel-packages] [Bug 1689446] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate from _int_malloc from _int_realloc from __GI___libc_realloc from dbus_realloc

2017-10-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  bluetoothd crashed with SIGSEGV in malloc_consolidate from _int_malloc
  from _int_realloc from __GI___libc_realloc from dbus_realloc

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.37-0ubuntu5, 
the problem page at 
https://errors.ubuntu.com/problem/7b313fd07b77a23c80ecbe44098ca4f1086407da 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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


[Kernel-packages] [Bug 1725086] Re: Spam of dmesg messages, Wi-Fi related

2017-10-19 Thread Leonardo Müller
I'm sorry for sending the information in chunks, but it's so unstable
there's no way I can do it all at once.

$ lspci
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 
08)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 
(rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 10)
02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter (rev 30)

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0cf3:e360 Atheros Communications, Inc. 
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
Bus 001 Device 003: ID 0bda:57f9 Realtek Semiconductor Corp. 
Bus 001 Device 006: ID 1a2c:0c23 China Resource Semico Co., Ltd 
Bus 001 Device 004: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  Spam of dmesg messages, Wi-Fi related

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hi

  After I upgraded from Xubuntu 17.04 to 17.10, a message is repeating
  every two minutes: https://pastebin.com/7FA69dme

  I am reporting against linux-firmware because it appears to be Wi-Fi
  related. The system looks like it's working fine, but this message is
  repeating.

  The notebook is a Lenovo Ideapad 310 and it has a QCA9377 wireless +
  bluetooth card.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-firmware 1.169
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 19 23:39:23 2017
  Dependencies:
   
  InstallationDate: Installed on 2017-06-13 (128 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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


[Kernel-packages] [Bug 1725086] Re: Spam of dmesg messages, Wi-Fi related

2017-10-19 Thread Leonardo Müller
My system is nigh unusable now. If I disconnect the wireless, the system
becomes very unstable: sudo and gksu stops working, many programs don't
open and other problems.

I've attached the dmesg. Now it's at that very unstable state, if
something happens to wireless it will become very unstable.

** Attachment added: "socorro"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1725086/+attachment/4977597/+files/socorro

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

Title:
  Spam of dmesg messages, Wi-Fi related

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hi

  After I upgraded from Xubuntu 17.04 to 17.10, a message is repeating
  every two minutes: https://pastebin.com/7FA69dme

  I am reporting against linux-firmware because it appears to be Wi-Fi
  related. The system looks like it's working fine, but this message is
  repeating.

  The notebook is a Lenovo Ideapad 310 and it has a QCA9377 wireless +
  bluetooth card.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-firmware 1.169
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 19 23:39:23 2017
  Dependencies:
   
  InstallationDate: Installed on 2017-06-13 (128 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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


[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

2017-10-19 Thread Kai-Heng Feng
It's in zesty-proposed. You need to enable -proposed to test it.

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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


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

2017-10-19 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

** Tags added: artful

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

Title:
  BUG: Bad page map in process vectr  pte:79 pmd:128798067

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  using ubuntu budgie

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1245 F pulseaudio
  Date: Thu Oct 19 22:44:26 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=55fd187a-8ec1-4809-afb6-1289f875d694 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: Bad page map in process vectr  pte:79 pmd:128798067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E3 v02.36
  dmi.board.name: 0A64h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL83006QJ
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.36:bd10/04/2011:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5750 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1725093] [NEW] BUG: Bad page map in process vectr pte:7900000000 pmd:128798067

2017-10-19 Thread Michael Hoke
Public bug reported:

using ubuntu budgie

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  michael1245 F pulseaudio
Date: Thu Oct 19 22:44:26 2017
Failure: oops
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=55fd187a-8ec1-4809-afb6-1289f875d694 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: BUG: Bad page map in process vectr  pte:79 pmd:128798067
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/04/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786E3 v02.36
dmi.board.name: 0A64h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: MXL83006QJ
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.36:bd10/04/2011:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq dc5750 Small Form Factor
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops artful kernel-oops

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

Title:
  BUG: Bad page map in process vectr  pte:79 pmd:128798067

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  using ubuntu budgie

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1245 F pulseaudio
  Date: Thu Oct 19 22:44:26 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=55fd187a-8ec1-4809-afb6-1289f875d694 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: BUG: Bad page map in process vectr  pte:79 pmd:128798067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E3 v02.36
  dmi.board.name: 0A64h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL83006QJ
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.36:bd10/04/2011:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc5750 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

2017-10-19 Thread Daniel van Vugt
Interesting to see Intel released a firmware update specifically for
HDMI on the NUC. If you can boot Windows to install it then it might be
worth trying for NUC owners like Neilen...

https://downloadcenter.intel.com/download/26609/NUCs-HDMI-2-0-Firmware-
Update-Tool-for-Intel-NUC-Kit-NUC7i3BN-NUC7i5BN-NUC7i7BN-
NUC6CAY?product=95062

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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


[Kernel-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

2017-10-19 Thread Daniel van Vugt
... but I mostly still expect this is a Linux kernel bug that applies to
all manufacturers.

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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


[Kernel-packages] [Bug 1725086] [NEW] Spam of dmesg messages, Wi-Fi related

2017-10-19 Thread Leonardo Müller
Public bug reported:

Hi

After I upgraded from Xubuntu 17.04 to 17.10, a message is repeating
every two minutes: https://pastebin.com/7FA69dme

I am reporting against linux-firmware because it appears to be Wi-Fi
related. The system looks like it's working fine, but this message is
repeating.

The notebook is a Lenovo Ideapad 310 and it has a QCA9377 wireless +
bluetooth card.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-firmware 1.169
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct 19 23:39:23 2017
Dependencies:
 
InstallationDate: Installed on 2017-06-13 (128 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Spam of dmesg messages, Wi-Fi related

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hi

  After I upgraded from Xubuntu 17.04 to 17.10, a message is repeating
  every two minutes: https://pastebin.com/7FA69dme

  I am reporting against linux-firmware because it appears to be Wi-Fi
  related. The system looks like it's working fine, but this message is
  repeating.

  The notebook is a Lenovo Ideapad 310 and it has a QCA9377 wireless +
  bluetooth card.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-firmware 1.169
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Oct 19 23:39:23 2017
  Dependencies:
   
  InstallationDate: Installed on 2017-06-13 (128 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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


[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

2017-10-19 Thread Andrey Vertexx
The problem still here...
Ubuntu 14.04.5 LTS (GNU/Linux 4.4.0-97-generic x86_64) on Hyper-V 2012 R2

** Attachment added: "2017102001.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679898/+attachment/4977438/+files/2017102001.JPG

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lo  

[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-19 Thread Steve Langasek
If I boot without the external monitor attached, my text VTs come up
correctly.

They continue to be available if I then dock the laptop.

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1572132] Re: SMB driver (SMBv2) does not show all files when mounting a windows top level share

2017-10-19 Thread Javiar C
I'm also experiencing this bug on Ubuntu 16.04.3.
I don't think Windows supports SMB 1.0 any longer due to security issues. 
(mount error(121): Remote I/O error)   
Adding vers=2.0 or 2.1 to the mount command line options successfully mounts 
the share, but using rsync to back up this Windows share is not reliable if it 
is missing 2 files.

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

Title:
  SMB driver (SMBv2) does not show all files when mounting a windows top
  level share

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using the SMBv2 Protocol to mount a top level windows share (such
  as C:\) not all files (or directories) are shown that exist  on the
  server side. Exactly 2 files are always missing...

  Steps to reproduce:
  On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top 
level share - a subfolder like C:\data\ seems to work)

  sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o
  domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0

  As a result always 2 Files (or directories) are missing in the mounted
  directory of the ubuntu installation.

  Seems to be a kernel bug (source tree: linux/fs/cifs).

  The ubuntu versions I have checked:
  Ubuntu 14.04LTS amd64
  Ubuntu 15.10 amd64
  Ubuntu 16.04 amd64

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.12
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Tue Apr 19 14:50:02 2016
  InstallationDate: Installed on 2016-04-19 (0 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160417.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72

2017-10-19 Thread Dexuan Cui
People are working on this issue: e.g. it looks the patch may work around it: 
https://patchwork.kernel.org/patch/10012603/ (it would be great if somebody can 
test the patch)

Long will send one more patch: 
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1517902.html

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

Title:
  [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration
  after installing kernel 4.4.0-72

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's 
on Hyper-V.
  Microsoft Hyper-v 2012r2 Gen2 VMs

  See Attachment for what happens is immediately after backup starts I
  get an error.

  Eventually the kernel reports it has run out of memory and the machine
  just continuously scrolls errors message related to page allocation.

  When reseting the virtual machine no logs can be found of the problem.

  kernel 4.4.0-72-generic problem still here

  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  SourcePackage: linux-lts-xenial
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  5 12:05 seq
   crw-rw 1 root audio 116, 33 Apr  5 12:05 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (409 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-72-generic N/A
   linux-backports-modules-4.4.0-72-generic  N/A
   linux-firmware1.127.23
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 4.4.0-72-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 10 10:33 seq
   crw-rw 1 root audio 116, 33 Apr 10 10:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2016-02-20 (414 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta 

[Kernel-packages] [Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport

2017-10-19 Thread Bug Watch Updater
** Changed in: linux
   Status: Unknown => Confirmed

** Changed in: linux
   Importance: Unknown => 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/1723619

Title:
  Ubuntu Desktop ISO fails to boot with nouveau on a displayport

Status in Linux:
  Confirmed
Status in Release Notes for Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the latest daily artful image (/current as of 2017-01-14), the
  following occurs on a system with nVidia graphics (on my system, a
  GTX970) when connected to a 4k display over a displayport:
  https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2

  Steps to reproduce:
  - Download latest daily image, check checksums, burn to USB
  - Boot from USB.
  - Choose "Install Ubuntu" or "try ubuntu" at the menu.

  This happens on the livecd, but also upon ugrading the system from a
  previous daily with a different kernel: my "old" daily booted and
  installed fine with kernel 4.12.0-12, then failed with same error once
  dist-upgraded.

  On the faulty system I could test with, it seems to *only* happen over
  displayport/on a 4k screen (I don't own a non-4k displayport screen to
  test the 4k out).

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

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


[Kernel-packages] [Bug 1724992] Re: [Hyper-V] PCI passthrough no longer works on 4.4.0-97

2017-10-19 Thread Joshua R. Poulson
Working ACPI messages from dmesg (dmesg | grep -i ACPI)

[0.00] BIOS-e820: [mem 0x1fff-0x1fffefff] ACPI data
[0.00] BIOS-e820: [mem 0x1000-0x1fff] ACPI NVS
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F5BF0 14 (v00 ACPIAM)
[0.00] ACPI: RSDT 0x1FFF 40 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: FACP 0x1FFF0200 81 (v02 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: DSDT 0x1FFF1D24 003CBE (v01 MSFTVM MSFTVM02 
0002 INTL 02002026)
[0.00] ACPI: FACS 0x1000 40
[0.00] ACPI: WAET 0x1FFF1A80 28 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: SLIC 0x1FFF1AC0 000176 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: OEM0 0x1FFF1CC0 64 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: SRAT 0x1FFF0800 000130 (v02 VRTUAL MICROSFT 
0001 MSFT 0001)
[0.00] ACPI: APIC 0x1FFF0300 000452 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: OEMB 0x1040 64 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x-0x1fff] hotplug
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x1-0xedfff] hotplug
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0xee020-0xfdfff] hotplug
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x2fe000-0xdf] hotplug
[0.00] ACPI: PM-Timer IO Port: 0x408
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: IRQ0 used by override.
[0.00] ACPI: IRQ9 used by override.
[0.00] Using ACPI (MADT) for SMP configuration information

On the failing device:
[0.00] BIOS-e820: [mem 0x1fff-0x1fffefff] ACPI data
[0.00] BIOS-e820: [mem 0x1000-0x1fff] ACPI NVS
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F5BF0 14 (v00 ACPIAM)
[0.00] ACPI: RSDT 0x1FFF 40 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: FACP 0x1FFF0200 81 (v02 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: DSDT 0x1FFF1D24 003CBE (v01 MSFTVM MSFTVM02 
0002 INTL 02002026)
[0.00] ACPI: FACS 0x1000 40
[0.00] ACPI: WAET 0x1FFF1A80 28 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: SLIC 0x1FFF1AC0 000176 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: OEM0 0x1FFF1CC0 64 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: SRAT 0x1FFF0800 000180 (v02 VRTUAL MICROSFT 
0001 MSFT 0001)
[0.00] ACPI: APIC 0x1FFF0300 000452 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: OEMB 0x1040 64 (v01 VRTUAL MICROSFT 
01001706 MSFT 0097)
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: PM-Timer IO Port: 0x408
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: IRQ0 used by override.
[0.00] ACPI: IRQ9 used by override.
[0.00] Using ACPI (MADT) for SMP configuration information

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

Title:
  [Hyper-V] PCI passthrough no longer works on 4.4.0-97

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Azure NV class:

  4.11.0-1013:
  jrp@jrpubuntuv:~$ lspci
  :00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (AGP disabled) (rev 03)
  :00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
  :00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
  :00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
  :00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual 
VGA
  983b:00:00.0 VGA compatible controller: NVIDIA Corporation GM204GL [Tesla 
M60] (rev a1) 

  4.11 finds it fine, but NVIDIA's GRID driver doesn't support newer
  kernels like 4.11.

  4.4.0-97:
  jrp@jrpubuntuv:~$ uname -r
  4.4.0-97-generic
  jrp@jrpubuntuv:~$ lspci
  00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
brid

[Kernel-packages] [Bug 1712709] Re: [Feature] KBL:Enable Suspend to Idle on Dell 9360 and Dell 9365.

2017-10-19 Thread Stefano
My bad, false statement. Suspend-to-idle is working indeed.
It is suspend-to-ram that doesn't, but probably isn't meant to, at all

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

Title:
  [Feature] KBL:Enable Suspend to Idle on Dell 9360 and Dell 9365.

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  This jira is to track the commits for making suspend to idle function
  on Dell 9360 and Dell 9365.

  0ce3fcaff92908c370334ce3b9111aeea71159d6
  33e4f80ee69b5168badf37edbfed796eb48434b9
  76380636280b46541a9d2fe5aac497475bfbcde8
  8110dd281e155e5010ffd657bba4742ebef7a93f
  880a66275ef4d1e08e5d4dcf4cec768de18c68ef
  c7b5a4e6e8fbef8fdf2c529f953000d24c561339
  eed4d47efe9508b855b09754cf6de4325d8a2f0d
  f3b7eaae1b35eb8077610eb7c7db042c9b0645e1

  Target Kernel: 4.13

  Target Release: 17.10

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

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


[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-19 Thread Chatty
No apport with affected kernel possible due to system freeze but see two
posts above.

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

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

Title:
  Boot freeze with Ubuntu 17.10-beta2 on Surface Book

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When trying to boot 17.10-beta2 from USB key on a Surface Book the
  system freezes immediately after "boot" in grub. Not even a
  uncompressing message. Something similar happens even with Fedora 27:
  https://bugzilla.redhat.com/show_bug.cgi?id=1500057

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  Date: Wed Oct 18 20:42:20 2017
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-10-19 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/1725004

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:19:11 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2017-10-19 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 1724657

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

Title:
  Boot freeze with Ubuntu 17.10-beta2 on Surface Book

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When trying to boot 17.10-beta2 from USB key on a Surface Book the
  system freezes immediately after "boot" in grub. Not even a
  uncompressing message. Something similar happens even with Fedora 27:
  https://bugzilla.redhat.com/show_bug.cgi?id=1500057

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  Date: Wed Oct 18 20:42:20 2017
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-10-19 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/1725002

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From the first reboot after a fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:21:13 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2017-10-19 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/1724994

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is from a fresh installation of Ubuntu 17.10. First reboot.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:22:14 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2017-10-19 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/1725003

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From the first boot after fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:21:13 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2017-10-19 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/1724998

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From the first reboot after a fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:19:11 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2017-10-19 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/1724997

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  From the first boot after the fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:18:10 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1724992] Re: [Hyper-V] PCI passthrough no longer works on 4.4.0-97

2017-10-19 Thread Joshua R. Poulson
** 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/1724992

Title:
  [Hyper-V] PCI passthrough no longer works on 4.4.0-97

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Azure NV class:

  4.11.0-1013:
  jrp@jrpubuntuv:~$ lspci
  :00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (AGP disabled) (rev 03)
  :00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
  :00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
  :00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
  :00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual 
VGA
  983b:00:00.0 VGA compatible controller: NVIDIA Corporation GM204GL [Tesla 
M60] (rev a1) 

  4.11 finds it fine, but NVIDIA's GRID driver doesn't support newer
  kernels like 4.11.

  4.4.0-97:
  jrp@jrpubuntuv:~$ uname -r
  4.4.0-97-generic
  jrp@jrpubuntuv:~$ lspci
  00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (AGP disabled) (rev 03)
  00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
  00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
  00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
  00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA 

  4.4.0-77, 79, 83, 87, 89, 91, 92, 93, and 96 also fail to find the
  hardware.

  These used to work, so I am also investigating on the host/hardware
  side.

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

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


[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation

2017-10-19 Thread Joseph Salisbury
I built a test kernel with a revert of commit
369e26773363a6c11186e2c5ec4d83a7c89fee9c.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1646277

Can you test that kernel and report back if it has the bug or not?

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

Title:
  Xenial server 16.04.x will have a black screen after PXE installation

Status in debian-installer package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in debian-installer source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

Bug description:
  The display will keep black screen after install 16.04.x via PXE(need
  use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode
  screen)

  Quanta team is installing Xenial server using PXE boot.   After the
  installation, the console will show a black screen.   Hitting ctl-
  alt-f1 displays the text mode screen OK.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+subscriptions

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


[Kernel-packages] [Bug 1724362] Re: Not booting - 17.10 Beta 2

2017-10-19 Thread Seth Forshee
I have no idea why that's happening ... is it the same if you boot the
Ubuntu kernel? Did you double check that your changes to custom.conf got
saved (since you're having disk problems)?

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

Title:
  Not booting - 17.10 Beta 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm testing the latest 17.10 beta and i'm having issues booting.

  It goes through grub, onto the Ubuntu boot screen ... the dots
  complete and then nothing the machine just stays on this screen then
  eventually the screen turns off.

  The only way I can get it to boot is to go into recovery mode and then
  "Resume normal boot"

  It will then operate but the screen resolution does look like its the
  wrong aspect ratio.

  Not sure what is not working ... help please.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mez3352 F pulseaudio
   /dev/snd/controlC0:  mez3352 F pulseaudio
   /dev/snd/controlC1:  mez3352 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:17:14 2017
  HibernationDevice: RESUME=UUID=353203bd-ca31-4cf9-a132-17f7060695ba
  InstallationDate: Installed on 2017-09-06 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDIONPC MS-7502
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d7df22fa-946c-443f-9093-24f1a777d5a2 ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/26/2007:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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

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


[Kernel-packages] [Bug 1724657] Re: Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-19 Thread Chatty
** Package changed: evince (Ubuntu) => kernel-package (Ubuntu)

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

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

Title:
  Boot freeze with Ubuntu 17.10-beta2 on Surface Book

Status in linux package in Ubuntu:
  New

Bug description:
  When trying to boot 17.10-beta2 from USB key on a Surface Book the
  system freezes immediately after "boot" in grub. Not even a
  uncompressing message. Something similar happens even with Fedora 27:
  https://bugzilla.redhat.com/show_bug.cgi?id=1500057

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.380
  CurrentDesktop: Unity:Unity7
  Date: Wed Oct 18 20:42:20 2017
  LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1725002] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]

2017-10-19 Thread Sethanath
Public bug reported:

>From the first reboot after a fresh installation.

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 803 F pulseaudio
  erick  1164 F pulseaudio
Date: Thu Oct 19 14:21:13 2017
Failure: oops
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.name: 30EA
dmi.board.vendor: Quanta
dmi.board.version: 86.09
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: Compaq Presario F700 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops artful kernel-driver-nouveau kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  New

Bug description:
  From the first reboot after a fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:21:13 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1725003] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]

2017-10-19 Thread Sethanath
Public bug reported:

>From the first boot after fresh installation.

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 803 F pulseaudio
  erick  1164 F pulseaudio
Date: Thu Oct 19 14:21:13 2017
Failure: oops
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.name: 30EA
dmi.board.vendor: Quanta
dmi.board.version: 86.09
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: Compaq Presario F700 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops artful kernel-driver-nouveau kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  New

Bug description:
  From the first boot after fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:21:13 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1724998] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

2017-10-19 Thread Sethanath
Public bug reported:

>From the first reboot after a fresh installation.

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 803 F pulseaudio
  erick  1164 F pulseaudio
Date: Thu Oct 19 14:19:11 2017
Failure: oops
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.name: 30EA
dmi.board.vendor: Quanta
dmi.board.version: 86.09
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: Compaq Presario F700 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops artful kernel-driver-nouveau kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  New

Bug description:
  From the first reboot after a fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:19:11 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1724997] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

2017-10-19 Thread Sethanath
Public bug reported:

>From the first boot after the fresh installation.

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 803 F pulseaudio
  erick  1164 F pulseaudio
Date: Thu Oct 19 14:18:10 2017
Failure: oops
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.name: 30EA
dmi.board.vendor: Quanta
dmi.board.version: 86.09
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: Compaq Presario F700 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops artful kernel-driver-nouveau kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  New

Bug description:
  From the first boot after the fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:18:10 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1725004] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

2017-10-19 Thread Sethanath
Public bug reported:

>From fresh installation.

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 803 F pulseaudio
  erick  1164 F pulseaudio
Date: Thu Oct 19 14:19:11 2017
Failure: oops
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.name: 30EA
dmi.board.vendor: Quanta
dmi.board.version: 86.09
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: Compaq Presario F700 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops artful kernel-driver-nouveau kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  New

Bug description:
  From fresh installation.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:19:11 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1724992] [NEW] [Hyper-V] PCI passthrough no longer works on 4.4.0-97

2017-10-19 Thread Joshua R. Poulson
Public bug reported:

Azure NV class:

4.11.0-1013:
jrp@jrpubuntuv:~$ lspci
:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (AGP disabled) (rev 03)
:00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
:00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
:00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
:00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual 
VGA
983b:00:00.0 VGA compatible controller: NVIDIA Corporation GM204GL [Tesla M60] 
(rev a1) 

4.11 finds it fine, but NVIDIA's GRID driver doesn't support newer
kernels like 4.11.

4.4.0-97:
jrp@jrpubuntuv:~$ uname -r
4.4.0-97-generic
jrp@jrpubuntuv:~$ lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled) (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA 

4.4.0-77, 79, 83, 87, 89, 91, 92, 93, and 96 also fail to find the
hardware.

These used to work, so I am also investigating on the host/hardware
side.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1724992

Title:
  [Hyper-V] PCI passthrough no longer works on 4.4.0-97

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Azure NV class:

  4.11.0-1013:
  jrp@jrpubuntuv:~$ lspci
  :00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (AGP disabled) (rev 03)
  :00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
  :00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
  :00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
  :00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual 
VGA
  983b:00:00.0 VGA compatible controller: NVIDIA Corporation GM204GL [Tesla 
M60] (rev a1) 

  4.11 finds it fine, but NVIDIA's GRID driver doesn't support newer
  kernels like 4.11.

  4.4.0-97:
  jrp@jrpubuntuv:~$ uname -r
  4.4.0-97-generic
  jrp@jrpubuntuv:~$ lspci
  00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host 
bridge (AGP disabled) (rev 03)
  00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
  00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
  00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
  00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA 

  4.4.0-77, 79, 83, 87, 89, 91, 92, 93, and 96 also fail to find the
  hardware.

  These used to work, so I am also investigating on the host/hardware
  side.

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

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


[Kernel-packages] [Bug 1724994] [NEW] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]

2017-10-19 Thread Sethanath
Public bug reported:

This is from a fresh installation of Ubuntu 17.10. First reboot.

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 803 F pulseaudio
  erick  1164 F pulseaudio
Date: Thu Oct 19 14:22:14 2017
Failure: oops
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.name: 30EA
dmi.board.vendor: Quanta
dmi.board.version: 86.09
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: Compaq Presario F700 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops artful kernel-driver-nouveau kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]

Status in linux package in Ubuntu:
  New

Bug description:
  This is from a fresh installation of Ubuntu 17.10. First reboot.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 803 F pulseaudio
erick  1164 F pulseaudio
  Date: Thu Oct 19 14:22:14 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=cf4a41e4-6a32-4a38-9fd2-9f4a87328676 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [ibus-x11:1165]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.08
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.08:bd04/25/2008:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1724657] [NEW] Boot freeze with Ubuntu 17.10-beta2 on Surface Book

2017-10-19 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When trying to boot 17.10-beta2 from USB key on a Surface Book the
system freezes immediately after "boot" in grub. Not even a
uncompressing message. Something similar happens even with Fedora 27:
https://bugzilla.redhat.com/show_bug.cgi?id=1500057

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: evince 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CasperVersion: 1.380
CurrentDesktop: Unity:Unity7
Date: Wed Oct 18 20:42:20 2017
LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty
-- 
Boot freeze with Ubuntu 17.10-beta2 on Surface Book
https://bugs.launchpad.net/bugs/1724657
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown

2017-10-19 Thread Lorenzo
So we just have to wait for the kernel update, I hope it will arrive
soon

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

Title:
  can't disable wi-fi and system hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If I try to turn off wi-fi the system freezes for few seconds and after that 
internet is not working and I can't open settings anymore, even if the wi-fi 
tray icon still shows a connection.
  When I shutdown the system it says that "A stop job for network-manager and 
wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension 
doesn't work neither.
  Everything was working just fine on 17.10 daily builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 23:18:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-22 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  IpRoute:
   default via 192.168.1.254 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Kernel-packages] [Bug 1724071] Re: Update firmware for 4.13 linux-hwe-edge kernel

2017-10-19 Thread Seth Forshee
** Description changed:

+ SRU Justification
+ 
+ Impact: New and updated firmware is needed to support the move to a 4.13
+ based hwe-edge kernel in xenial.
+ 
+ Fix: Cherry pick and backport relevant upstream commits, based primarily
+ on the fwinfo files from the artful kernel abi.
+ 
+ Regression Potential: In most cases these add completely new firmware
+ files which will not be used by older kernels in xenial. In a few cases
+ bug fix updates for existing firmware were also included, but these are
+ not expected to introduce regressions. In all cases the firmware files
+ have been in use in artful for well over a month.
+ 
+ ---
+ 
  Add and update firmware files as necessary to support a 4.12 based
  kernel in the xenial linux-hwe-edge package.

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

Title:
  Update firmware for 4.13 linux-hwe-edge kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: New and updated firmware is needed to support the move to a
  4.13 based hwe-edge kernel in xenial.

  Fix: Cherry pick and backport relevant upstream commits, based
  primarily on the fwinfo files from the artful kernel abi.

  Regression Potential: In most cases these add completely new firmware
  files which will not be used by older kernels in xenial. In a few
  cases bug fix updates for existing firmware were also included, but
  these are not expected to introduce regressions. In all cases the
  firmware files have been in use in artful for well over a month.

  ---

  Add and update firmware files as necessary to support a 4.12 based
  kernel in the xenial linux-hwe-edge package.

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

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


[Kernel-packages] [Bug 1711400] Re: Update firmware for 4.12 linux-hwe-edge kernel

2017-10-19 Thread Seth Forshee
** Description changed:

+ SRU Justification
+ 
+ Impact: New and updated firmware is needed to support the move to a 4.13
+ based hwe-edge kernel in xenial.
+ 
+ Fix: Cherry pick and backport relevant upstream commits, based primarily
+ on the fwinfo files from the artful kernel abi.
+ 
+ Regression Potential: In most cases these add completely new firmware
+ files which will not be used by older kernels in xenial. In a few cases
+ bug fix updates for existing firmware were also included, but these are
+ not expected to introduce regressions. In all cases the firmware files
+ have been in use in artful for well over a month.
+ 
+ ---
+ 
  Add and update firmware files as necessary to support a 4.12-based
  kernel in the xenial linux-hwe-edge package.

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

Title:
  Update firmware for 4.12 linux-hwe-edge kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

  Impact: New and updated firmware is needed to support the move to a
  4.13 based hwe-edge kernel in xenial.

  Fix: Cherry pick and backport relevant upstream commits, based
  primarily on the fwinfo files from the artful kernel abi.

  Regression Potential: In most cases these add completely new firmware
  files which will not be used by older kernels in xenial. In a few
  cases bug fix updates for existing firmware were also included, but
  these are not expected to introduce regressions. In all cases the
  firmware files have been in use in artful for well over a month.

  ---

  Add and update firmware files as necessary to support a 4.12-based
  kernel in the xenial linux-hwe-edge package.

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

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


[Kernel-packages] [Bug 1721856] Re: Suspend ends after seconds and laptop resumes

2017-10-19 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
1849f800fba32cd5a0b647f824f11426b85310d8

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1721856

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Suspend ends after seconds and laptop resumes

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  The suspend/standby ends after seconds and the laptop resumes like
  it'd wake up from suspend. I didn't use suspend for a long time
  (months or years) and can't even estimate when it worked for the last
  time.

  This issue is fixed in 4.14-rc3 mainline kernel - although some parts
  of the installation don't work, like ZFS and nvidia-340 which might
  cause the problem as well.

  I'm willing to do git bisect work if you confirm me that this makes
  sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter   18896 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Oct  6 20:21:35 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (664 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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


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

2017-10-19 Thread Andy Whitcroft
Hello Seth, or anyone else affected,

Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.13 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  Update firmware for 4.12 linux-hwe-edge kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  Add and update firmware files as necessary to support a 4.12-based
  kernel in the xenial linux-hwe-edge package.

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

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


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

2017-10-19 Thread Andy Whitcroft
Hello Seth, or anyone else affected,

Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.13 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

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

Title:
  Update firmware for 4.13 linux-hwe-edge kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  Add and update firmware files as necessary to support a 4.12 based
  kernel in the xenial linux-hwe-edge package.

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

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


[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

2017-10-19 Thread Adam Drew
Built a new kernel from the Ubuntu git and applied the patch to intel-
lpss-pci.c and the trackpad works fine again. I hope this gets into
artful very soon.

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1709708] Re: [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on an HDMI TV until power cycled.

2017-10-19 Thread Adam Kwarciak
Hi,

It seems that newest kernel candidate (from http://kernel.ubuntu.com/)
v4.14-rc5 mainline build fixes the sound issue. But on the other end it
kills LAN :)

Regards
Adam

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

Title:
  [Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but
  produces no sound on an HDMI TV until power cycled.

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Upon bootup, the HDMI output connected to a Samsung TV shows up as an
  output. If this output is selected and a sound test run (either using
  the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no
  sound is heard. Pavumeter does however show sound coming through.

  I found that sound can be fixed by allowing the display to sleep,
  waking it up, and then restarting pulseaudio (pulseaudio -k). After
  that sound output through HDMI to the TV will work until rebooted.

  The fix can be succesfully scripted as follows:

  xset dpms force off
  sleep 1
  pulseaudio -k

  The machine is an Intel NUC6CAYH, connected to a not particularly new
  Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu
  16.04.

  In earlier attempts at fixing the issue I set pulseaudio to never let
  the sound device sleep (commented out load-module module-suspend-on-
  idle in /etc/pulse/default.pa), and also set the default sampling rate
  to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not
  sure if these settings contributed to the fix, but they are not
  sufficient on their own.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug  9 21:48:39 2017
  InstallationDate: Installed on 2017-08-06 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect 
card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625
  dmi.board.name: NUC6CAYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J23203-402
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr:
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382
  mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085

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

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


[Kernel-packages] [Bug 1724362] Re: Not booting - 17.10 Beta 2

2017-10-19 Thread Paul Meredith
I only have Ubuntu on Xorg, or Unity to choose from on the sign in
screen.

System is all updated.

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

Title:
  Not booting - 17.10 Beta 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm testing the latest 17.10 beta and i'm having issues booting.

  It goes through grub, onto the Ubuntu boot screen ... the dots
  complete and then nothing the machine just stays on this screen then
  eventually the screen turns off.

  The only way I can get it to boot is to go into recovery mode and then
  "Resume normal boot"

  It will then operate but the screen resolution does look like its the
  wrong aspect ratio.

  Not sure what is not working ... help please.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mez3352 F pulseaudio
   /dev/snd/controlC0:  mez3352 F pulseaudio
   /dev/snd/controlC1:  mez3352 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:17:14 2017
  HibernationDevice: RESUME=UUID=353203bd-ca31-4cf9-a132-17f7060695ba
  InstallationDate: Installed on 2017-09-06 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDIONPC MS-7502
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d7df22fa-946c-443f-9093-24f1a777d5a2 ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/26/2007:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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

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


[Kernel-packages] [Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)

2017-10-19 Thread Dylan Borg
@jsalisbury I can see that this issue remains fixed with 4.13.6 and
4.13.8 (did not test 4.13.7).

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

Title:
  wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware
  (-22)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I
  get a hung shutdown with the message "wlp3s0: failed to remove key (1,
  ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to
  load firmware versions that do not exist on the system i.e. versions
  33 then 32 of the firmware. It then seems to load version 31 of the
  firmware. Wireless features seem to work normally. The issues are just
  at shutdown time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1621 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Oct  3 06:12:13 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1724912] Re: TSC_DEADLINE incorrectly disabled inside virtual guests

2017-10-19 Thread Dan Streetman
This requires two commits, 594a30fb12424717a41c62323d2a8bf167dbccad and
cc6afe2240298049585e86b1ade85efc8a7f225d, which are already upstream and
will be included in the 4.14 kernel; so this SRU is required only for
artful, as b-series will have the needed patches already.

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

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

Title:
  TSC_DEADLINE incorrectly disabled inside virtual guests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in bb-series:
  Fix Released

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date: Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  That commit is included in the Ubuntu kernels starting at artful
  v4.13.

  However, most hypervisors virtualize TSC deadline timer (and therefore
  it isn't affected by Intel CPU errata inside the guest), and even if
  any hypervisors directly exposed the hardware TSC deadline timer, the
  guests cannot update CPU microcode and therefore it's the hypervisor's
  job to disable/hide/virtualize the TSC deadline timer from the guest.

  This upstream commit skips the microcode check to disable the TSC
  deadline timer if it detects it's running under a hypervisor:

  commit cc6afe2240298049585e86b1ade85efc8a7f225d
  Author: Paolo Bonzini 
  Date:   Tue Oct 10 12:12:57 2017 +0200

  x86/apic: Silence "FW_BUG TSC_DEADLINE disabled due to Errata" on
  hypervisors

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

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


[Kernel-packages] [Bug 1724612] Re: x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

2017-10-19 Thread Eric Desrochers
** Also affects: linux (Ubuntu Artful)
   Importance: Medium
 Assignee: Dan Streetman (ddstreet)
   Status: 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/1724612

Title:
  x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date:   Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  
  That commit is included in the Ubuntu kernels starting at artful v4.13.  
However, the commit includes a check for Skylake Xeons, but the microcode 
update version number differs based on Skylake Xeon stepping, so an additional 
commit is required to correctly check the microcode level of both stepping 3 
and stepping 4 Skylake Xeons, and disable/enable TSC_DEADLINE appropriately.

  Upstream commit that corrects the check is:

  commit 616dd5872e52493863b0202632703eebd51243dc
  Author: Len Brown 
  Date:   Wed Oct 11 17:16:04 2017 -0400

  x86/apic: Update TSC_DEADLINE quirk with additional SKX stepping

  
  Without the additional commit, Skylake Xeon stepping-3 cpus with the fixed 
microcode version will incorrectly have their TSC_DEADLINE disabled.

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

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


[Kernel-packages] [Bug 1700657] Re: Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

2017-10-19 Thread Adam Drew
What's the current status on this? I updated to artful and expected this
to be fixed but my touchpad no longer works (I'd build a patched 4.10
with the fix on zenial).

Do we still have to build our own kernel on artful? Is there a package
in proposed for artful? I couldn't find one. Is there another bug open
for this on artful?

And, technical stuff aside, this bug is 4 months old and was reported on
the last release - why isn't this in artful?

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

Title:
  Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  SRU Justification:
  [Impact]
  Touchpad on Lenovo X1 Yoga / Yoga 720-15IKB does not work.

  [Test Case]
  Touchpad doesn't work on the system.
  With the patch, touchpad works.

  [Regression Potential]
  Minimal. The it adds a device ID to intel-lpss-pci, so it's limited to
  one device.

  ---

  Touchpad is not automatically detected in 14.04, 16.04 or 17.04. I
  tried in live mode and after full installation. I was able to connect
  an external mouse and a bluetooth mouse and both worked. I checked my
  xinput list and no sign:

  ⎡ Virtual core pointerid=2[master pointer
  (3)] ⎜   ↳ Virtual core XTEST pointer  id=4[slave
  pointer  (2)] ⎜   ↳ Wacom HID 50FE Finger touch id=12
  [slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen stylus
  id=13[slave  pointer  (2)] ⎜   ↳ Wacom HID 50FE Pen eraser
  id=16[slave  pointer  (2)] ⎜   ↳ byron's trackpad
  id=17[slave  pointer  (2)] ⎣ Virtual core keyboard
  id=3[master keyboard (2)]↳ Virtual core XTEST keyboard
  id=5[slave  keyboard (3)]↳ Power Button
  id=6[slave  keyboard (3)]↳ Video Bus
  id=7[slave  keyboard (3)]↳ Video Bus
  id=8[slave  keyboard (3)]↳ Power Button
  id=9[slave  keyboard (3)]↳ Apple Inc. Magic Keyboard
  id=10[slave  keyboard (3)]↳ EasyCamera
  id=11[slave  keyboard (3)]↳ Ideapad extra buttons
  id=14[slave  keyboard (3)]↳ AT Translated Set 2 keyboard
  id=15[slave  keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-24-generic 4.10.0-24.28
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  byron  1794 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Jun 26 16:51:37 2017
  InstallationDate: Installed on 2017-06-26 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80X7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic.efi.signed 
root=UUID=39280165-1a70-4b0d-b1fa-3b01e8bc1e25 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-24-generic N/A
   linux-backports-modules-4.10.0-24-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN20WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo YOGA 720-15IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN20WW(V1.06):bd04/12/2017:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLenovoYOGA720-15IKB:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-19 Thread Steve Langasek
The problem is reproducible if I boot with vt.handoff disabled.

It may be worth mentioning that this system has full-disk encryption,
therefore plymouthd is started from the initramfs, not from the root
disk.

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


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

2017-10-19 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/1724911

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps

2017-10-19 Thread Launchpad Bug Tracker
This bug was fixed in the package libseccomp - 2.3.1-2.1ubuntu2~17.04.1

---
libseccomp (2.3.1-2.1ubuntu2~17.04.1) zesty; urgency=medium

  * Backport artful's libseccomp to zesty (LP: #1567597)
- Add support for the SECCOMP_RET_LOG action

libseccomp (2.3.1-2.1ubuntu2) artful; urgency=medium

  * add-log-action.patch: Minimal backport to support the SECCOMP_RET_LOG
action that will be released in Linux kernel version 4.14. (LP: #1567597)

 -- Tyler Hicks   Fri, 06 Oct 2017 18:43:11 +

** Changed in: libseccomp (Ubuntu Zesty)
   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/1567597

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in libseccomp source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument

  [Linux Kernel Tes

[Kernel-packages] [Bug 1567597] Update Released

2017-10-19 Thread Brian Murray
The verification of the Stable Release Update for libseccomp 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/1567597

Title:
  implement 'complain mode' in seccomp for developer mode with snaps

Status in Snappy:
  In Progress
Status in libseccomp package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in libseccomp source package in Zesty:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  A requirement for snappy is that a snap may be placed in developer
  mode which will put the security sandbox in complain mode such that
  violations against policy are logged, but permitted. In this manner
  learning tools can be written to parse the logs, etc and make
  developing on snappy easier.

  Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while
  we can set complain mode to permit all calls, they are not logged at
  this time. I've discussed this with upstream and we are working
  together on the approach. This may require a kernel patch and an
  update to libseccomp, to filing this bug for now as a placeholder and
  we'll add other tasks as necessary.

  UPDATE: ubuntu-core-launcher now supports the '@complain' directive
  that is a synonym for '@unrestricted' so people can at least turn on
  developer mode and not be blocked by seccomp. Proper complain mode for
  seccomp needs to still be implemented (this bug).

  [Impact]

  Snapd needs a way to log seccomp actions without blocking any syscalls
  in order to have a more useful complain mode. Such functionality has
  been acked upstream and patches are on their way into the Linux 4.14
  kernel (backported to 4.12.0-13.14 in artful).

  The corresponding libseccomp changes are still undergoing review
  (https://github.com/seccomp/libseccomp/pull/92). The pull request adds
  a number of new symbols and probably isn't appropriate to backport
  until upstream has acked the pull request. However, only a small part
  of that larger pull request is needed by snapd and that change can be
  safely backported since the only added symbol, the SCMP_ACT_LOG macro,
  must match the SECCOMP_RET_LOG macro that has already been approved
  and merged in the upstream Linux kernel.

  [libseccomp Test Case]

  A large number of tests are ran as part of the libseccomp build.
  However, the "live" tests which test libseccomp with actual kernel
  enforcement are not ran at that time. They can be manually exercised
  to help catch any regressions. Note that on Artful, there's an
  existing test failure (20-live-basic_die%%002-1):

  $ sudo apt build-dep -y libseccomp
  $ sudo apt install -y cython
  $ apt source libseccomp
  $ cd libseccomp-*
  $ autoreconf -ivf && ./configure --enable-python && make check-build
  $ (cd tests && ./regression -T live)

  All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, 
you'll see one pre-existing failure:
  ...
  Test 20-live-basic_die%%002-1 result:   FAILURE 20-live-basic_die TRAP 
rc=159
  ...
  Regression Test Summary
   tests run: 12
   tests skipped: 0
   tests passed: 11
   tests failed: 1
   tests errored: 0
  

  

  Now we can build and run a small test program to test the SCMP_ACT_LOG
  action in the way that snapd wants to use it for developer mode:

  $ sudo apt install -y libseccomp-dev
  $ gcc -o lp1567597-test lp1567597-test.c -lseccomp
  $ ./lp1567597-test

  With a kernel that contains the logging patches and an updated
  libseccomp, the exit code should be 0 and you should have an entry in
  the system log that looks like this:

  audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000
  ses=2 pid=18451 comm="lp1567597-test"
  exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2
  compat=0 ip=0x7f547352c5c0 code=0x7ffc

  If you have an updated libseccomp with an old kernel, you'll see that
  seccomp_init() fails due to the added compatibility check inside of
  libseccomp determines that the kernel doesn't have proper support for
  the new log action:

  $ ./lp1567597-test
  ERROR: seccomp_init: Invalid argument

  [Linux Kernel Test Case]

  All of the libseccomp test cases apply here.

  

  Running the seccomp kernel selftests is als

[Kernel-packages] [Bug 1724912] Re: TSC_DEADLINE incorrectly disabled inside virtual guests

2017-10-19 Thread Eric Desrochers
** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
   Status: Fix Released

** Also affects: linux (Ubuntu Bb-series)
   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/1724912

Title:
  TSC_DEADLINE incorrectly disabled inside virtual guests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in bb-series:
  In Progress

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date: Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  That commit is included in the Ubuntu kernels starting at artful
  v4.13.

  However, most hypervisors virtualize TSC deadline timer (and therefore
  it isn't affected by Intel CPU errata inside the guest), and even if
  any hypervisors directly exposed the hardware TSC deadline timer, the
  guests cannot update CPU microcode and therefore it's the hypervisor's
  job to disable/hide/virtualize the TSC deadline timer from the guest.

  This upstream commit skips the microcode check to disable the TSC
  deadline timer if it detects it's running under a hypervisor:

  commit cc6afe2240298049585e86b1ade85efc8a7f225d
  Author: Paolo Bonzini 
  Date:   Tue Oct 10 12:12:57 2017 +0200

  x86/apic: Silence "FW_BUG TSC_DEADLINE disabled due to Errata" on
  hypervisors

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

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


[Kernel-packages] [Bug 1724912] Re: TSC_DEADLINE incorrectly disabled inside virtual guests

2017-10-19 Thread Dan Streetman
** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: linux (Ubuntu Bb-series)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

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

** Changed in: linux (Ubuntu Bb-series)
   Status: New => In Progress

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

Title:
  TSC_DEADLINE incorrectly disabled inside virtual guests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in bb-series:
  In Progress

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date: Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  That commit is included in the Ubuntu kernels starting at artful
  v4.13.

  However, most hypervisors virtualize TSC deadline timer (and therefore
  it isn't affected by Intel CPU errata inside the guest), and even if
  any hypervisors directly exposed the hardware TSC deadline timer, the
  guests cannot update CPU microcode and therefore it's the hypervisor's
  job to disable/hide/virtualize the TSC deadline timer from the guest.

  This upstream commit skips the microcode check to disable the TSC
  deadline timer if it detects it's running under a hypervisor:

  commit cc6afe2240298049585e86b1ade85efc8a7f225d
  Author: Paolo Bonzini 
  Date:   Tue Oct 10 12:12:57 2017 +0200

  x86/apic: Silence "FW_BUG TSC_DEADLINE disabled due to Errata" on
  hypervisors

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

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


[Kernel-packages] [Bug 1724911] [NEW] text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-10-19 Thread Steve Langasek
Public bug reported:

After upgrading my laptop to Ubuntu 17.10, I am unable to access gettys
on any of the text-mode VTs on my system.

gdm3 is running on VT1, my user session is running on VT2.  I can switch
between these.  If I switch to VT3, I know that the VT switch has
happened in the kernel because the X cursor disappears; but the display
retains the output of my X session, and the text console with getty
never appears.

Switching back to VT2 works fine.

The same problem occurs with either Wayland or X.

My laptop is docked with an external monitor, which could be a factor.
(I also notice that during boot, plymouth is only rendered on the
internal monitor, not the external monitor; this may be related).  I
have not yet tested whether this problem is reproducible if I undock.

The system is booting with vt.handoff=7, which I believe is still the
default in Ubuntu 17.10.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vorlon24080 F pulseaudio
 /dev/snd/controlC0:  vorlon24080 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 09:57:59 2017
HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
InstallationDate: Installed on 2010-09-24 (2582 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: LENOVO 2306CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET97WW (2.57 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
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: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2306CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful

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

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  Relate

[Kernel-packages] [Bug 1724912] [NEW] TSC_DEADLINE incorrectly disabled inside virtual guests

2017-10-19 Thread Dan Streetman
Public bug reported:

An upstream commit added Intel cpu model/microcode checks to disable
TSC_DEADLINE due to cpu errata:

commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
Author: Peter Zijlstra 
Date: Wed May 31 17:52:03 2017 +0200

x86/apic: Add TSC_DEADLINE quirk due to errata

That commit is included in the Ubuntu kernels starting at artful v4.13.

However, most hypervisors virtualize TSC deadline timer (and therefore
it isn't affected by Intel CPU errata inside the guest), and even if any
hypervisors directly exposed the hardware TSC deadline timer, the guests
cannot update CPU microcode and therefore it's the hypervisor's job to
disable/hide/virtualize the TSC deadline timer from the guest.

This upstream commit skips the microcode check to disable the TSC
deadline timer if it detects it's running under a hypervisor:

commit cc6afe2240298049585e86b1ade85efc8a7f225d
Author: Paolo Bonzini 
Date:   Tue Oct 10 12:12:57 2017 +0200

x86/apic: Silence "FW_BUG TSC_DEADLINE disabled due to Errata" on
hypervisors

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: linux (Ubuntu Artful)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Affects: linux (Ubuntu Bb-series)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

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

Title:
  TSC_DEADLINE incorrectly disabled inside virtual guests

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in bb-series:
  In Progress

Bug description:
  An upstream commit added Intel cpu model/microcode checks to disable
  TSC_DEADLINE due to cpu errata:

  commit bd9240a18edfbfa72e957fc2ba831cf1f13ea073
  Author: Peter Zijlstra 
  Date: Wed May 31 17:52:03 2017 +0200

  x86/apic: Add TSC_DEADLINE quirk due to errata

  That commit is included in the Ubuntu kernels starting at artful
  v4.13.

  However, most hypervisors virtualize TSC deadline timer (and therefore
  it isn't affected by Intel CPU errata inside the guest), and even if
  any hypervisors directly exposed the hardware TSC deadline timer, the
  guests cannot update CPU microcode and therefore it's the hypervisor's
  job to disable/hide/virtualize the TSC deadline timer from the guest.

  This upstream commit skips the microcode check to disable the TSC
  deadline timer if it detects it's running under a hypervisor:

  commit cc6afe2240298049585e86b1ade85efc8a7f225d
  Author: Paolo Bonzini 
  Date:   Tue Oct 10 12:12:57 2017 +0200

  x86/apic: Silence "FW_BUG TSC_DEADLINE disabled due to Errata" on
  hypervisors

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

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


Re: [Kernel-packages] [Bug 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

2017-10-19 Thread Ian Bruntlett
Hi Kal,

On 19 October 2017 at 18:17, Kai-Heng Feng 
wrote:

> Does this also happen to 64bit version?
>

The equipment being tested, a Samsung NC10 Netbook, is a 32-bit device, so
I am unable to test it on that.

For convenience, here are some hardware details:-
Intel Atom N270, 1.66GHz, 32-bit, 2GiB RAM, 149.05 GiB hard drive, no
optical drive, Ethernet and WiFi connections, lubuntu typically installed
via USB flashdrive

HTH

Ian

-- 
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1724909] [NEW] virtualbox DKMS package version clashes with in-kernel module version

2017-10-19 Thread Andy Whitcroft
Public bug reported:

The in kernel virtualbox driver module versions are carried by the DKMS
packages from which sync.  This means they also clash with those when
both are installed.  This triggers the ADT tests for virtualbox drivers
to fail with a "different contents" error.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  virtualbox DKMS package version clashes with in-kernel module version

Status in linux package in Ubuntu:
  In Progress

Bug description:
  The in kernel virtualbox driver module versions are carried by the
  DKMS packages from which sync.  This means they also clash with those
  when both are installed.  This triggers the ADT tests for virtualbox
  drivers to fail with a "different contents" error.

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

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


[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB

2017-10-19 Thread Kai-Heng Feng
https://marc.info/?l=linux-kernel&m=150843318726677&w=2

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

Title:
  Touchpad not detected - Lenovo ideapad 320-15IKB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 17.04
  Release:  17.04

  Basically the same bug as described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852

  I'm using a Lenovo ideapad 320-15IKB, though.

  I also tried the latest mainline kernel (4.13.7) which didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meradanis   1747 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct 15 14:23:54 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d
  InstallationDate: Installed on 2017-10-14 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 81BG
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JCN14WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 81BG
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

2017-10-19 Thread Kai-Heng Feng
Does this also happen to 64bit version?

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

2017-10-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  kdump service does not start after configure/reboot

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

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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


[Kernel-packages] [Bug 1722806] Re: [Hyper-V] kdump-tools service does not start at boot on Ubuntu 17.10

2017-10-19 Thread Thadeu Lima de Souza Cascardo
*** This bug is a duplicate of bug 1708409 ***
https://bugs.launchpad.net/bugs/1708409

** This bug has been marked a duplicate of bug 1708409
   kdump service does not start after configure/reboot

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

Title:
  [Hyper-V] kdump-tools service does not start at boot on Ubuntu 17.10

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Artful:
  Confirmed

Bug description:
  [Summary]
  kdump-tools service does not start automatically at boot on Ubuntu 17.10 
(4.13.0-12-generic x86_64 kernel). Because of this, the kernel crash dump is 
not working.

  [Steps]
  - Tried enabling it using systemctl. No errors were shown after enabling it, 
but after reboot the service is still not running.
  - "kdump-config show" is reporting "current state:Not ready to kdump"
  - "kdump-config load" command worked and the state changed to "ready to 
kdump". kdump-tools service is still stopped but VM reboots (and a dump is 
generated) if a crash is triggered.
  - Starting the kdump-tools service is also ok. After it is started, a crash 
dump is generated in case of system crash.

  [Additional logs]
  root@ubuntu1710:~# service kdump-tools status
  ● kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: ena
 Active: inactive (dead)

  root@ubuntu1710:~# dmesg | grep crashkernel
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/ubuntu1710--vg-root ro console=tty0 console=ttyS1 
crashkernel=384M
  [0.00] Reserving 384MB of memory at 400MB for crashkernel (System 
RAM: 2047MB)

  root@ubuntu1710:~# cat /var/log/syslog | grep kexec
  Oct 11 06:30:08 ubuntu1710 systemd[1]: Starting LSB: Execute the kexec -e 
command to reboot system...
  Oct 11 06:30:09 ubuntu1710 systemd[1]: Started LSB: Execute the kexec -e 
command to reboot system.
  Oct 11 06:30:10 ubuntu1710 systemd[1]: Starting LSB: Load kernel image with 
kexec...
  Oct 11 06:30:10 ubuntu1710 systemd[1]: Started LSB: Load kernel image with 
kexec.

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

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


[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB

2017-10-19 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Touchpad not detected - Lenovo ideapad 320-15IKB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 17.04
  Release:  17.04

  Basically the same bug as described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852

  I'm using a Lenovo ideapad 320-15IKB, though.

  I also tried the latest mainline kernel (4.13.7) which didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meradanis   1747 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct 15 14:23:54 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d
  InstallationDate: Installed on 2017-10-14 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 81BG
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JCN14WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 81BG
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1706243] Re: Stranded with ENODEV after mdadm --readonly

2017-10-19 Thread Trent Nelson
Confirmed with 4.10.0-38-generic from zesty-proposed.

Will this be hitting the 4.11.0 branch as well?  I'm actually using the
generic-hwe-16.04-edge package on xenial.

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

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

Title:
  Stranded with ENODEV after mdadm --readonly

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  == SRU Justification ==
  The bug reporter was trying to turn on the RAID journal.  One of the steps
  is to set the device readonly.  This did not work as planned, or indeed at
  all. After the first --readonly, all requests for the device report
  "No such device or address" until a reboot, though /proc/mdstat says the
  device is still there.

  This bug is fixed by mainline commit 065e519e71b2c1f41936cce75b46b5ab34adb588,
  which is in mainline as of 4.12-rc1.  The commit was also cc'd to stable, but
  upstream 4.10 is EOL, so that is the reason for the SRU request.

  == Fix ==
  commit 065e519e71b2c1f41936cce75b46b5ab34adb588
  Author: NeilBrown 
  Date:   Thu Apr 6 11:16:33 2017 +0800

  md: MD_CLOSING needs to be cleared after called md_set_readonly or
  do_md_stop

  == Regression Potential ==
  This commit was also cc'd to stable and accepted, so additional upstream 
review
  was performed.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3&id=065e519e71b2c1f41936cce75b46b5ab34adb588
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:

  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1722806] Re: [Hyper-V] kdump-tools service does not start at boot on Ubuntu 17.10

2017-10-19 Thread Brad Figg
** Also affects: makedumpfile (Ubuntu Artful)
   Importance: Undecided
   Status: Confirmed

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

Title:
  [Hyper-V] kdump-tools service does not start at boot on Ubuntu 17.10

Status in makedumpfile package in Ubuntu:
  Confirmed
Status in makedumpfile source package in Artful:
  Confirmed

Bug description:
  [Summary]
  kdump-tools service does not start automatically at boot on Ubuntu 17.10 
(4.13.0-12-generic x86_64 kernel). Because of this, the kernel crash dump is 
not working.

  [Steps]
  - Tried enabling it using systemctl. No errors were shown after enabling it, 
but after reboot the service is still not running.
  - "kdump-config show" is reporting "current state:Not ready to kdump"
  - "kdump-config load" command worked and the state changed to "ready to 
kdump". kdump-tools service is still stopped but VM reboots (and a dump is 
generated) if a crash is triggered.
  - Starting the kdump-tools service is also ok. After it is started, a crash 
dump is generated in case of system crash.

  [Additional logs]
  root@ubuntu1710:~# service kdump-tools status
  ● kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
preset: ena
 Active: inactive (dead)

  root@ubuntu1710:~# dmesg | grep crashkernel
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/ubuntu1710--vg-root ro console=tty0 console=ttyS1 
crashkernel=384M
  [0.00] Reserving 384MB of memory at 400MB for crashkernel (System 
RAM: 2047MB)

  root@ubuntu1710:~# cat /var/log/syslog | grep kexec
  Oct 11 06:30:08 ubuntu1710 systemd[1]: Starting LSB: Execute the kexec -e 
command to reboot system...
  Oct 11 06:30:09 ubuntu1710 systemd[1]: Started LSB: Execute the kexec -e 
command to reboot system.
  Oct 11 06:30:10 ubuntu1710 systemd[1]: Starting LSB: Load kernel image with 
kexec...
  Oct 11 06:30:10 ubuntu1710 systemd[1]: Started LSB: Load kernel image with 
kexec.

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

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


[Kernel-packages] [Bug 1724836] Re: Xenial update to 4.4.93 stable release

2017-10-19 Thread Stefan Bader
Manually applied "CIFS: Reconnect expired SMB sessions" ignoring some
fuzz and reverting the implementation of smb2_is_session_expired() to
its original 4.13 form as we carry related backports for bug #1670508
"CIFS: Enable encryption for SMB3".

Replace "UBUNTU: SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819"
with the upstream stable version.

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

Title:
  Xenial update to 4.4.93 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  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 4.4.93 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.93 stable release shall be applied:
  * brcmfmac: add length check in brcmf_cfg80211_escan_handler()
  * ext4: in ext4_seek_{hole,data}, return -ENXIO for negative offsets
  * CIFS: Reconnect expired SMB sessions
  * nl80211: Define policy for packet pattern attributes
  * iwlwifi: mvm: use IWL_HCMD_NOCOPY for MCAST_FILTER_CMD
  * rcu: Allow for page faults in NMI handlers
  * USB: dummy-hcd: Fix deadlock caused by disconnect detection
  * MIPS: math-emu: Remove pr_err() calls from fpu_emu()
  * dmaengine: edma: Align the memcpy acnt array size with the transfer
  * HID: usbhid: fix out-of-bounds bug
  * crypto: shash - Fix zero-length shash ahash digest crash
  * KVM: nVMX: fix guest CR4 loading when emulating L2 to L1 exit
  * usb: renesas_usbhs: Fix DMAC sequence for receiving zero-length packet
  * iommu/amd: Finish TLB flush in amd_iommu_unmap()
  * ALSA: usb-audio: Kill stray URB at exiting
  * ALSA: seq: Fix use-after-free at creating a port
  * ALSA: seq: Fix copy_from_user() call inside lock
  * ALSA: caiaq: Fix stray URB at probe error path
  * ALSA: line6: Fix leftover URB at error-path during probe
  * usb: gadget: composite: Fix use-after-free in
usb_composite_overwrite_options
  * direct-io: Prevent NULL pointer access in submit_page_section
  * fix unbalanced page refcounting in bio_map_user_iov
  * USB: serial: ftdi_sio: add id for Cypress WICED dev board
  * USB: serial: cp210x: add support for ELV TFD500
  * USB: serial: option: add support for TP-Link LTE module
  * Revert "UBUNTU: SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819"
  * USB: serial: qcserial: add Dell DW5818, DW5819
  * USB: serial: console: fix use-after-free after failed setup
  * x86/alternatives: Fix alt_max_short macro to really be a max()
  * Linux 4.4.93

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

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


[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

2017-10-19 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 makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1635597

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  [Impact]
  When the target device where to dump the kernel is under a multipath 
configuration, dumping will fail, possibly leaving the system stuck in the 
kdump kernel.
  The fix is to include some scsi device handlers needed for the multipath 
setup inside the initramfs image that is used by kdump.
  All modules currently loaded in the system are included.

  [Test Case]
  Setting up kdump to target a multipath device using an appropriate storage 
that requires such scsi_dh modules and triggering a crash will demonstrate that 
kdump fails.
  After the fix, it works fine.

  [Regression Potential]
  If a bug is introduced, loading kdump might fail, and a crash will not be 
generated. A worse regression that might be considered is the system is stuck 
in such a kdump kernel and needs to be rebooted locally (and the crash file is 
not generated either). But since this is what we are trying to fix, we don't 
expect other systems to break. This didn't happen on a small (less than 1GiB of 
RAM) x86 VM, though.

  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c080

[Kernel-packages] [Bug 1724836] Re: Xenial update to 4.4.93 stable release

2017-10-19 Thread Stefan Bader
** Description changed:

+ SRU Justification
  
- 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 4.4.93 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- 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 4.4.93 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.93 stable release shall be
- applied:
+ The following patches from the 4.4.93 stable release shall be applied:
+ * brcmfmac: add length check in brcmf_cfg80211_escan_handler()
+ * ext4: in ext4_seek_{hole,data}, return -ENXIO for negative offsets
+ * CIFS: Reconnect expired SMB sessions
+ * nl80211: Define policy for packet pattern attributes
+ * iwlwifi: mvm: use IWL_HCMD_NOCOPY for MCAST_FILTER_CMD
+ * rcu: Allow for page faults in NMI handlers
+ * USB: dummy-hcd: Fix deadlock caused by disconnect detection
+ * MIPS: math-emu: Remove pr_err() calls from fpu_emu()
+ * dmaengine: edma: Align the memcpy acnt array size with the transfer
+ * HID: usbhid: fix out-of-bounds bug
+ * crypto: shash - Fix zero-length shash ahash digest crash
+ * KVM: nVMX: fix guest CR4 loading when emulating L2 to L1 exit
+ * usb: renesas_usbhs: Fix DMAC sequence for receiving zero-length packet
+ * iommu/amd: Finish TLB flush in amd_iommu_unmap()
+ * ALSA: usb-audio: Kill stray URB at exiting
+ * ALSA: seq: Fix use-after-free at creating a port
+ * ALSA: seq: Fix copy_from_user() call inside lock
+ * ALSA: caiaq: Fix stray URB at probe error path
+ * ALSA: line6: Fix leftover URB at error-path during probe
+ * usb: gadget: composite: Fix use-after-free in
+   usb_composite_overwrite_options
+ * direct-io: Prevent NULL pointer access in submit_page_section
+ * fix unbalanced page refcounting in bio_map_user_iov
+ * USB: serial: ftdi_sio: add id for Cypress WICED dev board
+ * USB: serial: cp210x: add support for ELV TFD500
+ * USB: serial: option: add support for TP-Link LTE module
+ * Revert "UBUNTU: SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819"
+ * USB: serial: qcserial: add Dell DW5818, DW5819
+ * USB: serial: console: fix use-after-free after failed setup
+ * x86/alternatives: Fix alt_max_short macro to really be a max()
+ * Linux 4.4.93

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

Title:
  Xenial update to 4.4.93 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  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 4.4.93 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.93 stable release shall be applied:
  * brcmfmac: add length check in brcmf_cfg80211_escan_handler()
  * ext4: in ext4_seek_{hole,data}, return -ENXIO for negative offsets
  * CIFS: Reconnect expired SMB sessions
  * nl80211: Define policy for packet pattern attributes
  * iwlwifi: mvm: use IWL_HCMD_NOCOPY for MCAST_FILTER_CMD
  * rcu: Allow for page faults in NMI handlers
  * USB: dummy-hcd: Fix deadlock caused by disconnect detection
  * MIPS: math-emu: Remove pr_err() calls from fpu_emu()
  * dmaengine: edma: Align the memcpy acnt array size with the transfer
  * HID: usbhid: fix out-of-bounds bug
  * crypto: shash - Fix zero-length shash ahash digest crash
  * KVM: nVMX: fix guest CR4 loading when emulating L2 to L1 exit
  * usb: renesas_usbhs: Fix DMAC sequence for receiving zero-length packet
  * iommu/amd: Finish TLB flush in amd_iommu_unmap()
  * ALSA: usb-audio: Kill stray URB at exiting
  * ALSA: seq: Fix use-after-free at creating a port
  * ALSA: seq: Fix copy_from_user() call inside lock
  * ALSA: c

[Kernel-packages] [Bug 1712709] Re: [Feature] KBL:Enable Suspend to Idle on Dell 9360 and Dell 9365.

2017-10-19 Thread Stefano
Just upgraded to Artful, it still doesn't work.

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

Title:
  [Feature] KBL:Enable Suspend to Idle on Dell 9360 and Dell 9365.

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  This jira is to track the commits for making suspend to idle function
  on Dell 9360 and Dell 9365.

  0ce3fcaff92908c370334ce3b9111aeea71159d6
  33e4f80ee69b5168badf37edbfed796eb48434b9
  76380636280b46541a9d2fe5aac497475bfbcde8
  8110dd281e155e5010ffd657bba4742ebef7a93f
  880a66275ef4d1e08e5d4dcf4cec768de18c68ef
  c7b5a4e6e8fbef8fdf2c529f953000d24c561339
  eed4d47efe9508b855b09754cf6de4325d8a2f0d
  f3b7eaae1b35eb8077610eb7c7db042c9b0645e1

  Target Kernel: 4.13

  Target Release: 17.10

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

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


[Kernel-packages] [Bug 1658733] Re: Ubuntu 16.04.2KVM:kdump fails to mount root file system when noirqdistrib is missing as dump kernel parameter

2017-10-19 Thread Brad Figg
** Also affects: kexec-tools (Ubuntu Artful)
   Importance: High
 Assignee: Louis Bouchard (louis)
   Status: Invalid

** Also affects: makedumpfile (Ubuntu Artful)
   Importance: Undecided
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: In Progress

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

Title:
  Ubuntu 16.04.2KVM:kdump fails to mount root file system when
  noirqdistrib is missing as dump kernel parameter

Status in The Ubuntu-power-systems project:
  Confirmed
Status in kexec-tools package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in kexec-tools source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  New
Status in kexec-tools source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in kexec-tools source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  New
Status in kexec-tools source package in Artful:
  Invalid
Status in makedumpfile source package in Artful:
  In Progress

Bug description:
  [Impact]
  On Power Systems, some interrupts are missed, and dumping the crash will 
fail. Adding the noirqdistrib kernel parameter to the kdump kernel will fix 
this.

  [Test Case]
  Setting up kdump to target a virtio-scsi device on a Power System.

  [Regression Potential]
  The parameter could be interpreted differently on a different platform and 
kdump would fail. However, it has been verified that no other platform uses 
such parameter. If another parameter would have been incorrectly removed on the 
patch, kdump could fail on other systems.


  == Comment: #0 - Richard M. Scheller - 2016-12-14 16:50:26 ==

  ---Problem Description---

  On a KVM guest installed to a multipath root device, the kdump kernel
  fails to mount the root file system.  This error does not occur in a
  similar guest installed to a single path device.

  Full console output of the kdump failure is attached.  These messages
  from the output may be relevant:

  Begin: Loading multipath modules ... Success: loaded module dm-multipath.
  done.
  Begin: Loading multipath hardware handlers ... Failure: failed to load module 
sc
  si_dh_alua.
  Failure: failed to load module scsi_dh_rdac.
  Failure: failed to load module scsi_dh_emc.
  done.
  Begin: Starting multipathd ... done.

  ---uname output---
  Linux dotg9 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8247-22L Ubuntu 16.04.1 KVM guest

  ---Steps to Reproduce---
   - Install Ubuntu 16.04.1 to a muiltpath target disk
  - Install kdump-tools package
  - Configure kexec-tools to reserve sufficient RAM for the kdump kernel to 
load (I use 512MB) in /etc/default/grub.d/kexec-tools.cfg
  - Run update-grub
  - Reboot
  - Initiate a system crash using "echo c > /proc/sysrq-trigger"

  == Comment: #12 - Richard M. Scheller - 2016-12-20 20:37:45 ==
  Here is the log level 8 kdump console log requested in comment 10.

  == Comment: #21 - Richard M. Scheller - 2017-01-06 11:04:17 ==
  (In reply to comment #19)
  > Hi, I logged in dotkvm and I couldn't find the guest dotg9. Also, although I
  > found a dotg9.xml in /kte/xml/ it doesn't look like it uses multipath (it
  > uses .img files which I didn't found as disks).
  >
  > Could you please recreate the guest for further debug?

  Yes, I recreated the guest with its correct multipath lun
  configuration.  I have also attached the guest XML to this bug.

  > Besides that could you please let us know:
  >  - is the multipath the system's root? I mean / is installed/mounted on the
  > multipath device?

  Yes, the guest has only one disk.  That disk is actually a LUN from a
  fiber channel storage device with two paths on the host side.  I have
  passed through both paths to the guest, so the multipath nature of the
  target disk is known to the guest.

  In other words, the guest sees a multipath device and is using it as a
  multipath device.  The root file system is called /dev/mapper/mpatha-
  part2 on the guest.

  >  - how did you attach the device to the guest?

  Each FC LUN path on the host is mapped to a virtio-scsi controller on
  the guest using LUN passthrough.  (See the guest XML for details on
  this.)

  == Comment: #22 - Mauro Sergio Martins Rodrigues  - 2017-01-11 09:31:38 ==
  I managed to get kdump to mount rootfs and perform its tasks by setting 
KDUMP_CMDLINE_APPEND="nr_cpus=4" parameter in /etc/default/kdump-tools see 
http://pastebin.hursley.ibm.com/8239

  I'm still investigating to figure out what is the reason behind this
  behavior.

  Thanks,

  --
  maurosr

  == Comment: #23 - Mauricio Faria De Oliveira  - 2017-01-11 11:56:40 ==
  Mauro,

  (In reply to comment #22)
  > I managed to get kdump to mount rootfs and perform its tasks by setting
  

[Kernel-packages] [Bug 1724362] Re: Not booting - 17.10 Beta 2

2017-10-19 Thread Seth Forshee
Also update your system, seems there was a gnome-shell bug affecting
some AMD/Nvidia cards. It sounds similar to your problem and has been
fixed. Bug #1723577 for reference.

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

Title:
  Not booting - 17.10 Beta 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm testing the latest 17.10 beta and i'm having issues booting.

  It goes through grub, onto the Ubuntu boot screen ... the dots
  complete and then nothing the machine just stays on this screen then
  eventually the screen turns off.

  The only way I can get it to boot is to go into recovery mode and then
  "Resume normal boot"

  It will then operate but the screen resolution does look like its the
  wrong aspect ratio.

  Not sure what is not working ... help please.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mez3352 F pulseaudio
   /dev/snd/controlC0:  mez3352 F pulseaudio
   /dev/snd/controlC1:  mez3352 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 21:17:14 2017
  HibernationDevice: RESUME=UUID=353203bd-ca31-4cf9-a132-17f7060695ba
  InstallationDate: Installed on 2017-09-06 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: MEDIONPC MS-7502
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d7df22fa-946c-443f-9093-24f1a777d5a2 ro recovery nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7502
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/26/2007:svnMEDIONPC:pnMS-7502:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7502:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7502
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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

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


[Kernel-packages] [Bug 1724863] [NEW] bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2017-10-19 Thread Seth Forshee
Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-
  edge 4.13.0-16.19~16.04.3

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz

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

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


[Kernel-packages] [Bug 1724863] Re: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2017-10-19 Thread Seth Forshee
** Attachment added: "make.log"
   https://bugs.launchpad.net/bugs/1724863/+attachment/4976087/+files/make.log

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-
  edge 4.13.0-16.19~16.04.3

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz

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

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


[Kernel-packages] [Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown

2017-10-19 Thread Keerthi
I'm confirming this bug. System hangs on shutdown/reboot with the "A
stop job for network-manager and wpa supplicant is running" message.

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

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

Title:
  can't disable wi-fi and system hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If I try to turn off wi-fi the system freezes for few seconds and after that 
internet is not working and I can't open settings anymore, even if the wi-fi 
tray icon still shows a connection.
  When I shutdown the system it says that "A stop job for network-manager and 
wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension 
doesn't work neither.
  Everything was working just fine on 17.10 daily builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 23:18:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-22 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  IpRoute:
   default via 192.168.1.254 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Kernel-packages] [Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown

2017-10-19 Thread Keerthi
** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721880/+attachment/4976031/+files/lspci.txt

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

Title:
  can't disable wi-fi and system hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If I try to turn off wi-fi the system freezes for few seconds and after that 
internet is not working and I can't open settings anymore, even if the wi-fi 
tray icon still shows a connection.
  When I shutdown the system it says that "A stop job for network-manager and 
wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension 
doesn't work neither.
  Everything was working just fine on 17.10 daily builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 23:18:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-22 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  IpRoute:
   default via 192.168.1.254 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Kernel-packages] [Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown

2017-10-19 Thread Keerthi
** Attachment added: "lshw.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721880/+attachment/4976030/+files/lshw.txt

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

Title:
  can't disable wi-fi and system hangs on shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If I try to turn off wi-fi the system freezes for few seconds and after that 
internet is not working and I can't open settings anymore, even if the wi-fi 
tray icon still shows a connection.
  When I shutdown the system it says that "A stop job for network-manager and 
wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension 
doesn't work neither.
  Everything was working just fine on 17.10 daily builds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 23:18:01 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-22 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  IpRoute:
   default via 192.168.1.254 dev wlp3s0 proto static metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Kernel-packages] [Bug 1724635] Re: linux-azure-edge: 4.13.0-1002.2 -proposed tracker

2017-10-19 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** 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 4.13.0-1002.2 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
  
- kernel-stable-phase-changed:Wednesday, 18. October 2017 18:01 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-stable-phase-changed:Thursday, 19. October 2017 14:01 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.13.0-1002.2 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 --
- phase: Packaging
- kernel-stable-phase-changed:Thursday, 19. October 2017 14:01 UTC
- kernel-stable-phase:Uploaded
+ boot-testing-requested: true
+ phase: Uploaded

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

Title:
  linux-azure-edge: 4.13.0-1002.2 -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 promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.13.0-1002.2 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
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1719210] Re: Bluetooth audio to A2DP headset no longer works following upgrade from 4.12 to 4.13 in artful

2017-10-19 Thread Slomo
i also have to correct my statement
"options iwlwifi bt_coex_active=0" and Kernel 4.13 works for me, but with 4.14 
i still got wifi problems, but it's sill an RC and not default in 17.10

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

Title:
  Bluetooth audio to A2DP headset no longer works following upgrade from
  4.12 to 4.13 in artful

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using artful kernel 4.12.0-13.14, Bluetooth audio works great.

  Upgrading to artful kernel 4.13.0-11.12, there are severe Bluetooth
  audio issues which have manifested in a variety of weird ways:

  1) Playback would stall after 10-20 seconds
  2) Upon removing the device and attempting to redo pairing, no devices could 
be found to pair with
  3) After the device ended up reverting to low quality mono HSP mode, it could 
not be switched back to A2DP

  This is all rather vague - sorry - but it felt better to get notice of
  this regression into the bugtracker sooner rather than later.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maxb   2091 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 24 21:24:00 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=635db8ca-b352-4622-87eb-08f74460324b
  InstallationDate: Installed on 2016-08-16 (404 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Spectre Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-08-31 (23 days ago)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81A0
  dmi.board.vendor: HP
  dmi.board.version: 48.54
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1724836] Re: Xenial update to 4.4.93 stable release

2017-10-19 Thread Stefan Bader
** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

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

Title:
  Xenial update to 4.4.93 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  
  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 4.4.93 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.93 stable release shall be
  applied:

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

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


[Kernel-packages] [Bug 1724772] Re: Xenial update to 4.4.91 stable release

2017-10-19 Thread Stefan Bader
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Xenial update to 4.4.91 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  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 4.4.91 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.91 stable release shall be applied:
  * drm_fourcc: Fix DRM_FORMAT_MOD_LINEAR #define
  * drm: bridge: add DT bindings for TI ths8135
  * GFS2: Fix reference to ERR_PTR in gfs2_glock_iter_next
  * RDS: RDMA: Fix the composite message user notification
  * ARM: dts: r8a7790: Use R-Car Gen 2 fallback binding for msiof nodes
  * MIPS: Ensure bss section ends on a long-aligned address
  * MIPS: ralink: Fix incorrect assignment on ralink_soc
  * igb: re-assign hw address pointer on reset after PCI error
  * extcon: axp288: Use vbus-valid instead of -present to determine cable
presence
  * sh_eth: use correct name for ECMR_MPDE bit
  * hwmon: (gl520sm) Fix overflows and crash seen when writing into limit
attributes
  * iio: adc: axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register modifications
  * iio: adc: hx711: Add DT binding for avia,hx711
  * ARM: 8635/1: nommu: allow enabling REMAP_VECTORS_TO_RAM
  * tty: goldfish: Fix a parameter of a call to free_irq
  * IB/ipoib: Fix deadlock over vlan_mutex
  * IB/ipoib: rtnl_unlock can not come after free_netdev
  * IB/ipoib: Replace list_del of the neigh->list with list_del_init
  * drm/amdkfd: fix improper return value on error
  * USB: serial: mos7720: fix control-message error handling
  * USB: serial: mos7840: fix control-message error handling
  * partitions/efi: Fix integer overflow in GPT size calculation
  * ASoC: dapm: handle probe deferrals
  * audit: log 32-bit socketcalls
  * usb: chipidea: vbus event may exist before starting gadget
  * ASoC: dapm: fix some pointer error handling
  * MIPS: Lantiq: Fix another request_mem_region() return code check
  * net: core: Prevent from dereferencing null pointer when releasing SKB
  * net/packet: check length in getsockopt() called with PACKET_HDRLEN
  * team: fix memory leaks
  * usb: plusb: Add support for PL-27A1
  * mmc: sdio: fix alignment issue in struct sdio_func
  * bridge: netlink: register netdevice before executing changelink
  * netfilter: invoke synchronize_rcu after set the _hook_ to NULL
  * MIPS: IRQ Stack: Unwind IRQ stack onto task stack
  * exynos-gsc: Do not swap cb/cr for semi planar formats
  * netfilter: nfnl_cthelper: fix incorrect helper->expect_class_max
  * parisc: perf: Fix potential NULL pointer dereference
  * iommu/io-pgtable-arm: Check for leaf entry before dereferencing it
  * rds: ib: add error handle
  * md/raid10: submit bio directly to replacement disk
  * i2c: meson: fix wrong variable usage in meson_i2c_put_data
  * xfs: remove kmem_zalloc_greedy
  * libata: transport: Remove circular dependency at free time
  * drivers: firmware: psci: drop duplicate const from psci_of_match
  * IB/qib: fix false-postive maybe-uninitialized warning
  * ARM: remove duplicate 'const' annotations'
  * ALSA: au88x0: avoid theoretical uninitialized access
  * ttpci: address stringop overflow warning
  * Linux 4.4.91

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

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


[Kernel-packages] [Bug 1724836] [NEW] Xenial update to 4.4.93 stable release

2017-10-19 Thread Stefan Bader
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 4.4.93 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.93 stable release shall be
applied:

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   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/1724836

Title:
  Xenial update to 4.4.93 stable release

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

Bug description:
  
  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 4.4.93 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.93 stable release shall be
  applied:

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

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


[Kernel-packages] [Bug 1724783] Re: Xenial update to 4.4.92 stable release

2017-10-19 Thread Stefan Bader
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  Xenial update to 4.4.92 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  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 4.4.92 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.92 stable release shall be applied:
  * usb: gadget: inode.c: fix unbalanced spin_lock in ep0_write
  * USB: gadgetfs: Fix crash caused by inadequate synchronization
  * USB: gadgetfs: fix copy_to_user while holding spinlock
  * usb: gadget: udc: atmel: set vbus irqflags explicitly
  * usb-storage: unusual_devs entry to fix write-access regression for Seagate
external drives
  * usb: renesas_usbhs: fix the BCLR setting condition for non-DCP pipe
  * usb: renesas_usbhs: fix usbhsf_fifo_clear() for RX direction
  * ALSA: usb-audio: Check out-of-bounds access by corrupted buffer descriptor
  * usb: pci-quirks.c: Corrected timeout values used in handshake
  * USB: dummy-hcd: fix connection failures (wrong speed)
  * USB: dummy-hcd: fix infinite-loop resubmission bug
  * USB: dummy-hcd: Fix erroneous synchronization change
  * USB: devio: Don't corrupt user memory
  * usb: gadget: mass_storage: set msg_registered after msg registered
  * USB: g_mass_storage: Fix deadlock when driver is unbound
  * lsm: fix smack_inode_removexattr and xattr_getsecurity memleak
  * ALSA: compress: Remove unused variable
  * ALSA: usx2y: Suppress kernel warning at page allocation failures
  * driver core: platform: Don't read past the end of "driver_override" buffer
  * Drivers: hv: fcopy: restore correct transfer length
  * stm class: Fix a use-after-free
  * ftrace: Fix kmemleak in unregister_ftrace_graph
  * HID: i2c-hid: allocate hid buffers for real worst case
  * iwlwifi: add workaround to disable wide channels in 5GHz
  * scsi: sd: Do not override max_sectors_kb sysfs setting
  * USB: uas: fix bug in handling of alternate settings
  * USB: core: harden cdc_parse_cdc_header
  * usb: Increase quirk delay for USB devices
  * USB: fix out-of-bounds in usb_set_configuration
  * xhci: fix finding correct bus_state structure for USB 3.1 hosts
  * iio: adc: twl4030: Fix an error handling path in 'twl4030_madc_probe()'
  * iio: adc: twl4030: Disable the vusb3v1 rugulator in the error handling path
of 'twl4030_madc_probe()'
  * iio: ad_sigma_delta: Implement a dedicated reset function
  * staging: iio: ad7192: Fix - use the dedicated reset function avoiding dma
from stack.
  * iio: core: Return error for failed read_reg
  * iio: ad7793: Fix the serial interface reset
  * iio: adc: mcp320x: Fix readout of negative voltages
  * iio: adc: mcp320x: Fix oops on module unload
  * uwb: properly check kthread_run return value
  * uwb: ensure that endpoint is interrupt
  * brcmfmac: setup passive scan if requested by user-space
  * drm/i915/bios: ignore HDMI on port A
  * sched/cpuset/pm: Fix cpuset vs. suspend-resume bugs
  * ext4: fix data corruption for mmap writes
  * ext4: Don't clear SGID when inheriting ACLs
  * ext4: don't allow encrypted operations without keys
  * Linux 4.4.92

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

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


[Kernel-packages] [Bug 1711400] Re: Update firmware for 4.12 linux-hwe-edge kernel

2017-10-19 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu Xenial)
   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/1711400

Title:
  Update firmware for 4.12 linux-hwe-edge kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  Add and update firmware files as necessary to support a 4.12-based
  kernel in the xenial linux-hwe-edge package.

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

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


[Kernel-packages] [Bug 1481347] Re: Power8 Nest PMU Instrumentation support

2017-10-19 Thread bugproxy
** Tags removed: targetmilestone-inin1710
** Tags added: targetmilestone-inin1804

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

Title:
  Power8 Nest PMU Instrumentation support

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This is a bug for Canonical awareness that we want to have the
  following patches included in 15.10.

  They are still under development/review:

  https://patchwork.ozlabs.org/patch/482968/
  https://patchwork.ozlabs.org/patch/482969/
  https://patchwork.ozlabs.org/patch/482970/
  https://patchwork.ozlabs.org/patch/482971/
  https://patchwork.ozlabs.org/patch/482972/
  https://patchwork.ozlabs.org/patch/482973/
  https://patchwork.ozlabs.org/patch/482974/

  Patches under review.

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

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


[Kernel-packages] [Bug 1724071] Re: Update firmware for 4.13 linux-hwe-edge kernel

2017-10-19 Thread Seth Forshee
** Also affects: linux-firmware (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux-firmware (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  Update firmware for 4.13 linux-hwe-edge kernel

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Xenial:
  Fix Committed

Bug description:
  Add and update firmware files as necessary to support a 4.12 based
  kernel in the xenial linux-hwe-edge package.

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

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


[Kernel-packages] [Bug 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

2017-10-19 Thread Ian Bruntlett
As I mentioned earlier, when a screenshot is taken of the corrupted
screen, a perfect snapshot is produced, suggesting the frame buffer is
OK and the problem lies elsewhere.

** Attachment added: "screenshot-taken-does-not-match-view-on-screen.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/+attachment/4975876/+files/screenshot-taken-does-not-match-view-on-screen.png

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


  1   2   >