[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Tommy]

On a Lenovo Thinkpad s440 :
 - Impossible to access BIOS/UEFI screen (F1 or Fn+F1)
 - Impossible to access boot device menu (F12 or Fn+F12)

If the laptop boots on Windows (BIOS corrupted by live USB session), you
can use the official "BIOS Update Utility" provided by Lenovo to recover
the BIOS.

(link for Thinkpad S440 on Windows 8 :
https://pcsupport.lenovo.com/ru/en/products/laptops-and-
netbooks/thinkpad-s-series-laptops/thinkpad-s440/downloads/ds036070)

Should work for most laptop that boot on windows.

/!\ USE A BIOS UPDATE THAT MATCH YOUR LAPTOP MODEL AND OS 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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (20/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

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

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

[Kernel-packages] [Bug 1293882] [NEW] [TOSHIBA Satellite P50t-A] suspend/resume failure

[Tommy]

Public bug reported:

Not exactly sure how this happened. I just noticed the error message
after opening my laptop, logging in, and closing a whole bunch of
windows i had open from earlier.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-17-generic 3.13.0-17.37 [modified: 
boot/vmlinuz-3.13.0-17-generic]
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lodmot 1896 F pulseaudio
 /dev/snd/controlC0:  lodmot 1896 F pulseaudio
Date: Mon Mar 17 14:46:32 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=649f5ebd-4c4d-4499-a267-5dbff4acf728
InstallationDate: Installed on 2014-03-17 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316)
InterpreterPath: /usr/bin/python3.4
MachineType: TOSHIBA Satellite P50t-A
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=d33ec60f-ff23-49b3-a7ef-fca6881ee717 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:
 linux-restricted-modules-3.13.0-17-generic N/A
 linux-backports-modules-3.13.0-17-generic  N/A
 linux-firmware 1.126
SourcePackage: linux
Title: [TOSHIBA Satellite P50t-A] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 10/09/2013
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.40
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: VG10ST
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.40:bd10/09/2013:svnTOSHIBA:pnSatelliteP50t-A:pvrPSPMJU-07K02K:rvnTOSHIBA:rnVG10ST:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: Satellite P50t-A
dmi.product.version: PSPMJU-07K02K
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-kerneloops resume suspend trusty

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

Title:
  [TOSHIBA Satellite P50t-A] suspend/resume failure

Status in “linux” package in Ubuntu:
  New

Bug description:
  Not exactly sure how this happened. I just noticed the error message
  after opening my laptop, logging in, and closing a whole bunch of
  windows i had open from earlier.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-17-generic 3.13.0-17.37 [modified: 
boot/vmlinuz-3.13.0-17-generic]
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lodmot 1896 F pulseaudio
   /dev/snd/controlC0:  lodmot 1896 F pulseaudio
  Date: Mon Mar 17 14:46:32 2014
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=649f5ebd-4c4d-4499-a267-5dbff4acf728
  InstallationDate: Installed on 2014-03-17 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA Satellite P50t-A
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic 
root=UUID=d33ec60f-ff23-49b3-a7ef-fca6881ee717 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:
   linux-restricted-modules-3.13.0-17-generic N/A
   linux-backports-modules-3.13.0-17-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  Title: [TOSHIBA Satellite P50t-A] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/09/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.40
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10ST
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled 

[Kernel-packages] [Bug 1289112] Re: UDF filesystem on USB stick is corrupted when creating file or directory with certain name

[tommy]

Tested with latest mainline kernel, 3.14-rc7-trusty, bug still exists.

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  UDF filesystem on USB stick is corrupted when creating file or
  directory with certain name

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10 amd64

  I wiped a 32GB USB stick and created a UDF filesystem on it (as per
  instructions at http://duncanlock.net/blog/2013/05/13/using-udf-as-an-
  improved-filesystem-for-usb-flash-drives/ )

  reading and writing works fine, until I try to create a directory or
  file (using any method) with the exact name "Сергей Васильевич
  Рахманинов - Piano Concertos Nos. 2 & 4 (Concertgebouw Orchestra feat.
  piano: Vladimir Ashkenazy, conductor: Bernard Haitink)"

  after attempting to create this file or directory, it appears to
  succeed, but the name is truncated to "Сергей Васильев" and the
  directory containing it on the UDF filesystem becomes unwritable and
  undeletable, although it can still be read.

  Initially came across this bug by copying a directory with this name
  using nautilus, but also reproduced the problem with cp -r, mkdir and
  touch.

  Various parts of the name worked fine: "Сергей Васильевич Рахманинов"
  seems fine as a filename, as is "Piano Concertos Nos. 2 & 4
  (Concertgebouw Orchestra feat. piano: Vladimir Ashkenazy, conductor:
  Bernard Haitink)". A much longer directory name also worked fine. So
  I'm stumped as to what the problem is.

  The filesystem was created with the command:
  mkudffs -b 512 --media-type=hd --utf8 /dev/sdc
  and otherwise seems to work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-17-generic 3.11.0-17.31
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tommy  1965 F pulseaudio
   /dev/snd/controlC0:  tommy  1965 F pulseaudio
  Date: Fri Mar  7 16:23:50 2014
  HibernationDevice: RESUME=UUID=fc98e994-afc1-42e5-a89c-2a531b28982f
  InstallationDate: Installed on 2013-06-23 (256 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. G33M-DS2R
  MarkForUpload: True
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-17-generic 
root=/dev/mapper/ubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-17-generic N/A
   linux-backports-modules-3.11.0-17-generic  N/A
   linux-firmware 1.116.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to saucy on 2013-10-27 (130 days ago)
  dmi.bios.date: 06/11/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: G33M-DS2R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd06/11/2007:svnGigabyteTechnologyCo.,Ltd.:pnG33M-DS2R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG33M-DS2R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G33M-DS2R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1289112] [NEW] UDF filesystem on USB stick is corrupted when creating file or directory with certain name

[tommy]

Public bug reported:

Ubuntu 13.10 amd64

I wiped a 32GB USB stick and created a UDF filesystem on it (as per
instructions at http://duncanlock.net/blog/2013/05/13/using-udf-as-an-
improved-filesystem-for-usb-flash-drives/ )

reading and writing works fine, until I try to create a directory or
file (using any method) with the exact name "Сергей Васильевич
Рахманинов - Piano Concertos Nos. 2 & 4 (Concertgebouw Orchestra feat.
piano: Vladimir Ashkenazy, conductor: Bernard Haitink)"

after attempting to create this file or directory, it appears to
succeed, but the name is truncated to "Сергей Васильев" and the
directory containing it on the UDF filesystem becomes unwritable and
undeletable, although it can still be read.

Initially came across this bug by copying a directory with this name
using nautilus, but also reproduced the problem with cp -r, mkdir and
touch.

Various parts of the name worked fine: "Сергей Васильевич Рахманинов"
seems fine as a filename, as is "Piano Concertos Nos. 2 & 4
(Concertgebouw Orchestra feat. piano: Vladimir Ashkenazy, conductor:
Bernard Haitink)". A much longer directory name also worked fine. So I'm
stumped as to what the problem is.

The filesystem was created with the command:
mkudffs -b 512 --media-type=hd --utf8 /dev/sdc
and otherwise seems to work fine.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-17-generic 3.11.0-17.31
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER    PID ACCESS COMMAND
 /dev/snd/controlC1:  tommy  1965 F pulseaudio
 /dev/snd/controlC0:  tommy  1965 F pulseaudio
