[Kernel-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[higuita]

@Stunts: yes, it is the same issue. I can pair the phone, but no audio

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Fix Committed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1539158/+subscriptions

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

[Kernel-packages] [Bug 1578176] Re: Cannot place or recieve calls when using in-car bluetooth system

[higuita]

bug 1584362 have logs

several people with this problem are also in bug
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-
settings/+bug/1435040

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

Title:
  Cannot place or recieve calls when using in-car bluetooth system

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  After working around bug
  https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158 I was
  able to pair the phone (BQ Aquaris E4.5) with the car hands-free
  system.

  However, thing don't quite work as expected.
  I can use the car's system to place a call using the phone, but The audio is 
not getting properly routed. After placing the call, I can't hear any sounds 
(not even the "ringing" noise), I don't get any feedback after the other person 
has answered the phone, and the other person can't hear me either.

  Furthermore, Long after the other person has hung up the call, the
  phone still looks like the call is ongoing (I have to manually
  disconnect it).

  I can also use the system to answer an incoming call, but the
  sympthoms are the same. No audio on either end.

  Would a debug log be helpful in this situation 
(https://wiki.ubuntu.com/DebuggingBluetooth)?
  Or is something else required?

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

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

[Kernel-packages] [Bug 1578178] Re: Caller ID not displayed using in-car bluetooth system when recieving a call

[higuita]

dupe of https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578176

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

Title:
  Caller ID not displayed using in-car bluetooth system when recieving a
  call

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  When the phone is connected to the in-car hands free bluetooth system and I 
receive a call, I expect the caller ID to be displayed in the car's 
infotainment system. This was working until OTA9, which has made the system 
display "Unknown" when receiving a call.
  I can use the phone's contacts from the car, so no everything is broken in 
that respect.

  Would a verbose bluetooth log be helpful
  (https://wiki.ubuntu.com/DebuggingBluetooth), or would something else
  be required to help further investigate?

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

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

[Kernel-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

[higuita]

Still a problem and me and several others are ready to help de bug
this... Just tell us what you need. What logs to check, how to increase
the log level or load debug programs. Thanks

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

Title:
  Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions

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

[Kernel-packages] [Bug 1564217] Re: Hot add of a disk attached to LSI Logic SAS is not getting detected

[Yuhua Zou]

this issue is alive in Ubuntu 16.04.1.

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

Title:
  Hot add of a disk attached to LSI Logic SAS is not getting detected

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  when install VM ubuntu 16.04 beta1 image in VMware ESXi,  Hot add of
  a disk attached to LSI Logic SAS is not getting detected

  Steps to reproduce:
  1.Install ubuntu 16.04 beta1 with BUS logic SAS as boot controller in VMware 
ESXi 6.0GA.
  2.Power on the VM
  3.Hot add a hard disk to LSI SAS controller, the ubuntu 16.04 does not detect 
the disk

  the developer from VMware company investigate it and find it's a kernel issue.
  Bug 114611(https://bugzilla.kernel.org/show_bug.cgi?id=114611) is tracking it 
and now have fix for it.

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

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

[Kernel-packages] [Bug 1579066] Re: Error parsing PCC subspaces from PCCT --- On startup

[Christopher Kosciuk]

This bug also affects me. I'm using a Lenovo ThinkPad T450s with an
updated BIOS.

$ uname -a
Linux T450s 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
JBET61WW (1.25 )
07/13/2016

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

Title:
  Error parsing PCC subspaces from PCCT--- On startup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  New install of Ubuntu 16.04 from Windows 10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shieldrj   1781 F pulseaudio
   /dev/snd/controlC0:  shieldrj   1781 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  6 09:08:38 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3b95cab7-d12d-4d82-aad7-7b9697484746
  InstallationDate: Installed on 2016-05-03 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20DQ001LUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8a46bfbe-3fd3-4c14-b860-40af27c8c96b ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N19ET35W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DQ001LUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN19ET35W(1.08):bd03/25/2015:svnLENOVO:pn20DQ001LUS:pvrThinkPadS5Yoga15:rvnLENOVO:rn20DQ001LUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DQ001LUS
  dmi.product.version: ThinkPad S5 Yoga 15
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1606103] Re: modeset driver is missing some modes that the intel driver had

[Rocko]

Another Ubuntu Perthian! Excellent! I checked another laptop and the
kernel only listed the native resolution of the screen on that as well,
so perhaps the issue is in xserver/modeset after all. But out of
curiosity, what role is the kernel supposed to take here? It does list
all the modes for my external monitor, just not for the laptop screens.

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

Title:
  modeset driver is missing some modes that the intel driver had

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg-server package in Debian:
  New

Bug description:
  My laptop's 4K screen (Dell XPS 15 9550) has these resolutions,
  according to the intel driver:

 3840x2160 60.00 +
 3200x1800 60.00
 2880x1620 60.00
 2560x1440 60.00*
 2048x1536 60.00
 1920x1440 60.00
 1856x1392 60.01
 1792x1344 60.01
 2048x1152 60.00
 1920x1200 59.95
 1920x1080 60.0059.93
 1600x1200 60.00
 1680x1050 59.9559.88
 1600x1024 60.17
 1400x1050 59.98
 1600x900  60.00
 1280x1024 60.02
 1440x900  59.89
 1280x960  60.00
 1368x768  60.00
 1360x768  59.8059.96
 1152x864  60.00
 1280x720  60.00
 1024x768  60.00
 1024x576  60.00
 960x540   60.00
 800x600   60.3256.25
 864x486   60.00
 640x480   59.94
 720x405   60.00
 640x360   60.00

  But with the modeset driver, it detects these resolutions:

 3840x2160 60.00*+
 2048x1536 60.00
 1920x1440 60.00
 1856x1392 60.01
 1792x1344 60.01
 1920x1200 59.95
 1920x1080 59.93
 1600x1200 60.00
 1680x1050 59.9559.88
 1600x1024 60.17
 1400x1050 59.98
 1280x1024 60.02
 1440x900  59.89
 1280x960  60.00
 1360x768  59.8059.96
 1152x864  60.00
 1024x768  60.0460.00
 960x720   60.00
 928x696   60.05
 896x672   60.01
 960x600   60.00
 960x540   59.99
 800x600   60.0060.3256.25
 840x525   60.0159.88
 800x512   60.17
 700x525   59.98
 640x512   60.02
 720x450   59.89
 640x480   60.0059.94
 680x384   59.8059.96
 576x432   60.06
 512x384   60.00
 400x300   60.3256.34
 320x240   60.05

  It seems to be picking up some extra super-low resolutions (like
  320x240) but not the higher 16:9 resolutions. I normally run it at
  2560x1440, because the native resolution is too high with an external
  monitor attached at 1980x1080, but I can't do this with the modeset
  driver.

  I'm reporting this as per https://tjaalton.wordpress.com/2016/07/23
  /intel-graphics-gen4-and-newer-now-defaults-to-modesetting-driver-
  on-x/, although note that there are several inaccuracies in that post
  - there's a typo in ‘cp /usr/share/doc/xserver-xoeg-video-
  intel/xorg.conf /etc/X11‘, the file doesn't exist in any case if you
  correct the typo, and I couldn't use ubuntu-bug to report this against
  xorg-xserver, because ubuntu-bug said the xorg-xserver package doesn't
  exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg-server-source (not installed)
  Uname: Linux 4.6.4-040604-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jul 25 11:09:00 2016
  DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.6.4-040604-generic, x86_64: installed
   nvidia-367, 367.35, 4.4.0-28-generic, x86_64: installed
   nvidia-367, 367.35, 4.6.4-040604-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
  InstallationDate: Installed on 2016-07-04 (20 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.

[Kernel-packages] [Bug 1584528] Re: Inspiron 3543 TouchPad cursor jumps to left edge unexpectedly

[w2vy]

In my testing a used a Java program to test on the various releases.
I was surprised to discover that the 14.04 Live CD did not easily support Java.

So I switched my testing to a simpler method

Open System settings and move from one setting to another looking for
errors.

I am currently verifying Trusty Tahr and plan on exhaustively test it.
I will then move to Wily.

Tom

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

Title:
  Inspiron 3543 TouchPad cursor jumps to left edge unexpectedly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At times (mostly undetermined) when touching the glide pad to take an
  action the cursor will jump to the left edge of the screen.

  I do not recall the system ever taking ACTION based on the click at the new 
location.
  ex: side bar opening, etc

  It may not ever take the action at the ORIGINAL location, I can't be
  sure since I am only alerted when things don't happen as I expect.

  If I am using the keyboard to type or scroll (arrows) I have not
  noticed anything strange.

  I am not sure if it only happens when attempting a Left click or a
  Right Click.

  As a developer I think it is seeing my Click and reading the position
  incorrectly or hitting some other error condition. I do believe it is
  a result of my click.

  Tom

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tom2103 F pulseaudio
   /dev/snd/controlC0:  tom2103 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 16:30:13 2016
  HibernationDevice: RESUME=UUID=ebc3eae4-8f8a-49c6-9d22-a59e4bdf0ec5
  InstallationDate: Installed on 2015-07-17 (310 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3543
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=5b06297b-c923-468b-bc52-d2dfa945174c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-03 (19 days ago)
  dmi.bios.date: 03/20/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 01Y5DY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/20/2015:svnDellInc.:pnInspiron3543:pvrA04:rvnDellInc.:rn01Y5DY:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3543
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1590985] Re: Wifi non-functional after suspend (Intel 6205)

[Christopher M. Penalver]

Juraj, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Wifi non-functional after suspend (Intel 6205)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Often, but not always, on resume from suspend my wifi does not
  connect.  In the networking tray drop-down I can see one single wifi
  network listed (out of the many within range), and it can't reconnect
  to my network.

  I clear it with the hammer of:

  sudo rmmod iwldvm && sudo modprobe iwldvm

  I'm not sure what would be more appropriate, but that works.  Then my
  laptop auto-connects to the right network, as expected.

  Turning on/off the hardware wireless switch on the thinkpad does not
  clear the problem.

  Just before running ubuntu-bug to submit this, I had the problem, then
  reloaded the iwldvm module.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1934 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun  9 18:57:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-21 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2325KZ5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=72122534-7dd5-411b-9c56-c4844502e0ad ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA0WW (2.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325KZ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 518896
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA0WW(2.60):bd03/05/2013:svnLENOVO:pn2325KZ5:pvrThinkPadX230:rvnLENOVO:rn2325KZ5:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325KZ5
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1590985] Re: Wifi non-functional after suspend (Intel 6205)

[Juraj]

Here's my dmidecode for a Thinkpad W520:

8BET62WW (1.42 )
07/26/2013

It has the newest available BIOS.

lspci:
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor 
Peak] (rev 34)

Kernel:
Linux juraj 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  Wifi non-functional after suspend (Intel 6205)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Often, but not always, on resume from suspend my wifi does not
  connect.  In the networking tray drop-down I can see one single wifi
  network listed (out of the many within range), and it can't reconnect
  to my network.

  I clear it with the hammer of:

  sudo rmmod iwldvm && sudo modprobe iwldvm

  I'm not sure what would be more appropriate, but that works.  Then my
  laptop auto-connects to the right network, as expected.

  Turning on/off the hardware wireless switch on the thinkpad does not
  clear the problem.

  Just before running ubuntu-bug to submit this, I had the problem, then
  reloaded the iwldvm module.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1934 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun  9 18:57:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-21 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2325KZ5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=72122534-7dd5-411b-9c56-c4844502e0ad ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA0WW (2.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325KZ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 518896
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA0WW(2.60):bd03/05/2013:svnLENOVO:pn2325KZ5:pvrThinkPadX230:rvnLENOVO:rn2325KZ5:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325KZ5
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

** Description changed:

+ Note: Current workaround is to add pci=noaer to your kernel command
+ line:
+ 
+ 1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
+ GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
+ 2) run "sudo update-grub"
+ 3) reboot
+ 
+ 
+ 
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens after
  reboot.
  
  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
- [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
+ [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
- [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
+ [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
-  /dev/snd/controlC0:  david  1502 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
+  /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.2.0-19-generic N/A
-  linux-backports-modules-4.2.0-19-generic  N/A
-  linux-firmware1.153
+  linux-restricted-modules-4.2.0-19-generic N/A
+  linux-backports-modules-4.2.0-19-generic  N/A
+  linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

Title:
  AER: Corrected error received: id=00e0

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: 

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

Btw, I reported mine upstream long ago and got response from upstream
that "I've thought about this problem a bit, but realistically I don't
have time to do the fix I'd like to do /.../ Anybody else who is
interested should feel free to take a crack at it."

See http://permalink.gmane.org/gmane.linux.kernel.pci/48697

Also some googling finds me a few other reports with very similar
symptoms, e g:

https://bugzilla.kernel.org/show_bug.cgi?id=111601

https://lkml.org/lkml/2015/9/2/573


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

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

Title:
  AER: Corrected error received: id=00e0

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1558252] Re: Intel 8260 / iwlwifi Occasionally unusuable after restart

[openfred]

Please have a look at this solution: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590985
Post #9

I had a similar issue after restarting a Lenovo thinkpad T520 (iwlwifi on a 
Centrino 6205).
After a cold start, not all the time. Sometimes I needed up to 4 restart before 
the wifi connexion succeeds.

The solution described in bug 1590985 solved both issues: 
wifi connection at startup _AND_ wifi restore after suspend.

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

Title:
  Intel 8260 / iwlwifi Occasionally unusuable after restart

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  Some times my wifi card is inaccessible immediately after boot. Typically, 
restarting the machine or reloading the iwlwifi kernel module resolves the 
issue.

  dmesg on inaccessible card:

  [   13.146917] iwlwifi :04:00.0: Unsupported splx structure
  [   13.147620] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8000C-19.ucode failed with error -2
  [   13.147754] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8000C-18.ucode failed with error -2
  [   13.147765] iwlwifi :04:00.0: Direct firmware load for 
iwlwifi-8000C-17.ucode failed with error -2
  [   13.154952] iwlwifi :04:00.0: loaded firmware version 16.242414.0 
op_mode iwlmvm
  [   13.191912] iwlwifi :04:00.0: Detected Intel(R) Dual Band Wireless AC 
8260, REV=0x208
  [   13.198415] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
  [   13.199446] iwlwifi :04:00.0: L1 Enabled - LTR Enabled
  [   13.200661] iwlwifi :04:00.0: can't access the RSA semaphore it is 
write protected
  [   14.218185] iwlwifi :04:00.0: SecBoot CPU1 Status: 0x3090003, CPU2 
Status: 0x0
  [   14.218190] iwlwifi :04:00.0: Failed to start INIT ucode: -110
  [   14.219090] iwlwifi :04:00.0: Failed to run INIT ucode: -110
  [   14.219157] iwlwifi :04:00.0: L1 Enabled - LTR Enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ryan   1999 F pulseaudio
  Date: Wed Mar 16 12:00:48 2016
  HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d
  InstallationDate: Installed on 2015-09-21 (176 days ago)
  InstallationMedia: It
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FNCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-13-generic 
root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-13-generic N/A
   linux-backports-modules-4.4.0-13-generic  N/A
   linux-firmware1.156
  RfKill:
   0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (20 days ago)
  dmi.bios.date: 01/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET33W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FNCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FNCTO1WW
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[David Henningsson]

Out of curiousity, do all of you have the combination of Skylake +
RTL8723BE, and second, do you experience (as I do) that wifi doesn't
work very well (often loses connections etc)?

...as the errors seem to indicate some kind of physical error between
the Skylake/Sunrise Point host controller and the wifi card.

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

Title:
  AER: Corrected error received: id=00e0

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1590985] Re: Wifi non-functional after suspend (Intel 6205)

[openfred]

[Solved] Validated on a Lenovo Thinkpad T520 using a 6205 wifi card

$ lspci | grep 6205
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor 
Peak] (rev 34)

Just add a file for iwlwifi options in /etc/modprobe.d (1 line) -
filename can be anything:

$ cat /etc/modprobe.d/fred.conf 
options iwlwifi 11n_disable=1

Reboot after adding this file !

I prefer not to modify /etc/modprobe.d/iwlwifi.conf, as this file is
owned by package kmod, and can be modified at anytime.

I tried many times, wifi connection is restored in a 1 second. wifi
connection seems much stable.

Tried on Ubuntu Gnome 16.04 and Mint 18.

By the way, many posts are available on the internet about this issue,
and a lot of options are suggested. I recall that "modinfo -p" gives the
options available for a module:

$ sudo modinfo -p iwlwifi
swcrypto:using crypto in software (default 0 [hardware]) (int)
11n_disable:disable 11n functionality, bitmap: 1: full, 2: disable agg TX, 4: 
disable agg RX, 8 enable agg TX (uint)
amsdu_size_8K:enable 8K amsdu size (default 0) (int)
fw_restart:restart firmware in case of error (default true) (bool)
antenna_coupling:specify antenna coupling in dB (default: 0 dB) (int)
nvm_file:NVM file name (charp)
d0i3_disable:disable d0i3 functionality (default: Y) (bool)
lar_disable:disable LAR functionality (default: N) (bool)
uapsd_disable:disable U-APSD functionality (default: Y) (bool)
bt_coex_active:enable wifi/bt co-exist (default: enable) (bool)
led_mode:0=system default, 1=On(RF On)/Off(RF Off), 2=blinking, 3=Off (default: 
0) (int)
power_save:enable WiFi power management (default: disable) (bool)
power_level:default power save level (range from 1 - 5, default: 1) (int)
fw_monitor:firmware monitor - to debug FW (default: false - needs lots of 
memory) (bool)

$ iwconfig wlp3s0 
wlp3s0IEEE 802.11abg  ESSID:"freebox_CJBHVW"  
  Mode:Managed  Frequency:2.417 GHz  Access Point: F4:CA:E5:88:30:DC   
  Bit Rate=48 Mb/s   Tx-Power=15 dBm   
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Power Management:on
  Link Quality=48/70  Signal level=-62 dBm  
  Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
  Tx excessive retries:0  Invalid misc:71   Missed beacon:0

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

Title:
  Wifi non-functional after suspend (Intel 6205)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Often, but not always, on resume from suspend my wifi does not
  connect.  In the networking tray drop-down I can see one single wifi
  network listed (out of the many within range), and it can't reconnect
  to my network.

  I clear it with the hammer of:

  sudo rmmod iwldvm && sudo modprobe iwldvm

  I'm not sure what would be more appropriate, but that works.  Then my
  laptop auto-connects to the right network, as expected.

  Turning on/off the hardware wireless switch on the thinkpad does not
  clear the problem.

  Just before running ubuntu-bug to submit this, I had the problem, then
  reloaded the iwldvm module.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  1934 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun  9 18:57:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-21 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2325KZ5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=72122534-7dd5-411b-9c56-c4844502e0ad ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA0WW (2.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325KZ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: 518896
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA0WW(2.60):bd03/05/2013:svnLENOVO:pn2325KZ5:pvrThinkPadX230:rvnLENOVO:rn2325KZ5:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2325KZ5
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: 

[Kernel-packages] [Bug 695731] Re: sync hangs and can not be killed

[hanshenrik]

update: came back 2 hours later, and the sync had finished, guess it
could be unrelated to this bug then

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

Title:
  sync hangs and can not be killed

Status in linux package in Ubuntu:
  Expired

Bug description:
  Sync hangs.  strace stops logging anything after:
  sync(

  Process can not be killed and the server needs to be restarted.  This
  is similar to other reports of the same issue which I will link, but I
  have no USB/NFS/CIFS/etc filesystems.  I do have lvm2, HP cciss
  controller and ext4 filesystems.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: coreutils 7.4-2ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-25.45-server 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-server x86_64
  Architecture: amd64
  Date: Thu Dec 30 09:00:58 2010
  ExecutablePath: /bin/sync
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: coreutils

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

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

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Joseph Salisbury]

Can you test out the latest 4.6 based yakkety kernel while I get an
arm64 mainline kernel built?

The yakkety master-next kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1602577/yakkety/

Note that you need to install both the linux-image and linux-image-extra
.deb packages.

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1605731] Re: Kernel 4.4.0-31 Causes kernel panic at startup

[Robert Hrovat]

But, I found out I didn't have linux-headers-generic installed, only
linux-headers. Wi-Fi is working now.

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

Title:
  Kernel 4.4.0-31 Causes kernel panic at startup

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

Bug description:
  Latest kernel update 4.4.0-31 causes kernel panic at startup. Had to reboot 
with 4.4.0-28 which works fine. I have no idea if it's on all filesystems but 
I'm using btrfs.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robi   3230 F pulseaudio
   /dev/snd/pcmC1D0p:   robi   3230 F...m pulseaudio
   /dev/snd/controlC1:  robi   3230 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d64a307b-b7ea-4308-b997-0587321ff7ea
  InstallationDate: Installed on 2016-07-01 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X750LN
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e075f560-d606-43a0-9cc3-5596a9416d30 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X750LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr201:bd02/19/2014:svnASUSTeKCOMPUTERINC.:pnX750LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750LN:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: X750LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 695731] Re: sync hangs and can not be killed

[hanshenrik]

just happened to me on an xubuntu 16.04 live system, after having done
some heavy IO operations on 1 ntfs drive and 2 unmounted drives (had 2x
dd backup stored on an ntfs drive, restored them to the 2 unpartioned
drives, ran sync, and its been over 10 minutes now, not returning,
expected it to take a second or 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/695731

Title:
  sync hangs and can not be killed

Status in linux package in Ubuntu:
  Expired

Bug description:
  Sync hangs.  strace stops logging anything after:
  sync(

  Process can not be killed and the server needs to be restarted.  This
  is similar to other reports of the same issue which I will link, but I
  have no USB/NFS/CIFS/etc filesystems.  I do have lvm2, HP cciss
  controller and ext4 filesystems.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: coreutils 7.4-2ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-25.45-server 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-server x86_64
  Architecture: amd64
  Date: Thu Dec 30 09:00:58 2010
  ExecutablePath: /bin/sync
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: coreutils

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

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

[Kernel-packages] [Bug 1605344] Re: Regression caused by `fuse: Add support for pid namespaces` in 4.4.0-6.21

[Sheng Yang]

Works great for me, thank you Seth!

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

Title:
  Regression caused by `fuse: Add support for pid namespaces` in
  4.4.0-6.21

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

Bug description:
  The discussion starts at
  http://thread.gmane.org/gmane.linux.kernel.cgroups/15960/focus=2269876

  Commit in the tree is:

  commit a166e6726c6e12e28ac8489ff4e2faff7065a856
  Author: Seth Forshee 
  Date:   Wed Jul 2 16:29:19 2014 -0500

  UBUNTU: SAUCE: fuse: Add support for pid namespaces

  Description of the issue(copied from my report of lkml):

  This patch caused a regression in our major container use case with
  FUSE in Ubuntu 16.04, as patch was checked in as Ubuntu Sauce in
  Ubuntu 4.4.0-6.21 kernel.

  The use case is:
  1. Create a Docker container.
  2. Inside the container, start the FUSE backend, and mounted fs.
  3. Following step 2 in the container, create a loopback device to map
  a file in the mounted fuse to create a block device, which will be
  available to the whole system.

  It works well before this commit.

  The use case is broken because no matter which namespace losetup runs,
  the real request from loopback device seems always come from init ns,
  thus it will be in different ns running fuse backend. So the request
  will got denied, because the ns running fuse won't able to see the
  things from higher level(level 0 in fact) pid namespace.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature:
   
  Tags:  trusty
  Uname: Linux 4.4.6 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1605731] Re: Kernel 4.4.0-31 Causes kernel panic at startup

[Robert Hrovat]

@Seth, no, it's 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/1605731

Title:
  Kernel 4.4.0-31 Causes kernel panic at startup

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

Bug description:
  Latest kernel update 4.4.0-31 causes kernel panic at startup. Had to reboot 
with 4.4.0-28 which works fine. I have no idea if it's on all filesystems but 
I'm using btrfs.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robi   3230 F pulseaudio
   /dev/snd/pcmC1D0p:   robi   3230 F...m pulseaudio
   /dev/snd/controlC1:  robi   3230 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d64a307b-b7ea-4308-b997-0587321ff7ea
  InstallationDate: Installed on 2016-07-01 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X750LN
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e075f560-d606-43a0-9cc3-5596a9416d30 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X750LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr201:bd02/19/2014:svnASUSTeKCOMPUTERINC.:pnX750LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750LN:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: X750LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Bill Michaelson]

I seem to have this issue too, but related to a different device.
Running 16.04 with 4.4.0-31-generic.  New (used) machine so very
concering.  It ran fine for about an hour then spontaneously started
spewing this:

Jul 26 13:28:05 twin kernel: [8.837650] pcieport :00:03.0: AER: 
Multiple Corrected error received: id=0018
Jul 26 13:28:05 twin kernel: [8.837665] pcieport :00:03.0: PCIe Bus 
Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
Jul 26 13:28:05 twin kernel: [8.837675] pcieport :00:03.0:   device 
[8086:d138] error status/mask=0001/2000
Jul 26 13:28:05 twin kernel: [8.837685] pcieport :00:03.0:[ 0] 
Receiver Error (First)

lspci -nn gives me a match against this:

00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express
Root Port 1 [8086:d138] (rev 11)

and booting with pci=noaer suppresses the messages with no apparent ill
effects.

But I don't know what the message is supposed to mean and I fear that I
am suppressing a valid warning and gambling if I use the machine for
serious work.  Insights more than welcome.  The machine is an ASUS G73Jh
laptop Intel Core i7-720QM @ 1.60GHz / Nehalem 45nm).  TIA.

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

Title:
  AER: Corrected error received: id=00e0

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1278522] Re: asus n750jv cannot install with secure boot enabled

[Mathieu Trudel-Lapierre]

Given that the solution presented here on the same kind of system was to
set:

nomodeset acpi_osi=

It sounds a lot more like an issue in the kernel. Disabling Secure Boot
should not impact the system if it reaches the point of the boot splash
(the purple screen with the Ubuntu logo in the center, or with Ubuntu
text). Reassigning to 'linux'.

Marat, did this solution help you at all?

** Package changed: shim (Ubuntu) => linux (Ubuntu)

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

Title:
  asus n750jv cannot install with secure boot enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Cannot install ubuntu 13.10 with secure boot enabled and fast boot
  disabled and UEFI mode on asus n750jv with windows 8 preinstalled.
  Hungs on a purple start screen with an ubuntu word. Ubuntu installed
  well after disabling secure boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: shim 0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 10 21:48:34 2014
  Dependencies:
   
  InstallationDate: Installed on 2014-02-10 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: shim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1278522] [NEW] asus n750jv cannot install with secure boot enabled

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Cannot install ubuntu 13.10 with secure boot enabled and fast boot
disabled and UEFI mode on asus n750jv with windows 8 preinstalled. Hungs
on a purple start screen with an ubuntu word. Ubuntu installed well
after disabling secure boot.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: shim 0.4-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Mon Feb 10 21:48:34 2014
Dependencies:
 
