[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient

[Bryan Quigley]

@Daniel
I'm wrong, not fixed in 13.04+

I ran some tests:
@Chiluk first up vm images do only need 64 mb reserved:
Trusty 512 MB (m1.tiny) image on OpenStack:   allocted 64 MB of ram for 
crashdump and it worked. (dump size of 23 mb)

Desktop images fail 
Trusty 2047 MB (Vagrant/Virtualbox desktop image) - allocated 64 MB of ram for 
crashdump and hung.
Reran with 100MB for crashdump, worked (dump size of 32 mb)

Is there any way to not be guessing here and generate the right number
for the kernel you are using and modules that have been loaded?  (In
other words, get current kernel size and add percentage buffer).   Per
another private case we may have situations where 128 MB is not enough.

If we can't auto-detect this (building upon chiluk's' comment), I would suggest 
something like (the numbers can change but I think we do need more levels):
 1.5 GB of RAM:  is it virtual kernel?  then do 64 mb, if not do 128 mb
1.5 GB to 4 GB: everything do 192 mb
4 GB+:  256 mb
12 GB+: 512 mb (is there a point when we should stop?)

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

Title:
  Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux
  is insufficient

Status in “grub2” package in Ubuntu:
  Confirmed
Status in “kexec-tools” package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: grub-pc

  This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty.

  The /etc/grub.d/10_linux file contains this snippet:

  # add crashkernel option if we have the required tools
  if [ -x /usr/bin/makedumpfile ]  [ -x /sbin/kexec ]; then
  GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA 
crashkernel=384M-2G:64M,2G-:128M
  fi

  I am on a system with 2GB of RAM (reported as 2038MB), and according
  to the kernel startup messages, 64MB is reserved for the crash kernel.

  Unfortunately, this does not appear to be enough memory for the
  regular Ubuntu kernel to boot. I am attaching a kernel log obtained
  via serial cable; it shows the initial boot, a crash in the kernel's
  video-driver-related code, the subsequent crashkernel boot, and then
  an apparent out of memory kernel panic. (A side effect of the
  double crash is that the system is left unresponsive, requiring a
  manual reset instead of rebooting itself automatically.)

  If I double the memory numbers in the crashkernel=... argument, so
  that the reservation is 128MB, the system correctly goes on to attempt
  a vmcore dump and reboot.

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

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

[Kernel-packages] [Bug 1252280] Re: System crash when updating via synaptic

[Bryan Quigley]

I wasn't able to get a backtrace as I ended up reformatting with 12.04
for another reason.

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

Title:
  System crash when updating via synaptic

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  This has happened multiple times, but we haven't gotten a proper
  backtrace yet.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-2-generic 3.12.0-2.7
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  2146 F pulseaudio
   /dev/snd/controlC2:  bryan  2146 F pulseaudio
   /dev/snd/controlC0:  bryan  2146 F pulseaudio
  Date: Mon Nov 18 09:06:20 2013
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: BIOSTAR Group TA890GXE
  MarkForUpload: True
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic 
root=UUID=71c44d3f-46d7-4e1a-bcc2-2775f45c6c05 ro 
crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-2G:64M,2G-:128M 
crashkernel=384M-2G:64M,2G-:128M
  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.12.0-2-generic N/A
   linux-backports-modules-3.12.0-2-generic  N/A
   linux-firmware1.117
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2013-11-08 (10 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1252280] Re: System crash when updating via synaptic

[Bryan Quigley]

** Information type changed from Private to Public

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

Title:
  System crash when updating via synaptic

Status in “linux” package in Ubuntu:
  New

Bug description:
  This has happened multiple times, but we haven't gotten a proper
  backtrace yet.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-2-generic 3.12.0-2.7
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  2146 F pulseaudio
   /dev/snd/controlC2:  bryan  2146 F pulseaudio
   /dev/snd/controlC0:  bryan  2146 F pulseaudio
  Date: Mon Nov 18 09:06:20 2013
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: BIOSTAR Group TA890GXE
  MarkForUpload: True
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic 
root=UUID=71c44d3f-46d7-4e1a-bcc2-2775f45c6c05 ro 
crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-2G:64M,2G-:128M 
crashkernel=384M-2G:64M,2G-:128M
  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.12.0-2-generic N/A
   linux-backports-modules-3.12.0-2-generic  N/A
   linux-firmware1.117
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2013-11-08 (10 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient

[Bryan Quigley]

This appears to be fixed in 13.04+.   Any chance we can get a fix
backported to 12.04?

If not, can we increase the memory by default?

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

Title:
  Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux
  is insufficient

Status in “grub2” package in Ubuntu:
  Confirmed
Status in “kexec-tools” package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: grub-pc

  This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty.

  The /etc/grub.d/10_linux file contains this snippet:

  # add crashkernel option if we have the required tools
  if [ -x /usr/bin/makedumpfile ]  [ -x /sbin/kexec ]; then
  GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA 
crashkernel=384M-2G:64M,2G-:128M
  fi

  I am on a system with 2GB of RAM (reported as 2038MB), and according
  to the kernel startup messages, 64MB is reserved for the crash kernel.

  Unfortunately, this does not appear to be enough memory for the
  regular Ubuntu kernel to boot. I am attaching a kernel log obtained
  via serial cable; it shows the initial boot, a crash in the kernel's
  video-driver-related code, the subsequent crashkernel boot, and then
  an apparent out of memory kernel panic. (A side effect of the
  double crash is that the system is left unresponsive, requiring a
  manual reset instead of rebooting itself automatically.)

  If I double the memory numbers in the crashkernel=... argument, so
  that the reservation is 128MB, the system correctly goes on to attempt
  a vmcore dump and reboot.

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

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

[Kernel-packages] [Bug 1295215] [NEW] Look into switching to bluez 5.x

[Bryan Quigley]

Public bug reported:

The Bluez release has many new features (http://www.bluez.org/release-
of-bluez-5-0/)

Among them is the deprecation of their bluez-gstreamer package, removing
this blocker to removing gstreamer0.10 from the desktop image.

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

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

Title:
   Look into switching to bluez 5.x

Status in “bluez” package in Ubuntu:
  New

Bug description:
  The Bluez release has many new features (http://www.bluez.org/release-
  of-bluez-5-0/)

  Among them is the deprecation of their bluez-gstreamer package,
  removing this blocker to removing gstreamer0.10 from the desktop
  image.

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

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

[Kernel-packages] [Bug 344566] Re: kexec restarts in single user mode

[Bryan Quigley]

Is this still an issue for you?  What did you do to workaround it?

** Changed in: kexec-tools (Ubuntu)
   Status: New = Incomplete

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

Title:
  kexec restarts in single user mode

Status in “kexec-tools” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: kexec-tools

  Currently if you use kexec and you select one of the recovery lines
  in grub, then after that it will restart in recovery mode every time
  you choose to restart your system (at least from the current GNOME UI
  etc.).

  Maybe if 'single' is in '/proc/cmdline', the init script(s) should do
  something different somehow (e.g. don't use kexec, or use the default
  kernel cmdline as specified in grub's menu.lst)?

  
  Tested on an up-to-date jaunty system, kexec-tools version is 
2009-2.0.0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/344566/+subscriptions

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

[Kernel-packages] [Bug 1311834] [NEW] adds crashkernel line during install, but doesn't remove it when it's purged

[Bryan Quigley]

Public bug reported:

1) Ubuntu 14.04. 
2) kexec-tools (1:2.0.6-0ubuntu2) 
3) I expect that when removing kexec-tools it removed the crashkernel line that 
it added
4) It doesn't get removed (tried both remove and purge)because kexec-tools 
doesn't call update-grub

A workaround is just to manually do an update-grub.

** Affects: kexec-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  adds crashkernel line during install, but doesn't remove it when it's
  purged

Status in “kexec-tools” package in Ubuntu:
  New

Bug description:
  1) Ubuntu 14.04. 
  2) kexec-tools (1:2.0.6-0ubuntu2) 
  3) I expect that when removing kexec-tools it removed the crashkernel line 
that it added
  4) It doesn't get removed (tried both remove and purge)because kexec-tools 
doesn't call update-grub

  A workaround is just to manually do an update-grub.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1311834/+subscriptions

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

[Kernel-packages] [Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal

[Bryan Quigley]

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

** This bug has been marked a duplicate of bug 1324558
   [SRU] biosdevname returns identical names for two different devices.

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

Title:
  biosdevname gives name of device as rename7 in Quantal

Status in “linux” package in Ubuntu:
  Confirmed
Status in “udev” package in Ubuntu:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “udev” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “udev” source package in Raring:
  Confirmed

Bug description:
  In Quantal kernel biosdevname feature is not working as it suppose to
  be. On hardware we are seeing an issue where few of the network
  interface names are named as rename7 etc.. while biosdevname -d
  utility provides the correct biosname while kernel name have been
  messed up. There are total 16 network interfaces on the server which
  are ALOMs for Emulex card connected to system.

  It seems this issue is a race condition and will get fixed in Fedora
  18. But having fix in Quantal will help also.

  https://bugzilla.redhat.com/show_bug.cgi?id=782145

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

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

[Kernel-packages] [Bug 1174374] Re: libreoffice-calc crashes/hangs desktop on Ubuntu 12.10 and 13.04 when opening a .xlsx file

[Bryan Quigley]

@jastram

I can't reproduce this.  What kind of video card do you have?  And could
you see if it happens in either a guest session or on a LiveCD?

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

Title:
  libreoffice-calc crashes/hangs desktop on Ubuntu 12.10 and 13.04 when
  opening a .xlsx file

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 12.10 several months ago, but LibreOffice was
  entirely unusable. Whenever I opened a document, spreadsheet, etc. it
  would crash or hang the desktop. I waited for Ubuntu 13.04, hoping
  that this would be resolved, but the issue is the same. Has anyone
  else seen this? Any hints for getting past this? Or do I need to go
  back to 12.04?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-calc 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 09:41:23 2013
  InstallationDate: Installed on 2013-04-26 (3 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1174374] Re: libreoffice-calc crashes/hangs desktop on Ubuntu 12.10 and 13.04 when opening a .xlsx file

[Bryan Quigley]

@jastram - Just to confirm worked means LibreOffice loaded the
document with no issues?  (not that the bug worked)

In that case; did you try my instructions from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1174374/comments/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/1174374

Title:
  libreoffice-calc crashes/hangs desktop on Ubuntu 12.10 and 13.04 when
  opening a .xlsx file

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I installed Ubuntu 12.10 several months ago, but LibreOffice was
  entirely unusable. Whenever I opened a document, spreadsheet, etc. it
  would crash or hang the desktop. I waited for Ubuntu 13.04, hoping
  that this would be resolved, but the issue is the same. Has anyone
  else seen this? Any hints for getting past this? Or do I need to go
  back to 12.04?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-calc 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon Apr 29 09:41:23 2013
  InstallationDate: Installed on 2013-04-26 (3 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1252280] Re: System crash when updating via synaptic

[Bryan Quigley]

I have not been able to reproduce this for some time.  Closing.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  System crash when updating via synaptic

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  This has happened multiple times, but we haven't gotten a proper
  backtrace yet.

  ProblemType: KernelCrash
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-2-generic 3.12.0-2.7
  ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0
  Uname: Linux 3.12.0-2-generic x86_64
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  2146 F pulseaudio
   /dev/snd/controlC2:  bryan  2146 F pulseaudio
   /dev/snd/controlC0:  bryan  2146 F pulseaudio
  Date: Mon Nov 18 09:06:20 2013
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: BIOSTAR Group TA890GXE
  MarkForUpload: True
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic 
root=UUID=71c44d3f-46d7-4e1a-bcc2-2775f45c6c05 ro 
crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-2G:64M,2G-:128M 
crashkernel=384M-2G:64M,2G-:128M
  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.12.0-2-generic N/A
   linux-backports-modules-3.12.0-2-generic  N/A
   linux-firmware1.117
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2013-11-08 (10 days ago)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 785394] Re: Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux is insufficient

[Bryan Quigley]

128MB didn't work
256MB did
Nothing else was tested on this machine.

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

Title:
  Hard-coded crashkernel=... memory reservation in /etc/grub.d/10_linux
  is insufficient

Status in “grub” package in Ubuntu:
  Fix Released
Status in “kexec-tools” package in Ubuntu:
  Fix Released
Status in “grub” source package in Precise:
  In Progress
Status in “grub” source package in Quantal:
  In Progress
Status in “grub” source package in Raring:
  In Progress
Status in “grub” source package in Saucy:
  In Progress

Bug description:
  Binary package hint: grub-pc

  This concerns grub-pc 1.99~rc1-13ubuntu3 in Ubuntu Natty.

  The /etc/grub.d/10_linux file contains this snippet:

  # add crashkernel option if we have the required tools
  if [ -x /usr/bin/makedumpfile ]  [ -x /sbin/kexec ]; then
  GRUB_CMDLINE_EXTRA=$GRUB_CMDLINE_EXTRA 
crashkernel=384M-2G:64M,2G-:128M
  fi

  I am on a system with 2GB of RAM (reported as 2038MB), and according
  to the kernel startup messages, 64MB is reserved for the crash kernel.

  Unfortunately, this does not appear to be enough memory for the
  regular Ubuntu kernel to boot. I am attaching a kernel log obtained
  via serial cable; it shows the initial boot, a crash in the kernel's
  video-driver-related code, the subsequent crashkernel boot, and then
  an apparent out of memory kernel panic. (A side effect of the
  double crash is that the system is left unresponsive, requiring a
  manual reset instead of rebooting itself automatically.)

  If I double the memory numbers in the crashkernel=... argument, so
  that the reservation is 128MB, the system correctly goes on to attempt
  a vmcore dump and reboot.

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

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