Date: Fri Mar  7 16:23:50 2014
HibernationDevice: RESUME=UUID=fc98e994-afc1-42e5-a89c-2a531b28982f
InstallationDate: Installed on 2013-06-23 (256 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Gigabyte Technology Co., Ltd. G33M-DS2R
MarkForUpload: True
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-17-generic 
root=/dev/mapper/ubuntu-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-17-generic N/A
 linux-backports-modules-3.11.0-17-generic  N/A
 linux-firmware 1.116.2
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to saucy on 2013-10-27 (130 days ago)
dmi.bios.date: 06/11/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: G33M-DS2R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd06/11/2007:svnGigabyteTechnologyCo.,Ltd.:pnG33M-DS2R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG33M-DS2R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G33M-DS2R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug saucy udf

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

Title:
  UDF filesystem on USB stick is corrupted when creating file or
  directory with certain name

Status in “linux” package in Ubuntu:
  New

Bug description:
  Ubuntu 13.10 amd64

  I wiped a 32GB USB stick and created a UDF filesystem on it (as per
  instructions at http://duncanlock.net/blog/2013/05/13/using-udf-as-an-
  improved-filesystem-for-usb-flash-drives/ )

  reading and writing works fine, until I try to create a directory or
  file (using any method) with the exact name "Сергей Васильевич
  Рахманинов - Piano Concertos Nos. 2 & 4 (Concertgebouw Orchestra feat.
  piano: Vladimir Ashkenazy, conductor: Bernard Haitink)"

  after attempting to create this file or directory, it appears to
  succeed, but the name is truncated to "Сергей Васильев" and the
  directory containing it on the UDF filesystem becomes unwritable and
  undeletable, although it can still be read.

  Initially came across this bug by copying a directory with this name
  using nautilus, but also reproduced the problem with cp -r, mkdir and
  touch.

  Various parts of the name worked fine: "Сергей Васильевич Рахманинов"
  seems fine as a filename, as is "Piano Concertos Nos. 2 & 4
  (Concertgebouw Orchestra feat. piano: Vladimir Ashkenazy, conductor:
  Bernard Haitink)". A much longer directory name also worked fine. So
  I'm stumped as to what the problem is.

  The filesystem was created with the command:
  mkudffs -b 512 --media-type=hd --utf8 /dev/sdc
  and otherwise seems to work fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10

[Kernel-packages] [Bug 2039375] [NEW] Green screen

[Tommy]

Public bug reported:

This morning I did the kernel update that arrived yesterday. Now, after I login 
I get a solid green screen and that's where it stays.
the upgrade took the machine from:
vmlinuz-5.15.0-84-generic
To:
vmlinuz-5.15.0-86-generic

I rebooted into 84-generic and everything worked correctly, as pre-
update.

See more :
https://forums.linuxmint.com/viewtopic.php?t=405203&e=1&view=unread#unread

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

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

Title:
  Green screen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This morning I did the kernel update that arrived yesterday. Now, after I 
login I get a solid green screen and that's where it stays.
  the upgrade took the machine from:
  vmlinuz-5.15.0-84-generic
  To:
  vmlinuz-5.15.0-86-generic

  I rebooted into 84-generic and everything worked correctly, as pre-
  update.

  See more :
  https://forums.linuxmint.com/viewtopic.php?t=405203&e=1&view=unread#unread

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


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

[Kernel-packages] [Bug 2039375] Re: Green screen

[Tommy]

Impossible to obtain a log, because start-up is impossible, immediate
green screen after entering a session.

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

Title:
  Green screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This morning I did the kernel update that arrived yesterday. Now, after I 
login I get a solid green screen and that's where it stays.
  the upgrade took the machine from:
  vmlinuz-5.15.0-84-generic
  To:
  vmlinuz-5.15.0-86-generic

  I rebooted into 84-generic and everything worked correctly, as pre-
  update.

  See more :
  https://forums.linuxmint.com/viewtopic.php?t=405203&e=1&view=unread#unread

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


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

[Kernel-packages] [Bug 1907559] Re: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel module failed to build

[Tommy]

I am a noob at resolving this type of stuff, but I have a Dell Precision
m4700. I have an Intel i7-3540m and Nvidia Quadro k2000m. I don't know
how useful this is, but the battery is busted and doesn't work. Please
help me resolve this problem. I can't open any gpu intensefy tasks such
as games. If I try to launch them it shows this error message. Thank you
for helping.

** Attachment added: "Screenshot from 2021-01-12 12-38-40.png"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1907559/+attachment/5452405/+files/Screenshot%20from%202021-01-12%2012-38-40.png

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

Title:
  nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel
  module failed to build

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

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-57.63-generic 5.4.78
  Uname: Linux 5.4.0-57-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-32-generic
  Date: Thu Dec 10 10:17:15 2020
  Dependencies:
   
  DuplicateSignature: 
dkms:nvidia-kernel-source-390:390.138-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/390.138/build/common/inc/nv-linux.h:534:17:
 error: too many arguments to function ‘__vmalloc’
  InstallationDate: Installed on 2020-11-05 (34 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageVersion: 390.138-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-kernel-source-390 390.138-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

[Tommy Zone]

I have the same issue on Radeon 570 4gb, Ryzen 1700, MSI Tomahawk on
18.04.

The only way to boot is to use IOMMU=soft.

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

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

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1768852] Re: Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host controller dead

[Tommy Nevtelen]

I can also confirm that his fixes 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/1768852

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ===SRU Justification===
  [Impact]
  When unplugging the Thunderbolt 3 cable from the TBT controller, kernel
  oops.

  [Test]
  The user confirms this patch works.

  [Fix]
  tty_unregister_driver may be called more than 1 time in some
  hotplug cases,it will cause the kernel oops. This patch checked
  dbc_tty_driver to make sure it is unregistered only 1 time.

  [Regression Potential]
  Low. The change is to guard against null pointer, so it's the correct
  behavior.

  ===Original Bugreport===
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo 
Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Wo

[Kernel-packages] [Bug 1683587] Re: LSI Harpoon support in megaraid_sas module

[Tommy Giesler]

Hi

even though I'm late to the party, I could offer to test the modified
kernel with H330, H710 and H730.

If you send me all the necessary things and provide a list of what
things to look out for, then I could test these.

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

Title:
  LSI Harpoon support in megaraid_sas module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Dell PERC H740 series RAID controllers, codename "Harpoon", are
  not supported in standard Ubuntu kernels.

  There is a series of kernel patches required to support these:
  http://www.mail-archive.com/linux-
  ker...@vger.kernel.org/msg1307314.html

  There is also a relevant follow-up series:
  https://www.spinics.net/lists/linux-scsi/msg104667.html especially
  patches 1 and 12.

  The relevant PCI IDs from the PCI database
  (http://pciids.sourceforge.net/v2.2/pci.ids) are:

  0016 MegaRAID Tri-Mode SAS3508
  1028 1fc9 PERC H840 Adapter
  1028 1fcb PERC H740P Adapter
  1028 1fcd PERC H740P Mini
  1028 1fcf PERC H740P Mini

  They should be supported from Xenial onwards. The upstream commit is
  going in for 4.11, so this will need to be backported to v4.4 and
  v4.10.

  I am working on SRU patches for this.

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

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

[Kernel-packages] [Bug 1728727] [NEW] Just says internal error during start up

[Tommy Pollák]

Public bug reported:

I can continue without problems.

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
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tpollak2576 F pulseaudio
CurrentDesktop: XFCE
Date: Mon Oct 30 22:52:48 2017
HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
InstallationDate: Installed on 2012-10-28 (1828 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
MachineType: Dell Inc. Dell System XPS L502X
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 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: Upgraded to artful on 2017-10-25 (5 days ago)
dmi.bios.date: 07/20/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0NJT03
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: HuronRiver System
dmi.product.name: Dell System XPS L502X
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug artful i386

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

Title:
  Just says internal error during start up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can continue without problems.

  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
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2576 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 30 22:52:48 2017
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 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: Upgraded to artful on 2017-10-25 (5 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1728730] [NEW] duplicity gets stuck

[Tommy Pollák]

Public bug reported:

In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
worked again to my satisfaction.

Now in 17.10 there is a problem with duplicity again. It seems to get
stuck after a while. I can move the mouse and see the pointer move on
the display but nothing else works. Only way to get on is to power off
(and power on again).

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get
  stuck after a while. I can move the mouse and see the pointer move on
  the display but nothing else works. Only way to get on is to power off
  (and power on again).

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

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

[Kernel-packages] [Bug 1728730] Re: duplicity gets stuck

[Tommy Pollák]

apport information

** Tags added: apport-collected artful

** Description changed:

  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.
  
- Now in 17.10 there is a problem with duplicity again. It seems to get
- stuck after a while. I can move the mouse and see the pointer move on
- the display but nothing else works. Only way to get on is to power off
- (and power on again).
+ Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.1
+ Architecture: i386
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  tpollak2206 F pulseaudio
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 17.10
+ HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
+ InstallationDate: Installed on 2012-10-28 (1828 days ago)
+ InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
+ MachineType: Dell Inc. Dell System XPS L502X
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
+ Tags:  artful
+ Uname: Linux 4.13.0-16-generic i686
+ UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
+ UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/20/2011
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A06
+ dmi.board.name: 0NJT03
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.chassis.version: 0.1
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
+ dmi.product.family: HuronRiver System
+ dmi.product.name: Dell System XPS L502X
+ dmi.sys.vendor: Dell Inc.

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1728730/+attachment/5000977/+files/ProcCpuinfo.txt

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1728730] Lsusb.txt

[Tommy Pollák]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1728730/+attachment/5000976/+files/Lsusb.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/1728730

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1728730/+attachment/5000971/+files/CurrentDmesg.txt

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1728730/+attachment/5000982/+files/ProcInterrupts.txt

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1728730] JournalErrors.txt

[Tommy Pollák]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1728730/+attachment/5000973/+files/JournalErrors.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/1728730

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1728730/+attachment/5000974/+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/1728730

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1728730/+attachment/5000986/+files/UdevDb.txt

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

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

[Tommy Pollák]

apport information

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

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1728730] Re: duplicity gets stuck

[Tommy Pollák]

Added log files and changed status from Incomplete to 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/1728730

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1728730] RfKill.txt

[Tommy Pollák]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1728730/+attachment/5000985/+files/RfKill.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/1728730

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1728730] Re: duplicity gets stuck

[Tommy Pollák]

Though I downloaded 
linux-headers-4.14.0-041400rc7_4.14.0-041400rc7.201710292231_all.deb
linux-headers-4.14.0-041400rc7-generic_4.14.0-041400rc7.201710292231_i386.deb
linux-image-4.14.0-041400rc7-generic_4.14.0-041400rc7.201710292231_i386.deb
and executed
sudo dpkg -i *.deb
I can not see 4.14 when booting. So I listed /lib/modules
~$ ls /lib/modules/
3.11.0-19-generic  3.19.0-31-generic 3.8.0-31-generic
3.13.0-37-generic  3.2.0-45-generic-pae  4.10.0-37-generic
3.16.0-36-generic  3.5.0-37-generic  4.13.0-16-generic