InstallationDate: Installed on 2014-02-10 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: shim
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug saucy
-- 
asus n750jv cannot install with secure boot enabled
https://bugs.launchpad.net/bugs/1278522
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  NETDEV WATCHDOG: transmit queue 0 timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel module crash:

  [ 3537.262585] WARNING: CPU: 2 PID: 0 at 
/build/linux-dcxD3m/linux-4.4.0/net/sched/sch_generic.c:306 
dev_watchdog+0x237/0x240()
  [ 3537.262596] NETDEV WATCHDOG: wwp0s29u1u4 (qmi_wwan): transmit queue 0 
timed out
  [ 3537.262605] Modules linked in: hid_generic hidp hid rfcomm qmi_wwan 
cdc_wdm usbnet mii bnep intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp kvm_intel kvm qcserial usb_wwan usbserial irqbypass crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
v4l2_common videodev media joydev btusb btrtl btbcm btintel input_leds 
bluetooth serio_raw arc4 snd_hda_codec_hdmi iwldvm mac80211 
snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec 
iwlwifi snd_hda_core snd_hwdep cfg80211 snd_pcm lpc_ich shpchp snd_seq_midi 
snd_seq_midi_event snd_rawmidi thinkpad_acpi snd_seq nvram snd_seq_device 
snd_timer snd soundcore mac_hid mei_me mei parport_pc ppdev lp parport autofs4 
overlay
  [ 3537.262752]  nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs 