[Kernel-packages] [Bug 1368733] [NEW] general protection fault: 0000 [#1] SMP

[Bryan Quigley]

Public bug reported:

Asked to report bug.. no idea when this issue occurred.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-14-generic 3.16.0-14.20
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
NonfreeKernelModules: nvidia
Annotation: Your system might become unstablenow and might need to be restarted.
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bryan  2415 F pulseaudio
 /dev/snd/controlC0:  bryan  2415 F pulseaudio
Date: Thu Sep 11 23:20:08 2014
Failure: oops
InstallationDate: Installed on 2014-04-27 (137 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
 
 lxcbr0no wireless extensions.
MachineType: BIOSTAR Group TA890GXE
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=a391c643-63e1-42cd-938c-6565a0fad31f ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
RfKill:
 
SourcePackage: linux
Title: general protection fault:  [#1] SMP
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: TA890GXE
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
dmi.product.name: TA890GXE
dmi.sys.vendor: BIOSTAR Group

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


** Tags: amd64 apport-kerneloops kernel-oops 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/1368733

Title:
  general protection fault:  [#1] SMP

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Asked to report bug.. no idea when this issue occurred.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-14-generic 3.16.0-14.20
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  2415 F pulseaudio
   /dev/snd/controlC0:  bryan  2415 F pulseaudio
  Date: Thu Sep 11 23:20:08 2014
  Failure: oops
  InstallationDate: Installed on 2014-04-27 (137 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
  MachineType: BIOSTAR Group TA890GXE
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=a391c643-63e1-42cd-938c-6565a0fad31f ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1368733] Re: general protection fault: 0000 [#1] SMP

[Bryan Quigley]

I can't reproduce this at will, at least not yet.

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

Title:
  general protection fault:  [#1] SMP

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Asked to report bug.. no idea when this issue occurred.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-14-generic 3.16.0-14.20
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  2415 F pulseaudio
   /dev/snd/controlC0:  bryan  2415 F pulseaudio
  Date: Thu Sep 11 23:20:08 2014
  Failure: oops
  InstallationDate: Installed on 2014-04-27 (137 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
  MachineType: BIOSTAR Group TA890GXE
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=a391c643-63e1-42cd-938c-6565a0fad31f ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1368733] Re: general protection fault: 0000 [#1] SMP

[Bryan Quigley]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  general protection fault:  [#1] SMP

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  Asked to report bug.. no idea when this issue occurred.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-14-generic 3.16.0-14.20
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  2415 F pulseaudio
   /dev/snd/controlC0:  bryan  2415 F pulseaudio
  Date: Thu Sep 11 23:20:08 2014
  Failure: oops
  InstallationDate: Installed on 2014-04-27 (137 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   lxcbr0no wireless extensions.
  MachineType: BIOSTAR Group TA890GXE
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=a391c643-63e1-42cd-938c-6565a0fad31f ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
   
  SourcePackage: linux
  Title: general protection fault:  [#1] SMP
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[Bryan Quigley]

nfs_patch2.patch works for me w/ ~27000 home directory setup.   Thanks!
Please do link to the lkml if you can (might take a few days to appear).

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

Title:
  Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix
Status in “nfs-utils” source package in Trusty:
  New
Status in “linux” source package in Utopic:
  Won't Fix
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “nfs-utils” package in Debian:
  Incomplete
Status in Fedora:
  Unknown

Bug description:
  I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This 
server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 
662 homedirs for ldap authenticated users.
  /etc/exports is :
  /exports  192.168.0.0/24(rw,fsid=0,no_subtree_check)

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org

  [Translation]
  Method=nsswitch.

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  In /etc/default/nfs-kernel-server :
  RPCNFSDCOUNT=75
  RPCMOUNTDOPTS=--manage-gids

  2 Clients (rhel6 x86  Ubuntu 12.04.2 i686) are mounting this nfs4 exported 
directory with no problems :
  When doing ls -l /home on this clients, I have :
  ...
  drwx--   4 user100 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101 oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102 oldusers 4096 oct.   1 19:06 user102
  drwx--  36 user103 users4096 févr. 5 21:08 user103
  drwx--  36 user104 users4096 févr. 8 14:03 user104
  drwx--  30 user105 users4096 févr. 4 18:01 user105
  drwx--  28 user106 oldusers 4096 oct.   5  2011 user106
  drwx--  37 user107 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 user108 users4096 déc.  4 11:52 user108
  drwx--   4 user109 oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 user110 oldusers 4096 janv. 22 15:53 user109
  drwx--  31 user111 users4096 janv. 29 12:03 user110
  ...
  uid/gid mapping works fine, authldap works fine, ...

  All Clients running Ubuntu 12.10 i686  or  Ubuntu 12.10 amd64 are 
experiencing the same problem :
  The config files are the same that used in ubuntu 12.04.
  Auth ldap is correctly configured, user can log in.

  This is the /etc/fstab entry for /home :
  192.168.0.1:/ /home nfs  rw,nfsvers=4 0  0

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org
  [Translation]
  Method=nsswitch

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  /etc/nsswitch.conf is :
  passwd: files ldap
  group: files ldap
  shadow: files ldap

  When doing ls -l /home there is a strange problem :

  drwx--   4 4294967294 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102oldusers 4096 oct.   1 19:06 user102
  drwx--  36 4294967294 users4096 févr. 5 21:08 user103
  drwx--  36 4294967294 users4096 févr. 8 14:03 user104
  drwx--  30 4294967294 users4096 févr. 4 18:01 user105
  drwx--  28 4294967294 oldusers 4096 oct.   5  2011 user106
  drwx--  37 4294967294 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 4294967294 users4096 déc.  4 11:52 user108
  drwx--   4 user109oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 4294967294 oldusers 4096 janv. 22 15:53 user110
  drwx--  31 4294967294 users4096 janv. 29 12:03 user111

  for  571 homedirs (this number varies at each reboot)/662, the owner is the 
value 4294967294. For the  91 remaining homedirs,
  the owner is correct. The gidnumber is correctly mapped for all (only  5 
differents values used for gidNumber).

  In /var/log/syslog, I can see :

  For example : user110 is mapped as 4294967294.
  but the command id user110 returns :
  uid=31124(user110) gid=666(oldusers) groupes=666(oldusers)

  user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/
  :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images

  Then, he runs touch /home/user110/test :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 4294967294 oldusers0 févr. 13 16:01 test

  On the nfs server, If i do a ls -l in the same directory  :

  drwxr-xr-x 8 user110 oldusers 4096 janv.  19  2012 Bureau
  drwxr-xr-x 3 user110 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 user110 oldusers 4096 

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[Bryan Quigley]

For anyone following at home:
http://www.spinics.net/lists/linux-nfs/msg47185.html

@Carl,  For the future, it's probably better to use
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ at
least when you're pushing upstream.   It does help a lot for possibly
SRUing to know that it works on the trusty branch too :).  Thanks for
all your work!

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

Title:
  Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix
Status in “nfs-utils” source package in Trusty:
  New
Status in “linux” source package in Utopic:
  Won't Fix
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “nfs-utils” package in Debian:
  Incomplete
Status in Fedora:
  Unknown

Bug description:
  I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This 
server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 
662 homedirs for ldap authenticated users.
  /etc/exports is :
  /exports  192.168.0.0/24(rw,fsid=0,no_subtree_check)

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org

  [Translation]
  Method=nsswitch.

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  In /etc/default/nfs-kernel-server :
  RPCNFSDCOUNT=75
  RPCMOUNTDOPTS=--manage-gids

  2 Clients (rhel6 x86  Ubuntu 12.04.2 i686) are mounting this nfs4 exported 
directory with no problems :
  When doing ls -l /home on this clients, I have :
  ...
  drwx--   4 user100 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101 oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102 oldusers 4096 oct.   1 19:06 user102
  drwx--  36 user103 users4096 févr. 5 21:08 user103
  drwx--  36 user104 users4096 févr. 8 14:03 user104
  drwx--  30 user105 users4096 févr. 4 18:01 user105
  drwx--  28 user106 oldusers 4096 oct.   5  2011 user106
  drwx--  37 user107 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 user108 users4096 déc.  4 11:52 user108
  drwx--   4 user109 oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 user110 oldusers 4096 janv. 22 15:53 user109
  drwx--  31 user111 users4096 janv. 29 12:03 user110
  ...
  uid/gid mapping works fine, authldap works fine, ...

  All Clients running Ubuntu 12.10 i686  or  Ubuntu 12.10 amd64 are 
experiencing the same problem :
  The config files are the same that used in ubuntu 12.04.
  Auth ldap is correctly configured, user can log in.

  This is the /etc/fstab entry for /home :
  192.168.0.1:/ /home nfs  rw,nfsvers=4 0  0

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org
  [Translation]
  Method=nsswitch

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  /etc/nsswitch.conf is :
  passwd: files ldap
  group: files ldap
  shadow: files ldap

  When doing ls -l /home there is a strange problem :

  drwx--   4 4294967294 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102oldusers 4096 oct.   1 19:06 user102
  drwx--  36 4294967294 users4096 févr. 5 21:08 user103
  drwx--  36 4294967294 users4096 févr. 8 14:03 user104
  drwx--  30 4294967294 users4096 févr. 4 18:01 user105
  drwx--  28 4294967294 oldusers 4096 oct.   5  2011 user106
  drwx--  37 4294967294 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 4294967294 users4096 déc.  4 11:52 user108
  drwx--   4 user109oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 4294967294 oldusers 4096 janv. 22 15:53 user110
  drwx--  31 4294967294 users4096 janv. 29 12:03 user111

  for  571 homedirs (this number varies at each reboot)/662, the owner is the 
value 4294967294. For the  91 remaining homedirs,
  the owner is correct. The gidnumber is correctly mapped for all (only  5 
differents values used for gidNumber).

  In /var/log/syslog, I can see :

  For example : user110 is mapped as 4294967294.
  but the command id user110 returns :
  uid=31124(user110) gid=666(oldusers) groupes=666(oldusers)

  user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/
  :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images

  Then, he runs touch /home/user110/test :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 4294967294 oldusers0 févr. 13 16:01 test

  On the 

[Kernel-packages] [Bug 1364539] Re: [Dell Latitude E7440] suspend/resume failure

[Bryan Quigley]

@mr-ghettoblaster
In that case, please do try with a mainline kernel and see if it's still the 
case (see Christopher's instructions).

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

Title:
  [Dell Latitude E7440] suspend/resume failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  If relevant, I docked the laptop between suspending and resuming.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-11-generic 3.16.0-11.16
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael2707 F pulseaudio
   /dev/snd/controlC0:  michael2707 F pulseaudio
  Date: Tue Sep  2 19:58:10 2014
  DuplicateSignature: suspend/resume:Dell Inc. Latitude E7440:A10
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=6d651e5a-075d-4911-a5ce-6710f7246853
  InstallationDate: Installed on 2014-08-01 (32 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Latitude E7440
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic 
root=/dev/mapper/ubuntu--vg-root 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-11-generic N/A
   linux-backports-modules-3.16.0-11-generic  N/A
   linux-firmware 1.132
  SourcePackage: linux
  Title: [Dell Inc. Latitude E7440] suspend/resume failure
  UpgradeStatus: Upgraded to utopic on 2014-08-28 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RYCC9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[Bryan Quigley]

Interesting.. keyutils doesn't seem to help in my case.I'm running
ls on the ~27000 user accounts home directory..

I don't understand why this would help... all nfsidmap would do is clear
it once, and then it can fill up again/expire again.

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

Title:
  Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix
Status in “nfs-utils” source package in Trusty:
  New
Status in “linux” source package in Utopic:
  Won't Fix
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “nfs-utils” package in Debian:
  Incomplete
Status in Fedora:
  Unknown

Bug description:
  I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This 
server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 
662 homedirs for ldap authenticated users.
  /etc/exports is :
  /exports  192.168.0.0/24(rw,fsid=0,no_subtree_check)

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org

  [Translation]
  Method=nsswitch.

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  In /etc/default/nfs-kernel-server :
  RPCNFSDCOUNT=75
  RPCMOUNTDOPTS=--manage-gids

  2 Clients (rhel6 x86  Ubuntu 12.04.2 i686) are mounting this nfs4 exported 
directory with no problems :
  When doing ls -l /home on this clients, I have :
  ...
  drwx--   4 user100 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101 oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102 oldusers 4096 oct.   1 19:06 user102
  drwx--  36 user103 users4096 févr. 5 21:08 user103
  drwx--  36 user104 users4096 févr. 8 14:03 user104
  drwx--  30 user105 users4096 févr. 4 18:01 user105
  drwx--  28 user106 oldusers 4096 oct.   5  2011 user106
  drwx--  37 user107 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 user108 users4096 déc.  4 11:52 user108
  drwx--   4 user109 oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 user110 oldusers 4096 janv. 22 15:53 user109
  drwx--  31 user111 users4096 janv. 29 12:03 user110
  ...
  uid/gid mapping works fine, authldap works fine, ...

  All Clients running Ubuntu 12.10 i686  or  Ubuntu 12.10 amd64 are 
experiencing the same problem :
  The config files are the same that used in ubuntu 12.04.
  Auth ldap is correctly configured, user can log in.

  This is the /etc/fstab entry for /home :
  192.168.0.1:/ /home nfs  rw,nfsvers=4 0  0

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org
  [Translation]
  Method=nsswitch

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  /etc/nsswitch.conf is :
  passwd: files ldap
  group: files ldap
  shadow: files ldap

  When doing ls -l /home there is a strange problem :

  drwx--   4 4294967294 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102oldusers 4096 oct.   1 19:06 user102
  drwx--  36 4294967294 users4096 févr. 5 21:08 user103
  drwx--  36 4294967294 users4096 févr. 8 14:03 user104
  drwx--  30 4294967294 users4096 févr. 4 18:01 user105
  drwx--  28 4294967294 oldusers 4096 oct.   5  2011 user106
  drwx--  37 4294967294 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 4294967294 users4096 déc.  4 11:52 user108
  drwx--   4 user109oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 4294967294 oldusers 4096 janv. 22 15:53 user110
  drwx--  31 4294967294 users4096 janv. 29 12:03 user111

  for  571 homedirs (this number varies at each reboot)/662, the owner is the 
value 4294967294. For the  91 remaining homedirs,
  the owner is correct. The gidnumber is correctly mapped for all (only  5 
differents values used for gidNumber).

  In /var/log/syslog, I can see :

  For example : user110 is mapped as 4294967294.
  but the command id user110 returns :
  uid=31124(user110) gid=666(oldusers) groupes=666(oldusers)

  user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/
  :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images

  Then, he runs touch /home/user110/test :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 4294967294 oldusers0 févr. 13 16:01 test

  On the nfs server, If i do a ls -l in the same directory  :

  drwxr-xr-x 8 user110 oldusers 4096 janv.  19  2012 Bureau
 

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[Bryan Quigley]

@carlh
Ah, your kernel patch also fixes the case where the key cache get's filled.  
(Which is my 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/1124250

Title:
  Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix
Status in “nfs-utils” source package in Trusty:
  New
Status in “linux” source package in Utopic:
  Won't Fix
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “nfs-utils” package in Debian:
  Incomplete
Status in Fedora:
  Unknown

Bug description:
  I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This 
server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 
662 homedirs for ldap authenticated users.
  /etc/exports is :
  /exports  192.168.0.0/24(rw,fsid=0,no_subtree_check)

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org

  [Translation]
  Method=nsswitch.

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  In /etc/default/nfs-kernel-server :
  RPCNFSDCOUNT=75
  RPCMOUNTDOPTS=--manage-gids

  2 Clients (rhel6 x86  Ubuntu 12.04.2 i686) are mounting this nfs4 exported 
directory with no problems :
  When doing ls -l /home on this clients, I have :
  ...
  drwx--   4 user100 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101 oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102 oldusers 4096 oct.   1 19:06 user102
  drwx--  36 user103 users4096 févr. 5 21:08 user103
  drwx--  36 user104 users4096 févr. 8 14:03 user104
  drwx--  30 user105 users4096 févr. 4 18:01 user105
  drwx--  28 user106 oldusers 4096 oct.   5  2011 user106
  drwx--  37 user107 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 user108 users4096 déc.  4 11:52 user108
  drwx--   4 user109 oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 user110 oldusers 4096 janv. 22 15:53 user109
  drwx--  31 user111 users4096 janv. 29 12:03 user110
  ...
  uid/gid mapping works fine, authldap works fine, ...

  All Clients running Ubuntu 12.10 i686  or  Ubuntu 12.10 amd64 are 
experiencing the same problem :
  The config files are the same that used in ubuntu 12.04.
  Auth ldap is correctly configured, user can log in.

  This is the /etc/fstab entry for /home :
  192.168.0.1:/ /home nfs  rw,nfsvers=4 0  0

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org
  [Translation]
  Method=nsswitch

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  /etc/nsswitch.conf is :
  passwd: files ldap
  group: files ldap
  shadow: files ldap

  When doing ls -l /home there is a strange problem :

  drwx--   4 4294967294 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102oldusers 4096 oct.   1 19:06 user102
  drwx--  36 4294967294 users4096 févr. 5 21:08 user103
  drwx--  36 4294967294 users4096 févr. 8 14:03 user104
  drwx--  30 4294967294 users4096 févr. 4 18:01 user105
  drwx--  28 4294967294 oldusers 4096 oct.   5  2011 user106
  drwx--  37 4294967294 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 4294967294 users4096 déc.  4 11:52 user108
  drwx--   4 user109oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 4294967294 oldusers 4096 janv. 22 15:53 user110
  drwx--  31 4294967294 users4096 janv. 29 12:03 user111

  for  571 homedirs (this number varies at each reboot)/662, the owner is the 
value 4294967294. For the  91 remaining homedirs,
  the owner is correct. The gidnumber is correctly mapped for all (only  5 
differents values used for gidNumber).

  In /var/log/syslog, I can see :

  For example : user110 is mapped as 4294967294.
  but the command id user110 returns :
  uid=31124(user110) gid=666(oldusers) groupes=666(oldusers)

  user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/
  :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images

  Then, he runs touch /home/user110/test :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 4294967294 oldusers0 févr. 13 16:01 test

  On the nfs server, If i do a ls -l in the same directory  :

  drwxr-xr-x 8 user110 oldusers 4096 janv.  19  2012 Bureau
  drwxr-xr-x 3 user110 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 user110 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[Bryan Quigley]

Works for original case, except nogroup now returns 4294967294, will
ping list with results..

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

Title:
  Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix
Status in “nfs-utils” source package in Trusty:
  Confirmed
Status in “linux” source package in Utopic:
  Won't Fix
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “nfs-utils” package in Debian:
  Incomplete
Status in Fedora:
  Unknown

Bug description:
  I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This 
server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 
662 homedirs for ldap authenticated users.
  /etc/exports is :
  /exports  192.168.0.0/24(rw,fsid=0,no_subtree_check)

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org

  [Translation]
  Method=nsswitch.

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  In /etc/default/nfs-kernel-server :
  RPCNFSDCOUNT=75
  RPCMOUNTDOPTS=--manage-gids

  2 Clients (rhel6 x86  Ubuntu 12.04.2 i686) are mounting this nfs4 exported 
directory with no problems :
  When doing ls -l /home on this clients, I have :
  ...
  drwx--   4 user100 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101 oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102 oldusers 4096 oct.   1 19:06 user102
  drwx--  36 user103 users4096 févr. 5 21:08 user103
  drwx--  36 user104 users4096 févr. 8 14:03 user104
  drwx--  30 user105 users4096 févr. 4 18:01 user105
  drwx--  28 user106 oldusers 4096 oct.   5  2011 user106
  drwx--  37 user107 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 user108 users4096 déc.  4 11:52 user108
  drwx--   4 user109 oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 user110 oldusers 4096 janv. 22 15:53 user109
  drwx--  31 user111 users4096 janv. 29 12:03 user110
  ...
  uid/gid mapping works fine, authldap works fine, ...

  All Clients running Ubuntu 12.10 i686  or  Ubuntu 12.10 amd64 are 
experiencing the same problem :
  The config files are the same that used in ubuntu 12.04.
  Auth ldap is correctly configured, user can log in.

  This is the /etc/fstab entry for /home :
  192.168.0.1:/ /home nfs  rw,nfsvers=4 0  0

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org
  [Translation]
  Method=nsswitch

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  /etc/nsswitch.conf is :
  passwd: files ldap
  group: files ldap
  shadow: files ldap

  When doing ls -l /home there is a strange problem :

  drwx--   4 4294967294 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102oldusers 4096 oct.   1 19:06 user102
  drwx--  36 4294967294 users4096 févr. 5 21:08 user103
  drwx--  36 4294967294 users4096 févr. 8 14:03 user104
  drwx--  30 4294967294 users4096 févr. 4 18:01 user105
  drwx--  28 4294967294 oldusers 4096 oct.   5  2011 user106
  drwx--  37 4294967294 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 4294967294 users4096 déc.  4 11:52 user108
  drwx--   4 user109oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 4294967294 oldusers 4096 janv. 22 15:53 user110
  drwx--  31 4294967294 users4096 janv. 29 12:03 user111

  for  571 homedirs (this number varies at each reboot)/662, the owner is the 
value 4294967294. For the  91 remaining homedirs,
  the owner is correct. The gidnumber is correctly mapped for all (only  5 
differents values used for gidNumber).

  In /var/log/syslog, I can see :

  For example : user110 is mapped as 4294967294.
  but the command id user110 returns :
  uid=31124(user110) gid=666(oldusers) groupes=666(oldusers)

  user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/
  :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images

  Then, he runs touch /home/user110/test :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 4294967294 oldusers0 févr. 13 16:01 test

  On the nfs server, If i do a ls -l in the same directory  :

  drwxr-xr-x 8 user110 oldusers 4096 janv.  19  2012 Bureau
  drwxr-xr-x 3 user110 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 user110 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 user110 

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[Bryan Quigley]

Or not.. it seems my issue was fixed somewhere between 3.13 and
3.17rc7...

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

Title:
  Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix
Status in “nfs-utils” source package in Trusty:
  Confirmed
Status in “linux” source package in Utopic:
  Won't Fix
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “nfs-utils” package in Debian:
  Incomplete
Status in Fedora:
  Unknown

Bug description:
  I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This 
server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 
662 homedirs for ldap authenticated users.
  /etc/exports is :
  /exports  192.168.0.0/24(rw,fsid=0,no_subtree_check)

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org

  [Translation]
  Method=nsswitch.

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  In /etc/default/nfs-kernel-server :
  RPCNFSDCOUNT=75
  RPCMOUNTDOPTS=--manage-gids

  2 Clients (rhel6 x86  Ubuntu 12.04.2 i686) are mounting this nfs4 exported 
directory with no problems :
  When doing ls -l /home on this clients, I have :
  ...
  drwx--   4 user100 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101 oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102 oldusers 4096 oct.   1 19:06 user102
  drwx--  36 user103 users4096 févr. 5 21:08 user103
  drwx--  36 user104 users4096 févr. 8 14:03 user104
  drwx--  30 user105 users4096 févr. 4 18:01 user105
  drwx--  28 user106 oldusers 4096 oct.   5  2011 user106
  drwx--  37 user107 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 user108 users4096 déc.  4 11:52 user108
  drwx--   4 user109 oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 user110 oldusers 4096 janv. 22 15:53 user109
  drwx--  31 user111 users4096 janv. 29 12:03 user110
  ...
  uid/gid mapping works fine, authldap works fine, ...

  All Clients running Ubuntu 12.10 i686  or  Ubuntu 12.10 amd64 are 
experiencing the same problem :
  The config files are the same that used in ubuntu 12.04.
  Auth ldap is correctly configured, user can log in.

  This is the /etc/fstab entry for /home :
  192.168.0.1:/ /home nfs  rw,nfsvers=4 0  0

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org
  [Translation]
  Method=nsswitch

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  /etc/nsswitch.conf is :
  passwd: files ldap
  group: files ldap
  shadow: files ldap

  When doing ls -l /home there is a strange problem :

  drwx--   4 4294967294 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102oldusers 4096 oct.   1 19:06 user102
  drwx--  36 4294967294 users4096 févr. 5 21:08 user103
  drwx--  36 4294967294 users4096 févr. 8 14:03 user104
  drwx--  30 4294967294 users4096 févr. 4 18:01 user105
  drwx--  28 4294967294 oldusers 4096 oct.   5  2011 user106
  drwx--  37 4294967294 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 4294967294 users4096 déc.  4 11:52 user108
  drwx--   4 user109oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 4294967294 oldusers 4096 janv. 22 15:53 user110
  drwx--  31 4294967294 users4096 janv. 29 12:03 user111

  for  571 homedirs (this number varies at each reboot)/662, the owner is the 
value 4294967294. For the  91 remaining homedirs,
  the owner is correct. The gidnumber is correctly mapped for all (only  5 
differents values used for gidNumber).

  In /var/log/syslog, I can see :

  For example : user110 is mapped as 4294967294.
  but the command id user110 returns :
  uid=31124(user110) gid=666(oldusers) groupes=666(oldusers)

  user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/
  :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images

  Then, he runs touch /home/user110/test :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 4294967294 oldusers0 févr. 13 16:01 test

  On the nfs server, If i do a ls -l in the same directory  :

  drwxr-xr-x 8 user110 oldusers 4096 janv.  19  2012 Bureau
  drwxr-xr-x 3 user110 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 user110 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 user110 oldusers0 

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[Bryan Quigley]

It turns out in 3.17rc4 the root_maxkeys/bytes were greatly increased
which is actually what solved my issue..  Sorry for the noise.

Raw notes:
with key utils - 3.17.rc7 - main issue gone, nogroup is now 4294967294
without key utils - 3.17-rc7 - main issue gone, nogroup is fine too
 
all rest without key utils
3.17-rc4 - no 4294967294 in output
/proc/sys/kernel/keys/root_maxbytes 2500
/proc/sys/kernel/keys/root_maxkeys  100

3.17-rc3 - ~24000 in 3.17-rc4
/proc/sys/kernel/keys/root_maxkeys  200
/proc/sys/kernel/keys/root_maxbytes 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/1124250

Title:
  Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix
Status in “nfs-utils” source package in Trusty:
  Confirmed
Status in “linux” source package in Utopic:
  Won't Fix
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “nfs-utils” package in Debian:
  Incomplete
Status in Fedora:
  Unknown

Bug description:
  I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This 
server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 
662 homedirs for ldap authenticated users.
  /etc/exports is :
  /exports  192.168.0.0/24(rw,fsid=0,no_subtree_check)

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org

  [Translation]
  Method=nsswitch.

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  In /etc/default/nfs-kernel-server :
  RPCNFSDCOUNT=75
  RPCMOUNTDOPTS=--manage-gids

  2 Clients (rhel6 x86  Ubuntu 12.04.2 i686) are mounting this nfs4 exported 
directory with no problems :
  When doing ls -l /home on this clients, I have :
  ...
  drwx--   4 user100 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101 oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102 oldusers 4096 oct.   1 19:06 user102
  drwx--  36 user103 users4096 févr. 5 21:08 user103
  drwx--  36 user104 users4096 févr. 8 14:03 user104
  drwx--  30 user105 users4096 févr. 4 18:01 user105
  drwx--  28 user106 oldusers 4096 oct.   5  2011 user106
  drwx--  37 user107 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 user108 users4096 déc.  4 11:52 user108
  drwx--   4 user109 oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 user110 oldusers 4096 janv. 22 15:53 user109
  drwx--  31 user111 users4096 janv. 29 12:03 user110
  ...
  uid/gid mapping works fine, authldap works fine, ...

  All Clients running Ubuntu 12.10 i686  or  Ubuntu 12.10 amd64 are 
experiencing the same problem :
  The config files are the same that used in ubuntu 12.04.
  Auth ldap is correctly configured, user can log in.

  This is the /etc/fstab entry for /home :
  192.168.0.1:/ /home nfs  rw,nfsvers=4 0  0

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org
  [Translation]
  Method=nsswitch

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  /etc/nsswitch.conf is :
  passwd: files ldap
  group: files ldap
  shadow: files ldap

  When doing ls -l /home there is a strange problem :

  drwx--   4 4294967294 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102oldusers 4096 oct.   1 19:06 user102
  drwx--  36 4294967294 users4096 févr. 5 21:08 user103
  drwx--  36 4294967294 users4096 févr. 8 14:03 user104
  drwx--  30 4294967294 users4096 févr. 4 18:01 user105
  drwx--  28 4294967294 oldusers 4096 oct.   5  2011 user106
  drwx--  37 4294967294 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 4294967294 users4096 déc.  4 11:52 user108
  drwx--   4 user109oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 4294967294 oldusers 4096 janv. 22 15:53 user110
  drwx--  31 4294967294 users4096 janv. 29 12:03 user111

  for  571 homedirs (this number varies at each reboot)/662, the owner is the 
value 4294967294. For the  91 remaining homedirs,
  the owner is correct. The gidnumber is correctly mapped for all (only  5 
differents values used for gidNumber).

  In /var/log/syslog, I can see :

  For example : user110 is mapped as 4294967294.
  but the command id user110 returns :
  uid=31124(user110) gid=666(oldusers) groupes=666(oldusers)

  user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/
  :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images

  Then, he runs touch /home/user110/test :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[Bryan Quigley]

@Dariusz

My understanding is that we can't backport a config change (say to
trusty).  Since that was done upstream won't it just hit vivid in it's
own time?  In the mean time, this is configurable so a user can change
their config in 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/1124250

Title:
  Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

Status in “linux” package in Ubuntu:
  Confirmed
Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “linux” source package in Trusty:
  Won't Fix
Status in “nfs-utils” source package in Trusty:
  Confirmed
Status in “linux” source package in Utopic:
  Won't Fix
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “nfs-utils” package in Debian:
  Incomplete
Status in Fedora:
  Unknown

Bug description:
  I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This 
server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 
662 homedirs for ldap authenticated users.
  /etc/exports is :
  /exports  192.168.0.0/24(rw,fsid=0,no_subtree_check)

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org

  [Translation]
  Method=nsswitch.

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  In /etc/default/nfs-kernel-server :
  RPCNFSDCOUNT=75
  RPCMOUNTDOPTS=--manage-gids

  2 Clients (rhel6 x86  Ubuntu 12.04.2 i686) are mounting this nfs4 exported 
directory with no problems :
  When doing ls -l /home on this clients, I have :
  ...
  drwx--   4 user100 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101 oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102 oldusers 4096 oct.   1 19:06 user102
  drwx--  36 user103 users4096 févr. 5 21:08 user103
  drwx--  36 user104 users4096 févr. 8 14:03 user104
  drwx--  30 user105 users4096 févr. 4 18:01 user105
  drwx--  28 user106 oldusers 4096 oct.   5  2011 user106
  drwx--  37 user107 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 user108 users4096 déc.  4 11:52 user108
  drwx--   4 user109 oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 user110 oldusers 4096 janv. 22 15:53 user109
  drwx--  31 user111 users4096 janv. 29 12:03 user110
  ...
  uid/gid mapping works fine, authldap works fine, ...

  All Clients running Ubuntu 12.10 i686  or  Ubuntu 12.10 amd64 are 
experiencing the same problem :
  The config files are the same that used in ubuntu 12.04.
  Auth ldap is correctly configured, user can log in.

  This is the /etc/fstab entry for /home :
  192.168.0.1:/ /home nfs  rw,nfsvers=4 0  0

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org
  [Translation]
  Method=nsswitch

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  /etc/nsswitch.conf is :
  passwd: files ldap
  group: files ldap
  shadow: files ldap

  When doing ls -l /home there is a strange problem :

  drwx--   4 4294967294 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102oldusers 4096 oct.   1 19:06 user102
  drwx--  36 4294967294 users4096 févr. 5 21:08 user103
  drwx--  36 4294967294 users4096 févr. 8 14:03 user104
  drwx--  30 4294967294 users4096 févr. 4 18:01 user105
  drwx--  28 4294967294 oldusers 4096 oct.   5  2011 user106
  drwx--  37 4294967294 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 4294967294 users4096 déc.  4 11:52 user108
  drwx--   4 user109oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 4294967294 oldusers 4096 janv. 22 15:53 user110
  drwx--  31 4294967294 users4096 janv. 29 12:03 user111

  for  571 homedirs (this number varies at each reboot)/662, the owner is the 
value 4294967294. For the  91 remaining homedirs,
  the owner is correct. The gidnumber is correctly mapped for all (only  5 
differents values used for gidNumber).

  In /var/log/syslog, I can see :

  For example : user110 is mapped as 4294967294.
  but the command id user110 returns :
  uid=31124(user110) gid=666(oldusers) groupes=666(oldusers)

  user110 logs in (auth ldap) from tty1. He runs ls -l /home/user110/
  :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images

  Then, he runs touch /home/user110/test :

  drwxr-xr-x 8 4294967294 oldusers 4096 janv. 19  2012 Bureau
  drwxr-xr-x 3 4294967294 oldusers 4096 déc.   2  2011 Documents
  drwxr-xr-x 2 4294967294 oldusers 4096 déc.   2  2011 Images
  drwxr-xr-x 2 4294967294 oldusers0 févr. 13 16:01 test

  On the nfs server, If i do a ls -l in the same directory  :

  drwxr-xr-x 8 user110 oldusers 4096 janv.  19  2012 

[Kernel-packages] [Bug 1401741] [NEW] rtl8188ee wireless driver high packet loss

[Bryan Quigley]

Public bug reported:

I've seen this issue since trusty, very bad packet loss,varrying in ping
from 10%-45% to the gatewway. This is a toshiba c55d laptop.

Already tried mainline (3.18.0) with no noticable improvement.

Previously reported here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258870

AP is a MI424WR-GEN3I from Verizon with WPA2 running in  Compatibility 
Mode(802.11b/g/n)
No other devices on network have ever had this issue, in fact any loss of ICMP 
packets almost never occurs on other devices from same location.

I will be trying the Realtek (from their website) and
https://github.com/FreedomBen/rtl8188ce-linux-driver next.   Any other
ideas/suggestions welcome.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-28-generic 3.16.0-28.37
ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  erica  2366 F pulseaudio
 /dev/snd/controlC0:  erica  2366 F pulseaudio
CurrentDesktop: Unity
Date: Thu Dec 11 22:01:36 2014
HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
InstallationDate: Installed on 2014-05-29 (196 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: TOSHIBA Satellite C55D-A
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-28-generic N/A
 linux-backports-modules-3.16.0-28-generic  N/A
 linux-firmware 1.138
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
dmi.bios.date: 12/25/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.70
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: MP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C55D-A
dmi.product.version: PSCFWU-04C031
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug 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/1401741

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  New

Bug description:
  I've seen this issue since trusty, very bad packet loss,varrying in
  ping from 10%-45% to the gatewway. This is a toshiba c55d laptop.

  Already tried mainline (3.18.0) with no noticable improvement.

  Previously reported here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258870

  AP is a MI424WR-GEN3I from Verizon with WPA2 running in  Compatibility 
Mode(802.11b/g/n)
  No other devices on network have ever had this issue, in fact any loss of 
ICMP packets almost never occurs on other devices from same location.

  I will be trying the Realtek (from their website) and
  https://github.com/FreedomBen/rtl8188ce-linux-driver next.   Any other
  ideas/suggestions welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board 

[Kernel-packages] [Bug 1258870] Re: rtl8188ee wireless driver unusable: 25-30% packet loss. 13.10 Saucy

[Bryan Quigley]

Just FYI, reported a new bug on this here -
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401741

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

Title:
  rtl8188ee wireless driver unusable: 25-30% packet loss. 13.10 Saucy

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm seeing a consistent packet loss problem with the rtl8188ee Realtek
  wireless driver.  Long sequences of pings to the access point IP show
  25-30% packet loss.  Downloads get 'stuck', pages don't load, it's
  generally unusable.

  I've tried the following kernels:

  /boot/initrd.img-3.11.0-12-generic  /boot/initrd.img-3.12.3-031203-generic
  /boot/initrd.img-3.11.0-14-generic  /boot/initrd.img-3.13.0-031300rc3-generic

  all with the same result.  Packet capture shows lots of dup ACKs, some
  retransmits.

  I suspected 802.11n might be the culprit, but I've disabled it at the
  AP, and the driver seems to respect that judging by these log lines:

  Dec  7 21:50:52 congo kernel: [13812.218008] rtl8188ee :01:00.0 wlan0: 
disabling HT as WMM/QoS is not supported by the 
  AP
  Dec  7 21:50:52 congo kernel: [13812.218011] rtl8188ee :01:00.0 wlan0: 
disabling VHT as WMM/QoS is not supported by the
   AP

  Other than those lines there isn't anything noteworthy in syslog.

  Very interested in getting this fixed, please let me know how I can
  help debug.

  $ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  $ uname -a
  Linux congo 3.13.0-031300rc3-generic #201312061335 SMP Fri Dec 6 18:37:23 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo lshw -C network
*-network   
 description: Wireless interface
 product: RTL8188EE Wireless Network Adapter
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:01:00.0
 logical name: wlan0
 version: 01
 serial: 34:23:87:0d:23:85
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=rtl8188ee 
driverversion=3.13.0-031300rc3-generic firmware=N/A ip=192.168.1.68 latency=0 
link=yes multicast=yes wireless=IEEE 802.11bgn
 resources: irq:18 ioport:5000(size=256) memory:b260-b2603fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:09:00.0
 logical name: eth0
 version: 0c
 serial: 9c:b6:54:c1:7d:36
 size: 10Mbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8168g-2_0.0.1 02/06/13 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
 resources: irq:43 ioport:3000(size=256) memory:b250-b2500fff 
memory:b240-b2403fff

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

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

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

The FreedomBen driver doesn't appear to help.
Realtek's drivers on their site don't work on kernels 3.9... so I didn't test 
them.

New testing right next to the router, packet loss ~8%, latency average
8ms,  tops in the 100+ range

Changing to legacy b/g only - still packet loss.
 - channel 1 - no effect, still packet loss.
 - channel 5 - tests show no packet loss!
 - channel 6 - tests show no packet loss!
 - channel 11 - no, effect, still packet loss

b/g/n retesting:
 - channel 1 - still packet loss
 - channel 6 - no packet loss (sometimes groups of 100 0-3 packets lost).. 
much better than other channels. 
 - channel 11 - still packet loss

If you have the same issue, try using Channel 6.

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've seen this issue since trusty, very bad packet loss,varrying in
  ping from 10%-45% to the gatewway. This is a toshiba c55d laptop.

  Already tried mainline (3.18.0) with no noticable improvement.

  Previously reported here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258870

  AP is a MI424WR-GEN3I from Verizon with WPA2 running in  Compatibility 
Mode(802.11b/g/n)
  No other devices on network have ever had this issue, in fact any loss of 
ICMP packets almost never occurs on other devices from same location.

  I will be trying the Realtek (from their website) and
  https://github.com/FreedomBen/rtl8188ce-linux-driver next.   Any other
  ideas/suggestions welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

BIOS update (deployed via CD) doesn't appear to have changed anything in
regards to this issue.

$ sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date
1.80
01/27/2014


** Tags removed: bios-outdated-1.80

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've seen this issue since trusty, very bad packet loss,varrying in
  ping from 10%-45% to the gatewway. This is a toshiba c55d laptop.

  Already tried mainline (3.18.0) with no noticable improvement.

  Previously reported here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258870

  AP is a MI424WR-GEN3I from Verizon with WPA2 running in  Compatibility 
Mode(802.11b/g/n)
  No other devices on network have ever had this issue, in fact any loss of 
ICMP packets almost never occurs on other devices from same location.

  I will be trying the Realtek (from their website) and
  https://github.com/FreedomBen/rtl8188ce-linux-driver next.   Any other
  ideas/suggestions welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

@penalvch
Is there anything you're specifically looking for?  I went through that doc 
originally trying the items that were doable/made sense in my setup.

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a toshiba c55d laptop. I've seen this issue since trusty, very
  bad packet loss,varrying in ping from 10%-45% to  Verizon MI424WR-
  GEN3I AP with WPA2 running in Compatibility Mode(802.11b/g/n). No
  other devices on network have ever had this issue, in fact any loss of
  ICMP packets almost never occurs on other devices from same location.

  Already tried mainline (3.18.0) with no noticeable improvement.

  I will be trying the Realtek (from their website) and
  https://github.com/FreedomBen/rtl8188ce-linux-driver next.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

** Description changed:

  This is a toshiba c55d laptop. I've seen this issue since trusty, very
  bad packet loss,varrying in ping from 10%-45% to  Verizon MI424WR-GEN3I
  AP with WPA2 running in Compatibility Mode(802.11b/g/n). No other
  devices on network have ever had this issue, in fact any loss of ICMP
  packets almost never occurs on other devices from same location.
  
  Already tried mainline (3.18.0) with no noticeable improvement.
  
- I will be trying the Realtek (from their website) and
- https://github.com/FreedomBen/rtl8188ce-linux-driver next.
+ I will be trying the Realtek (from their website) - didn't work, not for this 
kernel.
+ https://github.com/FreedomBen/rtl8188ce-linux-driver - didn't help.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a toshiba c55d laptop. I've seen this issue since trusty, very
  bad packet loss,varrying in ping from 10%-45% to  Verizon MI424WR-
  GEN3I AP with WPA2 running in Compatibility Mode(802.11b/g/n). No
  other devices on network have ever had this issue, in fact any loss of
  ICMP packets almost never occurs on other devices from same location.

  Already tried mainline (3.18.0) with no noticeable improvement.

  I will be trying the Realtek (from their website) - didn't work, not for this 
kernel.
  https://github.com/FreedomBen/rtl8188ce-linux-driver - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset 

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

So far I've tried:

sudo modprobe rtl8188ee debug=3 swenc=1 ips=0 fwlps=0 disable_watchdog=1
also tried with msi= 0.

tried compat-wireless, 3.19-rc4,

my new test that I'm using is a ping router -i 0.2 -c 100.   I run it at
least 3 times, generally it has 1-7% packet loss.

I've switched routers, I'm not using a Buffalo WZR-300HP running DD-WRT.
Nothing changed, with laptop next to router I still get packet loss.

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a toshiba c55d laptop. I've seen this issue since trusty, very
  bad packet loss,varrying in ping from 10%-45% to  Verizon MI424WR-
  GEN3I AP with WPA2 running in Compatibility Mode(802.11b/g/n). No
  other devices on network have ever had this issue, in fact any loss of
  ICMP packets almost never occurs on other devices from same location.

  Already tried mainline (3.18.0) with no noticeable improvement.

  I will be trying the Realtek (from their website) - didn't work, not for this 
kernel.
  https://github.com/FreedomBen/rtl8188ce-linux-driver - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

Email sent to linux wireless mailing list.

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a toshiba c55d laptop. I've seen this issue since trusty, very
  bad packet loss,varrying in ping from 10%-45% to  Verizon MI424WR-
  GEN3I AP with WPA2 running in Compatibility Mode(802.11b/g/n). No
  other devices on network have ever had this issue, in fact any loss of
  ICMP packets almost never occurs on other devices from same location.

  Already tried mainline (3.18.0) with no noticeable improvement.

  I will be trying the Realtek (from their website) - didn't work, not for this 
kernel.
  https://github.com/FreedomBen/rtl8188ce-linux-driver - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a toshiba c55d laptop. I've seen this issue since trusty, very
  bad packet loss,varrying in ping from 10%-45% to  Verizon MI424WR-
  GEN3I AP with WPA2 running in Compatibility Mode(802.11b/g/n). No
  other devices on network have ever had this issue, in fact any loss of
  ICMP packets almost never occurs on other devices from same location.

  Already tried mainline (3.18.0) with no noticeable improvement.

  I will be trying the Realtek (from their website) - didn't work, not for this 
kernel.
  https://github.com/FreedomBen/rtl8188ce-linux-driver - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1431560] Re: kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!

[Bryan Quigley]

I was doing mount-image-callback at the time to be more specific.

I have no way to reproduce it despite trying the above command a bunch.

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

Title:
  kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not sure what caused this exactly.   Was doing a package update and
  testing out cloud utils.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-8-generic 3.19.0-8.8
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  2265 F pulseaudio
   /dev/snd/controlC2:  bryan  2265 F pulseaudio
   /dev/snd/controlC0:  bryan  2265 F pulseaudio
  Date: Thu Mar 12 16:47:52 2015
  Failure: oops
  InstallationDate: Installed on 2015-01-08 (62 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-8-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RfKill:
   
  SourcePackage: linux
  Title: kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1431560] [NEW] kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!

[Bryan Quigley]

Public bug reported:

Not sure what caused this exactly.   Was doing a package update and
testing out cloud utils.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-8-generic 3.19.0-8.8
ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
Uname: Linux 3.19.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
Annotation: Your system might become unstablenow and might need to be restarted.
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  bryan  2265 F pulseaudio
 /dev/snd/controlC2:  bryan  2265 F pulseaudio
 /dev/snd/controlC0:  bryan  2265 F pulseaudio
Date: Thu Mar 12 16:47:52 2015
Failure: oops
InstallationDate: Installed on 2015-01-08 (62 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
MachineType: BIOSTAR Group TA890GXE
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-8-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RfKill:
 
SourcePackage: linux
Title: kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: TA890GXE
dmi.board.vendor: BIOSTAR Group
dmi.chassis.asset.tag: None
dmi.chassis.type: 3
dmi.chassis.vendor: BIOSTAR Group
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
dmi.product.name: TA890GXE
dmi.sys.vendor: BIOSTAR Group

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


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

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

Title:
  kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not sure what caused this exactly.   Was doing a package update and
  testing out cloud utils.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-8-generic 3.19.0-8.8
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  2265 F pulseaudio
   /dev/snd/controlC2:  bryan  2265 F pulseaudio
   /dev/snd/controlC0:  bryan  2265 F pulseaudio
  Date: Thu Mar 12 16:47:52 2015
  Failure: oops
  InstallationDate: Installed on 2015-01-08 (62 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-8-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RfKill:
   
  SourcePackage: linux
  Title: kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1424727] Re: NFS access not revoked on kdestroy

[Bryan Quigley]

Just tested with v4.0-rc1, it's still there.

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

Title:
  NFS access not revoked on kdestroy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 14.04
  2) 3.13 kernel or mainline kernel 3.19.
  krb5-user [1.12+dfsg-2ubuntu5.1]
  nfs-common [1:1.2.8-6ubuntu1]
  3) What should happen:
  Start as unpriviledged (in a kerberos sense) user with access to a kerberos 
protected NFS share (in this case it contains home directories)
  kinit user1
  ls ~user1 #Test user1 permissions, this should always succeed (and does)

  kdestroy #should destroy user1 permissions

  kinit user2
  ls ~user2# this should succeed!
  ls ~user1# this should fail!

  4) What happened instead:
  After kinit user2:
  ls ~user2# this FAILS
  ls ~user1# this still WORKS

  This appears to be known upstream:
  http://www.citi.umich.edu/projects/nfsv4/linux/faq/#krb5_006

  Bits and pieces of an earlier attempt at a fix:
  http://www.spinics.net/lists/linux-nfs/msg34236.html
  nfslogin/logout prototype 
http://www.citi.umich.edu/projects/asci/icsi-alpha/nfs-utils-patches/1.0.10-asci-2/nfs-utils-1.0.10-asci-017-add_nfslogin.dif

  Another bug request: https://fedorahosted.org/gss-proxy/ticket/1  (and
  linked discussion)

  Workarounds:
  Unmount/Mount NFS share

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

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

[Kernel-packages] [Bug 1424727] Re: NFS access not revoked on kdestroy

[Bryan Quigley]

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

** Also affects: linux via
   http://bugzilla.kernel.org/show_bug.cgi?id=93891
   Importance: Unknown
   Status: Unknown

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

Title:
  NFS access not revoked on kdestroy

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 14.04
  2) 3.13 kernel or mainline kernel 3.19.
  krb5-user [1.12+dfsg-2ubuntu5.1]
  nfs-common [1:1.2.8-6ubuntu1]
  3) What should happen:
  Start as unpriviledged (in a kerberos sense) user with access to a kerberos 
protected NFS share (in this case it contains home directories)
  kinit user1
  ls ~user1 #Test user1 permissions, this should always succeed (and does)

  kdestroy #should destroy user1 permissions

  kinit user2
  ls ~user2# this should succeed!
  ls ~user1# this should fail!

  4) What happened instead:
  After kinit user2:
  ls ~user2# this FAILS
  ls ~user1# this still WORKS

  This appears to be known upstream:
  http://www.citi.umich.edu/projects/nfsv4/linux/faq/#krb5_006

  Bits and pieces of an earlier attempt at a fix:
  http://www.spinics.net/lists/linux-nfs/msg34236.html
  nfslogin/logout prototype 
http://www.citi.umich.edu/projects/asci/icsi-alpha/nfs-utils-patches/1.0.10-asci-2/nfs-utils-1.0.10-asci-017-add_nfslogin.dif

  Another bug request: https://fedorahosted.org/gss-proxy/ticket/1  (and
  linked discussion)

  Workarounds:
  Unmount/Mount NFS share

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

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

[Kernel-packages] [Bug 1446464] Re: System fails to boot stuck on Scanning for btrfs

[Bryan Quigley]

apport information

** Tags added: apport-collected vivid

** Description changed:

  Ubuntu 15.04 with 3.19.0-15-generic.
  
  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)
  
  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details
  
- Story of getting here:  Was playing Team Fortress 2 and Internet went
- down.   Trying to get network-manager to reload caused some issues.
- Eventually decided to reboot.  Hung at reboot and ended up powering down
- by switch.
+ Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
+ --- 
+ ApportVersion: 2.17.2-0ubuntu1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  bryan  1626 F pulseaudio
+  /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
+  /dev/snd/controlC0:  bryan  1626 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 15.04
+ InstallationDate: Installed on 2015-01-08 (102 days ago)
+ InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
+ MachineType: BIOSTAR Group TA890GXE
+ NonfreeKernelModules: nvidia_uvm nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
+ ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
+ RelatedPackageVersions:
+  linux-restricted-modules-3.19.0-15-generic N/A
+  linux-backports-modules-3.19.0-15-generic  N/A
+  linux-firmware 1.143
+ RfKill:
+  
+ Tags:  vivid
+ Uname: Linux 3.19.0-15-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 05/30/2011
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 080015
+ dmi.board.asset.tag: To Be Filled By O.E.M.
+ dmi.board.name: TA890GXE
+ dmi.board.vendor: BIOSTAR Group
+ dmi.chassis.asset.tag: None
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: BIOSTAR Group
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
+ dmi.product.name: TA890GXE
+ dmi.sys.vendor: BIOSTAR Group

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1446464/+attachment/4380314/+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/1446464

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1446464] Re: System fails to boot stuck on Scanning for btrfs

[Bryan Quigley]

** Attachment added: Call trace
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1446464/+attachment/4380312/+files/2015-04-21_01-00-19_587.jpg

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

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went
  down.   Trying to get network-manager to reload caused some issues.
  Eventually decided to reboot.  Hung at reboot and ended up powering
  down by switch.

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

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

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

[Bryan Quigley]

apport information

** Attachment added: JournalErrors.txt
   
https://bugs.launchpad.net/bugs/1446464/+attachment/4380318/+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/1446464

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1446464] UdevLog.txt

[Bryan Quigley]

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1446464/+attachment/4380327/+files/UdevLog.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/1446464

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1446464/+attachment/4380315/+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/1446464

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

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

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

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

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1446464/+attachment/4380320/+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/1446464

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1446464/+attachment/4380322/+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/1446464

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

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

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

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

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1446464] Re: System fails to boot stuck on Scanning for btrfs

[Bryan Quigley]

All I had to do to recover it was to boot up with a Ubuntu 14.04.2
livecd and mount the drive (I gathered logs looking to debug further).
Upon rebooting it seems to be working again.

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

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1446464/+attachment/4380324/+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/1446464

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1446464/+attachment/4380317/+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/1446464

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

** Attachment added: PulseList.txt
   
https://bugs.launchpad.net/bugs/1446464/+attachment/4380325/+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/1446464

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1446464/+attachment/4380328/+files/WifiSyslog.txt

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

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

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

[Bryan Quigley]

apport information

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

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went down.   
Trying to get network-manager to reload caused some issues.  Eventually decided 
to reboot.  Hung at reboot and ended up powering down by switch.
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  1626 F pulseaudio
   /dev/snd/pcmC0D0p:   bryan  1626 F...m pulseaudio
   /dev/snd/controlC0:  bryan  1626 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-01-08 (102 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  NonfreeKernelModules: nvidia_uvm nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-15-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1446464] [NEW] System fails to boot stuck on Scanning for btrfs

[Bryan Quigley]

Public bug reported:

Ubuntu 15.04 with 3.19.0-15-generic.

Current status:
System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
INFO: task exe:208 blocked for more than 120 seconds

INFO: task btrfs-transacti:230 blocked for more than 120 seconds
(message repeats every 2 minutes)

Ctrl-alt-delete does work to reboot system at this stage.
Booting with upstart still hangs.
Recovery mode fails to boot as well
Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

Story of getting here:  Was playing Team Fortress 2 and Internet went
down.   Trying to get network-manager to reload caused some issues.
Eventually decided to reboot.  Hung at reboot and ended up powering down
by switch.

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

** Attachment added: 2015-04-21_00-28-56_871.jpg
   
https://bugs.launchpad.net/bugs/1446464/+attachment/4380311/+files/2015-04-21_00-28-56_871.jpg

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

Title:
  System fails to boot stuck on Scanning for btrfs

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 with 3.19.0-15-generic.

  Current status:
  System fails to finish booting with Scanning for btrfs.  If you wait long 
enough you see:
  INFO: task exe:208 blocked for more than 120 seconds
  
  INFO: task btrfs-transacti:230 blocked for more than 120 seconds
  (message repeats every 2 minutes)

  Ctrl-alt-delete does work to reboot system at this stage.
  Booting with upstart still hangs.
  Recovery mode fails to boot as well
  Tried options system.debug-shell (from 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1444070) which got me a 
few more details

  Story of getting here:  Was playing Team Fortress 2 and Internet went
  down.   Trying to get network-manager to reload caused some issues.
  Eventually decided to reboot.  Hung at reboot and ended up powering
  down by switch.

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

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

[Kernel-packages] [Bug 1311834] Re: adds crashkernel line during install, but doesn't remove it when it's purged

[Bryan Quigley]

Still true in 15.04.

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

Title:
  adds crashkernel line during install, but doesn't remove it when it's
  purged

Status in kexec-tools package in Ubuntu:
  New

Bug description:
  1) Ubuntu 14.04. 
  2) kexec-tools (1:2.0.6-0ubuntu2) 
  3) I expect that when removing kexec-tools it removed the crashkernel line 