Obviously I have missed to do something. What? sudo apt-get ??

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro 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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1728727] Re: Just says internal error during start up

[Tommy Pollák]

This kind of bugs, not sure it is the same each time, occurs most times,
but note every, I boot.

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

Title:
  Just says internal error during start up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can continue without problems.

  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
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2576 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 30 22:52:48 2017
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 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: Upgraded to artful on 2017-10-25 (5 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1707641] [NEW] Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

Public bug reported:

When using Sunix latest low power VGA or DVI controller (see link below)
on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the
system to crash on boot (the system will not become reachable via
network too, so I cannot extract any logs).

By using a second graphics controller I was able to extract the attached
kernel message from the system.

The issue also occurs with the latest mainline kernel (tested up to
4.13-rc3).

Sunix changed their graphics chip at some point from Volari Z11 to
Silicon Motion SM750. With the older generation, which uses the Z11,
everything is working.

Links to the graphics controllers which were previously mentioned:

http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

previous generation Sunix 2D VGA controller:
http://www.sunix.com.tw/product/vga0411.html

When using Fedora 26 Server, which also uses Kernel 4.11+, everything is
working, too. So I'm not sure, if this is actually an upstream issue.

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

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/bugs/1707641/+attachment/4924549/+files/journal.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/1707641

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  New

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924551/+files/uname-a.log

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

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  New

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924552/+files/version.log

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

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  New

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924550/+files/lspci-vnvn.log

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

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  New

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

** Attachment added: "release.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924569/+files/release.log

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

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

** Attachment added: "policy.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924570/+files/policy.log

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1707641

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

Yes, exactly. There is no issue with Kernel 4.10 (16.04 HWE or 17.04).
Current 17.10 Kernel does not boot properly. Unfortunately there are no
logs, even on persistent journald. The OS freezes after switching from
initramfs to real rootfs.

Any hints what logs I could try to gather to pinpoint this 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/1707641

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

I have attached the dmesg log from the booted Fedora and the Kernel
config as requested:

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4925000/+files/dmesg.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/1707641

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

** Attachment added: "config-4.11.11-300.fc26.x86_64"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4925001/+files/config-4.11.11-300.fc26.x86_64

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

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

I have sent a message to the mailing list.

You are correct. When blacklisting the module everything is working fine
again.

Can you maybe also tell me how do I properly link this bug report to the
mailing list?

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

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot

[Tommy Giesler]

http://marc.info/?l=linux-fbdev&m=150157026614752&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/1707641