dm_mirror dm_region_hash dm_log i915 i2c_algo_bit drm_kms_helper psmouse 
syscopyarea sysfillrect sysimgblt e1000e fb_sys_fops sdhci_pci sdhci drm ahci 
ptp libahci pps_core wmi fjes video
  [ 3537.262820] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.4.0-31-generic 
#50-Ubuntu
  [ 3537.262829] Hardware name: LENOVO 4291PR5/4291PR5, BIOS 8DET70WW (1.40 ) 
05/14/2015
  [ 3537.262836]  0286 a2df4eaadf32735b 88041e283d98 
813f1143
  [ 3537.262846]  88041e283de0 81d66c78 88041e283dd0 
81081102
  [ 3537.262860]   8804062b5680 0002 
880405b32000
  [ 3537.262868] Call Trace:
  [ 3537.262874][] dump_stack+0x63/0x90
  [ 3537.262903]  [] warn_slowpath_common+0x82/0xc0
  [ 3537.262915]  [] warn_slowpath_fmt+0x5c/0x80
  [ 3537.262929]  [] dev_watchdog+0x237/0x240
  [ 3537.262944]  [] ? qdisc_rcu_free+0x40/0x40
  [ 3537.262958]  [] call_timer_fn+0x35/0x120
  [ 3537.262968]  [] ? qdisc_rcu_free+0x40/0x40
  [ 3537.262980]  [] run_timer_softirq+0x23a/0x2f0
  [ 3537.262992]  [] __do_softirq+0x101/0x290
  [ 3537.263003]  [] irq_exit+0xa3/0xb0
  [ 3537.263018]  [] smp_apic_timer_interrupt+0x42/0x50
  [ 3537.263027]  [] apic_timer_interrupt+0x82/0x90
  [ 3537.263031][] ? cpuidle_enter_state+0x10e/0x2b0
  [ 3537.263052]  [] cpuidle_enter+0x17/0x20
  [ 3537.263063]  [] call_cpuidle+0x32/0x60
  [ 3537.263072]  [] ? cpuidle_select+0x13/0x20
  [ 3537.263081]  [] cpu_startup_entry+0x290/0x350
  [ 3537.263093]  [] start_secondary+0x

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 6656 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: XFCE
  Date: Tue Jul 26 19:22:31 2016
  LiveMediaBuild: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  MachineType: LENOVO 4291PR5
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/Ubuntu/16.04x/desktop-amd64/casper/vmlinuz.efi 
append noprompt boot=casper nohibernate keyboard-configuration-layoutcode=pl 
console-setup/layoutcode=pl userfullname=User Name username=username 
hostname=hostname nfsroot=usb showmounts 
persistent-path=/Ubuntu/16.04x/desktop-amd64 persistent 
iso-scan/filename=/Ubuntu/16.04x/xubuntu-16.04.1-desktop-amd64.iso
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET70WW (1.40 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291PR5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET70WW(1.40):bd05/14/2015:svnLENOVO:pn4291PR5:pvrThinkPadX220:rvnLENOVO:rn4291PR5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291PR5
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1606642] [NEW] NETDEV WATCHDOG: transmit queue 0 timed out