that it added
  4) It doesn't get removed (tried both remove and purge)because kexec-tools 
doesn't call update-grub

  A workaround is just to manually do an update-grub.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1311834/+subscriptions

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

Thanks for the bisect results! We can confirm that this fixes the issue by 
manually specifying the max_sectors_kb and seeing if that fixes the issue.
1.  Boot the server installation and stop at the partitioning screen (this way 
we make sure it has detected everything)
2.  Switch to another VT (Ctrl-Alt-F2) 
3.  Confirm and post the values of cat /sys/block/xxx/queue/max_sectors_kb and 
max_hw_sectors_kb (where xxx is the block device for the Avago controller)
4.  Execute - echo 1024  /sys/block/vda/queue/max_sectors_kb
5.  Confirm it was really changed with cat
6.  Proceed with the installation

Now, if you want to use this as a more permanent workaround you need to
specify the 1024 value in sysfs on the installed system as well.  Once
confirmed, we would want to get from Avago (or at least some manual
testing) what the real hw maximum of this value should be and add it the
driver (as described in the commit message).

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

It would be worth trying 4.1 as well built from source as that should
match the other kernel test above.  Small fixes do make it after the
release and that should rule that out.

The most likely possibility that I see is that it is an Ubuntu specific kernel 
config change.
It could also be compiler differences between 14.10 and 15.04 - or some other 
Ubuntu kernel packaging change.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