Title:
  Sunix 2D VGA controller causes kernel panic and crash on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When using Sunix latest low power VGA or DVI controller (see link
  below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later
  cause the system to crash on boot (the system will not become
  reachable via network too, so I cannot extract any logs).

  By using a second graphics controller I was able to extract the
  attached kernel message from the system.

  The issue also occurs with the latest mainline kernel (tested up to
  4.13-rc3).

  Sunix changed their graphics chip at some point from Volari Z11 to
  Silicon Motion SM750. With the older generation, which uses the Z11,
  everything is working.

  Links to the graphics controllers which were previously mentioned:

  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1760
  http://www.sunix.com/en/product_detail.php?cid=1&kid=2&gid=15&pid=1766

  previous generation Sunix 2D VGA controller:
  http://www.sunix.com.tw/product/vga0411.html

  When using Fedora 26 Server, which also uses Kernel 4.11+, everything
  is working, too. So I'm not sure, if this is actually an upstream
  issue.

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

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

[Kernel-packages] [Bug 1704718] [NEW] random freeze of AMD Ryzen based workstations

[Tommy Giesler]

Public bug reported:

I'm currently looking into stability issues of several AMD Ryzen based
PCs in our company using Ubuntu 16.04 HWE and 17.04.

So far I was only able to find a single journal or log entry, which may be 
related to the problem:
->%-
Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:0 val:18739
Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:1 val:9897
Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:3 val:229
Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496
Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27
-%<-

The issue appears to occur mostly after the system was running idle for
a long time (e.g. several days during a weekend).

When you return to the frozen system it appears to show the last image,
which was displayed before the freeze.

The attached files were taken from the same workstation where I was able
to recover these log entries from.

All systems are using the latest BIOS version available at ASUS or MSI.
All memory was chosen by QVL and has already been replaced several
times.

Here the hardware configuration:
AMD Ryzen 7 1700X or AMD Ryzen 5 1600X
ASUS Prime B350M-A or MSI B350M PRO-VDH

Let me know if you need any additional information.

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

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1704718/+attachment/4915927/+files/lspci-vnvn.log

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

Title:
  random freeze of AMD Ryzen based workstations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently looking into stability issues of several AMD Ryzen based
  PCs in our company using Ubuntu 16.04 HWE and 17.04.

  So far I was only able to find a single journal or log entry, which may be 
related to the problem:
  ->%-
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:0 val:18739
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:1 val:9897
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:3 val:229
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27
  -%<-

  The issue appears to occur mostly after the system was running idle
  for a long time (e.g. several days during a weekend).

  When you return to the frozen system it appears to show the last
  image, which was displayed before the freeze.

  The attached files were taken from the same workstation where I was
  able to recover these log entries from.

  All systems are using the latest BIOS version available at ASUS or
  MSI. All memory was chosen by QVL and has already been replaced
  several times.

  Here the hardware configuration:
  AMD Ryzen 7 1700X or AMD Ryzen 5 1600X
  ASUS Prime B350M-A or MSI B350M PRO-VDH

  Let me know if you need any additional information.

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

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

[Kernel-packages] [Bug 1704718] Re: random freeze of AMD Ryzen based workstations

[Tommy Giesler]

** Attachment added: "release.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915929/+files/release.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/1704718

Title:
  random freeze of AMD Ryzen based workstations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently looking into stability issues of several AMD Ryzen based
  PCs in our company using Ubuntu 16.04 HWE and 17.04.

  So far I was only able to find a single journal or log entry, which may be 
related to the problem:
  ->%-
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:0 val:18739
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:1 val:9897
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:3 val:229
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27
  -%<-

  The issue appears to occur mostly after the system was running idle
  for a long time (e.g. several days during a weekend).

  When you return to the frozen system it appears to show the last
  image, which was displayed before the freeze.

  The attached files were taken from the same workstation where I was
  able to recover these log entries from.

  All systems are using the latest BIOS version available at ASUS or
  MSI. All memory was chosen by QVL and has already been replaced
  several times.

  Here the hardware configuration:
  AMD Ryzen 7 1700X or AMD Ryzen 5 1600X
  ASUS Prime B350M-A or MSI B350M PRO-VDH

  Let me know if you need any additional information.

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

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

[Kernel-packages] [Bug 1704718] Re: random freeze of AMD Ryzen based workstations

[Tommy Giesler]

** Attachment added: "policy.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915928/+files/policy.log

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

Title:
  random freeze of AMD Ryzen based workstations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently looking into stability issues of several AMD Ryzen based
  PCs in our company using Ubuntu 16.04 HWE and 17.04.

  So far I was only able to find a single journal or log entry, which may be 
related to the problem:
  ->%-
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:0 val:18739
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:1 val:9897
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:3 val:229
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27
  -%<-

  The issue appears to occur mostly after the system was running idle
  for a long time (e.g. several days during a weekend).

  When you return to the frozen system it appears to show the last
  image, which was displayed before the freeze.

  The attached files were taken from the same workstation where I was
  able to recover these log entries from.

  All systems are using the latest BIOS version available at ASUS or
  MSI. All memory was chosen by QVL and has already been replaced
  several times.

  Here the hardware configuration:
  AMD Ryzen 7 1700X or AMD Ryzen 5 1600X
  ASUS Prime B350M-A or MSI B350M PRO-VDH

  Let me know if you need any additional information.

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

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

[Kernel-packages] [Bug 1704718] Re: random freeze of AMD Ryzen based workstations

[Tommy Giesler]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915930/+files/version.log

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

Title:
  random freeze of AMD Ryzen based workstations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently looking into stability issues of several AMD Ryzen based
  PCs in our company using Ubuntu 16.04 HWE and 17.04.

  So far I was only able to find a single journal or log entry, which may be 
related to the problem:
  ->%-
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:0 val:18739
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:1 val:9897
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:3 val:229
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27
  -%<-

  The issue appears to occur mostly after the system was running idle
  for a long time (e.g. several days during a weekend).

  When you return to the frozen system it appears to show the last
  image, which was displayed before the freeze.

  The attached files were taken from the same workstation where I was
  able to recover these log entries from.

  All systems are using the latest BIOS version available at ASUS or
  MSI. All memory was chosen by QVL and has already been replaced
  several times.

  Here the hardware configuration:
  AMD Ryzen 7 1700X or AMD Ryzen 5 1600X
  ASUS Prime B350M-A or MSI B350M PRO-VDH

  Let me know if you need any additional information.

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

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

[Kernel-packages] [Bug 1704718] Re: random freeze of AMD Ryzen based workstations

[Tommy Giesler]

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915932/+files/journal.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/1704718

Title:
  random freeze of AMD Ryzen based workstations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently looking into stability issues of several AMD Ryzen based
  PCs in our company using Ubuntu 16.04 HWE and 17.04.

  So far I was only able to find a single journal or log entry, which may be 
related to the problem:
  ->%-
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:0 val:18739
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:1 val:9897
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:3 val:229
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27
  -%<-

  The issue appears to occur mostly after the system was running idle
  for a long time (e.g. several days during a weekend).

  When you return to the frozen system it appears to show the last
  image, which was displayed before the freeze.

  The attached files were taken from the same workstation where I was
  able to recover these log entries from.

  All systems are using the latest BIOS version available at ASUS or
  MSI. All memory was chosen by QVL and has already been replaced
  several times.

  Here the hardware configuration:
  AMD Ryzen 7 1700X or AMD Ryzen 5 1600X
  ASUS Prime B350M-A or MSI B350M PRO-VDH

  Let me know if you need any additional information.

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

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

[Kernel-packages] [Bug 1704718] Re: random freeze of AMD Ryzen based workstations

[Tommy Giesler]

I installed Kernel 4.13-rc1 on 3 workstations so far and tonight one of
them froze once again, this time leaving the attached Kernel panics in
the journal.

** Attachment added: "panic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4918653/+files/panic.txt

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  random freeze of AMD Ryzen based workstations

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently looking into stability issues of several AMD Ryzen based
  PCs in our company using Ubuntu 16.04 HWE and 17.04.

  So far I was only able to find a single journal or log entry, which may be 
related to the problem:
  ->%-
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:0 val:18739
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:1 val:9897
  Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state 
mm:94692f171f00 idx:3 val:229
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496
  Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27
  -%<-

  The issue appears to occur mostly after the system was running idle
  for a long time (e.g. several days during a weekend).

  When you return to the frozen system it appears to show the last
  image, which was displayed before the freeze.

  The attached files were taken from the same workstation where I was
  able to recover these log entries from.

  All systems are using the latest BIOS version available at ASUS or
  MSI. All memory was chosen by QVL and has already been replaced
  several times.

  Here the hardware configuration:
  AMD Ryzen 7 1700X or AMD Ryzen 5 1600X
  ASUS Prime B350M-A or MSI B350M PRO-VDH

  Let me know if you need any additional information.

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

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

[Kernel-packages] [Bug 1315069] Re: [Gateway NV77H] Brightness Keyboard Shortcuts no longer working after short time

[Tommy Miller]

Joseph, quick question, do I install the low-latency kernel, or the
generic? http://screencloud.net/v/BTe, and do i install both the headers
and the image?... More importantly, should I be installing a PPA to do
this instead?

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

Title:
  [Gateway NV77H] Brightness Keyboard Shortcuts no longer working after
  short time

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I am currently using Ubuntu 14.04 (upgraded from 13.10, and from that
  13.04) a Gateway NV77H Series laptop with an i5 core and intel's
  backlight controller. After the initial installation, the first bug
  workaround I had to do was set grub to have acpi_backlight=vendor, and
  that made brightness work in the first place. That should eventually
  be fixed, but the bigger problem I am having currently, is after the
  last upgrade to 14.04, the brightness keyboard shortcuts no longer
  work after a short period of time after boot. After reboot and log on,
  it all works fine, but after I focus to a window, it never seems to
  recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tommydrum   2760 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May  1 09:47:07 2014
  HibernationDevice: RESUME=UUID=7e7c38c2-7c45-4050-ab32-08f9031879ad
  InstallationDate: Installed on 2013-10-25 (187 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: Gateway NV77H
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=af4ccd2c-4d9b-4687-ab2d-4f3795910aae ro acpi=noirq quiet splash 
acpi_backlight=vendor intel_pstate=enable
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (33 days ago)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: Gateway
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SJV70_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnGateway:bvrV1.21:bd08/09/2012:svnGateway:pnNV77H:pvrV1.21:rvnGateway:rnSJV70_HR:rvrBaseBoardVersion:cvnGateway:ct10:cvrV1.21:
  dmi.product.name: NV77H
  dmi.product.version: V1.21
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1315069] Re: [Gateway NV77H] Brightness Keyboard Shortcuts no longer working after short time

[Tommy Miller]

Not sure if it is fixed, or what fixed it, but it seems to be working
correctly now.. marking as fixed unless it happens again (and figure out
what exactly caused it).

** Summary changed:

- [Gateway NV77H] Brightness Keyboard Shortcuts no longer working after short 
time
+ [Gateway NV77H] [Fixed?] Brightness Keyboard Shortcuts no longer working 
after short time

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

Title:
  [Gateway NV77H] [Fixed?] Brightness Keyboard Shortcuts no longer
  working after short time

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  [From last change: not sure if it was fixed, but the issue seems to
  have stopped within the last week of use, doing plenty of updates]

  
  I am currently using Ubuntu 14.04 (upgraded from 13.10, and from that 13.04) 
a Gateway NV77H Series laptop with an i5 core and intel's backlight controller. 
After the initial installation, the first bug workaround I had to do was set 
grub to have acpi_backlight=vendor, and that made brightness work in the first 
place. That should eventually be fixed, but the bigger problem I am having 
currently, is after the last upgrade to 14.04, the brightness keyboard 
shortcuts no longer work after a short period of time after boot. After reboot 
and log on, it all works fine, but after I focus to a window, it never seems to 
recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tommydrum   2760 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May  1 09:47:07 2014
  HibernationDevice: RESUME=UUID=7e7c38c2-7c45-4050-ab32-08f9031879ad
  InstallationDate: Installed on 2013-10-25 (187 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: Gateway NV77H
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=af4ccd2c-4d9b-4687-ab2d-4f3795910aae ro acpi=noirq quiet splash 
acpi_backlight=vendor intel_pstate=enable
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (33 days ago)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: Gateway
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SJV70_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnGateway:bvrV1.21:bd08/09/2012:svnGateway:pnNV77H:pvrV1.21:rvnGateway:rnSJV70_HR:rvrBaseBoardVersion:cvnGateway:ct10:cvrV1.21:
  dmi.product.name: NV77H
  dmi.product.version: V1.21
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1315069] Re: [Gateway NV77H] [Fixed?] Brightness Keyboard Shortcuts no longer working after short time

[Tommy Miller]

maybe? (issue has stopped, not sure if temporary or what fixed it)

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

** Description changed:

- I am currently using Ubuntu 14.04 (upgraded from 13.10, and from that
- 13.04) a Gateway NV77H Series laptop with an i5 core and intel's
- backlight controller. After the initial installation, the first bug
- workaround I had to do was set grub to have acpi_backlight=vendor, and
- that made brightness work in the first place. That should eventually be
- fixed, but the bigger problem I am having currently, is after the last
- upgrade to 14.04, the brightness keyboard shortcuts no longer work after
- a short period of time after boot. After reboot and log on, it all works
- fine, but after I focus to a window, it never seems to recover.
+ [From last change: not sure if it was fixed, but the issue seems to have
+ stopped within the last week of use, doing plenty of updates]
+ 
+ 
+ I am currently using Ubuntu 14.04 (upgraded from 13.10, and from that 13.04) 
a Gateway NV77H Series laptop with an i5 core and intel's backlight controller. 
After the initial installation, the first bug workaround I had to do was set 
grub to have acpi_backlight=vendor, and that made brightness work in the first 
place. That should eventually be fixed, but the bigger problem I am having 
currently, is after the last upgrade to 14.04, the brightness keyboard 
shortcuts no longer work after a short period of time after boot. After reboot 
and log on, it all works fine, but after I focus to a window, it never seems to 
recover.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tommydrum   2760 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May  1 09:47:07 2014
  HibernationDevice: RESUME=UUID=7e7c38c2-7c45-4050-ab32-08f9031879ad
  InstallationDate: Installed on 2013-10-25 (187 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: Gateway NV77H
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=af4ccd2c-4d9b-4687-ab2d-4f3795910aae ro acpi=noirq quiet splash 
acpi_backlight=vendor intel_pstate=enable
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (33 days ago)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: Gateway
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SJV70_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnGateway:bvrV1.21:bd08/09/2012:svnGateway:pnNV77H:pvrV1.21:rvnGateway:rnSJV70_HR:rvrBaseBoardVersion:cvnGateway:ct10:cvrV1.21:
  dmi.product.name: NV77H
  dmi.product.version: V1.21
  dmi.sys.vendor: Gateway

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

Title:
  [Gateway NV77H] [Fixed?] Brightness Keyboard Shortcuts no longer
  working after short time

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  [From last change: not sure if it was fixed, but the issue seems to
  have stopped within the last week of use, doing plenty of updates]

  
  I am currently using Ubuntu 14.04 (upgraded from 13.10, and from that 13.04) 
a Gateway NV77H Series laptop with an i5 core and intel's backlight controller. 
After the initial installation, the first bug workaround I had to do was set 
grub to have acpi_backlight=vendor, and that made brightness work in the first 
place. That should eventually be fixed, but the bigger problem I am having 
currently, is after the last upgrade to 14.04, the brightness keyboard 
shortcuts no longer work after a short period of time after boot. After reboot 
and log on, it all works fine, but after I focus to a window, it never seems to 
recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tommydrum   2760 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May  1 09:47:07 2014
  HibernationDevice: RESUME=UUID=7e7c38c2-7c45-4050-ab32-08f9031879ad
  InstallationDate: Installed on 2013-10-25 (187 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salama

[Kernel-packages] [Bug 1315069] Re: [Gateway NV77H] [Fixed?] Brightness Keyboard Shortcuts no longer working after short time

[Tommy Miller]

I may add that it may not be  time that was affecting the issue, I think
it may have been caused by focusing on a particular window/program.
Untested, but suspected.

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

Title:
  [Gateway NV77H] [Fixed?] Brightness Keyboard Shortcuts no longer
  working after short time

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  [From last change: not sure if it was fixed, but the issue seems to
  have stopped within the last week of use, doing plenty of updates]

  
  I am currently using Ubuntu 14.04 (upgraded from 13.10, and from that 13.04) 
a Gateway NV77H Series laptop with an i5 core and intel's backlight controller. 
After the initial installation, the first bug workaround I had to do was set 
grub to have acpi_backlight=vendor, and that made brightness work in the first 
place. That should eventually be fixed, but the bigger problem I am having 
currently, is after the last upgrade to 14.04, the brightness keyboard 
shortcuts no longer work after a short period of time after boot. After reboot 
and log on, it all works fine, but after I focus to a window, it never seems to 
recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tommydrum   2760 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May  1 09:47:07 2014
  HibernationDevice: RESUME=UUID=7e7c38c2-7c45-4050-ab32-08f9031879ad
  InstallationDate: Installed on 2013-10-25 (187 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: Gateway NV77H
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=af4ccd2c-4d9b-4687-ab2d-4f3795910aae ro acpi=noirq quiet splash 
acpi_backlight=vendor intel_pstate=enable
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (33 days ago)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: Gateway
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SJV70_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Gateway
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnGateway:bvrV1.21:bd08/09/2012:svnGateway:pnNV77H:pvrV1.21:rvnGateway:rnSJV70_HR:rvrBaseBoardVersion:cvnGateway:ct10:cvrV1.21:
  dmi.product.name: NV77H
  dmi.product.version: V1.21
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1315069] [NEW] Brightness Keyboard Shortcuts no longer working after short time

[Tommy Miller]

Public bug reported:

I am currently using Ubuntu 14.04 (upgraded from 13.10, and from that
13.04) a Gateway NV77H Series laptop with an i5 core and intel's
backlight controller. After the initial installation, the first bug
workaround I had to do was set grub to have acpi_backlight=vendor, and
that made brightness work in the first place. That should eventually be
fixed, but the bigger problem I am having currently, is after the last
upgrade to 14.04, the brightness keyboard shortcuts no longer work after
a short period of time after boot. After reboot and log on, it all works
fine, but after I focus to a window, it never seems to recover. The
included log from 'ubuntu-bug linux' might give a few extra bug reports
as well, but this is probably more important since it has to deal with a
common function of a laptop.

I am also sorry about not knowing what the package is, but the nature of
this bug, probably won't throw an exception anywhere, so locating it may
be difficult for my level of understanding.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tommydrum   2760 F pulseaudio
CurrentDesktop: Unity
Date: Thu May  1 09:47:07 2014
HibernationDevice: RESUME=UUID=7e7c38c2-7c45-4050-ab32-08f9031879ad
InstallationDate: Installed on 2013-10-25 (187 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
MachineType: Gateway NV77H
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=af4ccd2c-4d9b-4687-ab2d-4f3795910aae ro acpi=noirq quiet splash 
acpi_backlight=vendor intel_pstate=enable
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic  N/A
 linux-firmware 1.127
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-03-29 (33 days ago)
dmi.bios.date: 08/09/2012
dmi.bios.vendor: Gateway
dmi.bios.version: V1.21
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJV70_HR
dmi.board.vendor: Gateway
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.version: V1.21
dmi.modalias: 
dmi:bvnGateway:bvrV1.21:bd08/09/2012:svnGateway:pnNV77H:pvrV1.21:rvnGateway:rnSJV70_HR:rvrBaseBoardVersion:cvnGateway:ct10:cvrV1.21:
dmi.product.name: NV77H
dmi.product.version: V1.21
dmi.sys.vendor: Gateway

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


** Tags: amd64 apport-bug trusty

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

Title:
  Brightness Keyboard Shortcuts no longer working after short time

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I am currently using Ubuntu 14.04 (upgraded from 13.10, and from that
  13.04) a Gateway NV77H Series laptop with an i5 core and intel's
  backlight controller. After the initial installation, the first bug
  workaround I had to do was set grub to have acpi_backlight=vendor, and
  that made brightness work in the first place. That should eventually
  be fixed, but the bigger problem I am having currently, is after the
  last upgrade to 14.04, the brightness keyboard shortcuts no longer
  work after a short period of time after boot. After reboot and log on,
  it all works fine, but after I focus to a window, it never seems to
  recover. The included log from 'ubuntu-bug linux' might give a few
  extra bug reports as well, but this is probably more important since
  it has to deal with a common function of a laptop.

  I am also sorry about not knowing what the package is, but the nature
  of this bug, probably won't throw an exception anywhere, so locating
  it may be difficult for my level of understanding.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tommydrum   2760 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May  1 09:47:07 2014
  HibernationDevice: RESUME=UUID=7e7c38c2-7c45-4050-ab32-08f9031879ad
  InstallationDate: Installed on 2013-10-25 (187 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  MachineType: Gateway NV77H
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=af4ccd2c-4d9b-4687-ab2d-4f3795910aae ro acpi=noirq quiet splash 
acpi_backlight=vendor intel_pstate=enable
  RelatedPackageVersions:
   linux-restricted-module

[Kernel-packages] [Bug 1324095] Re: [Lenovo Yoga 2 Pro] ideapad_laptop kernel module breaks wireless

[Tommy Kowalski]

I am running trusty on a Lenovo Y40 and have this same bug. I have
blacklisted the module in order to use Wireless.

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

Title:
  [Lenovo Yoga 2 Pro] ideapad_laptop kernel module breaks wireless

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” package in Fedora:
  Unknown

Bug description:
  With the ideapad_laptop module loaded there is no wlan0 (or other wifi
  device) present. Booting without any explicit blacklist config the
  ideapad_laptop kernel module gets loaded, and there are no wlan0
  device present.

  If I yet again load the ideapad_laptop module, using modprobe, the wlan0 
device goes away. Here is the dmesg output from that.
  [  234.351406] input: Ideapad extra buttons as 
/devices/platform/VPC2004:00/input/input17
  [  234.353261] wlan0: deauthenticating from d8:5d:4c:bb:1a:f2 by local choice 
(reason=3)
  [  234.398900] cfg80211: Calling CRDA to update world regulatory domain
  [  234.401410] cfg80211: World regulatory domain updated:
  [  234.401412] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
  [  234.401414] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  234.401415] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  234.401416] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
  [  234.401418] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  234.401419] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
  [  234.555068] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

  WORKAROUND: For the wireless network to work on my Lenovo Yoga 2 Pro Laptop I 
need blacklist/rmmod the ideapad_laptop kernel module. Running rmmod on the 
module results in the wlan0 device becoming present, and NetworkManager being 
able to connect to a local wifi network. Here is the dmesg output after the 
rmmod command:
  [   74.908411] iwlwifi :01:00.0: L1 Disabled; Enabling L0S
  [   74.908627] iwlwifi :01:00.0: L1 Disabled; Enabling L0S
  [   74.920538] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [   76.371036] wlan0: authenticate with d8:5d:4c:bb:1a:f2
  [   76.372069] wlan0: send auth to d8:5d:4c:bb:1a:f2 (try 1/3)
  [   76.376670] wlan0: authenticated
  [   76.378169] wlan0: associate with d8:5d:4c:bb:1a:f2 (try 1/3)
  [   76.381908] wlan0: RX AssocResp from d8:5d:4c:bb:1a:f2 (capab=0x411 
status=0 aid=2)
  [   76.383305] wlan0: associated
  [   76.38] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-27-generic 3.13.0-27.50
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  andreas2492 F pulseaudio
   /dev/snd/controlC0:  andreas2492 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May 28 14:00:22 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-20 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20266
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic.efi.signed 
root=UUID=e70835c5-4ffe-49d3-aecc-403dbf538c1a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-27-generic N/A
   linux-backports-modules-3.13.0-27-generic  N/A
   linux-firmware 1.127.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900056PRO
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900056PRO:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1340376] Re: [Lenovo ThinkPad Edge E540] Suspend Failure

[Tommy Trussell]

The BIOS bug is being discussed on a Lenovo forum at
https://forums.lenovo.com/t5/11e-Windows-E-and-Edge-series/E540-Suspend-
Resume-failure/td-p/1780813

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

Title:
  [Lenovo ThinkPad Edge E540] Suspend Failure

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The laptop failed to suspend, screen went black but the fan stayed on.
  Resume was not possible. The suspend problem still occurs with
  mainline kernel-3.16-rc4.

  WORKAROUND: Disable USB3 in the BIOS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-31-generic 3.13.0-31.55
  ProcVersionSignature: Ubuntu 3.13.0-31.55-generic 3.13.11.4
  Uname: Linux 3.13.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jh 2145 F pulseaudio
   /dev/snd/controlC1:  jh 2145 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Jul 10 21:42:38 2014
  InstallationDate: Installed on 2014-06-06 (33 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 09da:9066 A4 Tech Co., Ltd
   Bus 001 Device 004: ID 04f2:b398 Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20C6CTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-31-generic 
root=UUID=9224c861-9b53-444d-9e76-641537f1428e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-31-generic N/A
   linux-backports-modules-3.13.0-31-generic  N/A
   linux-firmware 1.127.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET87WW (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET87WW(2.07):bd05/13/2014:svnLENOVO:pn20C6CTO1WW:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6CTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C6CTO1WW
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1408025] Re: Lenovo Thinkpad Edge E540 suspend/resume failure

[Tommy Trussell]

Also same as Bug 1340376

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

Title:
  Lenovo Thinkpad Edge E540 suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After an update of the Thinkpad Edge E540 BIOS to version v2.16 (J9ET96WW ) 
the suspend to RAM failes:
   -  general ThinkPad LED (the i's dot) behaved like normal: slowly blinking, 
which normally means "I'm suspended to RAM."
   - resume was impossible: wakeup failed through mouse clicks, various 
keyboard keys and combinations and also the power key, only a hard reset (5s or 
so holding down the power key) could bring it back to life

  Ubuntu 14.04.1 LTS
  Linux Lenovo-E540 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-43-generic 3.13.0-43.72
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  1501 F pulseaudio
   /dev/snd/controlC1:  peter  1501 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan  6 17:21:03 2015
  HibernationDevice: RESUME=UUID=9141fa35-dc66-4dcc-8a9f-c3b13be1bded
  InstallationDate: Installed on 2014-04-18 (262 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20C60043GE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed 
root=UUID=c79d162d-01c6-4fda-ba6b-a5884fc5f16d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-43-generic N/A
   linux-backports-modules-3.13.0-43-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET96WW (2.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C60043GE
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET96WW(2.16):bd10/14/2014:svnLENOVO:pn20C60043GE:pvrThinkPadEdgeE540:rvnLENOVO:rn20C60043GE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C60043GE
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Tommy Eriksen]

Hi,

Do we have any kind of pattern on this yet? I have (so far) 4 VMs exhibiting 
this behaviour constantly - but out of maybe 200 Ubuntu VMs on Hyper-V.
Problem is it's a production environment and I can't easily test different 
versions (as it requires proposing changes for each machine I want to update) - 
so would it be possible for you (who've had more testing time) to direct me to 
one of the 14.04 compatible kernels that you've had success with?

Thanks a lot in advance,
Tommy

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

[Tommy Eriksen]

Hi Guys,

Any news on the testing? We have an increasingly large number of servers
failing after their backup run; it is getting a bit critical,
unfortunately.

Thanks a lot,
Tommy

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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

[Kernel-packages] [Bug 1626894] [NEW] nvme drive probe failure

[Tommy Giesler]

Public bug reported:

After upgrading from linux-image-4.4.0-38-generic to proposed update
linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
shows a probe failure.

On the previous kernel version everything is working as expected.
->%-
[1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
[1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
[1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
[1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
[1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
[1.006433] Call Trace:
[1.006509]  [] dump_stack+0x63/0x90
[1.006589]  [] iounmap.part.1+0x7f/0x90
[1.006668]  [] iounmap+0x2c/0x30
[1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
[1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
[1.007140]  [] pci_device_remove+0x39/0xc0
[1.007220]  [] __device_release_driver+0xa1/0x150
[1.007301]  [] device_release_driver+0x23/0x30
[1.007382]  [] pci_stop_bus_device+0x8a/0xa0
[1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
[1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme]
[1.007642]  [] process_one_work+0x165/0x480
[1.007722]  [] worker_thread+0x4b/0x4c0
[1.007801]  [] ? process_one_work+0x480/0x480
[1.007881]  [] kthread+0xd8/0xf0
[1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
[1.008041]  [] ret_from_fork+0x3f/0x70
[1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
[1.008222] Trying to free nonexistent resource 

[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
[1.008281] Trying to free nonexistent resource 

[1.008282] nvme :02:00.0: Removing after probe failure
[1.008645] Trying to free nonexistent resource 

[1.027213] iounmap: bad address c90006ae
[1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
-%<-

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

** Attachment added: "dmesg.log"
   https://bugs.launchpad.net/bugs/1626894/+attachment/4746840/+files/dmesg.log

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Tommy Giesler]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746841/+files/lspci-vnvn.log

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Tommy Giesler]

** Attachment added: "policy.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746842/+files/policy.log

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Tommy Giesler]

** Attachment added: "release.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746843/+files/release.log

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Tommy Giesler]

** Attachment added: "uname-a.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746844/+files/uname-a.log

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Tommy Giesler]

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746845/+files/version.log

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Tommy Giesler]

Sorry for the late respond, I didn't have access to the hardware during
the weekend.

I've just tested both kernels and can confirm, that the second one works 
correctly:
->%-
root@Ubuntu-1604-xenial-64-minimal ~ # uname -a
Linux Ubuntu-1604-xenial-64-minimal 4.4.0-40-generic 
#60~lp1626894Commit30d6592Reverted SMP Fri Sep 23 17:06:33 UTC 2 x86_64 x86_64 
x86_64 GNU/Linux
root@Ubuntu-1604-xenial-64-minimal ~ # ls /dev/nvme*
/dev/nvme0  /dev/nvme0n1  /dev/nvme1  /dev/nvme1n1
-%<-

Let me know, if you need any additional testing.

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1626894] Re: nvme drive probe failure

[Tommy Giesler]

Thanks everyone for your quick response and fix of the problem!

I can also confirm that Kamal's Kernel works.

$ cat /proc/version
Linux version 4.4.0-41-generic (root@gomeisa) (gcc version 5.4.0 20160609 
(Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #61~lp1626894KamalPatched SMP Mon Sep 26 
19:28:58 UTC 2016
$ ls /dev/nvme*
/dev/nvme0  /dev/nvme0n1  /dev/nvme0n1p1  /dev/nvme0n1p2  /dev/nvme0n1p3  
/dev/nvme1  /dev/nvme1n1  /dev/nvme1n1p1  /dev/nvme1n1p2  /dev/nvme1n1p3

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

Title:
  nvme drive probe failure

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  After upgrading from linux-image-4.4.0-38-generic to proposed update
  linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg
  shows a probe failure.

  On the previous kernel version everything is working as expected.
  ->%-
  [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 
R1.12.0.SR.2 for D3417-B1x   04/01/2016
  [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
  [1.005484]  0286 b6c91251 880fe6e8bce0 
813f1f83
  [1.005800]  880fe02150f0 c90006a7c000 880fe6e8bd00 
8106bdff
  [1.006117]  880fe02150f0 880fe0215258 880fe6e8bd10 
8106be3c
  [1.006433] Call Trace:
  [1.006509]  [] dump_stack+0x63/0x90
  [1.006589]  [] iounmap.part.1+0x7f/0x90
  [1.006668]  [] iounmap+0x2c/0x30
  [1.006770]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
  [1.007048]  [] nvme_remove+0xce/0xe0 [nvme]
  [1.007140]  [] pci_device_remove+0x39/0xc0
  [1.007220]  [] __device_release_driver+0xa1/0x150
  [1.007301]  [] device_release_driver+0x23/0x30
  [1.007382]  [] pci_stop_bus_device+0x8a/0xa0
  [1.007462]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
  [1.007559]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 
[nvme]
  [1.007642]  [] process_one_work+0x165/0x480
  [1.007722]  [] worker_thread+0x4b/0x4c0
  [1.007801]  [] ? process_one_work+0x480/0x480
  [1.007881]  [] kthread+0xd8/0xf0
  [1.007959]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008041]  [] ret_from_fork+0x3f/0x70
  [1.008120]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [1.008222] Trying to free nonexistent resource 

  [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 
(timer)
  [1.008281] Trying to free nonexistent resource 

  [1.008282] nvme :02:00.0: Removing after probe failure
  [1.008645] Trying to free nonexistent resource 

  [1.027213] iounmap: bad address c90006ae
  [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic 
#59-Ubuntu
  -%<-

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

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

[Kernel-packages] [Bug 1031831] Re: 3.5.0-7.7~precise1-generic works except for broadcom bcmwl-kernel-source failure

[Tommy Trussell]

Just booted 12.04.2 64-bit ubuntu desktop live image (USB) on the Acer
Aspire One D260.

ubuntu@ubuntu$ uname -a 
Linux ubuntu 3.5.0-23-generic #35~precise1-Ubuntu SMP Fri Jan 25 17:13:26 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux

The networking works from the live image. I'm connected to my LAN.

However the Install Drivers icon appeared in the top bar and it suggests
I might want to install the proprietary Broadcom STA wireless drivers. I
don't know the different drivers, but the live boot image is using the
"brcmsmac" driver successfully on this hardware. It's my understanding
this is the "proper" open source driver for broadcom.

I don't understand why Ubuntu suggests the proprietary driver when
whatever is already in the kernel works fine, at least on this hardware.

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

Title:
  3.5.0-7.7~precise1-generic works except for broadcom bcmwl-kernel-
  source failure

Status in “bcmwl” package in Ubuntu:
  Expired

Bug description:
  I signed up to test backports of quantal kernel to precise LTS. Sorry
  I have not tested Quantal on this system yet.

  Fresh clean install of Ubuntu 12.04 LTS on an Acer Aspire One D260
  netbook.

  Major failure during installation: broadcom driver won't install.
  (Notes below) Attaching build log.

  Kernel does run on this hardware, suspend, sound, graphics seem good.

  Wireless non-functional (as expected due to install failure).

  Here are some pertinent lines from Terminal:

  Setting up linux-headers-3.5.0-7 (3.5.0-7.7~precise1) ...
  Setting up linux-headers-3.5.0-7-generic (3.5.0-7.7~precise1) ...
  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 3.5.0-7-generic 
/boot/vmlinuz-3.5.0-7-generic
  Error! Bad return status for module build on kernel: 3.5.0-7-generic (i686)
  Consult /var/lib/dkms/bcmwl/5.100.82.38+bdcom/build/make.log for more 
information.

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

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

[Kernel-packages] [Bug 1031831] Re: 3.5.0-7.7~precise1-generic works except for broadcom bcmwl-kernel-source failure

[Tommy Trussell]

It seems I can't really test bcmwl-kernel-source using a live iso on the
little USB drive I had available. (The 1Gb casper-rw persistence file
fills up REALLY fast, and the system becomes unbootable.) SO I haven't
yet tested the problem as I reported it. I'll have to drag out a larger
drive.

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

Title:
  3.5.0-7.7~precise1-generic works except for broadcom bcmwl-kernel-
  source failure

Status in “bcmwl” package in Ubuntu:
  Expired

Bug description:
  I signed up to test backports of quantal kernel to precise LTS. Sorry
  I have not tested Quantal on this system yet.

  Fresh clean install of Ubuntu 12.04 LTS on an Acer Aspire One D260
  netbook.

  Major failure during installation: broadcom driver won't install.
  (Notes below) Attaching build log.

  Kernel does run on this hardware, suspend, sound, graphics seem good.

  Wireless non-functional (as expected due to install failure).

  Here are some pertinent lines from Terminal:

  Setting up linux-headers-3.5.0-7 (3.5.0-7.7~precise1) ...
  Setting up linux-headers-3.5.0-7-generic (3.5.0-7.7~precise1) ...
  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 3.5.0-7-generic 
/boot/vmlinuz-3.5.0-7-generic
  Error! Bad return status for module build on kernel: 3.5.0-7-generic (i686)
  Consult /var/lib/dkms/bcmwl/5.100.82.38+bdcom/build/make.log for more 
information.

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

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

[Kernel-packages] [Bug 1031831] Re: 3.5.0-7.7~precise1-generic works except for broadcom bcmwl-kernel-source failure

[Tommy Trussell]

This probably isn't the place for this discussion but I checked
http://packages.ubuntu.com/precise/kernel/ and see that the 3.8 kernel
is available HOWEVER apparently only for 64 bit x86 SMP as a security
update, which is probably where the confusion lies. I gather you aren't
using 64 bit packages on your hardware. I'm not either, but I have also
moved beyond the Ubuntu 12.04LTS on the hardware I reported the bug
from.

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

Title:
  3.5.0-7.7~precise1-generic works except for broadcom bcmwl-kernel-
  source failure

Status in “bcmwl” package in Ubuntu:
  Expired

Bug description:
  I signed up to test backports of quantal kernel to precise LTS. Sorry
  I have not tested Quantal on this system yet.

  Fresh clean install of Ubuntu 12.04 LTS on an Acer Aspire One D260
  netbook.

  Major failure during installation: broadcom driver won't install.
  (Notes below) Attaching build log.

  Kernel does run on this hardware, suspend, sound, graphics seem good.

  Wireless non-functional (as expected due to install failure).

  Here are some pertinent lines from Terminal:

  Setting up linux-headers-3.5.0-7 (3.5.0-7.7~precise1) ...
  Setting up linux-headers-3.5.0-7-generic (3.5.0-7.7~precise1) ...
  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 3.5.0-7-generic 
/boot/vmlinuz-3.5.0-7-generic
  Error! Bad return status for module build on kernel: 3.5.0-7-generic (i686)
  Consult /var/lib/dkms/bcmwl/5.100.82.38+bdcom/build/make.log for more 
information.

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

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

[Kernel-packages] [Bug 1031831] Re: 3.5.0-7.7~precise1-generic works except for broadcom bcmwl-kernel-source failure

[Tommy Trussell]

@Bernardo,
I see your point. However, I have not tested the package using the current LTS 
kernel on that hardware, and indeed I recently did a fresh install of Ubuntu 
13.04 on that netbook and was impressed the Broadcom network works much more 
reliably without doing anything at all. 

I am not sure where the Broadcom compatible driver for Ubuntu 13.04 came
from (Ubuntu suggests the proprietary driver, but it's working very well
despite not choosing it).

I can download a current 12.04.2 LTS ISO, boot from it, and see what
happens with the Broadcom driver on my Acer Aspire One D260. However it
will take me some time to get to it. From what you're saying I presume
it's still broken.

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

Title:
  3.5.0-7.7~precise1-generic works except for broadcom bcmwl-kernel-
  source failure

Status in “bcmwl” package in Ubuntu:
  Expired

Bug description:
  I signed up to test backports of quantal kernel to precise LTS. Sorry
  I have not tested Quantal on this system yet.

  Fresh clean install of Ubuntu 12.04 LTS on an Acer Aspire One D260
  netbook.

  Major failure during installation: broadcom driver won't install.
  (Notes below) Attaching build log.

  Kernel does run on this hardware, suspend, sound, graphics seem good.

  Wireless non-functional (as expected due to install failure).

  Here are some pertinent lines from Terminal:

  Setting up linux-headers-3.5.0-7 (3.5.0-7.7~precise1) ...
  Setting up linux-headers-3.5.0-7-generic (3.5.0-7.7~precise1) ...
  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 3.5.0-7-generic 
/boot/vmlinuz-3.5.0-7-generic
  Error! Bad return status for module build on kernel: 3.5.0-7-generic (i686)
  Consult /var/lib/dkms/bcmwl/5.100.82.38+bdcom/build/make.log for more 
information.

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

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

[Kernel-packages] [Bug 1235864] Re: Network down after resume

[Tommy Trussell]

*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262

** This bug has been marked a duplicate of bug 1184262
   [logind] stuck in PrepareForSleep, causing network and other services to not 
resume

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

Title:
  Network down after resume

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  In Saucy, after resuming from suspend, the network is disabled.

  WORKAROUND: Running "sudo restart network-manager" fixes the problem
  each time.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu21
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic i686
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Sun Oct  6 08:11:23 2013
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2010-09-15 (1116 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  IpRoute:
   default via 192.168.0.254 dev wlan2  proto static
   192.168.0.0/24 dev wlan2  proto kernel  scope link  src 192.168.0.11  metric 
9
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   WirelessEnabled=true
   NetworkingEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to saucy on 2011-04-01 (918 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   eth2   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1
   wlan2  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Kernel-packages] [Bug 1242679] Re: network manager unconfigured after wake from suspend

[Tommy Trussell]

this may be a duplicate of  bug #1184262

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

Title:
  network manager unconfigured after wake from suspend

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I started a thread on this bug
  http://ubuntuforums.org/showthread.php?t=2182128

  After I upgraded to 13.10 when the desktop suspends and then wakes the 
networks are unconfigured.
  The led lights come on on the builtin nic card, but no networking, the empty 
triangle shows.

  run this command  sudo nmcli nm sleep false
  I get a message that says network now offline.

  Then you click the network icon and you see all the network cards
  Then tell it to enable networking, by selecting 'Auto Ethernet'
  And it comes back working as it should.

  So is the network-manager not awakening from sleep?

  The nics are intel and the drivers are e100 and e1000

  scott875@scott875-desktop:~$ apt-cache policy network-manager
  network-manager:
Installed: 0.9.8.0-0ubuntu22
Candidate: 0.9.8.0-0ubuntu22
Version table:
   *** 0.9.8.0-0ubuntu22 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  scott875@scott875-desktop:~$ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10
  scott875@scott875-desktop:~$

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

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

[Kernel-packages] [Bug 1234469] Re: Network does not come up after resuming from suspend.

[Tommy Trussell]

*** This bug is a duplicate of bug 1184262 ***
https://bugs.launchpad.net/bugs/1184262

** This bug has been marked a duplicate of bug 1184262
   [logind] stuck in PrepareForSleep, causing network and other services to not 
resume

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

Title:
  Network does not come up after resuming from suspend.

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  When my computer wakes up from being suspended, the wireless network 
connection doesn't come back up.
  I'm able to fix the problem by running "nmcli nm sleep false", which causes 
the wireless card to reconnect.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager 0.9.8.0-0ubuntu21
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  2 20:21:33 2013
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-08-09 (54 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.125.1 dev wlan0  proto static 
   192.168.125.0/24 dev wlan0  proto kernel  scope link  src 192.168.125.8  
metric 9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to saucy on 2013-08-09 (54 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 199a6c07f-9a94-4c8e-82dd-0381befd6f90   
802-3-ethernet1380753272   Wed 02 Oct 2013 05:34:32 PM CDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   9739  172c6f5c-b69c-40dd-ac1b-a279c84a17f8   
802-11-wireless   1380763079   Wed 02 Oct 2013 08:17:59 PM CDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled enabled

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

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

[Kernel-packages] [Bug 1022182] Re: Unity password field fails to appear

[Tommy Hoyer]

The issue has not repeated; this bug can be closed - Thank you!

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

Title:
  Unity password field fails to appear

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 12.04
  Kernel 3.2.0-26
  Dell Inspiron 1545
  After wake from system suspend, only the back round was displayed (with the 
upper panel), no login field. Upper panel icons do not respond. The same issue 
occurred a few times with Ubuntu 11.10 after energy save screen lock + display 
off.

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

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

[Kernel-packages] [Bug 1251500] [NEW] package linux-image-3.11.0-13-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Tommy Domingue]

Public bug reported:

tried to update all software after a fresh install without automatically
downloading updates.

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-13-generic (not installed)
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  tommy  2049 F pulseaudio
 /dev/snd/controlC0:  tommy  2049 F pulseaudio
CurrentDmesg: [   10.546300] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes 
ready
Date: Thu Nov 14 22:05:56 2013
DuplicateSignature: package:linux-image-3.11.0-13-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
HibernationDevice: RESUME=UUID=5016509f-a2f4-4ec8-8cca-d88b578d9615
InstallationDate: Installed on 2013-11-15 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IwConfig:
 eth0  no wireless extensions.
 
 eth1  no wireless extensions.
 
 lono wireless extensions.
MachineType: Shuttle Inc. SX58
MarkForUpload: True
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-12-generic 
root=UUID=4bd42f7a-715a-45f9-9854-a8b287c02d13 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not 
responding.
RelatedPackageVersions: grub-pc 2.00-19ubuntu2.1
RfKill:
 
SourcePackage: linux
Title: package linux-image-3.11.0-13-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: SX58
dmi.board.vendor: Shuttle Inc.
dmi.board.version: V10
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Intel
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080016:bd04/02/2012:svnShuttleInc.:pnSX58:pvrV10:rvnShuttleInc.:rnSX58:rvrV10:cvnIntel:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: SX58
dmi.product.version: V10
dmi.sys.vendor: Shuttle Inc.

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


** Tags: amd64 apport-package saucy

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

Title:
  package linux-image-3.11.0-13-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in “linux” package in Ubuntu:
  New

Bug description:
  tried to update all software after a fresh install without
  automatically downloading updates.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tommy  2049 F pulseaudio
   /dev/snd/controlC0:  tommy  2049 F pulseaudio
  CurrentDmesg: [   10.546300] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link 
becomes ready
  Date: Thu Nov 14 22:05:56 2013
  DuplicateSignature: package:linux-image-3.11.0-13-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=5016509f-a2f4-4ec8-8cca-d88b578d9615
  InstallationDate: Installed on 2013-11-15 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IwConfig:
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Shuttle Inc. SX58
  MarkForUpload: True
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-12-generic 
root=UUID=4bd42f7a-715a-45f9-9854-a8b287c02d13 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions: grub-pc 2.00-19ubuntu2.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-3.11.0-13-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080016
  dmi.board.asset.tag: To Be Filled By O

[Kernel-packages] [Bug 1527889] Re: Resolution >1080p (like 1440p) doesn't work on Intel Braswell ( Asrock N3150 )

[Tommy de Neef]

I have a Zotac ZBOX nano also with Intel Celeron n3150 which is also
affected by this bug.

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

Title:
  Resolution >1080p (like 1440p) doesn't work on Intel Braswell ( Asrock
  N3150 )

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  It seems that it tries many times display but no result, But 1080p
  works without issue. Not sure if it's some bios settings, now it is in
  UEFI mode. I will investigate it further.

  I turned off the other screen, it doesn't help

  In logs it looks pretty normal, but the screen is turned , but blank
  and the icon of the chainged source is coming from time to time.

  [  1499.601] (II) intel(0): resizing framebuffer to 2560x1440
  [  1499.668] (II) intel(0): switch to mode 2560x1440@60.0 on DP2 using pipe 
0, position (0, 0), rotation normal, reflection none

  The screen is Dell 2713H

  
  However there some errors in log

  Dec 19 15:30:19 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:20 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:26 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:30:26 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:05 stalagnat sudo[5511]:  mastier : TTY=pts/1 ; 
PWD=/home/mastier ; USER=root ; COMMAND=/bin/cat /var/log/Xorg.0.log
  Dec 19 15:32:05 stalagnat sudo[5511]: pam_unix(sudo:session): session opened 
for user root by mastier(uid=0)
  Dec 19 15:32:05 stalagnat sudo[5511]: pam_unix(sudo:session): session closed 
for user root
  Dec 19 15:32:07 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:07 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:21 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:22 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:22 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:22 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:34 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:35 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:35 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:32:35 stalagnat kernel: [drm:intel_cpu_fifo_underrun_irq_handler 
[i915]] *ERROR* CPU pipe A FIFO underrun
  Dec 19 15:33:05 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:05 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:05 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:06 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:09 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  Dec 19 15:33:09 stalagnat kernel: [drm:valleyview_update_wm [i915]] *ERROR* 
timed out waiting for Punit DDR DVFS request
  

[Kernel-packages] [Bug 1380183] [NEW] [SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P] suspend/resume failure

[Tommy the MetaKnight]

Public bug reported:

came up on startup.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-21-generic 3.16.0-21.28
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-21-generic i686
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.14.7-0ubuntu5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tommy  2474 F pulseaudio
Date: Sat Oct 11 13:40:50 2014
DuplicateSignature: suspend/resume:SAMSUNG ELECTRONICS CO., LTD. 
N150P/N210P/N220P:01KY.M008.20100430.RHU
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=2b6fecb9-d446-4646-9c89-662d3967fffe
InstallationDate: Installed on 2012-02-11 (973 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
InterpreterPath: /usr/bin/python3.4
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=bc9d04b4-a4b3-40a8-851e-a9a38f47d784 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:
 linux-restricted-modules-3.16.0-22-generic N/A
 linux-backports-modules-3.16.0-22-generic  N/A
 linux-firmware 1.135
SourcePackage: linux
Title: [SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/30/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01KY.M008.20100430.RHU
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N150P/N210P/N220P
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.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N150P/N210P/N220P
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: apport-kerneloops i386 resume suspend utopic

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

Title:
  [SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P] suspend/resume
  failure

Status in “linux” package in Ubuntu:
  New

Bug description:
  came up on startup.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-21-generic 3.16.0-21.28
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-21-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tommy  2474 F pulseaudio
  Date: Sat Oct 11 13:40:50 2014
  DuplicateSignature: suspend/resume:SAMSUNG ELECTRONICS CO., LTD. 
N150P/N210P/N220P:01KY.M008.20100430.RHU
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=2b6fecb9-d446-4646-9c89-662d3967fffe
  InstallationDate: Installed on 2012-02-11 (973 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  InterpreterPath: /usr/bin/python3.4
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=bc9d04b4-a4b3-40a8-851e-a9a38f47d784 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:
   linux-restricted-modules-3.16.0-22-generic N/A
   linux-backports-modules-3.16.0-22-generic  N/A
   linux-firmware 1.135
  SourcePackage: linux
  Title: [SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P] suspend/resume 
failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/30/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 01KY.M008.20100430.RHU
  dmi.board.asset.tag: SAMSUNG
  d

[Kernel-packages] [Bug 1380183] Re: [SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P] suspend/resume failure

[Tommy the MetaKnight]

** Description changed:

- came up on startup.
+ This came up on startup. My model is Samsung N150 Plus, model code
+ NP-N150-JP02CA. Basically a cheap netbook with an Intel atom CPU, and
+ integrated graphics.
  
  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-21-generic 3.16.0-21.28
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-21-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  tommy  2474 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  tommy  2474 F pulseaudio
  Date: Sat Oct 11 13:40:50 2014
  DuplicateSignature: suspend/resume:SAMSUNG ELECTRONICS CO., LTD. 
N150P/N210P/N220P:01KY.M008.20100430.RHU
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=2b6fecb9-d446-4646-9c89-662d3967fffe
  InstallationDate: Installed on 2012-02-11 (973 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  InterpreterPath: /usr/bin/python3.4
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
+  TERM=linux
+  PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=bc9d04b4-a4b3-40a8-851e-a9a38f47d784 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:
-  linux-restricted-modules-3.16.0-22-generic N/A
-  linux-backports-modules-3.16.0-22-generic  N/A
-  linux-firmware 1.135
+  linux-restricted-modules-3.16.0-22-generic N/A
+  linux-backports-modules-3.16.0-22-generic  N/A
+  linux-firmware 1.135
  SourcePackage: linux
  Title: [SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P] suspend/resume 
failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  dmi.bios.date: 04/30/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 01KY.M008.20100430.RHU
  dmi.board.asset.tag: SAMSUNG
  dmi.board.name: N150P/N210P/N220P
  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.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: N150P/N210P/N220P
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

Title:
  [SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P] suspend/resume
  failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This came up on startup. My model is Samsung N150 Plus, model code
  NP-N150-JP02CA. Basically a cheap netbook with an Intel atom CPU, and
  integrated graphics.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-21-generic 3.16.0-21.28
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-21-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tommy  2474 F pulseaudio
  Date: Sat Oct 11 13:40:50 2014
  DuplicateSignature: suspend/resume:SAMSUNG ELECTRONICS CO., LTD. 
N150P/N210P/N220P:01KY.M008.20100430.RHU
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=2b6fecb9-d446-4646-9c89-662d3967fffe
  InstallationDate: Installed on 2012-02-11 (973 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  InterpreterPath: /usr/bin/python3.4
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=bc9d04b4-a4b3-40a8-851e-a9a38f47d784 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No