[Marcin]

Public bug reported:

Kernel module crash:

[ 3537.262585] WARNING: CPU: 2 PID: 0 at 
/build/linux-dcxD3m/linux-4.4.0/net/sched/sch_generic.c:306 
dev_watchdog+0x237/0x240()
[ 3537.262596] NETDEV WATCHDOG: wwp0s29u1u4 (qmi_wwan): transmit queue 0 timed 
out
[ 3537.262605] Modules linked in: hid_generic hidp hid rfcomm qmi_wwan cdc_wdm 
usbnet mii bnep intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm qcserial usb_wwan usbserial irqbypass crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
v4l2_common videodev media joydev btusb btrtl btbcm btintel input_leds 
bluetooth serio_raw arc4 snd_hda_codec_hdmi iwldvm mac80211 
snd_hda_codec_conexant snd_hda_codec_generic snd_hda_intel snd_hda_codec 
iwlwifi snd_hda_core snd_hwdep cfg80211 snd_pcm lpc_ich shpchp snd_seq_midi 
snd_seq_midi_event snd_rawmidi thinkpad_acpi snd_seq nvram snd_seq_device 
snd_timer snd soundcore mac_hid mei_me mei parport_pc ppdev lp parport autofs4 
overlay
[ 3537.262752]  nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c reiserfs 
dm_mirror dm_region_hash dm_log i915 i2c_algo_bit drm_kms_helper psmouse 
syscopyarea sysfillrect sysimgblt e1000e fb_sys_fops sdhci_pci sdhci drm ahci 
ptp libahci pps_core wmi fjes video
[ 3537.262820] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.4.0-31-generic 
#50-Ubuntu
[ 3537.262829] Hardware name: LENOVO 4291PR5/4291PR5, BIOS 8DET70WW (1.40 ) 
05/14/2015
[ 3537.262836]  0286 a2df4eaadf32735b 88041e283d98 
813f1143
[ 3537.262846]  88041e283de0 81d66c78 88041e283dd0 
81081102
[ 3537.262860]   8804062b5680 0002 
880405b32000
[ 3537.262868] Call Trace:
[ 3537.262874][] dump_stack+0x63/0x90
[ 3537.262903]  [] warn_slowpath_common+0x82/0xc0
[ 3537.262915]  [] warn_slowpath_fmt+0x5c/0x80
[ 3537.262929]  [] dev_watchdog+0x237/0x240
[ 3537.262944]  [] ? qdisc_rcu_free+0x40/0x40
[ 3537.262958]  [] call_timer_fn+0x35/0x120
[ 3537.262968]  [] ? qdisc_rcu_free+0x40/0x40
[ 3537.262980]  [] run_timer_softirq+0x23a/0x2f0
[ 3537.262992]  [] __do_softirq+0x101/0x290
[ 3537.263003]  [] irq_exit+0xa3/0xb0
[ 3537.263018]  [] smp_apic_timer_interrupt+0x42/0x50
[ 3537.263027]  [] apic_timer_interrupt+0x82/0x90
[ 3537.263031][] ? cpuidle_enter_state+0x10e/0x2b0
[ 3537.263052]  [] cpuidle_enter+0x17/0x20
[ 3537.263063]  [] call_cpuidle+0x32/0x60
[ 3537.263072]  [] ? cpuidle_select+0x13/0x20
[ 3537.263081]  [] cpu_startup_entry+0x290/0x350
[ 3537.263093]  [] start_secondary+0x

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  marcin 6656 F pulseaudio
CasperVersion: 1.376
CurrentDesktop: XFCE
Date: Tue Jul 26 19:22:31 2016
LiveMediaBuild: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 4291PR5
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/Ubuntu/16.04x/desktop-amd64/casper/vmlinuz.efi 
append noprompt boot=casper nohibernate keyboard-configuration-layoutcode=pl 
console-setup/layoutcode=pl userfullname=User Name username=username 
hostname=hostname nfsroot=usb showmounts 
persistent-path=/Ubuntu/16.04x/desktop-amd64 persistent 
iso-scan/filename=/Ubuntu/16.04x/xubuntu-16.04.1-desktop-amd64.iso
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
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/14/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET70WW (1.40 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4291PR5
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET70WW(1.40):bd05/14/2015:svnLENOVO:pn4291PR5:pvrThinkPadX220:rvnLENOVO:rn4291PR5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4291PR5
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

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


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

Title:
  NETDEV WATCHDOG: transmit queue 0 timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel module crash:

  [ 3537.262585] WARNING: CPU: 2 PID: 0 at 
/build/linux-dcxD3m/linux-4.4.0/net/sched/sch_generic.c:306 
dev_watchdog+0x237/0x240()
  [ 3537.262596] NETDEV WATCHDOG: 

[Kernel-packages] [Bug 1605731] Re: Kernel 4.4.0-31 Causes kernel panic at startup

[Seth Forshee]

@Robert: Is there any chance you forgot to install the linux-image-extra
package? That would cause your wifi to fail to 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/1605731

Title:
  Kernel 4.4.0-31 Causes kernel panic at startup

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

Bug description:
  Latest kernel update 4.4.0-31 causes kernel panic at startup. Had to reboot 
with 4.4.0-28 which works fine. I have no idea if it's on all filesystems but 
I'm using btrfs.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robi   3230 F pulseaudio
   /dev/snd/pcmC1D0p:   robi   3230 F...m pulseaudio
   /dev/snd/controlC1:  robi   3230 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d64a307b-b7ea-4308-b997-0587321ff7ea
  InstallationDate: Installed on 2016-07-01 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X750LN
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e075f560-d606-43a0-9cc3-5596a9416d30 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X750LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr201:bd02/19/2014:svnASUSTeKCOMPUTERINC.:pnX750LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750LN:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: X750LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1605276] Re: Please update linux-firmware to add 1.7 broxton firmware