You can also try building 3.19 with the config from Ubuntu - see the
bottom of GitKernelBuild for more.  Alternatively you could grab the
config from a 15.04 using step 4 in GitKernelBuild.

[1] http://kernel.ubuntu.com/git/ubuntu/ubuntu-
vivid.git/tree/debian.master/config

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

Sorry, I forgot that was also in C#17.   I just wanted to minimize the
chance the kernel build/git operations would be affected by the IO
issues.  Sticking with 14.10 for the bisection is perfect.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

Sorry I misunderstood, I'm guessing if you go back to v3.16 it would be
fine?  Perhaps something about the build is wrong at the checkout
preventing that.

There are two ways to try proceeding:
git bisect skip (trys to pick another commit) and see if it builds PPC64LE
checkout v3.18 or 3.17 and see if you can get a PPC64LE to test from them

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

Hi Adi,

I would go ahead and proceed with a bisect.  The first step would be to
test if you can build[1] the 14.10 (git checkout v3.16) kernel and it
boots fine.

Then confirm the failure of 3.19 before proceeding to a normal bisect
[1].

Which if everything above is expected, would be git bisect start v3.19
v3.16

Kind regards,
Bryan

[1] 
https://wiki.ubuntu.com/KernelTeam/GitKernelBuild#Kernel_Build_and_Installation
[2] https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html