[Robert Hooker]

The 1.157.3 version in xenial-proposed does contain the 1.7 firmware and
it loads properly now on broxton, thanks!

** Tags added: verification-done

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

Title:
  Please update linux-firmware to add 1.7 broxton firmware

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

Bug description:
  There was errata in the 1.6 Broxton DMC firmware currently in linux-
  firmware and it no longer loads on 4.7 and higher based systems, which
  includes i915_bpo now that it has been updated to a 4.7 based
  backport.

  This is the error:
  [2.470468] [drm] Refusing to load old DMC firmware v1.6, please upgrade 
to v1.7 or later [https://01.org/linuxgraphics/intel-linux-graphics-firmwares].
  [2.470476] i915 :00:02.0: Failed to load DMC firmware 
[https://01.org/linuxgraphics/intel-linux-graphics-firmwares], disabling 
runtime power management.

  Pleae cherry-pick http://git.kernel.org/cgit/linux/kernel/git/firmware
  /linux-
  firmware.git/commit/?id=5e976de9e02b55563c28555361a7763bc043f5ec for
  xenial

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 21 10:25:01 2016
  Dependencies:
   
  InstallationDate: Installed on 2016-01-06 (196 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Joseph Salisbury]

Sorry, the arm64 kernels are not built automatically like the other
arches.  I'll build it an post a link shortly.

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1605731] Re: Kernel 4.4.0-31 Causes kernel panic at startup

[Joseph Salisbury]

** Tags removed: kernel-key

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

Title:
  Kernel 4.4.0-31 Causes kernel panic at startup

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

Bug description:
  Latest kernel update 4.4.0-31 causes kernel panic at startup. Had to reboot 
with 4.4.0-28 which works fine. I have no idea if it's on all filesystems but 
I'm using btrfs.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robi   3230 F pulseaudio
   /dev/snd/pcmC1D0p:   robi   3230 F...m pulseaudio
   /dev/snd/controlC1:  robi   3230 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d64a307b-b7ea-4308-b997-0587321ff7ea
  InstallationDate: Installed on 2016-07-01 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X750LN
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e075f560-d606-43a0-9cc3-5596a9416d30 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X750LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr201:bd02/19/2014:svnASUSTeKCOMPUTERINC.:pnX750LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750LN:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: X750LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1548009] Re: ZFS pools should be automatically scrubbed

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
   Importance: Wishlist => Medium

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

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

Title:
  ZFS pools should be automatically scrubbed

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  mdadm automatically checks MD arrays. ZFS should automatically scrub
  pools too. Scrubbing a pool allows ZFS to detect on-disk corruption
  and (when the pool has redundancy) correct it. Note that ZFS does not
  blindly assume the other copy is correct; it will only overwrite bad
  data with data that is known to be good (i.e. it passes the checksum).

  I've attached a debdiff which accomplishes this. It builds and
  installs cleanly.

  The meat of it is the scrub script I've been using on production
  systems, both servers and laptops, and recommending in my Ubuntu root-
  on-ZFS HOWTO, for years, which scrubs all *healthy* pools. If a pool
  is not healthy, scrubbing it is bad for two reasons: 1) It adds a lot
  of disk load which could theoretically lead to another failure. We
  should save that disk load for resilvering. 2) Performance is already
  less on a degraded pool and scrubbing can make that worse, even though
  scrubs are throttled. Arguably, I might be being too conservative
  here, but the marginal benefit of scrubbing a *degraded* pool is
  pretty minimal as pools should not be left degraded for very long.

  The cron.d in this patch scrubs on the second Sunday of the month.
  mdadm scrubs on the first Sunday of the month. This way, if a system
  has both MD and ZFS pools, the load doesn't all happen at the same
  time. If the system doesn't have both types, it shouldn't really
  matter which week. If you'd rather make it the same week as MD, I see
  no problem with that.

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

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

[Kernel-packages] [Bug 1570775] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-07-26 10:29 EDT---
makedumpfile & kdump from xenial-proposed as of today are version 
1.5.9-5ubuntu0.1 and are fixing that problem. Please promote it to 
xenial-updates.

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

Title:
  makekdump should re-exec with cio_ignore on s390x

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed

Bug description:
  [SRU justification]
  kernel crash dump fails to work without the modification.

  [Impact]
  Broken functionality.

  [Fix]
  Add cio_ignore -k -y output to the kexec command.

  [Test Case]
  Follow indication in comment #2 to reproduce. With the fix, kdump will 
function as expected.

  [Regression]
  A regression situation is outlined in comment #16. Newer channel devices may 
not be visible because of the added cio_ignore output. This may be worked 
around with a single command. 

  The resolution outweights this limitation that can be easily worked
  around.

  [Original description of the problem]

  As per
  
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1564475/comments/19

  We should re-exec with cio_ignore lines. As per report there, it
  should result in lowered required crashdump setting.

  Hypothetically, one should be able to test this imperially by lowering
  crashdump memory settings until kdump does not succeed anymore. And
  then generated and append `cio_ignore -k -u` to the
  KDUMP_CMDLINE_APPEND= and see that kdump starts working again with a
  lower memory usage.

  Once this is developed / verified / tested, we should probably SRU
  this back to xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1570775/+subscriptions

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

[Kernel-packages] [Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

[John Mazzie]

This version is working correctly.

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

Title:
  Broadwell ECRC Support missing in Ubuntu

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

Bug description:
  Here is the problem statement from the Dell team:

  When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel
  Quick Assist Card, the memory location that corresponds to ECRC is set
  to 0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.
  This causes the card to not function unless we implement the following
  workaround using setpci.

  “setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for
  the Intel Quick Assit Card.

  We’ve verified the memory location is correct when booting to other
  OSes, such as RHEL 7.2 and Windows Server 2012 R2.

  If there is any information you can give as to why this may be
  occurring in Ubuntu or where we may start to debug when the memory is
  changed, we would appreciate it.

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

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

[Kernel-packages] [Bug 1604310] Re: Plugging DisplayPort in L530 causes WiFi disconnection

[Dawid]

This issue started happening after upgrading to 16.04. I have tested
v4.7-rc7 kernel and its working okay. Adding tag and marking this bug as
confirmed.

** Tags added: kernel-fixed-upstream

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

Title:
  Plugging DisplayPort in L530 causes WiFi disconnection

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I connect running laptop to DisplayPort and wifi is going down (its
  not sending any packages, however the status is still connected for
  2-3 mins).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dawid  1918 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jul 19 10:38:28 2016
  HibernationDevice: RESUME=UUID=2d05849f-f06c-4368-88da-7c7e963ee647
  InstallationDate: Installed on 2015-08-10 (343 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 2478CK2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  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:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (85 days ago)
  dmi.bios.date: 10/14/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G3ETA2WW(2.62)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2478CK2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG3ETA2WW(2.62):bd10/14/2014:svnLENOVO:pn2478CK2:pvrThinkPadL530:rvnLENOVO:rn2478CK2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2478CK2
  dmi.product.version: ThinkPad L530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1598637] Re: Dell Inspiron 5555 touchpad not working

[pranav]

I just purchased the same laptop today, installed Ubuntu 16.04 first
thing and the only glitch was the trackpad.

Following the instructions shared by the reporter, I was able to use the
trackpad.

So, I can confirm that this is indeed a bug and the workaround might be
a bit intimidating for the average user who is looking to use Ubuntu.
Would be really great if this worked out-of-the-box :)

Thanks a ton everyone for the good work. I am glad the reporter shared
the workaround.

Gratitude to everyone who will work on fixing this!

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

Title:
  Dell Inspiron  touchpad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Ubuntu 16.04 64 bit (also Linux Mint and other Ubuntu 16.04
  based distros) on my Dell Inspiron  AMD A10-8700P Radeon R6.

  The touchpad sort-of works for a few seconds (pointer moves but
  cliking fails) and after a while it hangs completely. The USB mouse
  works with no issues though.

  I've found following the steps given here
  http://askubuntu.com/a/632570/55128 works:

  1. Run
  $ sudo -H gedit /etc/default/grub

  In the open window edit line

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  it should look this way

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.nopnp"

  Save file and run

  $ sudo update-grub

  2. Run
  $ echo "blacklist i2c_hid" | sudo tee /etc/modprobe.d/i2c-hid.conf
  $ sudo depmod -a
  $ sudo update-initramfs -u
  $ echo "synaptics_i2c" | sudo tee -a /etc/modules

  3. Reboot.

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

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

[Kernel-packages] [Bug 1602577] Re: [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

[Junien Fridrick]

I can't find an arm64 build in http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.7-rc7/

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

Title:
  [arm64] compute nodes unstable after upgrading from 4.2 to 4.4 kernel

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Hi,

  In order to investigate bug LP#1531768, we upgraded some arm64 compute
  nodes (swirlices) to a 4.4 kernel. I think it made the VMs work
  better, but the hosts became extremely unstable.

  After some time, getting a shell on them would be impossible.
  Connecting on the VSP, you'd get a prompt, and once you typed your
  username and password, you'd see the motd but the shell would never
  spawn.

  Because of these instability issues, all the arm64 compute nodes are
  now back on 4.2. However, we managed to capture "perf record" data
  when a host was failing. I'll attach it to the bug. Perhaps it will
  give you hints as to what we can do to help you troubleshoot this bug
  further.

  Once we have your instructions, we'll happily reboot one (or a few)
  nodes to 4.4 to continue troubleshooting.

  Thanks !
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 12 12:54 seq
   crw-rw 1 root audio 116, 33 Jul 12 12:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro compat_uts_machine=armv7l
  ProcVersionSignature: Ubuntu 4.2.0-41.48~14.04.1-generic 4.2.8-ckt11
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-41-generic N/A
   linux-backports-modules-4.2.0-41-generic  N/A
   linux-firmware1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 4.2.0-41-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1606147] Re: [APL][SAUCE] Slow system response time due to a monitor bug

[Chih-Hsyuan Ho]

** Summary changed:

- [APL][SAUCE] System works slowly due to a monitor bug
+ [APL][SAUCE] Slow system response time due to a monitor bug

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

Title:
  [APL][SAUCE] Slow system response time due to a monitor bug

Status in HWE Next:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  We've found a bug on some Apollo Lake system makes it runs very slow.
  From upstream it is caused by following reason:

  "Monitored cached line may not wake up from mwait on certain Goldmont
  based CPUs. This patch will avoid calling
  current_set_polling_and_test() and thereby not set the TIF_ flag. The
  result is that we'll always send IPIs for wakeups."

  [Fix]

  Upstream already provided a workaround[1] to fix this problem. This
  patches haven't been merged in latest(v4.7) release but already in
  linux-next.

  To fix this issue in Xenial it also needs another commit introduces
  macros use in the workaround:

  commit 970442c599b22ccd644ebfe94d1d303bf6f87c05
  Author: Dave Hansen 
  Date:   Thu Jun 2 17:19:27 2016 -0700

  x86/cpu/intel: Introduce macros for Intel family numbers

  This workaround checks CPU families and certain features, so no
  further regressions is expected

  [1]: https://lkml.org/lkml/2016/7/6/469

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1606147/+subscriptions

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

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

[deb2014]

I installed ubuntu 16.04 on an entirely encrypted disk, including swap.

Could these wakeup crashes be due to this fact ? I will test
hibernation/wakeup from a simple swap partiton.

Meanwhile, if you have any hints, whether what to debug or test, it
would be very much appreciated.

Regards

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1522766] Re: cryptsetup hangs after kernel upgrade to 3.13.0-72.115

[Stefan Bader]

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

Title:
  cryptsetup hangs after kernel upgrade to 3.13.0-72.115

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  After upgrading to the proposed kernel for Trusty (3.13.0-72.115) I
  cannot unlock a luks formatted usb drive. The cryptsetup process seems
  to hang with the following stack:

  [] __synchronize_srcu+0xfe/0x180
  [] synchronize_srcu+0x1d/0x20
  [] __dm_destroy+0x117/0x290
  [] dm_destroy+0x13/0x20
  [] dev_remove+0xde/0x120
  [] ctl_ioctl+0x255/0x500
  [] dm_ctl_ioctl+0x13/0x20
  [] do_vfs_ioctl+0x2e0/0x4c0
  [] SyS_ioctl+0x81/0xa0
  [] system_call_fastpath+0x1a/0x1f
  [] 0x

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

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

[Kernel-packages] [Bug 1313497] Re: USB keyboard unresponsive on fresh install

[Stefan Bader]

I am trying to clean up the bug reports I am assigned to. This one
sounds like it got resolved by changing the preseed in order to get the
correct set of modules installed. Closing it invalid which may sound a
bit harsh but it did not seem to be a bug in the kernel package after
all.

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

** Changed in: linux (Ubuntu)
 Assignee: Stefan Bader (smb) => (unassigned)

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

Title:
  USB keyboard unresponsive on fresh install

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I just did a fresh install of Ubuntu 14.04 LTS onto a machine here.
  During the installation (which is pre-seeded) and in the BIOS, my
  keyboard works flawlessly. However, the moment I boot the machine up,
  I note the keyboard is not operational.  Naturally, I discover this
  *after* buggering up my networking settings.

  The offending package is linux-image-3.13.0-24-generic version
  3.13.0-24.46.

  At one point I noticed an "irq 16: nobody cared" error message.  Due
  to there being no network connectivity, I was unable to capture the
  message displayed.  The output from `dmesg` (see attachment dmesg.txt)
  suggests it does see USB and the keyboard, but plugging the keyboard
  into any of the available ports and pressing keys has no effect on the
  console.

  The machine is a rack-mounted server, intended to run headless.  The
  motherboard is an Intel DQ77MK.  No peripheral cards are installed.

  I've had to do a rebuild already because of this bug (no console
  access then loosing network access pretty much means game over), so I
  can confirm 100% repeatability thus far.

  For interests' sake, the netboot image I used to perform this installation 