** Tags added: sts

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

** Changed in: linux (Ubuntu)
 Assignee: Chris J Arges (arges) = Bryan Quigley (bryanquigley)

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

1)  I would at least try booting multiple times.
If possible I would try partitioning so you have extra space and can set up a 
new ext4 partition on the Controller for every test.  Then deleting before 
running the next one.

In fact, I'd recommend for the next test to install 15.04 on a SATA
drive in the system and see if you can reproduce with the controller
just doing the above.  Try reproducing it at least 3 times to be sure it
freezes every time.

Then if you do another Git Kernel build (v3.19) it will use 15.04s
config by default (as well as the new compiler).  This would help rule
out it being an Ubuntu specific patch (or prove that it is).   Please do
post the 14.10 config from your GitKernelBuild so we can see the full
working config you used.

 2) There is no specific raid or ext4 change that I've been able to find
so if we can narrow it more that would help.

Another useful data point would be to try a wily development image (will
be 15.10) - http://cdimage.ubuntu.com/ubuntu-server/daily/current/.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

The machine has been running on an external wifi card for a while, and
it's working fine.   I've swapped out the RTL8188ee card for an Atheros
(mini pci) and this should let us see if it's really RTL8188ee to blame
or not (or a antenna, location issue).

I did complete a series of wireshark tests and determined packets are only lost 
on the receive side.   
I did ping -i 0.05 -c 1000 -s 512 to and from the machine in question, (to a 
machine 1 foot away).  Over 4 runs (2 from, 2 to), 2-9 packets were lost, ALL 
when going - RTL8188ee.  No packets were ever lost sending from RTL8188ee to 
other machine.

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a toshiba c55d laptop. I've seen this issue since trusty, very
  bad packet loss,varrying in ping from 10%-45% to  Verizon MI424WR-
  GEN3I AP with WPA2 running in Compatibility Mode(802.11b/g/n). No
  other devices on network have ever had this issue, in fact any loss of
  ICMP packets almost never occurs on other devices from same location.

  Already tried mainline (3.18.0) with no noticeable improvement.

  I will be trying the Realtek (from their website) - didn't work, not for this 
kernel.
  https://github.com/FreedomBen/rtl8188ce-linux-driver - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

1) I would definitely recommend booting up/checking the logs multiple times on 
every leg of the test to ensure that it gets a consistent result.   
2) I don't understand how this would have happened.  It does occur to me that 
if we're dealing with possible IO corruption there could be other issues too, 
I'd suggest:
If you can reproduce without having the OS or Kernel code on the Avago 
controller that would be the best option. (like I described in C#17)
If not, reboot back to the stable v3.16 kernel before doing any git or build 
commands.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

My next plan is to setup a packet dump on both a router (or laptop) and
the laptop with the issue (RTL8188ee) and see if the packets are being
dropped more on the send or receive side.  It might be a while, so if
anyone wants to get to it first :).

EMail to list: http://www.spinics.net/lists/linux-
wireless/msg132005.html,  RTL8188ee works fine for the maintainer.

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a toshiba c55d laptop. I've seen this issue since trusty, very
  bad packet loss,varrying in ping from 10%-45% to  Verizon MI424WR-
  GEN3I AP with WPA2 running in Compatibility Mode(802.11b/g/n). No
  other devices on network have ever had this issue, in fact any loss of
  ICMP packets almost never occurs on other devices from same location.

  Already tried mainline (3.18.0) with no noticeable improvement.

  I will be trying the Realtek (from their website) - didn't work, not for this 
kernel.
  https://github.com/FreedomBen/rtl8188ce-linux-driver - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

All that patch appears to do is to remove an artificial limit for all
devices to 1024.   I haven't been able to reproduce the option reset on
my systems, so here is what I would try:

Try setting the controller option and see if that sticks [1]: 
rmmod megaraid_sas
modprobe megaraid_sas max_sectors=2048

It may also be possible to do this while booting as a kernel command option 
like: megaraid_sas.max_sectors=2048
(2048 does actually mean 1024 for the other options).

Otherwise, I'd recommend switching to a Live CD and see if the option
works there.

If not, a last option would be to try using sysfs on the livecd to see if that 
will help ensure it:
sudo add-apt-repository universe
sudo apt update
edit /etc/sysfs.ctl adding block/xxx/queue/max_sectors_kb = 1024
sudo apt install sysfsutils
sudo service sysfsutils restart

[1] http://fendertech.blogspot.com/2013/04/how-to-increase-maxsectorskb-
for.html

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

Hi Adi,

I see the patch got posted here - https://www.spinics.net/lists/linux-
scsi/msg89336.html and it has been reviewed.

I'm guessing it will be part of a scsi pull request in the recently
opened 4.4 merge window.  That looks imminent.  Depending on when it
lands, the Ubuntu kernel update cycle takes about a month.

Kind regards,
Bryan

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

Yes it would only be for one boot, to use that as a workaround you want
to add it permanently to GRUB_CMDLINE_LINUX_DEFAULT in
/etc/default/grub.  Then run sudo update-grub.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

Hi Adi,

Just to confirm my understanding of this bug, did doing so change the
value of max_sectors_kb / max_hw_sectors_kb?  I don't believe it would
have survived the reboot after the install, but you could try adding it
to the kernel command line of the installed system and see.

Bryan

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

@kashyap-desai thanks for checking.  AFAICT it's been at 1024 for at
least the 14.04 release as well.

Thanks for noting what FW status 0x3 means, that will help any future
tests we do.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