was downloaded this morning, and has the following checksums:
  01f16ef8b1f11b29bd0ce940b0aad8ea950f5346  trusty/amd64/linux
  fbb74f8e7d0c1e2ce4b027fc4a0e1aca54cf0fe5  trusty/amd64/initrd.gz

  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 28 14:35 seq
   crw-rw 1 root audio 116, 33 Apr 28 14:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=c087705d-cbe4-4546-bfcd-436edfe047c8
  IwConfig: Error: [Errno 2] No such file or directory
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=8c972a72-4f98-4043-b9a1-d409f02d6dbc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/20/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: MKQ7710H.86A.0054.2012.1120.1444
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DQ77MK
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39642-500
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrMKQ7710H.86A.0054.2012.1120.1444:bd11/20/2012:svn:pn:pvr:rvnIntelCorporation:rnDQ77MK:rvrAAG39642-500:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1576564] Re: Xen 32bit dom0 on 64bit hypervisor: bad page flags

[Stefan Bader]

Fix released for Wily in Ubuntu-4.2.0-42.49~99.

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: Stefan Bader (smb) => (unassigned)

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

Title:
  Xen 32bit dom0 on 64bit hypervisor: bad page flags

Status in linux package in Ubuntu:
  Fix Released
Status in xen package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in xen source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in xen source package in Xenial:
  Invalid

Bug description:
  This problem is a mix between running certain versions of 32bit Linux
  kernel dom0 on certain versions of 64bit Xen hypervisor, combined with
  certain memory clamping settings (dom0_mem=xM, without setting the max
  limit).

  Xen 4.4.2 + Linux 3.13.x
  Xen 4.5.0 + linux 3.19.x
  Xen 4.6.0 + linux 4.0.x
  Xen 4.6.0 + linux 4.1.x
   -> all boot without messages
  Xen 4.5.1 + Linux 4.2.x
  Xen 4.6.0 + Linux 4.2.x
  Xen 4.6.0 + Linux 4.3.x
   * dom0_mem 512M, 4096M, or unlimited
     -> boot without messages
   * dom0_mem between 1024M and 3072M (inclusive)
     -> bad page messages (but finishes boot)
  Xen 4.6.0 + Linux 4.4.x
  Xen 4.6.0 + Linux 4.5.x
  Xen 4.6.0 + Linux 4.6-rc6
   The boot for 512M,4096M, and unlimited looks good as well. Though trying to
   start a domU without dom0_mem set caused a crash when ballooning (but I
   think this should be a seperate bug)
   Using a dom0_mem range between 1G and 3G it looks like still producing the
   bad page flags bug message and additionally panicking + reboot.

  The bad page bug generally looks like this (the pfn numbers seem to be
  towards the end of the allocated range.

  [8.980150] BUG: Bad page state in process swapper/0  pfn:7fc22
  [8.980238] page:f4566550 count:0 mapcount:0 mapping:  (null) index:0x0
  [8.980328] flags: 0x7000400(reserved)
  [8.980486] page dumped because: PAGE_FLAGS_CHECK_AT_PREP flag set
  [8.980575] bad because of flags:
  [8.980688] flags: 0x400(reserved)
  [8.980844] Modules linked in:
  [8.980960] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GB   
4.2.0-19-
  generic #23-Ubuntu
  [8.981084] Hardware name: Supermicro H8SGL/H8SGL, BIOS 3.0
08/31/2012
  [8.981177]  c1a649a7 23e07668  e9cafce4 c175e501 f4566550 
e9cafd08 c
  1166897
  [8.981608]  c19750a4 e9d183ec 0007fc22 007f c1975630 c1978e86 
0001 e
  9cafd74
  [8.982074]  c1169f83 0002 0141 0004a872 c1af3644  
ee44bce4 e
  e44bce4
  [8.982506] Call Trace:
  [8.982582]  [] dump_stack+0x41/0x52
  [8.982666]  [] bad_page+0xb7/0x110
  [8.982749]  [] get_page_from_freelist+0x2d3/0x610
  [8.982838]  [] __alloc_pages_nodemask+0x153/0x910
  [8.982926]  [] ? find_entry.isra.13+0x52/0x90
  [8.983013]  [] ? kmem_cache_alloc_trace+0x175/0x1e0
  [8.983102]  [] ? 
__raw_callee_save___pv_queued_spin_unlock+0x6/0x10
  [8.983223]  [] ? __kmalloc+0x21d/0x240
  [8.983308]  [] __vmalloc_node_range+0x10e/0x210
  [8.983433]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983518]  [] __vmalloc_node+0x66/0x70
  [8.983604]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983689]  [] __vmalloc+0x34/0x40
  [8.983773]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983859]  [] bpf_prog_alloc+0x37/0xa0
  [8.983944]  [] bpf_prog_create+0x2c/0x90
  [8.984034]  [] ? bsp_pm_check_init+0x11/0x11
  [8.984121]  [] ptp_classifier_init+0x2b/0x44
  [8.984207]  [] sock_init+0x7c/0x83
  [8.984291]  [] do_one_initcall+0xaa/0x200
  [8.984376]  [] ? bsp_pm_check_init+0x11/0x11
  [8.984463]  [] ? repair_env_string+0x12/0x54
  [8.984551]  [] ? kernel_init_freeable+0x126/0x1d9
  [8.984726]  [] kernel_init+0x10/0xe0
  [8.984846]  [] ? schedule_tail+0x11/0x50
  [8.984932]  [] ret_from_kernel_thread+0x21/0x30
  [8.985019]  [] ? rest_init+0x70/0x70

  break-fix: 92923ca3aacef63 4b50bcc7eda4d3cc9e3f2a0aa60e590fedf728c5

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

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

[Kernel-packages] [Bug 1576564] Re: Xen 32bit dom0 on 64bit hypervisor: bad page flags

[Stefan Bader]

Fix released for Xenial in Ubuntu-4.4.0-25.44~37.

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

** Changed in: xen (Ubuntu)
 Assignee: Stefan Bader (smb) => (unassigned)

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

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

Title:
  Xen 32bit dom0 on 64bit hypervisor: bad page flags

Status in linux package in Ubuntu:
  Fix Released
Status in xen package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in xen source package in Wily:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in xen source package in Xenial:
  Invalid

Bug description:
  This problem is a mix between running certain versions of 32bit Linux
  kernel dom0 on certain versions of 64bit Xen hypervisor, combined with
  certain memory clamping settings (dom0_mem=xM, without setting the max
  limit).

  Xen 4.4.2 + Linux 3.13.x
  Xen 4.5.0 + linux 3.19.x
  Xen 4.6.0 + linux 4.0.x
  Xen 4.6.0 + linux 4.1.x
   -> all boot without messages
  Xen 4.5.1 + Linux 4.2.x
  Xen 4.6.0 + Linux 4.2.x
  Xen 4.6.0 + Linux 4.3.x
   * dom0_mem 512M, 4096M, or unlimited
     -> boot without messages
   * dom0_mem between 1024M and 3072M (inclusive)
     -> bad page messages (but finishes boot)
  Xen 4.6.0 + Linux 4.4.x
  Xen 4.6.0 + Linux 4.5.x
  Xen 4.6.0 + Linux 4.6-rc6
   The boot for 512M,4096M, and unlimited looks good as well. Though trying to
   start a domU without dom0_mem set caused a crash when ballooning (but I
   think this should be a seperate bug)
   Using a dom0_mem range between 1G and 3G it looks like still producing the
   bad page flags bug message and additionally panicking + reboot.

  The bad page bug generally looks like this (the pfn numbers seem to be
  towards the end of the allocated range.

  [8.980150] BUG: Bad page state in process swapper/0  pfn:7fc22
  [8.980238] page:f4566550 count:0 mapcount:0 mapping:  (null) index:0x0
  [8.980328] flags: 0x7000400(reserved)
  [8.980486] page dumped because: PAGE_FLAGS_CHECK_AT_PREP flag set
  [8.980575] bad because of flags:
  [8.980688] flags: 0x400(reserved)
  [8.980844] Modules linked in:
  [8.980960] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GB   
4.2.0-19-
  generic #23-Ubuntu
  [8.981084] Hardware name: Supermicro H8SGL/H8SGL, BIOS 3.0
08/31/2012
  [8.981177]  c1a649a7 23e07668  e9cafce4 c175e501 f4566550 
e9cafd08 c
  1166897
  [8.981608]  c19750a4 e9d183ec 0007fc22 007f c1975630 c1978e86 
0001 e
  9cafd74
  [8.982074]  c1169f83 0002 0141 0004a872 c1af3644  
ee44bce4 e
  e44bce4
  [8.982506] Call Trace:
  [8.982582]  [] dump_stack+0x41/0x52
  [8.982666]  [] bad_page+0xb7/0x110
  [8.982749]  [] get_page_from_freelist+0x2d3/0x610
  [8.982838]  [] __alloc_pages_nodemask+0x153/0x910
  [8.982926]  [] ? find_entry.isra.13+0x52/0x90
  [8.983013]  [] ? kmem_cache_alloc_trace+0x175/0x1e0
  [8.983102]  [] ? 
__raw_callee_save___pv_queued_spin_unlock+0x6/0x10
  [8.983223]  [] ? __kmalloc+0x21d/0x240
  [8.983308]  [] __vmalloc_node_range+0x10e/0x210
  [8.983433]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983518]  [] __vmalloc_node+0x66/0x70
  [8.983604]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983689]  [] __vmalloc+0x34/0x40
  [8.983773]  [] ? bpf_prog_alloc+0x37/0xa0
  [8.983859]  [] bpf_prog_alloc+0x37/0xa0
  [8.983944]  [] bpf_prog_create+0x2c/0x90
  [8.984034]  [] ? bsp_pm_check_init+0x11/0x11
  [8.984121]  [] ptp_classifier_init+0x2b/0x44
  [8.984207]  [] sock_init+0x7c/0x83
  [8.984291]  [] do_one_initcall+0xaa/0x200
  [8.984376]  [] ? bsp_pm_check_init+0x11/0x11
  [8.984463]  [] ? repair_env_string+0x12/0x54
  [8.984551]  [] ? kernel_init_freeable+0x126/0x1d9
  [8.984726]  [] kernel_init+0x10/0xe0
  [8.984846]  [] ? schedule_tail+0x11/0x50
  [8.984932]  [] ret_from_kernel_thread+0x21/0x30
  [8.985019]  [] ? rest_init+0x70/0x70

  break-fix: 92923ca3aacef63 4b50bcc7eda4d3cc9e3f2a0aa60e590fedf728c5

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

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

[Kernel-packages] [Bug 1410363] Re: partition table updates require a reboot

[Stefan Bader]

No updates for more than a year. Closing as invalid.

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

** Changed in: linux (Ubuntu)
 Assignee: Stefan Bader (smb) => (unassigned)

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

Title:
  partition table updates require a reboot

Status in linux package in Ubuntu:
  Invalid

Bug description:
  We're seeing a problem in automated testing of ceph and swift in that
  partition tables always require a reboot:

  2015-01-13 16:50:07 INFO mon-relation-changed Setting name!
  2015-01-13 16:50:07 INFO mon-relation-changed partNum is 1
  2015-01-13 16:50:07 INFO mon-relation-changed REALLY setting name!
  2015-01-13 16:50:07 INFO mon-relation-changed Warning: The kernel is still 
using the old partition table.
  2015-01-13 16:50:07 INFO mon-relation-changed The new table will be used at 
the next reboot.
  2015-01-13 16:50:07 INFO mon-relation-changed The operation has completed 
successfully.
  2015-01-13 16:50:09 INFO mon-relation-changed Setting name!
  2015-01-13 16:50:09 INFO mon-relation-changed partNum is 0
  2015-01-13 16:50:09 INFO mon-relation-changed REALLY setting name!
  2015-01-13 16:50:09 INFO mon-relation-changed Warning: The kernel is still 
using the old partition table.
  2015-01-13 16:50:09 INFO mon-relation-changed The new table will be used at 
the next reboot.
  2015-01-13 16:50:09 INFO mon-relation-changed The operation has completed 
successfully.
  2015-01-13 16:50:09 INFO mon-relation-changed mkfs.xfs: cannot open 
/dev/vdb1: Device or resource busy
  2015-01-13 16:50:09 INFO mon-relation-changed ceph-disk: Error: Command 
'['/sbin/mkfs', '-t', 'xfs', '-f', '-i', 'size=2048', '--', '/dev/vdb1']' 
returned non-zero exit status 1
  2015-01-13 16:50:09 ERROR juju-log mon:1: Unable to initialize device: 
/dev/vdb
  2015-01-13 16:50:09 INFO mon-relation-changed Traceback (most recent call 
last):
  2015-01-13 16:50:09 INFO mon-relation-changed   File 
"/var/lib/juju/agents/unit-ceph-0/charm/hooks/mon-relation-changed", line 381, 
in 
  2015-01-13 16:50:09 INFO mon-relation-changed hooks.execute(sys.argv)
  2015-01-13 16:50:09 INFO mon-relation-changed   File 
"/var/lib/juju/agents/unit-ceph-0/charm/hooks/charmhelpers/core/hookenv.py", 
line 528, in execute
  2015-01-13 16:50:09 INFO mon-relation-changed self._hooks[hook_name]()
  2015-01-13 16:50:09 INFO mon-relation-changed   File 
"/var/lib/juju/agents/unit-ceph-0/charm/hooks/mon-relation-changed", line 217, 
in mon_relation
  2015-01-13 16:50:09 INFO mon-relation-changed reformat_osd(), 
config('ignore-device-errors'))
  2015-01-13 16:50:09 INFO mon-relation-changed   File 
"/var/lib/juju/agents/unit-ceph-0/charm/hooks/ceph.py", line 327, in osdize
  2015-01-13 16:50:09 INFO mon-relation-changed osdize_dev(dev, osd_format, 
osd_journal, reformat_osd, ignore_errors)
  2015-01-13 16:50:09 INFO mon-relation-changed   File 
"/var/lib/juju/agents/unit-ceph-0/charm/hooks/ceph.py", line 375, in osdize_dev
  2015-01-13 16:50:09 INFO mon-relation-changed raise e
  2015-01-13 16:50:09 INFO mon-relation-changed subprocess.CalledProcessError: 
Command '['ceph-disk-prepare', '--fs-type', u'xfs', '--zap-disk', u'/dev/vdb']' 
returned non-zero exit status 1

  this is obviously blocking deployment and subsequent testing; previous
  Ubuntu releases have been OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: User Name 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Jan 13 16:51:36 2015
  Ec2AMI: ami-006e
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-8-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-8-generic N/A
   linux-backports-modules-3.18.0-8-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: 

[Kernel-packages] [Bug 1179774] Re: ipmi kernel modules not detecting OCPv3 AMD Roadrunner BMC

[Stefan Bader]

Setting this to fix released but I do not know for sure. Sounds like it
was and this was back in Trusty, so I assume there would have been
updates if this did not get out.

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

** Changed in: linux (Ubuntu)
 Assignee: Stefan Bader (smb) => (unassigned)

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

Title:
  ipmi kernel modules not detecting OCPv3 AMD Roadrunner BMC

Status in The Open Compute Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  In order for the ipmi kernel modules to work on the OCPv3 AMD
  Roadrunner machine I need to run the attached script.

  Here is the output of the device information:

  test@precise2:~$ PCIADDRESS=`lspci | grep 16b9 | awk '{print $1}'`

  test@precise2:~# echo "BMC PCI Address is "$PCIADDRESS
  BMC PCI Address is 02:00.6

  test@precise2:~$ lspci -s $PCIADDRESS -vvv 
  02:00.6 IPMI SMIC interface: Broadcom Corporation Device 16b9 (prog-if 01)
Subsystem: Broadcom Corporation Device 96b9
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ipmi_si
Kernel modules: ipmi_si

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

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

[Kernel-packages] [Bug 1606452] [NEW] Self-built kernel module does not load after upgrade

[David Venhoek]

Public bug reported:

After the kernel upgrade from 3.13.0-91-generic to 3.13.0-92-generic,
the kernel modules I built for the MEDIATEK Corp. MT7630e 802 in my
laptop wont load anymore (hence no wifi), but they still do when using
the startup menu to boot 3.13.0-91-generic.

Problematic kernel version: 3.13.0-92-generic
Known good kernel version: 3.13.0.91-generic
Ubuntu version: Xubuntu 14.04.4 LTS

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

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

Title:
  Self-built kernel module does not load after upgrade

Status in linux-signed package in Ubuntu:
  New

Bug description:
  After the kernel upgrade from 3.13.0-91-generic to 3.13.0-92-generic,
  the kernel modules I built for the MEDIATEK Corp. MT7630e 802 in my
  laptop wont load anymore (hence no wifi), but they still do when using
  the startup menu to boot 3.13.0-91-generic.

  Problematic kernel version: 3.13.0-92-generic
  Known good kernel version: 3.13.0.91-generic
  Ubuntu version: Xubuntu 14.04.4 LTS

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

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