@kashyap-desai thanks for that, it could be a simple firmware reporting issue 
or the kernel code needs to be updated to handle a new case.
megaraid_sas_base.c [1] mentions that it generates the max_sectors limits from 
data provided from the firmware.
4096 is defined in a few other places within the driver [2] so I'm guessing 
other megaraids do support 4096?

Testing on non-powerpc would still be useful as would reverting to a
released firmware to see if max_sectors changes or the error changes.

[1] /*
 * Compute the max allowed sectors per IO: The controller info has two
 * limits on max sectors. Driver should use the minimum of these two.
 *
 * 1 << stripe_sz_ops.min = max sectors per strip
 *
 * Note that older firmwares ( < FW ver 30) didn't report information
 * to calculate max_sectors_1. So the number ended up as zero always.
 */
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid/megaraid_sas_base.c
[2] 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/megaraid.h

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

So assuming the the value max_sectors_kb is changed to 1024 (with the
2048 kernel command line) that means we need to figure out what the
correct value is for the Avago controller.  Currently it's set as 4096
in the kernel according to C#28.  It appears 1024 works, but if we get
the actual value that's better for performance.

What is the actual hardware limitation of the Avago controller?
If the limit is really 4096 that would imply that it's just broken on PPC64LE 
which could be another driver or a firmware bug that was only revealed when the 
default limit was changed from 1024.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

@kashyap
>Current Driver count max_sectors based on PAGE_SIZE. This is wrong. We will 
>fix and send patch to upstream.
Thanks for the analysis and working upstream.   Post here when it lands and I 
can see about getting it back to 15.04/15.10.  

Just for clarify workaround of anyone reading:
megaraid_sas.max_sectors=512  (for released 256k compatible firmware)
megaraid_sas.max_sectors=2048 (for unreleased 1024k compatible firmware)

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1431560] Re: kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!

[Bryan Quigley]

One time event and no evidence of it happening again on 4.2 kernel.

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

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

Title:
  kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Not sure what caused this exactly.   Was doing a package update and
  testing out cloud utils.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-8-generic 3.19.0-8.8
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bryan  2265 F pulseaudio
   /dev/snd/controlC2:  bryan  2265 F pulseaudio
   /dev/snd/controlC0:  bryan  2265 F pulseaudio
  Date: Thu Mar 12 16:47:52 2015
  Failure: oops
  InstallationDate: Installed on 2015-01-08 (62 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108)
  MachineType: BIOSTAR Group TA890GXE
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-8-generic 
root=UUID=1bd032ea-0757-4aee-82d4-bbee08fd0eb8 ro rootflags=subvol=@ quiet 
splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RfKill:
   
  SourcePackage: linux
  Title: kernel BUG at /build/buildd/linux-3.19.0/fs/buffer.c:3006!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: TA890GXE
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: TA890GXE
  dmi.sys.vendor: BIOSTAR Group

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

Oops.. .Nvm I forgot that this won't be an issue until after commit
34b48db, regardless of the same code being in the kernel.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

@kashyap-desai
I was just looking at cherrypicking this fix to 15.10, but then realized I 
don't see why this wouldn't affect 12.04 or 14.04 as well.   Does this affect 
all supported Ubuntu releases?

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1163587] Re: mtrr_cleanup: can not find optimal value, perhaps no longer needed?

[Bryan Quigley]

It seems MTRR support is being deprecated now -
http://lkml.iu.edu/hypermail/linux/kernel/1508.3/04830.html, commit
2baa891e42d84159b693eadd44f6fe1486285bdc.

Perhaps disabling MTRR (as opposed to just mtrr_cleanup) might be
considered for xenial?  I believe it may affect boot time when the
cleanup is ran.

** Tags removed: raring
** Tags added: xenial

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

Title:
  mtrr_cleanup: can not find optimal value, perhaps no longer needed?

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The actual common error message from dmesg:

  [0.00] original variable MTRRs
  [0.00] reg 0, base: 0GB, range: 32GB, type WB
  [0.00] reg 1, base: 3584MB, range: 512MB, type UC
  [0.00] reg 2, base: 3548MB, range: 4MB, type UC
  [0.00] reg 3, base: 3552MB, range: 32MB, type UC
  [0.00] total RAM covered: 32220M
  [0.00]  gran_size: 64K  chunk_size: 64K num_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 128Knum_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 256Knum_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 512Knum_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 1M  num_reg: 7  lose cover 
RAM: 28676M
  ...
  [0.00]  gran_size: 256M chunk_size: 2G  num_reg: 6  lose 
cover RAM: 220M
  [0.00]  gran_size: 512M chunk_size: 512Mnum_reg: 5
  lose cover RAM: 476M
  [0.00]  gran_size: 512M chunk_size: 1G  num_reg: 5  lose 
cover RAM: 476M
  [0.00]  gran_size: 512M chunk_size: 2G  num_reg: 5  lose 
cover RAM: 476M
  [0.00]  gran_size: 1G   chunk_size: 1G  num_reg: 5  lose cover 
RAM: 476M
  [0.00]  gran_size: 1G   chunk_size: 2G  num_reg: 5  lose cover 
RAM: 476M
  [0.00]  gran_size: 2G   chunk_size: 2G  num_reg: 4  lose cover 
RAM: 1500M
  [0.00] mtrr_cleanup: can not find optimal value
  [0.00] please specify mtrr_gran_size/mtrr_chunk_size

  I have found errors like this on many machines (one with 128 GB of
  RAM, mine with just 4GB).   The instructions want you to specify
  kernel options that you don't need to do.  Just turning off
  mtrr_cleanup appears to be the best option.  You can fix it be
  specifying disable_mtrr_cleanup.

  According to kernel paramaters
  (https://www.kernel.org/doc/Documentation/kernel-parameters.txt)

disable_mtrr_cleanup [X86]
The kernel tries to adjust MTRR layout from continuous
to discrete, to make X server driver able to add WB
entry later. This parameter disables that.

  From this I understand it was here to help allow leave the X server
  space if it needed it in the future.  That should no longer be
  necessary, correct?   I have an Intel GPU and noticed no performance
  problems by disabling it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-16-generic 3.8.0-16.26
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  1978 F pulseaudio
  Date: Tue Apr  2 16:56:13 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-04 (56 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130204.1)
  MachineType: Dell Inc. Inspiron 1545
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic 
root=UUID=0983e077-6f15-4e52-a776-faa186229dc8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-16-generic N/A
   linux-backports-modules-3.8.0-16-generic  N/A
   linux-firmware1.104
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1508706] Re: Networking hangs on azure using hv_netvsc; bisected

[Bryan Quigley]

Got another confirmation that the patch (first one) 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/1508706

Title:
  Networking hangs on azure using hv_netvsc; bisected

Status in linux package in Ubuntu:
  Triaged

Bug description:
  
  Running Ubuntu instances on azure, testing basic networking between two 
instances.  This involves configuring VXLAN between the two instances and 
running iperf and rsync of the kernel tree between the instances, e.g.,

  ip link add vxlan0 type vxlan id 999 local 10.88.0.12 remote 10.88.0.11 dev 
eth0
  ip l set vxlan0 up
  ip addr add 242.0.0.12/8 dev vxlan0

  After some time (sometimes instantly, sometimes up to 30 minutes of
  activity), the networking will hang.  This hang takes two forms:  a
  complete loss of connectivity (all network, even the ssh session used
  to log in), or just a loss of connectivity between instances (the ssh
  session remains active).  Sometimes for the latter case, the ssh
  session will then later hang.

  This first appeared when testing with the Ubuntu 3.19 kernel, and I
  subsequently bisected this to:

  commit effa2012d207f78cbc5a8360e62d420a8860b7e9
  Author: KY Srinivasan 
  Date:   Mon May 11 15:39:46 2015 -0700

  hv_netvsc: Use the xmit_more skb flag to optimize signaling the
  host

  BugLink: http://bugs.launchpad.net/bugs/1454892

  Based on the information given to this driver (via the xmit_more skb 
flag),
  we can defer signaling the host if more packets are on the way. This will 
help
  make the host more efficient since it can potentially process a larger 
batch of
  packets. Implement this optimization.

  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: David S. Miller 
  Acked-by: Tim Gardner 
  Acked-by: Brad Figg 
  Signed-off-by: Brad Figg 

  I also tested the mainline kernel (net-next); it fails with the
  equivalent commit:

  commit 82fa3c776e5abba7ed6e4b4f4983d14731c37d6a
  Author: KY Srinivasan 
  Date:   Mon May 11 15:39:46 2015 -0700

  hv_netvsc: Use the xmit_more skb flag to optimize signaling the
  host

  For both kernel trees, I also tested the prior commit and it did not
  exhibit the failure after many hours.  For ubuntu, this was

  commit a4aeb290bd75af5e16a6144a418291476ac6140c
  Author: K. Y. Srinivasan 
  Date:   Wed Mar 18 12:29:29 2015 -0700

  Drivers: hv: vmbus: Export the vmbus_sendpacket_pagebuffer_ctl()

  and for mainline it was

  commit 9eea92226407e7a117ef1ceef45380ebd000a0e2
  Author: Alexei Starovoitov 
  Date:   Mon May 11 15:19:48 2015 -0700

  pktgen: fix packet generation

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

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

[Kernel-packages] [Bug 1475166] Re: Ubuntu 15.04 Install Error with Avago Controller

[Bryan Quigley]

It's landed in linus' tree as commit
357ae967ad66e357f78b5cfb5ab6ca07fb4a7758.

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

Title:
  Ubuntu 15.04 Install Error with Avago Controller

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello Canonical Team

  We are running to an issue installing ubuntu PPC64LE 15.04 full blown
  image on our servers  (with RAID controller).  Installation hangs
  around 70% of progress.

  An important part of our configuration is Avago RAID controller:
  9361-8i Firmware version we used is 4.300.00-4429, and the package is
  24.10.0-0002.

  IMPORTANT: It has to be noted that with same hardware configuration
  14.10 full blown image installs fine.

  Dmesg logs are attached:

  Looking at dmesg logs point out that:
  LSI (avago) driver loads fine
  During further interaction with raid volume during the installation process, 
firmware errors are seen 
  [  196.991417] megasas: FW status 0x3

  [  196.999376] megasas: FW status 0x3

  [  197.007376] megasas: FW status 0x3
  Further down the  process I/O errors are thrown
  [  217.438664] Buffer I/O error on device sda2, logical block 22052864

  [  217.438671] Buffer I/O error on device sda2, logical block 22052865

  [  217.438678] Buffer I/O error on device sda2, logical block 22052866

  [  217.438686] Buffer I/O error on device sda2, logical block 22052867

  Full dmesg log is attached. Snippet is pasted below highlighting:

  It can be noted that there’s a Mellanox Connectx 3 pro card with some test 
Firmware on our setup. 
  We can Ignore any diagnostic messages from that card in dmesg logs for the 
purpose of this bug. 

  Thanks
  Adi Gangidi

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

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

[Kernel-packages] [Bug 1311834] Re: adds crashkernel line during install, but doesn't remove it when it's purged

[Bryan Quigley]

This was fixed at least in 16.10 (and likely in 16.04 as well).
(kexec-tools no longer makes the change by default).

** Changed in: kexec-tools (Ubuntu)
   Status: New => Fix Released

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

Title:
  adds crashkernel line during install, but doesn't remove it when it's
  purged

Status in kexec-tools package in Ubuntu:
  Fix Released

Bug description:
  1) Ubuntu 14.04. 
  2) kexec-tools (1:2.0.6-0ubuntu2) 
  3) I expect that when removing kexec-tools it removed the crashkernel line 
that it added
  4) It doesn't get removed (tried both remove and purge)because kexec-tools 
doesn't call update-grub

  A workaround is just to manually do an update-grub.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1311834/+subscriptions

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

[Kernel-packages] [Bug 1401741] Re: rtl8188ee wireless driver high packet loss

[Bryan Quigley]

Does anyone still have this issue or should I close this?

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

Title:
   rtl8188ee wireless driver high packet loss

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is a toshiba c55d laptop. I've seen this issue since trusty, very
  bad packet loss,varrying in ping from 10%-45% to  Verizon MI424WR-
  GEN3I AP with WPA2 running in Compatibility Mode(802.11b/g/n). No
  other devices on network have ever had this issue, in fact any loss of
  ICMP packets almost never occurs on other devices from same location.

  Already tried mainline (3.18.0) with no noticeable improvement.

  I will be trying the Realtek (from their website) - didn't work, not for this 
kernel.
  https://github.com/FreedomBen/rtl8188ce-linux-driver - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-28-generic 3.16.0-28.37
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  erica  2366 F pulseaudio
   /dev/snd/controlC0:  erica  2366 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:01:36 2014
  HibernationDevice: RESUME=UUID=47ff810c-172e-4cd8-b7b3-12f03d42cf70
  InstallationDate: Installed on 2014-05-29 (196 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite C55D-A
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed 
root=UUID=3c0c45ee-7e15-45e4-988c-339d83805035 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.138
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (70 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.70:bd12/25/2013:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-04C031:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-04C031
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1533043] Re: AUFS can hang up; Please update to v20160111

[Bryan Quigley]

@mkostrikin
That provides another confirmation like from comment #17 about the 4.2.0 
kernel/wily.

We could still use testing for:
3.13.0-78 (on trusty - Non-HWE)
3.16.0-61 (on trusty - utopic-HWE -  linux-image-generic-lts-utopic)
3.19.0-50 (on trusty - vivid-HWE - linux-image-generic-lts-vivid)

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

Title:
  AUFS can hang up; Please update to v20160111

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Committed
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Fix Committed
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux source package in Xenial:
  In Progress
Status in linux-lts-utopic source package in Xenial:
  Invalid

Bug description:
  AUFS  can hang up (more precisely, produces unkillable processes) with some 
kernels that contain the commit 296291cdd1629c308114504b850dc343eabc278.
  - 14.04LTS:  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=b8702f3cf9c06914476fb3206039131c2c3d8450
  - 15.04: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/commit/?id=6b08592b8acc677d5b9bb7986343fdd6e0ad3303
  - 15.10: 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-wily.git/commit/?id=4d291df30fb7a94d13c6d38addf8d85d38f0111b

  Many docker users have been experiencing this issue:
  https://github.com/docker/docker/issues/18180

  
  The issue has been fixed since AUFS v20160111: 
http://permalink.gmane.org/gmane.linux.file-systems.aufs.user/5345
  So I suggest updating AUFS to v20160111.

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

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

[Kernel-packages] [Bug 378975] Re: Huawei E220 can't connect on Ubuntu 9.04, after estabilish connection under Windows XP

[Bryan Quigley]

This bug was marked Incomplete some time ago and was supposed to
autoclose after 90 days.  I'm going to close it manually due to no
activity (and likely the issue has gone away/been fixed).

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Huawei E220 can't connect on Ubuntu 9.04, after estabilish connection
  under Windows XP

Status in Linux:
  Expired
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: network-manager

  I have motherboard Asus A8V-VM and Huawei E220 USB modem.

  I use both Ubuntu 9.04 Jaunty and WIndows XP.

  When I run Windows XP and establish connection (Polish operator PLAY), 
  and next I restart Windows XP system and run Ubuntu 9.04 Jaunty, the Huawei 
E220 modem can't connect to the network.

  Only when I turn off computer, and run Ubuntu again or I switch the
  USB connection, then it starts working.

  The Windows XP alway connect properly to the network.

  [lsusb]
  Bus 002 Device 002: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA 
Modem / E270 HSDPA/HSUPA Modem

  [uname -a]
  Linux a-desktop 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:27:06 UTC 2009 
i686 GNU/Linux

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

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

[Kernel-packages] [Bug 1163587] Re: mtrr_cleanup: can not find optimal value, perhaps no longer needed?

[Bryan Quigley]

My testing could not find any difference in boot time using systemd's
tools.

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

Title:
  mtrr_cleanup: can not find optimal value, perhaps no longer needed?

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The actual common error message from dmesg:

  [0.00] original variable MTRRs
  [0.00] reg 0, base: 0GB, range: 32GB, type WB
  [0.00] reg 1, base: 3584MB, range: 512MB, type UC
  [0.00] reg 2, base: 3548MB, range: 4MB, type UC
  [0.00] reg 3, base: 3552MB, range: 32MB, type UC
  [0.00] total RAM covered: 32220M
  [0.00]  gran_size: 64K  chunk_size: 64K num_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 128Knum_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 256Knum_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 512Knum_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 1M  num_reg: 7  lose cover 
RAM: 28676M
  ...
  [0.00]  gran_size: 256M chunk_size: 2G  num_reg: 6  lose 
cover RAM: 220M
  [0.00]  gran_size: 512M chunk_size: 512Mnum_reg: 5
  lose cover RAM: 476M
  [0.00]  gran_size: 512M chunk_size: 1G  num_reg: 5  lose 
cover RAM: 476M
  [0.00]  gran_size: 512M chunk_size: 2G  num_reg: 5  lose 
cover RAM: 476M
  [0.00]  gran_size: 1G   chunk_size: 1G  num_reg: 5  lose cover 
RAM: 476M
  [0.00]  gran_size: 1G   chunk_size: 2G  num_reg: 5  lose cover 
RAM: 476M
  [0.00]  gran_size: 2G   chunk_size: 2G  num_reg: 4  lose cover 
RAM: 1500M
  [0.00] mtrr_cleanup: can not find optimal value
  [0.00] please specify mtrr_gran_size/mtrr_chunk_size

  I have found errors like this on many machines (one with 128 GB of
  RAM, mine with just 4GB).   The instructions want you to specify
  kernel options that you don't need to do.  Just turning off
  mtrr_cleanup appears to be the best option.  You can fix it be
  specifying disable_mtrr_cleanup.

  According to kernel paramaters
  (https://www.kernel.org/doc/Documentation/kernel-parameters.txt)

disable_mtrr_cleanup [X86]
The kernel tries to adjust MTRR layout from continuous
to discrete, to make X server driver able to add WB
entry later. This parameter disables that.

  From this I understand it was here to help allow leave the X server
  space if it needed it in the future.  That should no longer be
  necessary, correct?   I have an Intel GPU and noticed no performance
  problems by disabling it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-16-generic 3.8.0-16.26
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  1978 F pulseaudio
  Date: Tue Apr  2 16:56:13 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-04 (56 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130204.1)
  MachineType: Dell Inc. Inspiron 1545
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic 
root=UUID=0983e077-6f15-4e52-a776-faa186229dc8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-16-generic N/A
   linux-backports-modules-3.8.0-16-generic  N/A
   linux-firmware1.104
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1603719] Re: [regression] NFS client: access problems after updating to kernel 4.4.0-31-generic

[Bryan Quigley]

Thanks Seth.  That kernel fixes it for me.

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

Title:
  [regression] NFS client: access problems after updating to kernel
  4.4.0-31-generic

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

Bug description:
  I am denied access to the subfilesystems exported by my nfs server
  (the top level filesystem itself is unaffected).

  The client is reporting that I do not have the necessary permissions.
  However, all was fine until the day before yesterday.

  When I revert my client to 4.4.0-28, everything is in working order again. I 
assume the permission problem is really a bug in kernel 4.4.0-31.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jurgen 1743 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=569da237-3a37-4fe3-b885-83213aae8b52
  InstallationDate: Installed on 2016-04-07 (101 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6f6bd51-4d4f-4547-b615-90319625d909 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7514
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd05/28/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7514
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Kernel-packages] [Bug 1603719] Re: NFS client: access problems after updating to kernel 4.4.0-31-generic

[Bryan Quigley]

I also tried Upstream v4.4.15 (35467dc7630af60abacc330f64029d081f160530)
which does not have the issue.  Going to bisect shortly.

** Summary changed:

- NFS client: access problems after updating to kernel 4.4.0-31-generic
+ [regression] NFS client: access problems after updating to kernel 
4.4.0-31-generic

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

Title:
  [regression] NFS client: access problems after updating to kernel
  4.4.0-31-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am denied access to the subfilesystems exported by my nfs server
  (the top level filesystem itself is unaffected).

  The client is reporting that I do not have the necessary permissions.
  However, all was fine until the day before yesterday.

  When I revert my client to 4.4.0-28, everything is in working order again. I 
assume the permission problem is really a bug in kernel 4.4.0-31.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jurgen 1743 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=569da237-3a37-4fe3-b885-83213aae8b52
  InstallationDate: Installed on 2016-04-07 (101 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6f6bd51-4d4f-4547-b615-90319625d909 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7514
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd05/28/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7514
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Kernel-packages] [Bug 1603719] Re: [regression] NFS client: access problems after updating to kernel 4.4.0-31-generic

[Bryan Quigley]

Verified working with both -33 and -34 kernels

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

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

Title:
  [regression] NFS client: access problems after updating to kernel
  4.4.0-31-generic

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

Bug description:
  SRU Justification

  Impact: A regression in xenial causes automatic mounting of exported
  submounts of an nfs mount to fail.

  Fix: Change nfs to use sget_userns instead of sget, bypassing a
  capability check that is not necessary for nfs.

  Regression Potential: The behavior after the fix is functionally
  equivalent to upstream, so this is unlikely to cause regressions.

  ---

  I am denied access to the subfilesystems exported by my nfs server
  (the top level filesystem itself is unaffected).

  The client is reporting that I do not have the necessary permissions.
  However, all was fine until the day before yesterday.

  When I revert my client to 4.4.0-28, everything is in working order again. I 
assume the permission problem is really a bug in kernel 4.4.0-31.
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jurgen 1743 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=569da237-3a37-4fe3-b885-83213aae8b52
  InstallationDate: Installed on 2016-04-07 (101 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160405)
  IwConfig:
   lono wireless extensions.

   enp4s0no wireless extensions.
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7514
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f6f6bd51-4d4f-4547-b615-90319625d909 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/28/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7514
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd05/28/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7514:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7514:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7514
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Kernel-packages] [Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

[Bryan Quigley]

The fixes mentioned are also part of the 4.4.16 stable series, which will land 
in the next kernel cycle (August 29th ish). That should be 4.4.0-35 (or higher) 
in Ubuntu kernel versions.
See- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1607404

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

Title:
  divide error:  [#1] SMP in task_numa_migrate - handle_mm_fault

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

Bug description:
  While running qemu 2.5 on a trusty host running 4.4.0-15.31~14.04.1
  the host system has crashed (load > 200) 3 times in the last 3 days.

  Always with this stack trace:

  Apr  9 19:01:09 cnode9.0 kernel: [197071.195577] divide error:  [#1] SMP 
  Apr  9 19:01:09 cnode9.0 kernel: [197071.195633] Modules linked in: vhost_net 
vhost macvtap macvlan arc4 md4 nls_utf8 ci
  fs nfnetlink_queue nfnetlink xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 
xt_NFQUEUE xt_CLASSIFY ip6table_mangle sch_sfq sch_htb veth dccp_diag
   dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
ebtable_filter ebtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_fil
  ter ip6_tables iptable_mangle xt_CT iptable_raw xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack iptable_filter ip_tables x_tables dum
  my bridge stp llc ipmi_ssif ipmi_devintf intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm dcdbas irqbypass crct10dif_p
  clmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd joydev input_leds nf_nat_ftp sb_edac nf_conntrack_ftp e
  dac_core cdc_ether nf_nat_pptp usbnet nf_conntrack_pptp mii nf_nat_proto_gre 
lpc_ich nf_nat_sip ioatdma nf_nat nf_conntrack_sip nfsd ipmi_si 
  8250_fintek nf_conntrack_proto_gre ipmi_msghandler acpi_pad wmi shpchp 
nf_conntrack acpi_power_meter mac_hid auth_rpcgss nfs_acl bonding nfs 
  lp lockd parport grace sunrpc fscache tcp_htcp xfs btrfs hid_generic usbhid 
hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_
  xor async_tx xor ixgbe raid6_pq libcrc32c igb vxlan raid1 i2c_algo_bit 
ip6_udp_tunnel dca udp_tunnel ahci raid0 ptp libahci megaraid_sas mult
  ipath pps_core mdio linear fjes
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197014] CPU: 13 PID: 3147726 Comm: 
ceph-osd Not tainted 4.4.0-15-generic #31~14
  .04.1-Ubuntu
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197085] Hardware name: Dell Inc. 
PowerEdge R720/0XH7F2, BIOS 2.5.2 01/28/2015
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197154] task: 88252be1ee00 ti: 
8824fc0d4000 task.ti: 8824fc0d4000
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197221] RIP: 
0010:[]  [] task_numa_find_cpu+0x238/0x700
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197300] RSP: :8824fc0d7ba8  
EFLAGS: 00010257
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197340] RAX:  RBX: 
8824fc0d7c48 RCX: 
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197406] RDX:  RSI: 
88479f18 RDI: 884782a47600
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197473] RBP: 8824fc0d7c10 R08: 
000102eea157 R09: 01a8
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197540] R10: 0002404b R11: 
023f R12: 88238093
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197606] R13: 0008 R14: 
008c R15: 0124
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197673] FS:  7f19aab5b700() 
GS:88479f18() knlGS:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197741] CS:  0010 DS:  ES:  
CR0: 80050033
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197782] CR2: 25469600 CR3: 
0023846bc000 CR4: 000426e0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197848] Stack:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197880]  817425fb 
8829af3e9e00 00f6 88252be1ee00
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197965]  008d 
0225 00016d40 008d
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198047]  88252be1ee00 
01ad 8824fc0d7c48 00e1
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198132] Call Trace:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198172]  [] ? 
tcp_schedule_loss_probe+0x12b/0x1b0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198219]  [] 
task_numa_migrate+0x4a0/0x930
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198264]  [] ? 
release_sock+0x117/0x160
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198306]  [] 
numa_migrate_preferred+0x79/0x80
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198350]  [] 
task_numa_fault+0x91d/0xcc0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198395]  [] ? 
mpol_misplaced+0x14e/0x190
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198439]  [] 
handle_pte_fault+0x5a8/0x14c0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198485] 

[Kernel-packages] [Bug 1607404] Re: Xenial update to v4.4.16 stable release

[Bryan Quigley]

@David, yes with few exceptions the kernel gets backported to Trusty HWE
after it's released for Xenial.  As an example, the 4.4.0-34 kernel was
just released for Xenial and is also in Trusty as HWE already.

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

Title:
  Xenial update to v4.4.16 stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the v4.4.16 stable release shall be
  applied:

  mac80211: fix fast_tx header alignment
  mac80211: mesh: flush mesh paths unconditionally
  mac80211_hwsim: Add missing check for HWSIM_ATTR_SIGNAL
  mac80211: Fix mesh estab_plinks counting in STA removal case
  EDAC, sb_edac: Fix rank lookup on Broadwell
  IB/cm: Fix a recently introduced locking bug
  IB/mlx4: Properly initialize GRH TClass and FlowLabel in AHs
  powerpc/pseries: Fix IBM_ARCH_VEC_NRCORES_OFFSET since POWER8NVL was added
  powerpc/tm: Always reclaim in start_thread() for exec() class syscalls
  usb: dwc2: fix regression on big-endian PowerPC/ARM systems
  USB: EHCI: declare hostpc register as zero-length array
  usb: common: otg-fsm: add license to usb-otg-fsm
  mnt: fs_fully_visible test the proper mount for MNT_LOCKED
  mnt: Account for MS_RDONLY in fs_fully_visible
  mnt: If fs_fully_visible fails call put_filesystem.
  of: fix autoloading due to broken modalias with no 'compatible'
  of: irq: fix of_irq_get[_byname]() kernel-doc
  locking/ww_mutex: Report recursive ww_mutex locking early
  locking/qspinlock: Fix spin_unlock_wait() some more
  locking/static_key: Fix concurrent static_key_slow_inc()
  x86, build: copy ldlinux.c32 to image.iso
  kprobes/x86: Clear TF bit in fault on single-stepping
  x86/amd_nb: Fix boot crash on non-AMD systems
  Revert "gpiolib: Split GPIO flags parsing and GPIO configuration"
  uvc: Forward compat ioctls to their handlers directly
  thermal: cpu_cooling: fix improper order during initialization
  writeback: use higher precision calculation in domain_dirty_limits()
  nfsd4/rpc: move backchannel create logic into rpc code
  nfsd: Always lock state exclusively.
  nfsd: Extend the mutex holding region around in nfsd4_process_open2()
  posix_acl: Add set_posix_acl
  nfsd: check permissions when setting ACLs
  make nfs_atomic_open() call d_drop() on all ->open_context() errors.
  NFS: Fix another OPEN_DOWNGRADE bug
  ARM: imx6ul: Fix Micrel PHY mask
  ARM: 8578/1: mm: ensure pmd_present only checks the valid bit
  ARM: 8579/1: mm: Fix definition of pmd_mknotpresent
  MIPS: KVM: Fix modular KVM under QEMU
  mm: Export migrate_page_move_mapping and migrate_page_copy
  UBIFS: Implement ->migratepage()
  sched/fair: Fix cfs_rq avg tracking underflow
  packet: Use symmetric hash for PACKET_FANOUT_HASH.
  net_sched: fix mirrored packets checksum
  cdc_ncm: workaround for EM7455 "silent" data interface
  ipv6: Fix mem leak in rt6i_pcpu
  ARCv2: Check for LL-SC livelock only if LLSC is enabled
  ARCv2: LLSC: software backoff is NOT needed starting HS2.1c
  kvm: Fix irq route entries exceeding KVM_MAX_IRQ_ROUTES
  KVM: nVMX: VMX instructions: fix segment checks when L1 is in long mode.
  HID: elo: kill not flush the work
  HID: hiddev: validate num_values for HIDIOCGUSAGES, HIDIOCSUSAGES commands
  tracing: Handle NULL formats in hold_module_trace_bprintk_format()
  base: make module_create_drivers_dir race-free
  iommu/arm-smmu: Wire up map_sg for arm-smmu-v3
  iommu/vt-d: Enable QI on all IOMMUs before setting root entry
  iommu/amd: Fix unity mapping initialization race
  drm/mgag200: Black screen fix for G200e rev 4
  ipmi: Remove smi_msg from waiting_rcv_msgs list before handle_one_recv_msg()
  arm64: Rework valid_user_regs
  vfs: add d_real_inode() helper
  af_unix: fix hard linked sockets on overlay
  btrfs: account for non-CoW'd blocks in btrfs_abort_transaction
  drm/radeon: fix asic initialization for virtualized environments
  drm/amdgpu/gfx7: fix broken condition check
  ubi: Make recover_peb power cut aware
  drm/amdkfd: unbind only existing processes
  drm/amdkfd: destroy dbgmgr in notifier release
  drm/dp/mst: Always clear proposed vcpi table for port.
  drm/nouveau/disp/sor/gf119: both links use the same training register
  drm/nouveau/gr/gf100-: update sm error decoding from gk20a 

[Kernel-packages] [Bug 1163587] Re: mtrr_cleanup: can not find optimal value, perhaps no longer needed?

[Bryan Quigley]

>From my latest testing, we do currently support machines that don't have
PAT support (really old 32 bit x86).  So this can be revisited at some
future point when we go 64 bit only for x86.

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

Title:
  mtrr_cleanup: can not find optimal value, perhaps no longer needed?

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The actual common error message from dmesg:

  [0.00] original variable MTRRs
  [0.00] reg 0, base: 0GB, range: 32GB, type WB
  [0.00] reg 1, base: 3584MB, range: 512MB, type UC
  [0.00] reg 2, base: 3548MB, range: 4MB, type UC
  [0.00] reg 3, base: 3552MB, range: 32MB, type UC
  [0.00] total RAM covered: 32220M
  [0.00]  gran_size: 64K  chunk_size: 64K num_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 128Knum_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 256Knum_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 512Knum_reg: 7  lose 
cover RAM: 28676M
  [0.00]  gran_size: 64K  chunk_size: 1M  num_reg: 7  lose cover 
RAM: 28676M
  ...
  [0.00]  gran_size: 256M chunk_size: 2G  num_reg: 6  lose 
cover RAM: 220M
  [0.00]  gran_size: 512M chunk_size: 512Mnum_reg: 5
  lose cover RAM: 476M
  [0.00]  gran_size: 512M chunk_size: 1G  num_reg: 5  lose 
cover RAM: 476M
  [0.00]  gran_size: 512M chunk_size: 2G  num_reg: 5  lose 
cover RAM: 476M
  [0.00]  gran_size: 1G   chunk_size: 1G  num_reg: 5  lose cover 
RAM: 476M
  [0.00]  gran_size: 1G   chunk_size: 2G  num_reg: 5  lose cover 
RAM: 476M
  [0.00]  gran_size: 2G   chunk_size: 2G  num_reg: 4  lose cover 
RAM: 1500M
  [0.00] mtrr_cleanup: can not find optimal value
  [0.00] please specify mtrr_gran_size/mtrr_chunk_size

  I have found errors like this on many machines (one with 128 GB of
  RAM, mine with just 4GB).   The instructions want you to specify
  kernel options that you don't need to do.  Just turning off
  mtrr_cleanup appears to be the best option.  You can fix it be
  specifying disable_mtrr_cleanup.

  According to kernel paramaters
  (https://www.kernel.org/doc/Documentation/kernel-parameters.txt)

disable_mtrr_cleanup [X86]
The kernel tries to adjust MTRR layout from continuous
to discrete, to make X server driver able to add WB
entry later. This parameter disables that.

  From this I understand it was here to help allow leave the X server
  space if it needed it in the future.  That should no longer be
  necessary, correct?   I have an Intel GPU and noticed no performance
  problems by disabling it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-16-generic 3.8.0-16.26
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  1978 F pulseaudio
  Date: Tue Apr  2 16:56:13 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-04 (56 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130204.1)
  MachineType: Dell Inc. Inspiron 1545
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic 
root=UUID=0983e077-6f15-4e52-a776-faa186229dc8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-16-generic N/A
   linux-backports-modules-3.8.0-16-generic  N/A
   linux-firmware1.104
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

[Bryan Quigley]

I thought it was related to my system being a brand new Ryzen with ZRam
and 32GB of memory (no real swap) but apparently not.

A BIOS update bricked that motherboard so I'm back on my older
Phenom(tm) II X4 945 with 12 GB of RAM (now no ZRAM). Just got the issue
again.  Now, I have *no* swap enabled at all and still got it.

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

Title:
  kernel BUG at /build/linux-
  7LGLH_/linux-4.10.0/include/linux/swapops.h:129

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Randomly, khugepaged process will take 100% CPU, and I can only
  restart the computer to recover it.

  Relevant dmesg attached (dmesg_crash.txt).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mathieu2221 F pulseaudio
   /dev/snd/pcmC1D0p:   mathieu2221 F...m pulseaudio
   /dev/snd/controlC1:  mathieu2221 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Mar 21 23:03:23 2017
  HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd
  InstallationDate: Installed on 2016-01-31 (415 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: LENOVO 20344
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago)
  dmi.bios.date: 10/16/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN29WW(V1.15)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 957426] Re: [spread] no support for slideshow wallpapers

[Bryan Quigley]

** Changed in: unity-2d
   Status: Confirmed => Invalid

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

Title:
  [spread] no support for slideshow wallpapers

Status in unity-2d:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Black screens like image in atachement.

  This only happens when it is selected the wallpaper that changes the
  image automatically.

  --- 
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  CheckboxSubmission: 622b42fa9ef9d3b69804517c9688ce18
  CheckboxSystem: 6a51181f3da22e0f4cddc1735a0ba0ba
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Package: linux (not installed)
  Tags:  precise
  Uname: Linux 3.3.0-030300rc7-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to precise on 2012-03-13 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SIS966 [HDA SIS966], device 0: ALC662 rev1 Analog [ALC662 rev1 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andre  1824 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SIS966'/'HDA SIS966 at 0xd040 irq 18'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,15580809,00100101'
 Controls  : 25
 Simple ctrls  : 13
  CheckboxSubmission: 622b42fa9ef9d3b69804517c9688ce18
  CheckboxSystem: 6a51181f3da22e0f4cddc1735a0ba0ba
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=f03abafc-eada-4f23-983e-46cccab2e9c4
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B 
Wireless 802.11g 54Mbps Network Adapter
   Bus 001 Device 003: ID 5986:0200 Acer, Inc OrbiCam
  MachineType: CLEVO Co. W760SUA
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae 
root=UUID=61ee0314-3639-4af0-8356-ed98230c754c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-18-generic-pae N/A
   linux-backports-modules-3.2.0-18-generic-pae  N/A
   linux-firmware1.71
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  precise
  Uname: Linux 3.2.0-18-generic-pae i686
  UpgradeStatus: Upgraded to precise on 2012-03-13 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 08/28/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W760SUA
  dmi.board.vendor: CLEVO Co.
  dmi.board.version: SI94B-20+SI96A-33
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: CLEVO Co.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd08/28/2009:svnCLEVOCo.:pnW760SUA:pvrRev.A1:rvnCLEVOCo.:rnW760SUA:rvrSI94B-20+SI96A-33:cvnCLEVOCo.:ct1:cvrN/A:
  dmi.product.name: W760SUA
  dmi.product.version: Rev. A1
  dmi.sys.vendor: CLEVO Co.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-2d/+bug/957426/+subscriptions

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

[Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

[Bryan Quigley]

I'm curious if it works if you just remove the splash line from the
command line (press F6 when booting).

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

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

[Bryan Quigley]

Thanks for trying,  not so easy to debug on a live session. Lets see if
we can reproduce it locally.

I'm hoping you are running Ubuntu locally (which version?), if so could you try 
to see if you can reproduce the problem using a mainline kernel build of 4.13 - 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.3/ seems like a good first 
try)
https://wiki.ubuntu.com/Kernel/MainlineBuilds

This would just install the kernel and should make it easier to bisect
the issue.

If v4.13.3 doesn't cause the issue, try v4.13-rc7, otherwise we can be
relatively sure it's not a kernel issue (or at least not just a kernel
issue)

If v4.13.3 doe cause the issue, try v4.14-rc1 to see if it's fixed in a newer 
release. 
Then try v4.12.14 to see if it was present in 4.12, if it wasn't we want to try 
maybe v4.13-rc3/.
If it is present in v4.12.14 then we want to try maybe v4.12-rc5/.

Ideally we'd work it down to exactly where it was introduced - and then
maybe do Git bisects.

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

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1718688] Re: Can't connect to a Cisco AP with Wi-Fi Direct Client Policy enabled

[Bryan Quigley]

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

Title:
  Can't connect to a Cisco AP with Wi-Fi Direct Client Policy enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is a setting available on selected Cisco hardware named "Wi-Fi
  Direct Client Policy". One of the allowed option there is 'not-allow'.
  It's intention is to block WiFi P2P capable devices from connecting to
  it. If a device trying to associate with an AP with this setting
  enabled is identified as "P2P capable" it gets blacklisted (I believe
  for a preconfigured time). More info about the option available at [1]
  and [2].

  This leads to a situation that it is impossible to connect to certain
  APs using certain WiFi chips using iwlwifi driver. I was able to
  determine that this at least affects Intel 8260 chip.

  What's going on on the WiFi level is:
  The AP broadcasts beacon frames with P2P IE:
  Tag: Vendor Specific: Wi-FiAll: P2P
  Tag Number: Vendor Specific (221)
  Tag length: 8
  OUI: 50-6f-9a (Wi-FiAll)
  Vendor Specific OUI Type: 9
  P2P Manageability: Bitmap field 0x5
  Attribute Type: P2P Manageability (10)
  Attribute Length: 1
  Manageability Bitmap field: 0x05
   ...1 = P2P Device Management: 0x1
   ..0. = Cross Connection Permitted: 0x0
   .1.. = Coexistence Optional: 0x1

  The client then sends a Probe Request, also with a P2P IE in it:
  Tag: Vendor Specific: Wi-FiAll: P2P
  Tag Number: Vendor Specific (221)
  Tag length: 17
  OUI: 50-6f-9a (Wi-FiAll)
  Vendor Specific OUI Type: 9
  P2P Capability: Device 0x25  Group 0x0
  Attribute Type: P2P Capability (2)
  Attribute Length: 2
  Device Capability Bitmap: 0x25
   ...1 = Service Discovery: 0x1
   ..0. = P2P Client Discoverability: 0x0
   .1.. = Concurrent Operation: 0x1
   0... = P2P Infrastructure Managed: 0x0
  ...0  = P2P Device Limit: 0x0
  ..1.  = P2P Invitation Procedure: 0x1
  Group Capability Bitmap: 0x00
   ...0 = P2P Group Owner: 0x0
   ..0. = Persistent P2P Group: 0x0
   .0.. = P2P Group Limit: 0x0
   0... = Intra-BSS Distribution: 0x0
  ...0  = Cross Connection: 0x0
  ..0.  = Persistent Reconnect: 0x0
  .0..  = Group Formation: 0x0
  Listen Channel: Operating Class 81  Channel Number 1
  Attribute Type: Listen Channel (6)
  Attribute Length: 5
  Country String: XX\004
  Operating Class: 81
  Channel Number: 1

  The AP never replies to that Probe Request and blacklists the device
  for a given period of time from all communication.

  I was able to test a custom kernel with all P2P interfaces commented
  out from iwlwifi/mvm/mac80211.c - it was able to connect to the AP
  without any issues.

  For instance this issue does not affect bcm43224 device running with
  brcm80211 - in this case the client device sends a Probe Request
  without the P2P IE. Despite it's is actually P2P-capable the AP does
  not recognize it as such and allows it to connect.

  I have also started a mailing list thread about it [3].

  What I think could fix it is either:
  * making it behave more like the broadcom driver so it allows users to connect
  * provide an user-friendly option of disabling p2p capabilites (including 
transmitting probe reuqests without P2P IE)
  * as suggested on the ML [4] implement sections 3.4.3/3.4.4 of the WiFi 
Direct spec in the driver

  According to my knowledge it affects all currently supported releases:
  Trusty, Xenial, Zesty plus Artful.

  [1] 
https://supportforums.cisco.com/t5/security-and-network-management/wi-fi-direct-client-policy/td-p/2253033
  [2] 
https://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_01010.html
  [3] https://marc.info/?l=linux-wireless=150306048824814=2
  [4] https://marc.info/?l=linux-wireless=150461784431430=2

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

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

[Kernel-packages] [Bug 882147] Re: overlayfs does not implement inotify interfaces correctly

[Bryan Quigley]

tail -f /var/log/syslog worked for me with 17.10 dev | kernel 4.12.
(Tested by turning network on and off).

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

Title:
  overlayfs does not implement inotify interfaces correctly

Status in coreutils package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in coreutils source package in Precise:
  Confirmed
Status in linux source package in Precise:
  Triaged

Bug description:
  When using tail on the liveCD some updates are not reported.  This
  seems to be triggered by tail using inotify to identify modified
  files.  Overlayfs does not appear to be implementing inotify quite the
  way you might hope reporting only against the underlying filesystems.

  Related bugs:
   * bug 1213925:  upstart should notice "/etc" inode change

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 0/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw2296 F pulseaudio
   /dev/snd/pcmC0D0c:   apw2296 F...m pulseaudio
   /dev/snd/pcmC0D0p:   apw2296 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 47'
     Mixer name : 'Intel Cantiga HDMI'
     Components : 'HDA:111d7675,1028029f,00100103 
HDA:80862802,80860101,0010'
     Controls  : 20
     Simple ctrls  : 11
  Date: Wed Oct 26 17:46:16 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d8328455-deac-4bae-877d-c408d371cefe
  MachineType: Dell Inc. Studio 1537
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (9 days ago)
  WpaSupplicantLog:

  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Studio 1537
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 882147] Re: overlayfs does not implement inotify interfaces correctly

[Bryan Quigley]

Good to know. If tail works around this by default is there any other
reason to keep the coreutils task open?

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

Title:
  overlayfs does not implement inotify interfaces correctly

Status in coreutils package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in coreutils source package in Precise:
  Confirmed
Status in linux source package in Precise:
  Triaged

Bug description:
  When using tail on the liveCD some updates are not reported.  This
  seems to be triggered by tail using inotify to identify modified
  files.  Overlayfs does not appear to be implementing inotify quite the
  way you might hope reporting only against the underlying filesystems.

  Related bugs:
   * bug 1213925:  upstart should notice "/etc" inode change

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-12-generic 3.0.0-12.20
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 0/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw2296 F pulseaudio
   /dev/snd/pcmC0D0c:   apw2296 F...m pulseaudio
   /dev/snd/pcmC0D0p:   apw2296 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 47'
     Mixer name : 'Intel Cantiga HDMI'
     Components : 'HDA:111d7675,1028029f,00100103 
HDA:80862802,80860101,0010'
     Controls  : 20
     Simple ctrls  : 11
  Date: Wed Oct 26 17:46:16 2011
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d8328455-deac-4bae-877d-c408d371cefe
  MachineType: Dell Inc. Studio 1537
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-12-generic N/A
   linux-backports-modules-3.0.0-12-generic  N/A
   linux-firmware1.60
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (9 days ago)
  WpaSupplicantLog:

  dmi.bios.date: 09/22/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Studio 1537
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1732013] Re: Drop Floppy Drive Support from kernel?

[Bryan Quigley]

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

Title:
  Drop Floppy Drive Support from kernel?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) Proposed for 18.04
  2) Whichever kernel 4.14 or 4.15

  Can we drop Floppy support from the kernel for Bionic?

  I see very small activity about Floppy drives in the 2012 timeframe
  (LP and AskUbuntu), but I can't see much of a use for floppy drives in
  2018.

  Advantages to remove
  * It's being removed for various cloud vendors - 
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1729673.  I can't 
reproduce the speed difference locally though.
  * It removes attack service.  Hard to quantify but QEMU has gotten hit by a 
bad floppy disk exploit (https://usn.ubuntu.com/usn/usn-2608-1/)

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

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