[Kernel-packages] [Bug 1705378] Re: ideapad_laptop don't support v310-14isk

[Bin Li]

Verified on zesty, this issue was fixed.
$ uname -an
Linux u-Lenovo-V310-14ISK 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: ideapad_bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: yes
2: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no


$ uname -an
Linux u-Lenovo-V310-14ISK 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:28 
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no


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

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

Title:
  ideapad_laptop don't support v310-14isk

Status in HWE Next:
  Fix Committed
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed

Bug description:
  we found the wireless and bluetooth can't work, the device had driver
  already, just wereo blocked by ideapad_laptop module. After remove it,
  it works fine.

  $ sudo rfkill list
  0: ideapad_wlan: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
  1: ideapad_bluetooth: Bluetooth
  Soft blocked: no
  Hard blocked: yes
  2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
  3: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

  SRU Justification
  =

  [Impact]
  wireless and bluetooth were blocked by ideapad_laptop module.

  [Fix]
  Fix it by adding those models to no_hw_rfkill_list.

  [Test Case]
  Wireless and BT works fine.

  [Regression Potential]
  This patch add several dmi entry in struct.
  Regression Potential is low.

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

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

[Kernel-packages] [Bug 842560] Re: bnx2 firmware missing

[Kai-Heng Feng]

@Gus,

Please file a new bug report.

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

Title:
  bnx2 firmware missing

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project oneiric series:
  Fix Released
Status in OEM Priority Project precise series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Fix Released
Status in linux source package in Oneiric:
  Invalid
Status in udev source package in Oneiric:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in udev source package in Precise:
  Fix Released

Bug description:
  SRU justification:
  udev in Ubuntu 11.10 has regressed support for certain hardware 
configurations, resulting in firmware failing to be loaded at boot time due to 
a race condition when shutting down udev in the initramfs.  This causes network 
interfaces to fail to come up in a usable state on systems previously 
supported, and also causes long boot-time delays on these same systems.

  Regression potential:
  The nature of the fix introduces the possibility that some systems that are 
not affected by this bug will have their boot slowed down as a result of udev 
being forced to process more events before it's able to exit.  However, since 
only events with a timeout requirement will actually be dispatched for 
processing, the impact here should be minimal.

  Test case:
  1. boot oneiric on a system such as a Dell PowerEdge 2950 which has two NICs 
that use the bnx2 driver and require the bnx2-mips-06-6.2.1.fw firmware
  2. observe that the boot has a 60-second delay and that there is an error in 
dmesg that the firmware fails to load for one of the NICs
  3. install the udev package from oneiric-proposed
  4. reboot 6 times to confirm that the system now boots up with no delay and 
that there is no error in dmesg even after multiple reboots

  Installing the latest Beta 1 of Ubuntu 11.10 (downloaded iso on
  09-06-2011) fails after the first reboot with this error:

  bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.1.fw"
  udevd[107]: '/sbin/modprobe -bv 
pci:v14E4d164Csv1028sd01B2bc02sc00i00' [172] terminated by 
signal 9 (Killed)

  Earlier stable versions of Ubuntu Server (11.04) work fine on this
  machine.

  For further investigations i collected some additional information for
  you. (Attachments)

  Are there any other needed information i can supply?

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/842560/+subscriptions

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

[Kernel-packages] [Bug 1708372] Re: The Precision Touchpad(PTP) button sends incorrect event code

[Shrirang Bagul]

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

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

Title:
  The Precision Touchpad(PTP) button sends incorrect event code

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  The touchpad right button should send 273(BTN_RIGHT),
  and the left button should send 272(BTN_LEFT)
  But the touchpad right button sends 274(BTN_MIDDLE),
  and the left button sends 273 (BTN_RIGHT)

  [Fix]
  The fix is pretty simple to just decrease the event code by 1.

  [Test Case]
  Verified on the machine has this issue, and confirm this patch works.

  [Regression Potential]
  The patch has strict if statement, so it won't affect other touchpad devices.
  And no more rework on this code snip after this commit.

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

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

[Kernel-packages] [Bug 1712218] Re: Docking station ethernet port no longer works

[Kai-Heng Feng]

I guess it works on Zesty?

Download and install Linux 4.10 from [1]

If 4.10 also has this issue, try 4.9, 4.8, ... in descending order.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline

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

Title:
  Docking station ethernet port no longer works

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded to artful (xenial -> zesty -> artful).

  Now when I plug in my docking station I see this[1] in syslog and no
  network device appear.

  The docking station is a ThinkPad OneLink+ Dock, my laptop a ThinkPad
  X1 Carbon 4th gen.

  [1] http://pastebin.ubuntu.com/25365943/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  leecj2 9255 F pulseaudio
   /dev/snd/controlC1:  leecj2 9255 F pulseaudio
   /dev/snd/controlC0:  leecj2 9255 F pulseaudio
  CurrentDesktop: i3
  Date: Tue Aug 22 11:45:28 2017
  HibernationDevice: RESUME=UUID=82a0abb2-5063-47d1-988e-2d57f6a2fe15
  InstallationDate: Installed on 2017-03-06 (168 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 20FBCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f951cac3-6644-45d2-aada-c8542004c252 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-08-15 (6 days ago)
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET47W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET47W(1.21):bd11/28/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1701486] Re: System brightness slider doesn't work any more

[Kai-Heng Feng]

Remove all the kernel parameters and check if this issue still happens.

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

Title:
  System brightness slider doesn't work any more

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Update from 4.10.0-24 to 26 broke it. Using Linux Mint 18.1 x64
  Cinnamon.

  Changing /sys/class/backlight/intel_backlight/brightness manually
  works though.

  $ cat /proc/version_signature
  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 07)
Subsystem: Dell Skylake Host Bridge/DRAM Registers [1028:0706]
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: skl_uncore

  00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) 
[8086:1901] (rev 07) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Intel Corporation Skylake PCIe Controller 
(x16) [8086:2015]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218  Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled+ CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending+ InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:01.1 PCI bridge [0604]: Intel Corporation

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1660052

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

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

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

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

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

Title:
  Disappearing text in windows on waking

Status in ubuntu-mate:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu Mate 16.4 on a Macbook Air. Every once in a while,
  when I wake my laptop from sleep, the text in the windows and menus is
  mostly missing, shown in this attached image. It's only fixed by
  rebooting or restarting the X server. Sometimes mousing over the
  buttons restores the text on that button for a sec, sometimes makes it
  disappear.

  Ubuntu Mate 16.04.1, LTS x86_64
  Mate version 1.12.1

  Apologies if I'm missing something about this or it's already been
  reported - I'm no pro, but haven't found anything so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1660052/+subscriptions

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

[Kernel-packages] [Bug 1660052] Re: Disappearing text in windows on waking

[Martin Wimpress]

I can't reproduce this on the hardware I have available.

** Changed in: ubuntu-mate
   Status: New => Incomplete

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

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

Title:
  Disappearing text in windows on waking

Status in ubuntu-mate:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  I am running Ubuntu Mate 16.4 on a Macbook Air. Every once in a while,
  when I wake my laptop from sleep, the text in the windows and menus is
  mostly missing, shown in this attached image. It's only fixed by
  rebooting or restarting the X server. Sometimes mousing over the
  buttons restores the text on that button for a sec, sometimes makes it
  disappear.

  Ubuntu Mate 16.04.1, LTS x86_64
  Mate version 1.12.1

  Apologies if I'm missing something about this or it's already been
  reported - I'm no pro, but haven't found anything so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1660052/+subscriptions

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

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1633597

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

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

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

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

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

Title:
  Function keys controlling volume don't work perfectly

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my laptop (Medion P7643), the function keys that control volume ('volume 
up', 'volume down' and 'mute') don't work properly. There are no steps in 
volume, only completely loud or mute.
  This bug is also in Linux Mint 18, which I used before.

  My computer:
  Medion P7643
  Intel i5 6200U
  Nvidia GTX 950m

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1633597/+subscriptions

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

[Kernel-packages] [Bug 1633597] Re: Function keys controlling volume don't work perfectly

[Martin Wimpress]

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

** Changed in: ubuntu-mate
   Status: New => Invalid

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

Title:
  Function keys controlling volume don't work perfectly

Status in ubuntu-mate:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my laptop (Medion P7643), the function keys that control volume ('volume 
up', 'volume down' and 'mute') don't work properly. There are no steps in 
volume, only completely loud or mute.
  This bug is also in Linux Mint 18, which I used before.

  My computer:
  Medion P7643
  Intel i5 6200U
  Nvidia GTX 950m

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1633597/+subscriptions

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

[Kernel-packages] [Bug 1701423] Re: APST quirk needed for Samsung 256GB NVMe drive

[Josh Lilly]

The 16.04 HWE kernel has been upgraded to 4.10.x, and after a few weeks
of use this bug has not occurred. Currently I'm using 4.10.0-32-generic.

I guess this can be closed off as 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/1701423

Title:
  APST quirk needed for Samsung 256GB NVMe drive

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This bug is a follow on from a previously fixed bug.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184

  The nature of this bug is identical to the previously reported bug, however 
it also affects 256GB drives as well.
  The wording at the start is a bit confusing, as it states that the 256GB 
drive already has a quirk added. Following the trail back a little, however, 
shows that a fix for high power drain was introduced, which then caused the 
NVMe controller lockups and system hangs.

  I am running Ubuntu 16.04 with HWE kernel [4.8.x, yakkety] on a Dell XPS15 
9550 with a Samsung 256GB NVMe SSD.
  This bug commenced with the kernel linux (4.8.0-47.50) yakkety, with the 
specific change found at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602

  **

  
  Here is my output of nvme-cli

  **
  nvme list

  Node SN Model Version Namespace Usage Format FW Rev
    
  - 
--  
  /dev/nvme0n1 S29NNXAGC38399 PM951 NVMe SAMSUNG 256GB 1.1 1 201.30 GB / 256.06 
GB 512 B + 0 B BXV77D0Q

  nvme id-ctrl /dev/nvme0n1

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S29NNXAGC38399
  mn : PM951 NVMe SAMSUNG 256GB
  fr : BXV77D0Q
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 5
  cntlid : 1
  ver : 0
  rtd3r : 0
  rtd3e : 0
  oaes : 0
  oacs : 0x17
  acl : 7
  aerl : 3
  frmw : 0x6
  lpa : 0
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 0
  cctemp : 0
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 0
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.00W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:4.20W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:3.10W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-

  

  Also, as requested:

  lspci -nn

  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 07)
  00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) 
[8086:1901] (rev 07)
  00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake 
Integrated Graphics [8086:191b] (rev 06)
  00:04.0 Signal processing controller [1180]: Intel Corporation Skylake 
Processor Thermal Subsystem [8086:1903] (rev 07)
  00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller [8086:a12f] (rev 31)
  00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-H Thermal subsystem [8086:a131] (rev 31)
  00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-H LPSS I2C Controller #0 [8086:a160] (rev 31)
  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-H LPSS I2C Controller #1 [8086:a161] (rev 31)
  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H 
CSME HECI #1 [8086:a13a] (rev 31)
  00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA 
Controller [AHCI mode] [8086:a103] (rev 31)
  00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #1 [8086:a110] (rev f1)
  00:1c.1 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #2 [8086:a111] (rev f1)
  00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #9 [8086:a118] (rev f1)
  00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #13 [8086:a11c] (rev f1)
  00:1d.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #15 [8086:a11e] (rev f1)
  00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller 
[8086:a14e] (rev 31)
  00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC 
[8086:a121] (rev 31)
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio 
[8086:a170] (rev 31)
  00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] 
(rev 31)
  01:00.0 3D control

[Kernel-packages] [Bug 1701423] Re: APST quirk needed for Samsung 256GB NVMe drive

[Josh Lilly]

16.04 HWE has moved to 4.10.x kernel. Bug does not appear to be present
after several weeks of usage.

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

Title:
  APST quirk needed for Samsung 256GB NVMe drive

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  This bug is a follow on from a previously fixed bug.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184

  The nature of this bug is identical to the previously reported bug, however 
it also affects 256GB drives as well.
  The wording at the start is a bit confusing, as it states that the 256GB 
drive already has a quirk added. Following the trail back a little, however, 
shows that a fix for high power drain was introduced, which then caused the 
NVMe controller lockups and system hangs.

  I am running Ubuntu 16.04 with HWE kernel [4.8.x, yakkety] on a Dell XPS15 
9550 with a Samsung 256GB NVMe SSD.
  This bug commenced with the kernel linux (4.8.0-47.50) yakkety, with the 
specific change found at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602

  **

  
  Here is my output of nvme-cli

  **
  nvme list

  Node SN Model Version Namespace Usage Format FW Rev
    
  - 
--  
  /dev/nvme0n1 S29NNXAGC38399 PM951 NVMe SAMSUNG 256GB 1.1 1 201.30 GB / 256.06 
GB 512 B + 0 B BXV77D0Q

  nvme id-ctrl /dev/nvme0n1

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S29NNXAGC38399
  mn : PM951 NVMe SAMSUNG 256GB
  fr : BXV77D0Q
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 5
  cntlid : 1
  ver : 0
  rtd3r : 0
  rtd3e : 0
  oaes : 0
  oacs : 0x17
  acl : 7
  aerl : 3
  frmw : 0x6
  lpa : 0
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 0
  cctemp : 0
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 0
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.00W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:4.20W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:3.10W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-

  

  Also, as requested:

  lspci -nn

  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 07)
  00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) 
[8086:1901] (rev 07)
  00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake 
Integrated Graphics [8086:191b] (rev 06)
  00:04.0 Signal processing controller [1180]: Intel Corporation Skylake 
Processor Thermal Subsystem [8086:1903] (rev 07)
  00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller [8086:a12f] (rev 31)
  00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-H Thermal subsystem [8086:a131] (rev 31)
  00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-H LPSS I2C Controller #0 [8086:a160] (rev 31)
  00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise 
Point-H LPSS I2C Controller #1 [8086:a161] (rev 31)
  00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H 
CSME HECI #1 [8086:a13a] (rev 31)
  00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA 
Controller [AHCI mode] [8086:a103] (rev 31)
  00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #1 [8086:a110] (rev f1)
  00:1c.1 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #2 [8086:a111] (rev f1)
  00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #9 [8086:a118] (rev f1)
  00:1d.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #13 [8086:a11c] (rev f1)
  00:1d.6 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root 
Port #15 [8086:a11e] (rev f1)
  00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller 
[8086:a14e] (rev 31)
  00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC 
[8086:a121] (rev 31)
  00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD Audio 
[8086:a170] (rev 31)
  00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] 
(rev 31)
  01:00.0 3D controller [0302]: NVIDIA 

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Upgrade from 14.04 -> 16.04; then tell me “not an official package”

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrade from 14.04 -> 16.04; then tell me “not an official ubuntu
  package, please remove any third party package and try again”.

  Yezheng Li

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-83.106~14.04.1-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  acer   1999 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 22 00:20:45 2017
  HibernationDevice: RESUME=UUID=e6987287-b0d4-4bec-b494-e45569495b56
  InstallationDate: Installed on 2016-02-16 (553 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire 4752
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=UUID=2f528c1d-3e13-470f-adfa-fd59b30a9619 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-08-22 (0 days ago)
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.17
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire 4752
  dmi.board.vendor: Acer
  dmi.board.version: V2.17
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.17
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.17:bd02/14/2012:svnAcer:pnAspire4752:pvrV2.17:rvnAcer:rnAspire4752:rvrV2.17:cvnAcer:ct9:cvrV2.17:
  dmi.product.name: Aspire 4752
  dmi.product.version: V2.17
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1712243] Re: Upgrade from 14.04 -> 16.04; then tell me “not an official package”

[Steve Beattie]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Upgrade from 14.04 -> 16.04; then tell me “not an official package”

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrade from 14.04 -> 16.04; then tell me “not an official ubuntu
  package, please remove any third party package and try again”.

  Yezheng Li

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-83.106~14.04.1-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  acer   1999 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug 22 00:20:45 2017
  HibernationDevice: RESUME=UUID=e6987287-b0d4-4bec-b494-e45569495b56
  InstallationDate: Installed on 2016-02-16 (553 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire 4752
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=UUID=2f528c1d-3e13-470f-adfa-fd59b30a9619 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-83-generic N/A
   linux-backports-modules-4.4.0-83-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-08-22 (0 days ago)
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.17
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire 4752
  dmi.board.vendor: Acer
  dmi.board.version: V2.17
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.17
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.17:bd02/14/2012:svnAcer:pnAspire4752:pvrV2.17:rvnAcer:rnAspire4752:rvrV2.17:cvnAcer:ct9:cvrV2.17:
  dmi.product.name: Aspire 4752
  dmi.product.version: V2.17
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1698965] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 - IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]

[Benjamin]

I've seen the very same bug again today, with Linux 4.10.0-32-generic
#36-Ubuntu.

This happened again when there were continuous writes to a large btrfs array 
with high CPU load (bitcoin-qt).
The crash seems to be related to the GPU driver though. And even though X 
crashes/freezes, Apps keep running (musik keeps playing).

Since I don't know how to reproduce this error, I don't know whether I
can say for sure whether an upstream kernel would fix the issue.

[ 8916.254610] BUG: unable to handle kernel NULL pointer dereference at 
0018
[ 8916.254666] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915]
[ 8916.254683] PGD 0 

[ 8916.254696] Oops: 0002 [#1] SMP
[ 8916.254707] Modules linked in: bnep pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) xt_multiport iptable_filter intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm binfmt_misc 
snd_usb_audio nls_iso8859_1 irqbypass crct10dif_pclmul snd_hda_codec_hdmi 
crc32_pclmul ghash_clmulni_intel snd_usbmidi_lib snd_seq_midi 
snd_seq_midi_event snd_hda_codec_realtek dm_crypt snd_hda_codec_generic pcbc 
snd_rawmidi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq 
aesni_intel aes_x86_64 crypto_simd glue_helper uvcvideo cryptd 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 intel_cstate input_leds 
snd_seq_device videobuf2_core joydev intel_rapl_perf snd_timer serio_raw 
videodev snd media soundcore shpchp mei_me mei intel_pch_thermal hci_uart btbcm 
btqca btintel
[ 8916.254868]  bluetooth acpi_als kfifo_buf intel_lpss_acpi industrialio 
intel_lpss mac_hid acpi_pad parport_pc ppdev lp parport ip_tables x_tables 
autofs4 btrfs xor raid6_pq hid_generic usbhid mxm_wmi i915 i2c_algo_bit 
drm_kms_helper syscopyarea sysfillrect e1000e ptp pps_core sysimgblt 
fb_sys_fops drm ahci libahci wmi video pinctrl_sunrisepoint pinctrl_intel 
i2c_hid hid fjes
[ 8916.254949] CPU: 0 PID: 6098 Comm: chrome Tainted: G   OE   
4.10.0-32-generic #36-Ubuntu
[ 8916.254982] Hardware name: To Be Filled By O.E.M. To Be Filled By 
O.E.M./B150M Pro4S/D3, BIOS P7.00 12/06/2016
[ 8916.255010] task: 8964e23eab00 task.stack: b58f82a08000
[ 8916.255040] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 
[i915]
[ 8916.255058] RSP: 0018:b58f82a0b880 EFLAGS: 00010246
[ 8916.255070] RAX: 8964bf5a3000 RBX: 0003 RCX: 0003
[ 8916.255086] RDX:  RSI: 89655c51a000 RDI: 89655d03
[ 8916.255103] RBP: b58f82a0b8d8 R08:  R09: 
[ 8916.255119] R10:  R11: 0001 R12: 89638ddf
[ 8916.255136] R13: 896498c78550 R14: fab5e000 R15: 4000
[ 8916.255153] FS:  7f83e0324b00() GS:89656dc0() 
knlGS:
[ 8916.255172] CS:  0010 DS:  ES:  CR0: 80050033
[ 8916.255185] CR2: 0018 CR3: 000167932000 CR4: 002406f0
[ 8916.255203] Call Trace:
[ 8916.255224]  gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915]
[ 8916.255240]  ? swiotlb_map_sg_attrs+0x49/0x110
[ 8916.255261]  gen8_alloc_va_range+0x23d/0x470 [i915]
[ 8916.255287]  i915_vma_bind+0x7e/0x170 [i915]
[ 8916.255308]  __i915_vma_do_pin+0x2a5/0x450 [i915]
[ 8916.255337]  i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915]
[ 8916.255368]  i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915]
[ 8916.255400]  i915_gem_do_execbuffer.isra.38+0x4ca/0x15c0 [i915]
[ 8916.255419]  ? reservation_object_get_fences_rcu+0x27d/0x290
[ 8916.255452]  ? shmem_pwrite+0xca/0xe4 [i915]
[ 8916.255482]  i915_gem_execbuffer2+0xa1/0x1e0 [i915]
[ 8916.255512]  drm_ioctl+0x21b/0x4c0 [drm]
[ 8916.255541]  ? i915_gem_execbuffer+0x310/0x310 [i915]
[ 8916.26]  ? __seccomp_filter+0x67/0x250
[ 8916.255569]  do_vfs_ioctl+0xa3/0x610
[ 8916.255582]  ? __secure_computing+0x3f/0xd0
[ 8916.255596]  ? syscall_trace_enter+0xcd/0x2e0
[ 8916.255608]  SyS_ioctl+0x79/0x90
[ 8916.255618]  do_syscall_64+0x5b/0xc0
[ 8916.255630]  entry_SYSCALL64_slow_path+0x25/0x25
[ 8916.255644] RIP: 0033:0x7f83d996b587
[ 8916.255654] RSP: 002b:7ffdf218ffc8 EFLAGS: 0246 ORIG_RAX: 
0010
[ 8916.255673] RAX: ffda RBX: 10955864d800 RCX: 7f83d996b587
[ 8916.255692] RDX: 7ffdf2190010 RSI: c0406469 RDI: 000e
[ 8916.255710] RBP: 7ffdf2190010 R08:  R09: 
[ 8916.255727] R10: 4df0 R11: 0246 R12: c0406469
[ 8916.255743] R13: 000e R14:  R15: 
[ 8916.255776] Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 
48 83 ca 03 e8 aa cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 
24 ca 48 0f ab 08 0f 1f 44 00 00 e9 53 ff ff ff 65 8b 05 
[ 8916.255859] RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 
[i915] RSP: b58f82a0b880
[ 8916.255881] CR2: 0018
[ 8916.261987] ---[ end trace fbab8cf7afe4214e ]---

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1712427/+attachment/4937234/+files/Lsusb.txt

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1712427/+attachment/4937232/+files/JournalErrors.txt

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1712427/+attachment/4937241/+files/RfKill.txt

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1712427/+attachment/4937233/+files/Lspci.txt

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

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

[Brain]

apport information

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

[Kernel-packages] [Bug 1712427] Re: No audio output to Speakers when HDMI cable removed

[Brain]

apport information

** Tags added: apport-collected xenial

** Description changed:

  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.
  
  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.10
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  brain  2435 F pulseaudio
+  /dev/snd/controlC1:  brain  2435 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
+ InstallationDate: Installed on 2015-05-26 (819 days ago)
+ InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
+ MachineType: ASUSTeK COMPUTER INC. N501JW
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-33-generic N/A
+  linux-backports-modules-4.10.0-33-generic  N/A
+  linux-firmware 1.157.12
+ Tags:  xenial
+ Uname: Linux 4.10.0-33-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 08/03/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: N501JW.210
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: N501JW
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: ATN12345678901234567
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.name: N501JW
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No up

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1712427

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

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

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

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

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brain  2435 F pulseaudio
   /dev/snd/controlC1:  brain  2435 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=5165b586-2b44-4e4b-be49-177090e3b609
  InstallationDate: Installed on 2015-05-26 (819 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. N501JW
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=299cfed8-e49e-40d4-a8dd-fd66089e6d8a ro quiet splash 
iwlwifi.power_save=1 iwlwifi.power_level=5 acpi_osi= acpi_backlight=vendor 
acpi_enforce_resources=lax acpi=force nmi_watchdog=0 drm.vblankoffdelay=1 
i915.semaphores=1 i915.enable_rc6=7 i915.lvds_downclock=1 
rcutree.rcu_idle_gp_delay=1 pcie_aspm=force i915.enable_psr=1 i915.enable_fbc=1 
i915.disable_power_well=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-33-generic N/A
   linux-backports-modules-4.10.0-33-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dialout dip disk lp lpadmin opt plugdev 
sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501JW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501JW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501JW.210:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnN501JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501JW
  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/1712427/+subscriptions

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

[Kernel-packages] [Bug 1712427] Re: No audio output to Speakers when HDMI cable removed

[Brain]

** Summary changed:

- Audio output improperly switches to Speakers when HDMI removed
+ No audio output to Speakers when HDMI cable removed

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

Title:
  No audio output to Speakers when HDMI cable removed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.

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

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

[Kernel-packages] [Bug 1712427] [NEW] Audio output improperly switches to Speakers when HDMI removed

[Brain]

Public bug reported:

The Sound Settings dialog in Unity allows to switch between various
audio outputs.

If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
The expected behaviour would be to actually play audio on the speakers without 
the need to switch forth and back.

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

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

Title:
  Audio output improperly switches to Speakers when HDMI removed

Status in linux package in Ubuntu:
  New

Bug description:
  The Sound Settings dialog in Unity allows to switch between various
  audio outputs.

  If HDMI is selected and the cable removed the dialog shows that Speakers are 
selected. But there is no audio. To actually output audio to speakers one needs 
to click some other output ("Simultaneous output ...") and then again on 
Speakers.
  The expected behaviour would be to actually play audio on the speakers 
without the need to switch forth and back.

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

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

[Kernel-packages] [Bug 1712168] Re: Linux 4.12 refuses to load self-signed modules under Secure Boot with properly enrolled keys

[Seth Forshee]

Confirmed the bug in 4.12 and 4.13, applied fix to both artful kernel
trees and confirmed that it fixes the issue.

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

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

Title:
  Linux 4.12 refuses to load self-signed modules under Secure Boot with
  properly enrolled keys

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Since version 4.12, Linux refuses to load my self-signed VirtualBox
  modules.

  $ lsb_release -d
  Description:  Ubuntu Artful Aardvark (development branch)

  $ uname -rvm
  4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:26:42 UTC 2017 x86_64

  $ sudo modprobe -v vboxdrv
  insmod /lib/modules/4.12.0-11-generic/misc/vboxdrv.ko 
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available

  
  I've followed [this guide](https://askubuntu.com/a/768310/65926) to import 
the key an sign the modules. It worked until kernel 4.11.

  
  The key is properly enrolled:

  $ sudo mokutil --test-key .mok/mok-eric-carvalho.der 
  .mok/mok-eric-carvalho.der is already enrolled

  
  I think this happens because the kernel was built without 
CONFIG_MODULE_SIG_UEFI:

  $ ls -1 /boot/config-*
  /boot/config-4.11.0-13-generic
  /boot/config-4.12.0-11-generic

  $ grep CONFIG_MODULE_SIG_UEFI /boot/config-*
  /boot/config-4.11.0-13-generic:CONFIG_MODULE_SIG_UEFI=y

  
  Same problem with kernel 4.12.0-12.13 from the proposed repository.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carvalho   3077 F pulseaudio
   /dev/snd/controlC0:  carvalho   3077 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Mon Aug 21 15:37:56 2017
  HibernationDevice: RESUME=UUID=8766d3eb-a19c-403c-829a-ff5fa7878e87
  InstallationDate: Installed on 2016-12-15 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161214)
  MachineType: LENOVO 80JE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed 
root=UUID=ca49cfac-7b28-4152-bf45-006806f69224 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CNA0WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 4A1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G40-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CNA0WW:bd09/30/2016:svnLENOVO:pn80JE:pvrLenovoG40-80:rvnLENOVO:rnLancer4A1:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoG40-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80JE
  dmi.product.version: Lenovo G40-80
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1712218] Re: Docking station ethernet port no longer works

[Christopher Lee]

@kaihengfeng, which kernel would that be? In grub I only see (taken from  "dpkg 
--list | grep linux-image | grep ii"):
  - linux-image-4.12.0-11-generic
  - linux-image-4.13.0-041300rc6-generic

I take it I would have to install a previous kernel to check this one
out?

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

Title:
  Docking station ethernet port no longer works

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I recently upgraded to artful (xenial -> zesty -> artful).

  Now when I plug in my docking station I see this[1] in syslog and no
  network device appear.

  The docking station is a ThinkPad OneLink+ Dock, my laptop a ThinkPad
  X1 Carbon 4th gen.

  [1] http://pastebin.ubuntu.com/25365943/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  leecj2 9255 F pulseaudio
   /dev/snd/controlC1:  leecj2 9255 F pulseaudio
   /dev/snd/controlC0:  leecj2 9255 F pulseaudio
  CurrentDesktop: i3
  Date: Tue Aug 22 11:45:28 2017
  HibernationDevice: RESUME=UUID=82a0abb2-5063-47d1-988e-2d57f6a2fe15
  InstallationDate: Installed on 2017-03-06 (168 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 20FBCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f951cac3-6644-45d2-aada-c8542004c252 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-08-15 (6 days ago)
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET47W (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET47W(1.21):bd11/28/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1567557] Re: Performance degradation of "zfs clone"

[Stéphane Graber]

** No longer affects: lxd (Ubuntu Xenial)

** No longer affects: lxd (Ubuntu Zesty)

** No longer affects: lxd (Ubuntu Artful)

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

Title:
  Performance degradation of "zfs clone"

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Zesty:
  Fix Committed
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  [SRU Justification]

  Creating tens of hundreds of clones can be prohibitively slow. The
  underlying mechanism to gather clone information is using a 16K buffer
  which limits performance.  Also, the initial assumption is to pass in
  zero sized buffer to   the underlying ioctl() to get an idea of the
  size of the buffer required to fetch information back to userspace.
  If we bump the initial buffer to a larger size then we reduce the need
  for two ioctl calls which improves performance.

  [Fix]
  Bump initial buffer size from 16K to 256K

  [Regression Potential]
  This is minimal as this is just a tweak in the initial buffer size and larger 
sizes are handled correctly by ZFS since they are normally used on the second 
ioctl() call once we have established the size of the buffer required from the 
first ioctl() call. Larger initial buffers just remove the need for the initial 
size estimation for most cases where the number of clones is less than ~5000.  
There is a risk that a larger buffer size could lead to a ENOMEM issue when 
allocating the buffer, but the size of buffer used is still trivial for modern 
large 64 bit servers running ZFS.

  [Test case]
  Create 4000 clones. With the fix this takes 35-40% less time than without the 
fix. See the example test.sh script as an example of how to create this many 
clones.


  
  --

  I've been running some scale tests for LXD and what I've noticed is
  that "zfs clone" gets slower and slower as the zfs filesystem is
  getting busier.

  It feels like "zfs clone" requires some kind of pool-wide lock or
  something and so needs for all operations to complete before it can
  clone a new filesystem.

  A basic LXD scale test with btrfs vs zfs shows what I mean, see below
  for the reports.

  The test is run on a completely dedicated physical server with the
  pool on a dedicated SSD, the exact same machine and SSD was used for
  the btrfs test.

  The zfs filesystem is configured with those settings:
   - relatime=on
   - sync=disabled
   - xattr=sa

  So it shouldn't be related to pending sync() calls...

  The workload in this case is ultimately 1024 containers running busybox as 
their init system and udhcpc grabbing an IP.
  The problem gets significantly worse if spawning busier containers, say a 
full Ubuntu system.

  === zfs ===
  root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 
--image=images:alpine/edge/amd64 --privileged=true
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: zfs
    Storage version: 5
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    Batch size: 8
    Remainder: 0

  [Apr  3 06:42:51.170] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 06:42:52.657] Starting the test
  [Apr  3 06:42:53.994] Started 8 containers in 1.336s
  [Apr  3 06:42:55.521] Started 16 containers in 2.864s
  [Apr  3 06:42:58.632] Started 32 containers in 5.975s
  [Apr  3 06:43:05.399] Started 64 containers in 12.742s
  [Apr  3 06:43:20.343] Started 128 containers in 27.686s
  [Apr  3 06:43:57.269] Started 256 containers in 64.612s
  [Apr  3 06:46:09.112] Started 512 containers in 196.455s
  [Apr  3 06:58:19.309] Started 1024 containers in 926.652s
  [Apr  3 06:58:19.309] Test completed in 926.652s

  === btrfs ===
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: btrfs
    Storage version: 4.4
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    Batch size: 8
    Remainder: 0

  [Apr  3 07:42:12.053] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 07:42:13.351] Starting the test
  [Apr  3 07:42:14.793] Started 8 containers in 1.442s
  [Apr  3 07:42:16.495] Started 16 containers in 3.144s
  [Apr  3 07:42:19.881] Sta

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

[Logi Leifsson]

Also affecting me on Ubuntu 14.04 Asus UX305CA.

Could this be the reason my computer could not resume from suspend
anymore?

After a very recent system update my computer never resumed fully from
suspend and after a hard restart I got an apportcheckresume error. Only
thing I could notice was the same error being described here so I wonder
if that has been preventing my computer from resuming 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/1521173

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

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
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/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 1708734] Re: hisi_sas performance improvements

[dann frazier]

Note: in the above:
  old = 4.10.0-32.36
  new = 4.10.0-33.37

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

Title:
  hisi_sas performance improvements

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

Bug description:
  [Impact]
  Recent changes to the upstream driver improve write performance scalability 
with large numbers of disks.

  [Test Case]
  Attach SSDs to the controller, and run fio with the attached configuration 
file (adjust disk names as appropriate). You should see a nearly 2x improvement.

  [Regression Risk]
  The fixes are localized to the hisi_sas driver.

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

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

[Kernel-packages] [Bug 1708734] Re: hisi_sas performance improvements

[dann frazier]

For a 1 disk setup, I'm seeing a tiny - possibly insignificant -
improvement. There's no obvious regression, so I'll go ahead and mark
verified.

dannf@d05-3:~$ tail -n2 fio.out.*
==> fio.out.new <==
Disk stats (read/write):
  sda: ios=45/80729, merge=0/4929748, ticks=856/3320144, in_queue=3321592, 
util=100.00%

==> fio.out.old <==
Disk stats (read/write):
  sda: ios=0/80887, merge=0/4933228, ticks=0/3324968, in_queue=3325680, 
util=99.93%

I've requested some testing w/ a larger array to confirm the scaling
improvements.

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

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

Title:
  hisi_sas performance improvements

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

Bug description:
  [Impact]
  Recent changes to the upstream driver improve write performance scalability 
with large numbers of disks.

  [Test Case]
  Attach SSDs to the controller, and run fio with the attached configuration 
file (adjust disk names as appropriate). You should see a nearly 2x improvement.

  [Regression Risk]
  The fixes are localized to the hisi_sas driver.

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

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

[Kernel-packages] [Bug 1701486] Re: System brightness slider doesn't work any more

[Mygod]

Bug still present in 4.11.0-14-generic.

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

Title:
  System brightness slider doesn't work any more

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Update from 4.10.0-24 to 26 broke it. Using Linux Mint 18.1 x64
  Cinnamon.

  Changing /sys/class/backlight/intel_backlight/brightness manually
  works though.

  $ cat /proc/version_signature
  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  $ sudo lspci -vnvn 
  00:00.0 Host bridge [0600]: Intel Corporation Sky Lake Host Bridge/DRAM 
Registers [8086:1910] (rev 07)
Subsystem: Dell Skylake Host Bridge/DRAM Registers [1028:0706]
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: skl_uncore

  00:01.0 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x16) 
[8086:1901] (rev 07) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Intel Corporation Skylake PCIe Controller 
(x16) [8086:2015]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218  Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 256 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled+ CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Via WAKE# ARIFwd-
LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending+ InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Capabilities: [d94 v1] #19
Kernel driver in use: pcieport
Kernel modules: shpchp

  00:01.1 PCI bridge [0604]: Intel Corporation Sky Lake PCIe Controller (x8) 

[Kernel-packages] [Bug 1705712] Re: hns: ethtool selftest crashes system

[dann frazier]

dannf@d05-3:~$ sudo dmesg -c > /dev/null
[sudo] password for dannf: 
dannf@d05-3:~$ sudo ethtool -t enahisic2i1
The test result is PASS
The test extra info:
MacLoopback test 0
Serdes Loopback test 0
PhyLoopback test 0

dannf@d05-3:~$ dmesg
[439684.269761] IPv6: ADDRCONF(NETDEV_UP): enahisic2i1: link is not ready
[439687.329545] hns-nic HISI00C2:01 enahisic2i1: link up
[439688.513351] IPv6: ADDRCONF(NETDEV_CHANGE): enahisic2i1: link becomes ready
dannf@d05-3:~$ cat /proc/version
Linux version 4.10.0-33-generic (buildd@bos01-arm64-014) (gcc version 5.4.0 
20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #37~16.04.1-Ubuntu SMP Fri 
Aug 11 14:02:55 UTC 2017

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

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

Title:
  hns: ethtool selftest crashes system

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

Bug description:
  [Impact]
  Running ethtool selftest on an onboard NIC can crash the system

  [Test Case]
  On a HiSilicon D05 board:

  ubuntu@d05-3:~$ sudo ethtool -t enahisic2i1
  [sudo] password for ubuntu: 
  [  133.554255] hns-nic HISI00C2:01: PhyLoopback test recv fail, cnt=0x0, 
budget=0x1
  The test result is FAIL
  The test extra info:
  MacLoopback test   0
  Serdes Loopback test   0
  PhyLoopback test   3

  [Regression Risk]
  The fix is restricted to the hns driver's ethtool routines. Any regressions 
would be isolated to these HiSilicon platforms, and only during ethtool 
funcionality (i.e. workaround for regression would be don't-do-that).

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

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

[Kernel-packages] [Bug 1708714] Re: scsi: hisi_sas: add null check before indirect pointer dereference

[dann frazier]

Regression tested by doing a kernel compile using disk attached to the
hisi_sas controller.

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

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

Title:
  scsi: hisi_sas: add null check before indirect pointer dereference

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

Bug description:
  [Impact]
  Coverity scanning discovered a potential NULL dereference in this driver. 
Though I'm unaware of anyone hitting it in practice, it is an obvious bug.

  [Test Case]
  There is no known reproducer for this, so it can only be regression tested.

  [Regression Risk]
  The fix is localized to a driver and is a clean cherry pick from upstream.
  The bug fix looks straightforward - don't dereference the pointer if it is 
NULL. The only regression theory I have would be if this means that, instead of 
crashing, we now execute code that is *worse* than crashing (e.g. resulting in 
corruption, etc).

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

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

[Kernel-packages] [Bug 1708730] Re: hisi_sas driver reports mistakes timed out task for internal abort

[dann frazier]

Regression tested by doing a kernel compile using disk attached to the
hisi_sas controller.

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

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

Title:
  hisi_sas driver reports mistakes timed out task for internal abort

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

Bug description:
  [Impact]
  The driver may incorrectly report "internal task abort: timeout" errors in 
cases where the task has actually completed the abort.

  [Test Case]
  There is no known reliable reproducer for this bug, so we can only regression 
test it.

  [Regression Risk]
  The fix is localized to a specific driver, and is a clean cherry-pick from 
upstream. Regressions would be localized to systems w/ this (onboard) hardware.

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

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

[Kernel-packages] [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59

[Jake Billo]

With the sysctl settings provided by Pete (vm.min_free_kbytes = 100
and vm.zone_reclaim_mode = 1), we've been running the linux-aws
4.4.0-1028.37 kernel successfully without an OOM killer invocation for
about four days now. Previously we would have seen three or more
occurrences of this per day, so it's a positive indication.

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

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in linux-aws source package in Xenial:
  New
Status in linux-raspi2 source package in Xenial:
  Confirmed

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Bram Biesbrouck]

It seems to be fixed here on KDE neon...

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

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

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1712384] Re: Nvidia driver (proprietary) fails to load after suspend

[Brain]

** Package changed: linux (Ubuntu) => nvidia-graphics-drivers-375
(Ubuntu)

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

Title:
  Nvidia driver (proprietary) fails to load after suspend

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

Bug description:
  I'm running Ubuntu 16.04.3 on Asus UX501JW. The laptop has the NVidia
  Optimus technology (Intel HD4600 and NVidia GM107M (GeForce GTX
  960M)). The latest nvidia-384 driver and bumblebee are installed.

  After boot-up everything works fine. Until when the laptop gets
  suspended by closing the lid and then wakes up. Then the syslog is
  flooded with the below errors and the battery starts draining with 20W
  as the kernel is trying to reload the failing module. A reboot "cures"
  it (until the next suspend).

  Interestingly - when suspending via the keyboard "Zzz" button this
  does not happen.

  This error appeared recently, a month or a couple ago.
  I have been using this set-up for a few years and this wasn't a problem.

  The same problem happens with nvidia-375 and older drivers.

  Greatly appreciated if anybody could help me to shed some light on
  this.

  Aug 22 17:26:26 glorybook kernel: [46572.508501] pci_bus :02: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.508514] pci_bus :3b: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.508540] pci_bus :3c: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.508633] pci_bus :3d: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.710716] pcieport :00:01.0: 
bridge configuration invalid ([bus 00-00]), reconfiguring
  Aug 22 17:26:26 glorybook kernel: [46572.710795] pci_bus :3f: busn_res: 
can not insert [bus 3f-ff] under [bus 00-7e] (conflicts with (null) [bus 00-7e])
  Aug 22 17:26:26 glorybook kernel: [46572.710813] pci :3f:00.0: 
[10de:139b] type 00 class 0x030200
  Aug 22 17:26:26 glorybook kernel: [46572.710830] pci :3f:00.0: reg 0x10: 
[mem 0x-0x00ff]
  Aug 22 17:26:26 glorybook kernel: [46572.710844] pci :3f:00.0: reg 0x14: 
[mem 0x-0x0fff 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.710858] pci :3f:00.0: reg 0x1c: 
[mem 0x-0x01ff 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.710865] pci :3f:00.0: reg 0x24: 
[io  0x-0x007f]
  Aug 22 17:26:26 glorybook kernel: [46572.710874] pci :3f:00.0: reg 0x30: 
[mem 0x-0x0007 pref]
  Aug 22 17:26:26 glorybook kernel: [46572.710882] pci :3f:00.0: Max 
Payload Size set to 256 (was 128, max 256)
  Aug 22 17:26:26 glorybook kernel: [46572.711040] pci :3f:00.0: System 
wakeup disabled by ACPI
  Aug 22 17:26:26 glorybook kernel: [46572.711094] pcieport :00:01.0: PCI 
bridge to [bus 3f-ff]
  Aug 22 17:26:26 glorybook kernel: [46572.711101] pci_bus :3f: busn_res: 
[bus 3f-ff] end is updated to 3f
  Aug 22 17:26:26 glorybook kernel: [46572.711104] pci_bus :3f: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.711123] pci :3f:00.0: BAR 1: no 
space for [mem size 0x1000 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711125] pci :3f:00.0: BAR 1: 
failed to assign [mem size 0x1000 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711128] pci :3f:00.0: BAR 3: no 
space for [mem size 0x0200 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711129] pci :3f:00.0: BAR 3: 
failed to assign [mem size 0x0200 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711131] pci :3f:00.0: BAR 0: no 
space for [mem size 0x0100]
  Aug 22 17:26:26 glorybook kernel: [46572.711133] pci :3f:00.0: BAR 0: 
failed to assign [mem size 0x0100]
  Aug 22 17:26:26 glorybook kernel: [46572.711135] pci :3f:00.0: BAR 6: 
assigned [mem 0xed08-0xed0f pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711137] pci :3f:00.0: BAR 5: 
assigned [io  0xe080-0xe0ff]
  Aug 22 17:26:26 glorybook kernel: [46572.738219] nvidia-nvlink: Nvlink Core 
is being initialized, major device number 243
  Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: This is a 64-bit BAR 
mapped above 4GB by the system
  Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: BIOS or the Linux 
kernel, but the PCI bridge
  Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: immediately upstream 
of this GPU does not define
  Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: a matching 
prefetchable memory window.
  Aug 22 17:26:26 glorybook kernel: [46572.739216] NVRM: This may be due to a 
known Linux kernel bug.  Please
  Aug 22 17:26:26 glorybook kernel: [46572.739216] NVRM: see the README section 
on 64-bit BARs for additional
  Aug 22 17:26:26 glorybook kernel: [46572.739216] NVRM: information.
  Aug 22 17:26:26 glorybook kernel: [46572.739224] nvidia: probe of 
:01:00.0 failed with err

[Kernel-packages] [Bug 1697027] Re: ath9k freezes suspend resume Ubuntu 17.04

[Kleber Sacilotto de Souza]

Hi @pureblood,

Could you please verify if the zesty kernel currently in -proposed fixes
the issue?

Thank you.

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

Title:
  ath9k freezes suspend resume Ubuntu 17.04

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

Bug description:
  [SRU Justification]
  [Impact]
  Ath9k stops working after system resume from suspend.

  [Test Case]
  Suspend/resume the system.
  Ath9k should no longer freeze.

  [Regression Potential]
  This patch only effects ath9k, also, the change is pretty small.
  The regression potential should be really low.

  ---

  Description: Ubuntu Zesty Zapus
  Release: 17.04

  What was expected to happen?
  I expected the laptop would suspend and resume without issues

  What happened instead?
  First the network fails, then all other programs slowly start to fail as well 
until the system freezes completely. The system is unable to shutdown and it 
requires a forced shutdown.

  Often when suspending my system, a recent upgrade to 17.04 from 16.10,
  after resuming the network does not work and then slowly the whole
  system freezes. Looking at dmesg, the problem seems to arise just
  before the system suspends with the kernel trace attached below.

  My best guess is that the issue is caused by ath9k. My system is a
  Dell XPS13 version 9333 (2013) running kernel 4.10.0-22-generic (with
  8GB of RAM and no swap) and it is often connected to a Dell U3011
  monitor.

  I could not find other reports of this bug and this behaviour is new
  to 17.04, that is, it was not present in 16.10. I was always able to
  suspend and resume without issues before. I have been waiting to see
  bug 1674838 fixed before reporting this bug thinking that they might
  be related, but they are clearly independent as I am still having this
  suspend issue.

  Happy to try to collect more info if this information is not enough to
  understand where the problem lies, however it is impossible to run
  apport once the bug arises.

  [11292.289928] [ cut here ]
  [11292.289935] WARNING: CPU: 0 PID: 943 at 
/build/linux-nOqmtv/linux-4.10.0/kernel/kthread.c:69 kthread_stop+0x102/0x110
  [11292.289936] Modules linked in: ccm rfcomm cmac bnep hid_generic dell_wmi 
sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel dell_laptop dell_smbios kvm dcdbas snd_hda_codec_hdmi irqbypass 
snd_hda_codec_realtek uvcvideo snd_hda_codec_generic arc4 crct10dif_pclmul 
videobuf2_vmalloc snd_hda_intel crc32_pclmul videobuf2_memops ath9k 
snd_hda_codec ghash_clmulni_intel videobuf2_v4l2 ath9k_common pcbc snd_hda_core 
videobuf2_core ath9k_hw snd_hwdep usbhid videodev ath snd_pcm aesni_intel uas 
media ath3k mac80211 usb_storage hid aes_x86_64 btusb snd_seq_midi crypto_simd 
snd_seq_midi_event btrtl glue_helper cfg80211 snd_rawmidi cryptd btbcm btintel 
snd_seq bluetooth intel_cstate snd_seq_device intel_rapl_perf snd_timer snd 
input_leds joydev soundcore serio_raw shpchp mei_me mei
  [11292.289977]  lpc_ich acpi_als kfifo_buf industrialio mac_hid binfmt_misc 
parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit 
drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops ahci drm 
libahci wmi fjes video
  [11292.289995] CPU: 0 PID: 943 Comm: NetworkManager Not tainted 
4.10.0-22-generic #24-Ubuntu
  [11292.289996] Hardware name: Dell Inc.  Dell System XPS 
L322X/0PJHXN, BIOS A09 05/15/2013
  [11292.289997] Call Trace:
  [11292.290001]  dump_stack+0x63/0x81
  [11292.290003]  __warn+0xcb/0xf0
  [11292.290005]  warn_slowpath_null+0x1d/0x20
  [11292.290007]  kthread_stop+0x102/0x110
  [11292.290014]  ath9k_rng_stop+0x1a/0x20 [ath9k]
  [11292.290018]  ath9k_stop+0x3b/0x1d0 [ath9k]
  [11292.290036]  drv_stop+0x33/0x100 [mac80211]
  [11292.290055]  ieee80211_stop_device+0x43/0x50 [mac80211]
  [11292.290072]  ieee80211_do_stop+0x55a/0x860 [mac80211]
  [11292.290075]  ? _raw_spin_unlock_bh+0x1e/0x20
  [11292.290077]  ? dev_deactivate_many+0x205/0x240
  [11292.290093]  ieee80211_stop+0x1a/0x20 [mac80211]
  [11292.290096]  __dev_close_many+0x99/0x100
  [11292.290098]  __dev_close+0x45/0x70
  [11292.290100]  __dev_change_flags+0x9d/0x160
  [11292.290102]  dev_change_flags+0x29/0x60
  [11292.290104]  do_setlink+0x338/0xd20
  [11292.290107]  ? load_balance+0x1b4/0xa00
  [11292.290109]  ? update_load_avg+0x6b/0x510
  [11292.290112]  ? dequeue_entity+0xed/0x420
  [11292.290114]  ? nla_parse+0x31/0x110
  [11292.290115]  rtnl_newlink+0x5c6/0x860
  [11292.290118]  ? lookup_fast+0x57/0x310
  [11292.290121]  ? security_capget+0x60/0x70
  [11292.290123]  ? ns_capable_common+0x68/0x80
  [11292.290125]  ? ns_capable+0x13/0x20
  [11292.290127]  rtnetlink_rcv_msg+0xe6/0x210
  [11292.290130]  ? __kmalloc_node_track_caller+0x1f0/0x2a0
  [11292.290133]  ? 

[Kernel-packages] [Bug 1567557] Re: Performance degradation of "zfs clone"

[Stéphane Graber]

** No longer affects: lxd (Ubuntu)

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

Title:
  Performance degradation of "zfs clone"

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in lxd source package in Xenial:
  New
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in lxd source package in Zesty:
  New
Status in zfs-linux source package in Zesty:
  Fix Committed
Status in lxd source package in Artful:
  Confirmed
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  [SRU Justification]

  Creating tens of hundreds of clones can be prohibitively slow. The
  underlying mechanism to gather clone information is using a 16K buffer
  which limits performance.  Also, the initial assumption is to pass in
  zero sized buffer to   the underlying ioctl() to get an idea of the
  size of the buffer required to fetch information back to userspace.
  If we bump the initial buffer to a larger size then we reduce the need
  for two ioctl calls which improves performance.

  [Fix]
  Bump initial buffer size from 16K to 256K

  [Regression Potential]
  This is minimal as this is just a tweak in the initial buffer size and larger 
sizes are handled correctly by ZFS since they are normally used on the second 
ioctl() call once we have established the size of the buffer required from the 
first ioctl() call. Larger initial buffers just remove the need for the initial 
size estimation for most cases where the number of clones is less than ~5000.  
There is a risk that a larger buffer size could lead to a ENOMEM issue when 
allocating the buffer, but the size of buffer used is still trivial for modern 
large 64 bit servers running ZFS.

  [Test case]
  Create 4000 clones. With the fix this takes 35-40% less time than without the 
fix. See the example test.sh script as an example of how to create this many 
clones.


  
  --

  I've been running some scale tests for LXD and what I've noticed is
  that "zfs clone" gets slower and slower as the zfs filesystem is
  getting busier.

  It feels like "zfs clone" requires some kind of pool-wide lock or
  something and so needs for all operations to complete before it can
  clone a new filesystem.

  A basic LXD scale test with btrfs vs zfs shows what I mean, see below
  for the reports.

  The test is run on a completely dedicated physical server with the
  pool on a dedicated SSD, the exact same machine and SSD was used for
  the btrfs test.

  The zfs filesystem is configured with those settings:
   - relatime=on
   - sync=disabled
   - xattr=sa

  So it shouldn't be related to pending sync() calls...

  The workload in this case is ultimately 1024 containers running busybox as 
their init system and udhcpc grabbing an IP.
  The problem gets significantly worse if spawning busier containers, say a 
full Ubuntu system.

  === zfs ===
  root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 
--image=images:alpine/edge/amd64 --privileged=true
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: zfs
    Storage version: 5
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    Batch size: 8
    Remainder: 0

  [Apr  3 06:42:51.170] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 06:42:52.657] Starting the test
  [Apr  3 06:42:53.994] Started 8 containers in 1.336s
  [Apr  3 06:42:55.521] Started 16 containers in 2.864s
  [Apr  3 06:42:58.632] Started 32 containers in 5.975s
  [Apr  3 06:43:05.399] Started 64 containers in 12.742s
  [Apr  3 06:43:20.343] Started 128 containers in 27.686s
  [Apr  3 06:43:57.269] Started 256 containers in 64.612s
  [Apr  3 06:46:09.112] Started 512 containers in 196.455s
  [Apr  3 06:58:19.309] Started 1024 containers in 926.652s
  [Apr  3 06:58:19.309] Test completed in 926.652s

  === btrfs ===
  Test environment:
    Server backend: lxd
    Server version: 2.0.0.rc8
    Kernel: Linux
    Kernel architecture: x86_64
    Kernel version: 4.4.0-16-generic
    Storage backend: btrfs
    Storage version: 4.4
    Container backend: lxc
    Container version: 2.0.0.rc15

  Test variables:
    Container count: 1024
    Container mode: privileged
    Image: images:alpine/edge/amd64
    Batches: 128
    Batch size: 8
    Remainder: 0

  [Apr  3 07:42:12.053] Importing image into local store: 
64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7
  [Apr  3 07:42:13.351] Starting the test
  [Apr  3 07:42:14.793] Started 8 containers in 1.442s
  [Apr  3 07:42:16.495] Started 

[Kernel-packages] [Bug 1708130] Re: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests

[Joseph Salisbury]

Thanks for the update and being willing to perform the SRU.  It's best
to wait for the testing results like you say.

Thanks,

Joe

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

Title:
  ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while
  changing SMT value with Leaf IO and BASE tests

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2017-07-07 
03:56:54 ==
  Description:
  --
  Started Leaf IO and BASE(without smt tests)and then tried to change the SMT 
value manually where it hangs

UBUNTU BUILD: 4.10.0-26-generic

  Steps to re-create:
  --
  > Installed latest Ubuntu160403 kernel on system lotkvm
  4.10.0-26-generic

  > Leaf microcode: KMIPP113

  > Started Leaf IO and BASE tests(without smt tests).

  root@lotkvm:/home# show.report.py
  HOSTNAMEKERNEL VERSION   DISTRO INFO
  ----
  lotkvm  4.10.0-26-genericUbuntu 16.04.2 LTS \n \l

   Current Time: Tue Jul  4 00:55:37 2017 
  Job-IDFOCUS   Start-Time  DurationFunction
  ---   --  
  1 IO  20170704-00:44:45   0.0 hr(s) 10.0 min(s)   IO_Focus
  2 BASE20170704-00:44:52   0.0 hr(s) 10.0 min(s)   Test

  FOCUS IO  BASESUM
  TOTAL 76  25  101
  FAIL  0   4   4
  PASS  76  21  97
  (%)   (100%)  (84%)   (96%)

  >Now manually changed the smt value

  root@lotkvm:/home# ppc64_cpu --smt
  SMT=8
  root@lotkvm:/home# date
  Tue Jul  4 00:46:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=2
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=2
  root@lotkvm:/home# date
  Tue Jul  4 00:50:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=4
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=4
  root@lotkvm:/home# date
  Tue Jul  4 00:54:38 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=8

  
  [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2055.142915]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2055.143226]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 
seconds.
  [ 2055.143647]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 
seconds.
  [ 2055.144029]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds.
  [ 2055.144353]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds.
  [ 2055.144665]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds.
  [ 2055.144936]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds.
  [ 2055.145195]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2175.974848]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2175.975144]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  >  root@lotkvm:# ps -eaf | grep ppc*
  root  48054  12068  0 01:24 pts/000:00:00 grep --color=auto ppc*
  root  80305   5719  0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8

  > ppc64_cpu --smt command hangs here . Not able to change the SMT
  value from 4 to 8.

  > Attached dmesg logs

  == 

[Kernel-packages] [Bug 1712384] Re: Nvidia driver (proprietary) fails to load after suspend

[Brain]

I'm sorry, the 'apport-collect 1712384' command does not work.

The "Collecting problem information" window appears, however the moving
bar stops moving very soon and the window stops responding, while the
python process is taking 100% CPU. Even after 5 minutes there is still
no response (and still 100% CPU usage).

Console output (after breaking the collection process):

$ apport-collect 1712384
dpkg-query: no packages found matching linux
^CTraceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 597, in 
app.run_argv()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 658, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 547, in 
run_update_report
self.collect_info(ignore_uninstalled=True)
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 1028, in 
collect_info
self.ui_pulse_info_collection_progress()
  File "/usr/share/apport/apport-gtk", line 463, in 
ui_pulse_info_collection_progress
while Gtk.events_pending():
KeyboardInterrupt


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

Title:
  Nvidia driver (proprietary) fails to load after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 16.04.3 on Asus UX501JW. The laptop has the NVidia
  Optimus technology (Intel HD4600 and NVidia GM107M (GeForce GTX
  960M)). The latest nvidia-384 driver and bumblebee are installed.

  After boot-up everything works fine. Until when the laptop gets
  suspended by closing the lid and then wakes up. Then the syslog is
  flooded with the below errors and the battery starts draining with 20W
  as the kernel is trying to reload the failing module. A reboot "cures"
  it (until the next suspend).

  Interestingly - when suspending via the keyboard "Zzz" button this
  does not happen.

  This error appeared recently, a month or a couple ago.
  I have been using this set-up for a few years and this wasn't a problem.

  The same problem happens with nvidia-375 and older drivers.

  Greatly appreciated if anybody could help me to shed some light on
  this.

  Aug 22 17:26:26 glorybook kernel: [46572.508501] pci_bus :02: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.508514] pci_bus :3b: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.508540] pci_bus :3c: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.508633] pci_bus :3d: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.710716] pcieport :00:01.0: 
bridge configuration invalid ([bus 00-00]), reconfiguring
  Aug 22 17:26:26 glorybook kernel: [46572.710795] pci_bus :3f: busn_res: 
can not insert [bus 3f-ff] under [bus 00-7e] (conflicts with (null) [bus 00-7e])
  Aug 22 17:26:26 glorybook kernel: [46572.710813] pci :3f:00.0: 
[10de:139b] type 00 class 0x030200
  Aug 22 17:26:26 glorybook kernel: [46572.710830] pci :3f:00.0: reg 0x10: 
[mem 0x-0x00ff]
  Aug 22 17:26:26 glorybook kernel: [46572.710844] pci :3f:00.0: reg 0x14: 
[mem 0x-0x0fff 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.710858] pci :3f:00.0: reg 0x1c: 
[mem 0x-0x01ff 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.710865] pci :3f:00.0: reg 0x24: 
[io  0x-0x007f]
  Aug 22 17:26:26 glorybook kernel: [46572.710874] pci :3f:00.0: reg 0x30: 
[mem 0x-0x0007 pref]
  Aug 22 17:26:26 glorybook kernel: [46572.710882] pci :3f:00.0: Max 
Payload Size set to 256 (was 128, max 256)
  Aug 22 17:26:26 glorybook kernel: [46572.711040] pci :3f:00.0: System 
wakeup disabled by ACPI
  Aug 22 17:26:26 glorybook kernel: [46572.711094] pcieport :00:01.0: PCI 
bridge to [bus 3f-ff]
  Aug 22 17:26:26 glorybook kernel: [46572.711101] pci_bus :3f: busn_res: 
[bus 3f-ff] end is updated to 3f
  Aug 22 17:26:26 glorybook kernel: [46572.711104] pci_bus :3f: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.711123] pci :3f:00.0: BAR 1: no 
space for [mem size 0x1000 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711125] pci :3f:00.0: BAR 1: 
failed to assign [mem size 0x1000 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711128] pci :3f:00.0: BAR 3: no 
space for [mem size 0x0200 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711129] pci :3f:00.0: BAR 3: 
failed to assign [mem size 0x0200 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711131] pci :3f:00.0: BAR 0: no 
space for [mem size 0x0100]
  Aug 22 17:26:26 glorybook kernel: [46572.711133] pci :3f:00.0: BAR 0: 
failed to assign [mem size 0x0100]
  Aug 22 17:26:26 glorybook kernel: [46572.711135] pci :3f:00.0: BAR 6: 
assigned [mem 0xed08-0xed0f 

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[monteleo]

I have the same problem on a fresh installation of kubuntu 17.04,

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

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

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1696445] Re: OpenPower: Some multipaths temporarily have only a single path

[Kleber Sacilotto de Souza]

Hi Mauricio,

Could you please verify the fix with the xenial kernel currently in
-proposed?

Thank you!

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

Title:
  OpenPower: Some multipaths temporarily have only a single path

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * The SES driver causes a long delay in disk discovery when
     a large number of disks is present in the disk enclosure,
     which increases with the number of disks attached.

   * This delays the addition and visibility of the disk devices
     to userspace, which among other things causes multipath not
     to have multiple paths, actually, until the disk discovery
     eventually/finally finishes.

   * The fix significantly shortens the time taken by the SES
     driver to handle disk discovery, causing no extra delays,
     by removing a superfluous SCSI command sent to enclosure.

  [Test Case]

   * Load the module to access the enclosure and its disks; e.g.,

     $ sudo modprobe mpt3sas

   * Notice the interval between the discovery of each disk; e.g., dmesg

     $ dmesg -T | grep 'Attached SCSI disk' | tail -n2
     [Thu Jun 1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk
     [Thu Jun 1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk

   * The interval should be in the same second or so range with the fix.

     $ dmesg -T | grep 'Attached SCSI disk' | tail -n2
     [Wed Jun  7 13:11:59 2017] sd 18:0:176:0: [sdly] Attached SCSI disk
     [Wed Jun  7 13:11:59 2017] sd 18:0:175:0: [sdlx] Attached SCSI disk

  [Regression Potential]

   * The power status of the disks in the enclosure is no longer
     checked during probe time.  However, the patch demonstrates that
     initial value was never used in any way.  So, little regression
     potential.

   * Nonetheless, users of SES enclosures which verify the power status
     of disks in the enclosure might _theoretically_ see a problem, iff
     the fix has a problem (which has not been found yet).

  [Other Info]

   * None at this time.

  
  Problem Description:
  

  This week, I went ahead and scaled up my test configuration to max
  configuration 2x5U84_Enclosures,_MaxCfg_168HDDs. This time, it hit a
  different issue. The issue is that some multipaths only have a single
  path and no redundancy. Others have multiple paths and redundancy.

  Checkpoint #1:
  ==
  - system reboot around 2pm (14:00)

  Checkpoint # 2:
  ===
  - It took several minutes for first disk to be detected.

  
  root@smb1p1:~# multipath -ll|grep dm |wc -l
  103

  root@smb1p1:~# dmesg -T | grep 'sd 1[78]:' |  grep 'Attached SCSI disk' | tail
  [Thu Jun  1 14:18:30 2017] sd 17:0:100:0: [sdcr] Attached SCSI disk
  [Thu Jun  1 14:18:35 2017] sd 17:0:101:0: [sdcs] Attached SCSI disk
  [Thu Jun  1 14:18:40 2017] sd 17:0:102:0: [sdct] Attached SCSI disk
  [Thu Jun  1 14:18:44 2017] sd 17:0:103:0: [sdcu] Attached SCSI disk
  [Thu Jun  1 14:18:54 2017] sd 17:0:105:0: [sdcv] Attached SCSI disk
  [Thu Jun  1 14:18:59 2017] sd 17:0:106:0: [sdcw] Attached SCSI disk
  [Thu Jun  1 14:19:04 2017] sd 17:0:107:0: [sdcx] Attached SCSI disk
  [Thu Jun  1 14:19:09 2017] sd 17:0:108:0: [sdcy] Attached SCSI disk
  [Thu Jun  1 14:19:14 2017] sd 17:0:109:0: [sdcz] Attached SCSI disk
  [Thu Jun  1 14:19:19 2017] sd 17:0:110:0: [sdda] Attached SCSI disk
  root@smb1p1:~#

  ...

  root@smb1p1:~# multipath -ll|grep dm |wc -l
  142
  root@smb1p1:~# dmesg -T | grep 'sd 1[78]:' |  grep 'Attached SCSI disk' | tail
  [Thu Jun  1 14:21:54 2017] sd 17:0:141:0: [sdee] Attached SCSI disk
  [Thu Jun  1 14:21:58 2017] sd 17:0:142:0: [sdef] Attached SCSI disk
  [Thu Jun  1 14:22:04 2017] sd 17:0:143:0: [sdeg] Attached SCSI disk
  [Thu Jun  1 14:22:08 2017] sd 17:0:144:0: [sdeh] Attached SCSI disk
  [Thu Jun  1 14:22:14 2017] sd 17:0:145:0: [sdei] Attached SCSI disk
  [Thu Jun  1 14:22:18 2017] sd 17:0:146:0: [sdej] Attached SCSI disk
  [Thu Jun  1 14:22:24 2017] sd 17:0:147:0: [sdek] Attached SCSI disk
  [Thu Jun  1 14:22:29 2017] sd 17:0:148:0: [sdel] Attached SCSI disk
  [Thu Jun  1 14:22:34 2017] sd 17:0:149:0: [sdem] Attached SCSI disk
  [Thu Jun  1 14:22:39 2017] sd 17:0:150:0: [sden] Attached SCSI disk
  root@smb1p1:~#

  
  ...

  - After 43  minutes, multipath -ll command shows some paths with only
  single path and no redundancy and some path with multiple paths and
  redundancy.

  root@smb1p1:~# date
  Thu Jun  1 14:43:00 CDT 2017
  root@smb1p1:~# multipath -ll | grep -c 'sd[a-z]\+'
  252
  root@smb1p1:~#

  ...

  - After 47 minutes, multipath -ll command still shows some paths with

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1712384

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

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

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

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

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

Title:
  Nvidia driver (proprietary) fails to load after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 16.04.3 on Asus UX501JW. The laptop has the NVidia
  Optimus technology (Intel HD4600 and NVidia GM107M (GeForce GTX
  960M)). The latest nvidia-384 driver and bumblebee are installed.

  After boot-up everything works fine. Until when the laptop gets
  suspended by closing the lid and then wakes up. Then the syslog is
  flooded with the below errors and the battery starts draining with 20W
  as the kernel is trying to reload the failing module. A reboot "cures"
  it (until the next suspend).

  Interestingly - when suspending via the keyboard "Zzz" button this
  does not happen.

  This error appeared recently, a month or a couple ago.
  I have been using this set-up for a few years and this wasn't a problem.

  The same problem happens with nvidia-375 and older drivers.

  Greatly appreciated if anybody could help me to shed some light on
  this.

  Aug 22 17:26:26 glorybook kernel: [46572.508501] pci_bus :02: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.508514] pci_bus :3b: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.508540] pci_bus :3c: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.508633] pci_bus :3d: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.710716] pcieport :00:01.0: 
bridge configuration invalid ([bus 00-00]), reconfiguring
  Aug 22 17:26:26 glorybook kernel: [46572.710795] pci_bus :3f: busn_res: 
can not insert [bus 3f-ff] under [bus 00-7e] (conflicts with (null) [bus 00-7e])
  Aug 22 17:26:26 glorybook kernel: [46572.710813] pci :3f:00.0: 
[10de:139b] type 00 class 0x030200
  Aug 22 17:26:26 glorybook kernel: [46572.710830] pci :3f:00.0: reg 0x10: 
[mem 0x-0x00ff]
  Aug 22 17:26:26 glorybook kernel: [46572.710844] pci :3f:00.0: reg 0x14: 
[mem 0x-0x0fff 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.710858] pci :3f:00.0: reg 0x1c: 
[mem 0x-0x01ff 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.710865] pci :3f:00.0: reg 0x24: 
[io  0x-0x007f]
  Aug 22 17:26:26 glorybook kernel: [46572.710874] pci :3f:00.0: reg 0x30: 
[mem 0x-0x0007 pref]
  Aug 22 17:26:26 glorybook kernel: [46572.710882] pci :3f:00.0: Max 
Payload Size set to 256 (was 128, max 256)
  Aug 22 17:26:26 glorybook kernel: [46572.711040] pci :3f:00.0: System 
wakeup disabled by ACPI
  Aug 22 17:26:26 glorybook kernel: [46572.711094] pcieport :00:01.0: PCI 
bridge to [bus 3f-ff]
  Aug 22 17:26:26 glorybook kernel: [46572.711101] pci_bus :3f: busn_res: 
[bus 3f-ff] end is updated to 3f
  Aug 22 17:26:26 glorybook kernel: [46572.711104] pci_bus :3f: Allocating 
resources
  Aug 22 17:26:26 glorybook kernel: [46572.711123] pci :3f:00.0: BAR 1: no 
space for [mem size 0x1000 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711125] pci :3f:00.0: BAR 1: 
failed to assign [mem size 0x1000 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711128] pci :3f:00.0: BAR 3: no 
space for [mem size 0x0200 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711129] pci :3f:00.0: BAR 3: 
failed to assign [mem size 0x0200 64bit pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711131] pci :3f:00.0: BAR 0: no 
space for [mem size 0x0100]
  Aug 22 17:26:26 glorybook kernel: [46572.711133] pci :3f:00.0: BAR 0: 
failed to assign [mem size 0x0100]
  Aug 22 17:26:26 glorybook kernel: [46572.711135] pci :3f:00.0: BAR 6: 
assigned [mem 0xed08-0xed0f pref]
  Aug 22 17:26:26 glorybook kernel: [46572.711137] pci :3f:00.0: BAR 5: 
assigned [io  0xe080-0xe0ff]
  Aug 22 17:26:26 glorybook kernel: [46572.738219] nvidia-nvlink: Nvlink Core 
is being initialized, major device number 243
  Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: This is a 64-bit BAR 
mapped above 4GB by the system
  Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: BIOS or the Linux 
kernel, but the PCI bridge
  Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: immediately upstream 
of th

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

[bugproxy]

--- Comment From mauri...@br.ibm.com 2017-08-22 11:50 EDT---
@Joseph,

> @Mauricio,
>
> Do you plan on submitting an SRU request to the Ubuntu kernel team mailing
> list once testing is verified by Indira?

Yes, exactly.

If you'd recommend to submit it earlier, since already accepted
upstream, I can do that --

We know this patch fixes problems with similar symptoms on other distros
/ duplicates, but since this involves a SRU request to LTS, in an area
such as RCU, I'm clearly following the SRU requirement of testing first.
:- )

cheers,
Mauricio

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

Title:
  ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while
  changing SMT value with Leaf IO and BASE tests

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2017-07-07 
03:56:54 ==
  Description:
  --
  Started Leaf IO and BASE(without smt tests)and then tried to change the SMT 
value manually where it hangs

UBUNTU BUILD: 4.10.0-26-generic

  Steps to re-create:
  --
  > Installed latest Ubuntu160403 kernel on system lotkvm
  4.10.0-26-generic

  > Leaf microcode: KMIPP113

  > Started Leaf IO and BASE tests(without smt tests).

  root@lotkvm:/home# show.report.py
  HOSTNAMEKERNEL VERSION   DISTRO INFO
  ----
  lotkvm  4.10.0-26-genericUbuntu 16.04.2 LTS \n \l

   Current Time: Tue Jul  4 00:55:37 2017 
  Job-IDFOCUS   Start-Time  DurationFunction
  ---   --  
  1 IO  20170704-00:44:45   0.0 hr(s) 10.0 min(s)   IO_Focus
  2 BASE20170704-00:44:52   0.0 hr(s) 10.0 min(s)   Test

  FOCUS IO  BASESUM
  TOTAL 76  25  101
  FAIL  0   4   4
  PASS  76  21  97
  (%)   (100%)  (84%)   (96%)

  >Now manually changed the smt value

  root@lotkvm:/home# ppc64_cpu --smt
  SMT=8
  root@lotkvm:/home# date
  Tue Jul  4 00:46:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=2
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=2
  root@lotkvm:/home# date
  Tue Jul  4 00:50:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=4
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=4
  root@lotkvm:/home# date
  Tue Jul  4 00:54:38 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=8

  
  [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2055.142915]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2055.143226]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 
seconds.
  [ 2055.143647]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 
seconds.
  [ 2055.144029]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds.
  [ 2055.144353]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds.
  [ 2055.144665]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds.
  [ 2055.144936]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds.
  [ 2055.145195]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2175.974848]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2175.975144]   Not tainted 4.10.0-

[Kernel-packages] [Bug 1712384] [NEW] Nvidia driver (proprietary) fails to load after suspend

[Brain]

Public bug reported:

I'm running Ubuntu 16.04.3 on Asus UX501JW. The laptop has the NVidia
Optimus technology (Intel HD4600 and NVidia GM107M (GeForce GTX 960M)).
The latest nvidia-384 driver and bumblebee are installed.

After boot-up everything works fine. Until when the laptop gets
suspended by closing the lid and then wakes up. Then the syslog is
flooded with the below errors and the battery starts draining with 20W
as the kernel is trying to reload the failing module. A reboot "cures"
it (until the next suspend).

Interestingly - when suspending via the keyboard "Zzz" button this does
not happen.

This error appeared recently, a month or a couple ago.
I have been using this set-up for a few years and this wasn't a problem.

The same problem happens with nvidia-375 and older drivers.

Greatly appreciated if anybody could help me to shed some light on this.

Aug 22 17:26:26 glorybook kernel: [46572.508501] pci_bus :02: Allocating 
resources
Aug 22 17:26:26 glorybook kernel: [46572.508514] pci_bus :3b: Allocating 
resources
Aug 22 17:26:26 glorybook kernel: [46572.508540] pci_bus :3c: Allocating 
resources
Aug 22 17:26:26 glorybook kernel: [46572.508633] pci_bus :3d: Allocating 
resources
Aug 22 17:26:26 glorybook kernel: [46572.710716] pcieport :00:01.0: bridge 
configuration invalid ([bus 00-00]), reconfiguring
Aug 22 17:26:26 glorybook kernel: [46572.710795] pci_bus :3f: busn_res: can 
not insert [bus 3f-ff] under [bus 00-7e] (conflicts with (null) [bus 00-7e])
Aug 22 17:26:26 glorybook kernel: [46572.710813] pci :3f:00.0: [10de:139b] 
type 00 class 0x030200
Aug 22 17:26:26 glorybook kernel: [46572.710830] pci :3f:00.0: reg 0x10: 
[mem 0x-0x00ff]
Aug 22 17:26:26 glorybook kernel: [46572.710844] pci :3f:00.0: reg 0x14: 
[mem 0x-0x0fff 64bit pref]
Aug 22 17:26:26 glorybook kernel: [46572.710858] pci :3f:00.0: reg 0x1c: 
[mem 0x-0x01ff 64bit pref]
Aug 22 17:26:26 glorybook kernel: [46572.710865] pci :3f:00.0: reg 0x24: 
[io  0x-0x007f]
Aug 22 17:26:26 glorybook kernel: [46572.710874] pci :3f:00.0: reg 0x30: 
[mem 0x-0x0007 pref]
Aug 22 17:26:26 glorybook kernel: [46572.710882] pci :3f:00.0: Max Payload 
Size set to 256 (was 128, max 256)
Aug 22 17:26:26 glorybook kernel: [46572.711040] pci :3f:00.0: System 
wakeup disabled by ACPI
Aug 22 17:26:26 glorybook kernel: [46572.711094] pcieport :00:01.0: PCI 
bridge to [bus 3f-ff]
Aug 22 17:26:26 glorybook kernel: [46572.711101] pci_bus :3f: busn_res: 
[bus 3f-ff] end is updated to 3f
Aug 22 17:26:26 glorybook kernel: [46572.711104] pci_bus :3f: Allocating 
resources
Aug 22 17:26:26 glorybook kernel: [46572.711123] pci :3f:00.0: BAR 1: no 
space for [mem size 0x1000 64bit pref]
Aug 22 17:26:26 glorybook kernel: [46572.711125] pci :3f:00.0: BAR 1: 
failed to assign [mem size 0x1000 64bit pref]
Aug 22 17:26:26 glorybook kernel: [46572.711128] pci :3f:00.0: BAR 3: no 
space for [mem size 0x0200 64bit pref]
Aug 22 17:26:26 glorybook kernel: [46572.711129] pci :3f:00.0: BAR 3: 
failed to assign [mem size 0x0200 64bit pref]
Aug 22 17:26:26 glorybook kernel: [46572.711131] pci :3f:00.0: BAR 0: no 
space for [mem size 0x0100]
Aug 22 17:26:26 glorybook kernel: [46572.711133] pci :3f:00.0: BAR 0: 
failed to assign [mem size 0x0100]
Aug 22 17:26:26 glorybook kernel: [46572.711135] pci :3f:00.0: BAR 6: 
assigned [mem 0xed08-0xed0f pref]
Aug 22 17:26:26 glorybook kernel: [46572.711137] pci :3f:00.0: BAR 5: 
assigned [io  0xe080-0xe0ff]
Aug 22 17:26:26 glorybook kernel: [46572.738219] nvidia-nvlink: Nvlink Core is 
being initialized, major device number 243
Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: This is a 64-bit BAR 
mapped above 4GB by the system
Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: BIOS or the Linux 
kernel, but the PCI bridge
Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: immediately upstream of 
this GPU does not define
Aug 22 17:26:26 glorybook kernel: [46572.739214] NVRM: a matching prefetchable 
memory window.
Aug 22 17:26:26 glorybook kernel: [46572.739216] NVRM: This may be due to a 
known Linux kernel bug.  Please
Aug 22 17:26:26 glorybook kernel: [46572.739216] NVRM: see the README section 
on 64-bit BARs for additional
Aug 22 17:26:26 glorybook kernel: [46572.739216] NVRM: information.
Aug 22 17:26:26 glorybook kernel: [46572.739224] nvidia: probe of :01:00.0 
failed with error -1
Aug 22 17:26:26 glorybook kernel: [46572.739246] nvidia :3f:00.0: enabling 
device ( -> 0001)
Aug 22 17:26:26 glorybook kernel: [46572.739445] NVRM: This PCI I/O region 
assigned to your NVIDIA device is invalid:
Aug 22 17:26:26 glorybook kernel: [46572.739445] NVRM: BAR0 is 0M @ 0x0 
(PCI::3f:00.0)
Aug 22 17:26:26 glorybook kernel: [46572.739446] NVRM: The system BIOS may have 
misconfigured your GPU.
Aug 22 17:26:26 glorybook kernel: [46572.73944

[Kernel-packages] [Bug 1697892] Re: linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link speeds

[Kleber Sacilotto de Souza]

Hi @nicolas-dichtel,

Could you please verify the fix with the xenial and xesty kernel
currently on -proposed?

Thank you.

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

Title:
  linux >= 4.2: bonding 802.3ad does not work with 5G, 25G and 50G link
  speeds

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  These upstream patches are needed to correctly handle 5G, 25G and 50G
  speeds in 802.3ad:

  19ddde1eeca1 bonding: add 802.3ad support for 25G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=19ddde1eeca1e

  c7c550670afd bonding: fix 802.3ad support for 5G and 50G speeds
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=c7c550670af

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

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

[Kernel-packages] [Bug 1704102] Re: bonding: stack dump when unregistering a netdev

[Kleber Sacilotto de Souza]

Confirmed the issue to be fixed on xenial linux-image-4.4.0-93-generic
and zesty linux-image-4.10.0-33-generic.

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty

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

Title:
  bonding: stack dump when unregistering a netdev

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  Here is the reproducer:

  ip netns add foo
  ip -n foo link add dummy1 type dummy
  ip -n foo link add dummy2 type dummy
  modprobe bonding
  ip -n foo link add bond1 type bond
  ip -n foo link set dev bond1 down
  ip -n foo addr add 10.10.10.1/24 dev bond1
  ip -n foo link set dev bond1 up
  ip -n foo link set dummy1 master bond1
  ip -n foo link set dummy2 master bond1
  ip -n foo link set bond1 mtu 1540

  # Move slaves to init_net
  ip -n foo link set dummy1 netns 1
  ip -n foo link set dummy2 netns 1

  # idev are still in netns foo for dummy interfaces:
  ip netns exec foo ls /proc/sys/net/ipv4/conf/
  ip netns exec foo ls /proc/net/dev_snmp6/

  ip netns del foo
  dmesg

  The bug has been fixed upstream by this patch:

  f51048c3e07b ("bonding: avoid NETDEV_CHANGEMTU event when
  unregistering slave")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/bonding?id=f51048c3e07b

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

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

[Kernel-packages] [Bug 1635597] Re: Ubuntu16.10:talclp1: Kdump failed with multipath disk

[Andrew Cloke]

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

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

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

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

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

Title:
  Ubuntu16.10:talclp1: Kdump failed with multipath disk

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  New
Status in makedumpfile source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  Confirmed
Status in linux source package in Zesty:
  New
Status in makedumpfile source package in Zesty:
  Confirmed

Bug description:
  Problem  Description
  ==
  On talclp1, I enabled kdump. But kdump failed and it drop to BusyBox.

  root@talclp1:~# echo c> /proc/sysrq-trigger
  [  132.643690] sysrq: SysRq : Trigger a crash
  [  132.643739] Unable to handle kernel paging request for data at address 
0x
  [  132.643745] Faulting instruction address: 0xc05c28f4
  [  132.643749] Oops: Kernel access of bad area, sig: 11 [#1]
  [  132.643753] SMP NR_CPUS=2048 NUMA pSeries
  [  132.643758] Modules linked in: fuse ufs qnx4 hfsplus hfs minix ntfs msdos 
jfs rpadlpar_io rpaphp rpcsec_gss_krb5 nfsv4 dccp_diag cifs nfs dns_resolver 
dccp tcp_diag fscache udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
binfmt_misc xfs libcrc32c pseries_rng rng_core ghash_generic gf128mul 
vmx_crypto sg nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables 
autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq 
dm_round_robin sr_mod sd_mod cdrom ses enclosure scsi_transport_sas ibmveth 
crc32c_vpmsum ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath dm_mod
  [  132.643819] CPU: 49 PID: 10174 Comm: bash Not tainted 4.8.0-15-generic 
#16-Ubuntu
  [  132.643824] task: c00111767080 task.stack: c000d82e
  [  132.643828] NIP: c05c28f4 LR: c05c39d8 CTR: 
c05c28c0
  [  132.643832] REGS: c000d82e3990 TRAP: 0300   Not tainted  
(4.8.0-15-generic)
  [  132.643836] MSR: 80009033   CR: 28242422  
XER: 0001
  [  132.643848] CFAR: c00087d0 DAR:  DSISR: 4200 
SOFTE: 1
  GPR00: c05c39d8 c000d82e3c10 c0f67b00 0063
  GPR04: c0011d04a9b8 c0011d05f7e0 c0047fb0 00015998
  GPR08: 0007 0001  0001
  GPR12: c05c28c0 c7b4b900  2200
  GPR16: 10170dc8 01002b566368 10140f58 100c7570
  GPR20:  1017dd58 10153618 1017b608
  GPR24: 3e87a294 0001 c0ebff60 0004
  GPR28: c0ec0320 0063 c0e72a90 
  [  132.643906] NIP [c05c28f4] sysrq_handle_crash+0x34/0x50
  [  132.643911] LR [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643914] Call Trace:
  [  132.643917] [c000d82e3c10] [c0a245e8] 0xc0a245e8 
(unreliable)
  [  132.643923] [c000d82e3c30] [c05c39d8] __handle_sysrq+0xe8/0x280
  [  132.643928] [c000d82e3cd0] [c05c4188] 
write_sysrq_trigger+0x78/0xa0
  [  132.643935] [c000d82e3d00] [c03ad770] proc_reg_write+0xb0/0x110
  [  132.643941] [c000d82e3d50] [c030fc3c] __vfs_write+0x6c/0xe0
  [  132.643946] [c000d82e3d90] [c0311144] vfs_write+0xd4/0x240
  [  132.643950] [c000d82e3de0] [c0312e5c] SyS_write+0x6c/0x110
  [  132.643957] [c000d82e3e30] [c00095e0] system_call+0x38/0x108
  [  132.643961] Instruction dump:
  [  132.643963] 38425240 7c0802a6 f8010010 f821ffe1 6000 6000 3d220019 
3949ba60
  [  132.643972] 3921 912a 7c0004ac 3940 <992a> 38210020 
e8010010 7c0803a6
  [  132.643981] ---[ end trace eed6bbcd2c3bdfdf ]---
  [  132.646105]
  [  132.646176] Sending IPI to other CPUs
  [  132.647490] IPI complete
  I'm in purgatory
   -> smp_release_cpus()
  spinning_secondaries = 104
   <- smp_release_cpus()
  [2.011346] alg: hash: Test 1 failed for crc32c-vpmsum
  [2.729254] sd 0:2:0:0: [sda] Assuming drive cache: write through
  [2.731554] sd 1:2:5:0: [sdn] Assuming drive cache: write through
  [2.739087] sd 1:2:4:0: [sdm] Assuming drive cache: write through
  [2.739089] sd 1:2:6:0: [sdo] Assuming drive cache: write through
  [2.739110] sd 1:2:7:0: [sdp] Assuming drive cache: write through
  [2.739115] sd 1:2:0:0: [sdi] Assuming drive cache: write through
  [2.739122] sd 1:2:3:0: [sdl] Assuming drive 

[Kernel-packages] [Bug 1708130] Re: ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while changing SMT value with Leaf IO and BASE tests

[Joseph Salisbury]

@Mauricio,

Do you plan on submitting an SRU request to the Ubuntu kernel team
mailing list once testing is verified by Indira?

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

Title:
  ISST-LTE: Ubuntu16.04.03: PowerNV: 'ppc64_cpu' commands hangs while
  changing SMT value with Leaf IO and BASE tests

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2017-07-07 
03:56:54 ==
  Description:
  --
  Started Leaf IO and BASE(without smt tests)and then tried to change the SMT 
value manually where it hangs

UBUNTU BUILD: 4.10.0-26-generic

  Steps to re-create:
  --
  > Installed latest Ubuntu160403 kernel on system lotkvm
  4.10.0-26-generic

  > Leaf microcode: KMIPP113

  > Started Leaf IO and BASE tests(without smt tests).

  root@lotkvm:/home# show.report.py
  HOSTNAMEKERNEL VERSION   DISTRO INFO
  ----
  lotkvm  4.10.0-26-genericUbuntu 16.04.2 LTS \n \l

   Current Time: Tue Jul  4 00:55:37 2017 
  Job-IDFOCUS   Start-Time  DurationFunction
  ---   --  
  1 IO  20170704-00:44:45   0.0 hr(s) 10.0 min(s)   IO_Focus
  2 BASE20170704-00:44:52   0.0 hr(s) 10.0 min(s)   Test

  FOCUS IO  BASESUM
  TOTAL 76  25  101
  FAIL  0   4   4
  PASS  76  21  97
  (%)   (100%)  (84%)   (96%)

  >Now manually changed the smt value

  root@lotkvm:/home# ppc64_cpu --smt
  SMT=8
  root@lotkvm:/home# date
  Tue Jul  4 00:46:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=2
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=2
  root@lotkvm:/home# date
  Tue Jul  4 00:50:01 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=4
  root@lotkvm:/home# ppc64_cpu --smt
  SMT=4
  root@lotkvm:/home# date
  Tue Jul  4 00:54:38 CDT 2017
  root@lotkvm:/home# ppc64_cpu --smt=8

  
  [ 2055.142781] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2055.142915]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.142978] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143150] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2055.143226]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143570] INFO: task kworker/u259:3:22436 blocked for more than 120 
seconds.
  [ 2055.143647]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.143709] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.143953] INFO: task kworker/8:188:118516 blocked for more than 120 
seconds.
  [ 2055.144029]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144091] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144289] INFO: task mkfs.ntfs:95505 blocked for more than 120 seconds.
  [ 2055.144353]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144600] INFO: task ppc64_cpu:80305 blocked for more than 120 seconds.
  [ 2055.144665]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144727] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.144872] INFO: task rm:80950 blocked for more than 120 seconds.
  [ 2055.144936]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.144998] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2055.145133] INFO: task rm:80951 blocked for more than 120 seconds.
  [ 2055.145195]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2055.145257] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.974718] INFO: task jbd2/nvme0n1p6-:22052 blocked for more than 120 
seconds.
  [ 2175.974848]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.974912] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2175.975068] INFO: task kworker/48:0H:21755 blocked for more than 120 
seconds.
  [ 2175.975144]   Not tainted 4.10.0-26-generic #30~16.04.1-Ubuntu
  [ 2175.975206] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  >  root@lotkvm:# ps -eaf | grep ppc*
  root  48054  12068  0 01:24 pts/000:00:00 grep --color=auto ppc*
  root  80305   5719  0 00:54 hvc0 00:00:00 ppc64_cpu --smt 8

  > ppc64_cpu --smt command hangs here . Not able to change the SMT
  value from 4 to 8.

  > Attached dmesg logs

  == Com

[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

[Joseph Salisbury]

Let's try further back, can you test 4.4.0-10:
https://launchpad.net/ubuntu/+source/linux/4.4.0-10.25/+build/9287900

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Si Dedman]

Also affects Xubuntu 16.06, 16.10 & 17.04. Potentially could/should
change bug name to reflect wider generality of problem.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

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

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 842560] Re: bnx2 firmware missing

[Gus Hoppes]

Hi. I just did a do-release-upgrade from Ubuntu Server 12.04 to 14.04
just as Jaap did. I got the same issue. The network card will not start.
Its on a Dell PowerEdge 2950 with a static address on eth0 only (dual
nics).

RTNETLINK answers: no such process
[61709.025401] bnx2: can't load firmware file bnx2/bnx2-mips-06-6.2.3.fw
no such file or directory

Is there a fix I can try?

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

Title:
  bnx2 firmware missing

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project oneiric series:
  Fix Released
Status in OEM Priority Project precise series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Fix Released
Status in linux source package in Oneiric:
  Invalid
Status in udev source package in Oneiric:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in udev source package in Precise:
  Fix Released

Bug description:
  SRU justification:
  udev in Ubuntu 11.10 has regressed support for certain hardware 
configurations, resulting in firmware failing to be loaded at boot time due to 
a race condition when shutting down udev in the initramfs.  This causes network 
interfaces to fail to come up in a usable state on systems previously 
supported, and also causes long boot-time delays on these same systems.

  Regression potential:
  The nature of the fix introduces the possibility that some systems that are 
not affected by this bug will have their boot slowed down as a result of udev 
being forced to process more events before it's able to exit.  However, since 
only events with a timeout requirement will actually be dispatched for 
processing, the impact here should be minimal.

  Test case:
  1. boot oneiric on a system such as a Dell PowerEdge 2950 which has two NICs 
that use the bnx2 driver and require the bnx2-mips-06-6.2.1.fw firmware
  2. observe that the boot has a 60-second delay and that there is an error in 
dmesg that the firmware fails to load for one of the NICs
  3. install the udev package from oneiric-proposed
  4. reboot 6 times to confirm that the system now boots up with no delay and 
that there is no error in dmesg even after multiple reboots

  Installing the latest Beta 1 of Ubuntu 11.10 (downloaded iso on
  09-06-2011) fails after the first reboot with this error:

  bnx2: Can't load firmware file "bnx2/bnx2-mips-06-6.2.1.fw"
  udevd[107]: '/sbin/modprobe -bv 
pci:v14E4d164Csv1028sd01B2bc02sc00i00' [172] terminated by 
signal 9 (Killed)

  Earlier stable versions of Ubuntu Server (11.04) work fine on this
  machine.

  For further investigations i collected some additional information for
  you. (Attachments)

  Are there any other needed information i can supply?

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/842560/+subscriptions

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

[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

[Stuart Page]

I believe this issue is effecting me too after a fresh install of Ubuntu
server 16.04.3 with the HWE kernel 4.10 today (fully updated). After
seeing the issue, was unable to log in or SSH in.


** Attachment added: "Picture of errors in tty"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405/+attachment/4937113/+files/IMG_20170822_153622453.jpg

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will
  randomly freeze up, sometimes before the login screen, sometimes while
  I'm in the middle of using a program. This sometimes happens on the
  Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel
  4.2.0-22.

  Important part of log:

  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112129] NMI watchdog: BUG: soft 
lockup - CPU#0 stuck for 22s! [kerneloops:814]
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112134] Modules linked in: rfcomm 
bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul 
sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae 
glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic 
snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core 
joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi 
serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device 
snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore 
edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp 
parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid 
amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes 
video
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112183] CPU: 0 PID: 814 Comm: 
kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112184] Hardware name: ASUSTeK 
COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 
07/09/2015
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112186] task: 88031146d400 
ti: 88030e838000 task.ti: 88030e838000
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112188] RIP: 
0010:[]  [] __do_softirq+0x76/0x250
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112194] RSP: 
0018:88031fc03f30  EFLAGS: 0202
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112196] RAX: 88030e83c000 
RBX:  RCX: 40400040
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112197] RDX:  
RSI: 613e RDI: 0380
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112198] RBP: 88031fc03f80 
R08: 0029f8fa1411 R09: 88031fc169f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112199] R10: 0020 
R11: 0004 R12: 88031fc169c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112201] R13: 88030df8e200 
R14:  R15: 0001
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112202] FS:  
7f6c266ac880() GS:88031fc0() knlGS:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112203] CS:  0010 DS:  ES: 
 CR0: 80050033
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112205] CR2: 7ffef000bff8 
CR3: 00030f368000 CR4: 000406f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112206] Stack:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112207]  404000401fc03f78 
88030e83c000 0121 8803000a
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112209]  00021fc0d640 
 88031fc169c0 88030df8e200
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112211]   
0001 88031fc03f90 81081d23
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112213] Call Trace:
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112215]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112219]  [] 
irq_exit+0xa3/0xb0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.11]  [] 
smp_apic_timer_interrupt+0x42/0x50
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112225]  [] 
apic_timer_interrupt+0x82/0x90
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112226]   
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112230]  [] ? 
finish_task_switch+0x67/0x1c0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112232]  [] 
__schedule+0x36c/0x980
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112234]  [] 
schedule+0x33/0x80
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112236]  [] 
do_nanosleep+0x6f/0xf0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112239]  [] 
hrtimer_nanosleep+0xdc/0x1f0
  Dec 31 19:13:12 COMPUTERNAME kernel: [   64.112241]  [] ? 
__hrtimer_init+0x90/0x90
  Dec 31 19:13:12 

[Kernel-packages] [Bug 1553178] Re: perf: POWER8: Allow specifying Power PMU events by name rather than raw codes

[Leann Ogasawara]

Setting this to Fix Released for Zesty 17.04 and newer since the patches
landed upstream in v4.9 and v4.10:

867a979a83d38fb82c4e7534a0281a02ef1700a3
v4.9-rc1~63^2~1^2~17   
80eeb67fe577aa76b2d1bb5b029bca097f0f25bc
v4.9-rc1~63^2~1^2~16   
933f82ff72d7d1641663462f61f3056ee1fe3f8b
v4.9-rc1~63^2~1^2~15   
ce88f27ccc724fa8e6766fdd4140768931f42f88
v4.9-rc1~63^2~1^2~14  
f33d1227197e0fe9d3682c5a766fdc74559da78e
v4.9-rc1~63^2~1^2~13  
dc720ffc9863b618a192f5949234c54aad00ed24
v4.9-rc1~63^2~1^2~12  
08e60ed15d0483be38a87d17538ccf02acff5b1f
v4.9-rc1~63^2~1^2~11  
61eb2eb434b3430c6ef70536eb3d16b616b5ee52
v4.9-rc1~63^2~1^2~10  
1c5f01fe8660fc48625a94a5ed10e4dbaea95d5f
v4.9-rc1~63^2~1^2~9   
fc06e2a5aad9fcf7efaabd7550ac31f648d2f2bc
v4.9-rc1~63^2~1^2~8   
794ba54a8393456d503958d6217874e455b6a771
v4.9-rc1~63^2~1^2~7   
c8d6828a6510c9363180ebf662b51d032e0eb85a
v4.9-rc1~63^2~1^2~6   
dd5f10368a5f27ec926395056d959513ca4578cc
v4.9-rc1~63^2~1^2~5
06d839b4f712065d76cba92e7e10e9d771771c5a
 v4.9-rc1~63^2~1^2~4 
06835545b144cab6e7748748576145ea15f68dff
v4.9-rc1~63^2~1^2~3 
e312bcf13053970c0f07ec2c02d7d9be1a036ce0
v4.9-rc1~63^2~1^2~2 
0b1db474314c883d0bfc6720278667a6155e995a
v4.9-rc1~63^2~1^2~1 
b42c7369e3f451e22c2b0be5d193955498d37546
v4.9-rc1~63^2~1^2   
72c6ff2583fba824dc38c0ce87b838631cdb8294
v4.9-rc1~63^2^2~8   
27b565b1eb04a277027953cab13b5aad5d469390
v4.10-rc1~190^2~14^2~20 
b74d1315cab113ce1e0ee5e10eb6638219c1b0d1
v4.10-rc1~190^2~14^2~19 
19c0389b60d486010d508d5a1551ee9b6a8b2f45
v4.10-rc1~190^2~14^2~18 
052aa3cce3f2b91e339318e5fe9806d0cfd822f0
v4.10-rc1~190^2~14^2~17 
4a00680b059a6c2c378945e2dffa2fa2876a4fc1
v4.10-rc1~190^2~14^2~16 
dcfbad10c7ba0bd2f4993c8d8a258471eb6083ff
v4.10-rc1~190^2~14^2~15 
ede007404388cd1ba306760a2881dc9722f5bb47
  
v4.10-rc1~190^2~14^2~14   
4b90798ebb0bab8fe1ed9065e80879503f5601d2
 
v4.10-rc1~190^2~14^2~13
d910f0ba6d72a0917ae30b6aed5131988e3096e4
v4.10-rc1~190^2~14^2~12
902ea4ee33e6dccece0f78a68e882eee9be9577f
v4.10-rc1~190^2~14^2~11
55d42d272ee30cd781e74a9c4ab152664c6417fc
v4.10-rc1~190^2~14^2~10
edaa78b4c050ec0a0fc7f436cdf6a73c91af64e0
v4.10-rc1~190^2~14^2~9
d8c303858582d4dcd90f13ebbe9db812a70d0948
v4.10-rc1~190^2~14^2~8
47cbd67e243a6bbb4133d719edd24ee6a315462d
v4.10-rc1~190^2~14^2~7
1b0978458300164046d12e1b7930c9de38057e1d
v4.10-rc1~190^2~14^2~6
6e82bdae472355fe0953e12eb29a36079e155ddb
v4.10-rc1~190^2~14^2~5
1f888acd92c8f88b0ab9640cef0794bc5424c668
v4.10-rc1~190^2~14^2~4
01dd25455b3588431d3f59c70e7b934a91d66121
v4.10-rc1~190^2~14^2~3
1fbd54b2e2356659f9f87920dc514792db6ff602
v4.10-rc1~190^2~14^2~2
2a81fa3bb5edb4a9dc9cb04cd591c99d41eb4f4c
v4.10-rc1~190^2~14^2~1
46b627a25f228adca952b8691e6aed32011cc3cf
v4.10-rc1~190^2~14^2


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

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

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

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

Title:
  perf: POWER8: Allow specifying Power PMU events by name rather than
  raw codes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == Comment: #0 - Sukadev Bhattiprolu  - 2015-10-19
  20:45:40 ==

  Power processor provides the ability to monitor a large number of Performance
  Monitoring events. However the linux kernel/perf tool requires that a vast 
majority
  of these events be specified by their raw codes:

   perf stat -e r100f2 sleep 1

  We would instead like to be able to specify the events by its name:

 perf stat -e pm_1plus_ppc_cmpl sleep 1

  where the event name name 'pm_1plus_ppc_cmpl' is defined in
  the POWER PMU specs

  == Comment: #1 - Sukadev Bhattiprolu  2015-10-27 13:43:20 ==
  Here is a pointer to a newer version of the patch set:

https://lkml.org/lkml/2015/10/26/624

  == Comment: #10 - Sukadev Bhattiprolu - 2016-03-01 13:50:37 ==
  (In reply to comment #9)
  > any change in upstream status? If not, should we re-target this to 16.04.1
  > and 16.10?

  No, no comments yet from maintainer, so patches still stuck. Yes we could
  re-target to 16.10 for now.

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

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

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

[bugproxy]

--- Comment From hbath...@in.ibm.com 2017-08-22 10:32 EDT---
(In reply to comment #20)
> Hi, hbathini.
>

Hello Cascardo,

> Why is it needed to restart kdump-tools after a DLPAR? Does it refer
to a

Yes. It refers to either of memory or CPU hot add/remove operations, when
kdump kernel needs to be reloaded - to rebuild the vmcore elf notes.
> memory hotplug operation? What is LTC bug #150353? Is it mirrored to
> launchpad already?

Yes, it is mirrored. LTC Bug 150353 refers to Launchpad bug 1658968.

Thanks
Hari

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1703430] Re: Set CONFIG_SATA_HIGHBANK=y on armhf

[Dan Nicholson]

I commented out sata_highbank from /etc/initramfs-tools/modules and was
able to boot both proposed kernels. I also saw messages from
sata_highbank in dmesg. This was on a xenial system, but I hope that's
enough testing to verify this particular change.

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty

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

Title:
  Set CONFIG_SATA_HIGHBANK=y on armhf

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: CONFIG_SATA_HIGHBANK was changed from y to m after trusty,
  with no justification appearing in the git history. This can cause
  problems booting on some systems.

  Fix: Change the option back to y.

  Regression Potential: Minimal, as this only switches a driver from
  being a module to being built-in, and the driver will only be used if
  the device appears in a platform's device tree.

  ---

  Sometime between trusty and xenial, CONFIG_SATA_HIGHBANK was changed
  from y to m. I believe the change was in utopic, but it's hard to
  tell.

  This makes booting on Calxeda Highbank systems pretty difficult since
  you can't get to the root filesystem on a SATA disk unless you were
  smart enough to have initramfs-tools include the sata_highbank module.
  On a clean install, you'd need to know to drop out of the installer,
  and rebuild the initramfs appropriately.

  Any chance that could be changed back to y for armhf?

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

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

[Kernel-packages] [Bug 1711526] Re: Xenial update to 4.4.81 stable release

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Xenial update to 4.4.81 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.81 stable release shall be applied:
  * libata: array underflow in ata_find_dev()
  * workqueue: restore WQ_UNBOUND/max_active==1 to be ordered
  * ALSA: hda - Fix speaker output from VAIO VPCL14M1R
  * ASoC: do not close shared backend dailink
  * KVM: async_pf: make rcu irq exit if not triggered from idle task
  * mm/page_alloc: Remove kernel address exposure in free_reserved_area()
  * ext4: fix SEEK_HOLE/SEEK_DATA for blocksize < pagesize
  * ext4: fix overflow caused by missing cast in ext4_resize_fs()
  * ARM: dts: armada-38x: Fix irq type for pca955
  * media: platform: davinci: return -EINVAL for VPFE_CMD_S_CCDC_RAW_PARAMS
ioctl
  * target: Avoid mappedlun symlink creation during lun shutdown
  * iscsi-target: Always wait for kthread_should_stop() before kthread exit
  * iscsi-target: Fix early sk_data_ready LOGIN_FLAGS_READY race
  * iscsi-target: Fix initial login PDU asynchronous socket close OOPs
  * iscsi-target: Fix delayed logout processing greater than
SECONDS_FOR_LOGOUT_COMP
  * iser-target: Avoid isert_conn->cm_id dereference in isert_login_recv_done
  * mm, mprotect: flush TLB if potentially racing with a parallel reclaim
leaving stale TLB entries
  * media: lirc: LIRC_GET_REC_RESOLUTION should return microseconds
  * f2fs: sanity check checkpoint segno and blkoff
  * drm: rcar-du: fix backport bug
  * saa7164: fix double fetch PCIe access condition
  * ipv4: ipv6: initialize treq->txhash in cookie_v[46]_check()
  * net: Zero terminate ifr_name in dev_ifname().
  * ipv6: avoid overflow of offset in ip6_find_1stfragopt
  * ipv4: initialize fib_trie prior to register_netdev_notifier call.
  * rtnetlink: allocate more memory for dev_set_mac_address()
  * mcs7780: Fix initialization when CONFIG_VMAP_STACK is enabled
  * openvswitch: fix potential out of bound access in parse_ct
  * packet: fix use-after-free in prb_retire_rx_blk_timer_expired()
  * ipv6: Don't increase IPSTATS_MIB_FRAGFAILS twice in ip6_fragment()
  * net: ethernet: nb8800: Handle all 4 RGMII modes identically
  * dccp: fix a memleak that dccp_ipv6 doesn't put reqsk properly
  * dccp: fix a memleak that dccp_ipv4 doesn't put reqsk properly
  * dccp: fix a memleak for dccp_feat_init err process
  * sctp: don't dereference ptr before leaving _sctp_walk_{params, errors}()
  * sctp: fix the check for _sctp_walk_params and _sctp_walk_errors
  * net/mlx5: Fix command bad flow on command entry allocation failure
  * net: phy: Correctly process PHY_HALTED in phy_stop_machine()
  * net: phy: Fix PHY unbind crash
  * xen-netback: correctly schedule rate-limited queues
  * sparc64: Measure receiver forward progress to avoid send mondo timeout
  * wext: handle NULL extra data in iwe_stream_add_point better
  * sh_eth: R8A7740 supports packet shecksumming
  * net: phy: dp83867: fix irq generation
  * tg3: Fix race condition in tg3_get_stats64().
  * x86/boot: Add missing declaration of string functions
  * phy state machine: failsafe leave invalid RUNNING state
  * scsi: qla2xxx: Get mutex lock before checking optrom_state
  * drm/virtio: fix framebuffer sparse warning
  * virtio_blk: fix panic in initialization error path
  * ARM: 8632/1: ftrace: fix syscall name matching
  * mm, slab: make sure that KMALLOC_MAX_SIZE will fit into MAX_ORDER
  * lib/Kconfig.debug: fix frv build failure
  * signal: protect SIGNAL_UNKILLABLE from unintentional clearing.
  * mm: don't dereference struct page fields of invalid pages
  * workqueue: implicit ordered attribute should be overridable
  * Linux 4.4.81

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

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

[Kernel-packages] [Bug 1710646] Re: Xenial update to 4.4.80 stable release

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Xenial update to 4.4.80 stable release

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

Bug description:
  
  SRU Justification

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

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.80 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1711535] Re: Xenial update to 4.4.82 stable release

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Xenial update to 4.4.82 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.82 stable release shall be applied:
  * tcp: avoid setting cwnd to invalid ssthresh after cwnd reduction states
  * net: fix keepalive code vs TCP_FASTOPEN_CONNECT
  * bpf, s390: fix jit branch offset related to ldimm64
  * net: sched: set xt_tgchk_param par.nft_compat as 0 in ipt_init_target
  * tcp: fastopen: tcp_connect() must refresh the route
  * net: avoid skb_warn_bad_offload false positives on UFO
  * sparc64: Prevent perf from running during super critical sections
  * KVM: arm/arm64: Handle hva aging while destroying the vm
  * mm/mempool: avoid KASAN marking mempool poison checks as use-after-free
  * Linux 4.4.82

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

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

[Kernel-packages] [Bug 1711557] Re: Xenial update to 4.4.83 stable release

[Thadeu Lima de Souza Cascardo]

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

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

Title:
  Xenial update to 4.4.83 stable release

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

Bug description:
  SRU Justification

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

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.83 stable release shall be applied:
  * cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()
  * mm: ratelimit PFNs busy info message
  * iscsi-target: fix memory leak in iscsit_setup_text_cmd()
  * iscsi-target: Fix iscsi_np reset hung task during parallel delete
  * fuse: initialize the flock flag in fuse_file on allocation
  * nfs/flexfiles: fix leak of nfs4_ff_ds_version arrays
  * USB: serial: option: add D-Link DWM-222 device ID
  * USB: serial: cp210x: add support for Qivicon USB ZigBee dongle
  * USB: serial: pl2303: add new ATEN device id
  * usb: musb: fix tx fifo flush handling again
  * USB: hcd: Mark secondary HCD as dead if the primary one died
  * staging:iio:resolver:ad2s1210 fix negative IIO_ANGL_VEL read
  * iio: accel: bmc150: Always restore device to normal mode after
suspend-resume
  * iio: light: tsl2563: use correct event code
  * uas: Add US_FL_IGNORE_RESIDUE for Initio Corporation INIC-3069
  * USB: Check for dropped connection before switching to full speed
  * usb: core: unlink urbs from the tail of the endpoint's urb_list
  * usb: quirks: Add no-lpm quirk for Moshi USB to Ethernet Adapter
  * usb:xhci:Add quirk for Certain failing HP keyboard on reset after resume
  * iio: adc: vf610_adc: Fix VALT selection value for REFSEL bits
  * pnfs/blocklayout: require 64-bit sector_t
  * pinctrl: sunxi: add a missing function of A10/A20 pinctrl driver
  * pinctrl: samsung: Remove bogus irq_[un]mask from resource management
  * Linux 4.4.83

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

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

[Kernel-packages] [Bug 1553178] [NEW] perf: POWER8: Allow specifying Power PMU events by name rather than raw codes

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Sukadev Bhattiprolu  - 2015-10-19
20:45:40 ==

Power processor provides the ability to monitor a large number of Performance
Monitoring events. However the linux kernel/perf tool requires that a vast 
majority
of these events be specified by their raw codes:

 perf stat -e r100f2 sleep 1

We would instead like to be able to specify the events by its name:

   perf stat -e pm_1plus_ppc_cmpl sleep 1

where the event name name 'pm_1plus_ppc_cmpl' is defined in
the POWER PMU specs

== Comment: #1 - Sukadev Bhattiprolu  2015-10-27 13:43:20 ==
Here is a pointer to a newer version of the patch set:

  https://lkml.org/lkml/2015/10/26/624

== Comment: #10 - Sukadev Bhattiprolu - 2016-03-01 13:50:37 ==
(In reply to comment #9)
> any change in upstream status? If not, should we re-target this to 16.04.1
> and 16.10?

No, no comments yet from maintainer, so patches still stuck. Yes we could
re-target to 16.10 for now.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Leann Ogasawara (leannogasawara)
 Status: Confirmed


** Tags: architecture-ppc64 bot-comment bugnameltc-132028 severity-medium 
targetmilestone-inin1704
-- 
perf: POWER8: Allow specifying Power PMU events by name rather than raw codes
https://bugs.launchpad.net/bugs/1553178
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 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation

[malikons]

Hi,

Sorry for the delay in responding. I have tested the kernel few days ago
and it is working as expected. I do not see anymore kernel warnings.

Thanks,
Shiraz

** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty

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

Title:
  misleading kernel warning skb_warn_bad_offload during checksum
  calculation

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

Bug description:
  Even when the packet says checksum calculation is unnecessary the
  kernel will still check the checksum and display a warning that the
  checksum is bad.

  This has been fixed upstream in Kernel 4.11 by commit id:
  b2504a5dbef3305ef41988ad270b0e8ec289331c

  We have reports of Ubuntu 16.04 virtual machines (with ip forward
  enabled) displaying these warnings:

  
  [10480.074664] [ cut here ]
  [10480.074667] WARNING: CPU: 1 PID: 0 at 
/build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 
skb_warn_bad_offload+0xd1/0x120
  [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) 
len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1
  [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net 
pata_acpi floppy
  [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW  O
4.8.0-52-generic #55~16.04.1-Ubuntu
  [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 
04/01/2014
  [10480.074697]  0286 ec176c2ae03bc036 8beef5643870 
b7a2e7b3
  [10480.074699]  8beef56438c0  8beef56438b0 
b768314b
  [10480.074702]  098cb84fba80 8bed61f82000 8bee9915c000 
0005
  [10480.074704] Call Trace:
  [10480.074704][] dump_stack+0x63/0x90
  [10480.074708]  [] __warn+0xcb/0xf0
  [10480.074710]  [] warn_slowpath_fmt+0x5f/0x80
  [10480.074713]  [] ? ___ratelimit+0xa2/0xf0
  [10480.074714]  [] skb_warn_bad_offload+0xd1/0x120
  [10480.074716]  [] __skb_gso_segment+0xd8/0x140
  [10480.074717]  [] validate_xmit_skb+0x14f/0x2a0
  [10480.074719]  [] __dev_queue_xmit+0x322/0x6d0
  [10480.074720]  [] ? nf_nat_ipv4_fn+0x1a6/0x230 
[nf_nat_ipv4]
  [10480.074723]  [] dev_queue_xmit+0x10/0x20
  [10480.074725]  [] ip_finish_output2+0x292/0x380
  [10480.074726]  [] ? ipv4_confirm+0x7d/0x100 
[nf_conntrack_ipv4]
  [10480.074728]  [] ip_finish_output+0x132/0x1d0
  [10480.074729]  [] ? nf_hook_slow+0x73/0xd0
  [10480.074731]  [] ip_output+0x6e/0xf0
  [10480.074733]  [] ? 
__ip_flush_pending_frames.isra.40+0x90/0x90
  [10480.074736]  [] ip_forward_finish+0x43/0x70
  [10480.074738]  [] ip_forward+0x384/0x480
  [10480.074739]  [] ? ip_frag_mem+0x50/0x50
  [10480.074741]  [] ip_rcv_finish+0x11b/0x400
  [10480.074743]  [] ip_rcv+0x28b/0x3c0
  [10480.074744]  [] ? inet_del_offload+0x40/0x40
  [10480.074746]  [] __netif_receive_skb_core+0x524/0xab0
  [10480.074747]  [] ? kmem_cache_alloc+0xd7/0x1b0
  [10480.074749]  [] ? __build_skb+0x2a/0xe0
  [10480.074751]  [] __netif_receive_skb+0x18/0x60
  [10480.074753]  [] netif_receive_skb_internal+0x32/0xa0
  [10480.074754]  [] napi_gro_receive+0xcd/0x120
  [10480.074756]  [] virtnet_receive+0x1c3/0x970 [virtio_net]
  [10480.074758]  [] ? update_cfs_rq_load_avg+0x1f9/0x4c0
  [10480.074760]  [] virtnet_poll+0x1d/0x80 [virtio_net]
  [10480.074762]  [] net_rx_action+0x238/0x380
  [10480.074764]  [] __do_softirq+0xf6/0x280
  [10480.074765]  [] irq_exit+0xa3/0xb0
  [10480.074766]  [] do_IRQ+0x54/0xd0
  [10480.074768]  [] common_interrupt+0x82/0x82
  [10480.074768][] ? native_safe_halt+0x6/0x10
  [10480.074772]  [] default_idle+0x1e/0xd0
  [10480.074774]  [] arch_cpu_idle+0xf/0x20
  [10480.074775]  [] default_idle_call+0x2a/0x40
  [10480.074776]  [] cpu_startup_entry+0x2ea/0x350
  [10480.074778]  [] start_secondary+0x151/0x190
  [10480.074781] ---[ end trace 3a9bd18de5564b05 ]---

  
  We have recompiled your latest 16.04.2 kernel with this patch and confirmed 
that this warning does not happen. Could you please consider including this fix 
in your next 16.04 LTS release?

To manage notifications about this bug go to:
https://bugs.launchpad.net

[Kernel-packages] [Bug 1709032] Re: Creating conntrack entry failure with kernel 4.4.0-89

[Kleber Sacilotto de Souza]

Hi @libosvar,

Could you please verify the follow-up fix with the xenial kernel in
-proposed?

Thank you.

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

Title:
  Creating conntrack entry failure with kernel 4.4.0-89

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

Bug description:
  The functional job failure rate is at 100%. Every time some test gets
  stuck and job is killed after timeout.

  logstash query:
  
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
  %22gate-neutron-dsvm-functional-ubuntu-
  
xenial%5C%22%20AND%20tags%3Aconsole%20AND%20message%3A%5C%22Killed%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20timeout%20-s%209%5C%22

  2017-08-05 12:36:50.127672 | /home/jenkins/workspace/gate-neutron-
  dsvm-functional-ubuntu-xenial/devstack-gate/functions.sh: line 1129:
  15261 Killed  timeout -s 9 ${REMAINING_TIME}m bash -c
  "source $WORKSPACE/devstack-gate/functions.sh && $cmd"

  There are a few test executors left, which means there are more tests
  stuck:

  stack15468 15445 15468  0.0  0.0   328   796 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDTLPoX
  stack15469 15468 15469  1.5  1.8 139332 150008 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDTLPoX
  stack15470 15445 15470  0.0  0.0   328   700 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpICNqRQ
  stack15471 15470 15471  1.6  2.0 152056 164812 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpICNqRQ
  stack15474 15445 15474  0.0  0.0   328   792 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpe646Tl
  stack15475 15474 15475  1.6  1.9 149972 162516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpe646Tl
  stack15476 15445 15476  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpv2ovhz
  stack15477 15476 15477  1.2  1.8 136760 149160 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpv2ovhz
  stack15478 15445 15478  0.0  0.0   328   712 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpDqXE8S
  stack15479 15478 15479  1.5  1.9 148784 161004 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpDqXE8S
  stack15480 15445 15480  0.0  0.0   328   804 /bin/sh -c 
OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \ 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \ OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
\ OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-160} \ ${PYTHON:-python} -m subunit.run 
discover -t ./ ${OS_TEST_PATH:-./neutron/tests/unit}  --load-list /tmp/tmpTmmShS
  stack15482 15480 15482  1.6  1.9 148856 161516 python -m subunit.run 
discover -t ./ ./neutron/tests/functional --load-list /tmp/tmpTmmShS

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

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

[Kernel-packages] [Bug 1712254] Re: blktrace-smoke-test failed on s390x LPAR / zKVM with Xenial

[Colin Ian King]

Fix committed: http://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=d366d713b5ef09600f55131f8c473ebd82e6e330

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

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

Title:
  blktrace-smoke-test failed on s390x LPAR / zKVM with Xenial

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  This test failed on Xenial with:

  FAILED (expecting at least 1024 block traces events from the dd process, got 
0)
  FAILED (expecting at least 1024 block read traces events, got 107)
  FAILED (expecting at least 1024 block write traces events, got 8)

  Fail rate 2 out of 2 on each node (s2lp3 and s2lp6g001)

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

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

[Kernel-packages] [Bug 1682644] Re: IPR driver causes multipath to fail paths/stuck IO on Medium Errors

[Joseph Salisbury]

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

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

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

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

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

Title:
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

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

Bug description:
  SRU Justification:

  Impact: stuck I/O to multipath disks with medium errors (on IPR controllers)
  Fix: upstream commit for IPR driver to allow SCSI layer to handle the error
  Testcase: perform I/O to a failing disk which is multipathed (on IPR
controller), which returns SCSI Medium Errors (without the fix,
the I/O gets stuck). 
the commit message describes a test-case w/ sg_dd.

  
  ---Problem Description---
  IPR driver causes multipath to fail paths/stuck IO on Medium Errors

  This problem is resolved with this upstream accepted patch, scheduled for 
4.11.
  The detailed problem description and resolution are described in the commit 
message.

  > scsi: ipr: do not set DID_PASSTHROUGH on CHECK CONDITION
  > 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a470496d8e0a32e3d39f376984eb2c98ca5b3

  Please apply to 17.04 (target 16.04.3 HWE kernel) and 16.04 (GA kernel).
  Patch already applied to 17.10.

  The business justification for the SRU is:

  Clients with a dual-controller multipathed IPR configuration that
  eventually runs into failing disk/sectors, will experience an I/O hang
  once the drive reports a Medium Error, which can hang an application
  or even the root filesystem (whatever is doing I/O to the failing
  drive), potentially hanging the system.

  Thanks.

  ---Additional Hardware Info---
  Dual (IPR) controller setup, multipath enabled

  ---Steps to Reproduce---
  1) Use a disk with bad sectors (or force such condition, via internal/special 
tools)
  2) Multipath that disk
  3) Run IO to the multipath device on the bad sectors
  4) Both paths will be failed, and IO is stuck due to queue_if_no_path 
(enabled by default for IPR)

  The detailed problem description and resolution are described in the
  commit message.

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

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

[Kernel-packages] [Bug 1710922] Re: Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with QEMU upstream

[Joseph Salisbury]

bug 1709171 now disables CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE, so this
bug may be a duplicate of that?

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

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

Title:
  Ubuntu 17.10 ppc64el guest with MEMORY_HOTPLUG_DEFAULT_ONLINE=y gets a
  "kernel BUG at mm/memory_hotplug.c:2185" when hotplugging LMBs with
  QEMU upstream

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Daniel Henrique Barboza  - 2017-08-08 
09:13:31 ==
  - Host information: Ubuntu 16.10 running upstream QEMU

  $ uname -a
  Linux louis 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:16 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  $ cat /proc/cpuinfo
  processor : 0
  cpu   : POWER8E (raw), altivec supported
  clock : 2061.00MHz
  revision  : 2.1 (pvr 004b 0201)
  (...)
  timebase  : 51200
  platform  : PowerNV
  model : 8247-42L
  machine   : PowerNV 8247-42L
  firmware  : OPAL

  
  - qemu command line that launched the Ubuntu 17.10 ppc64el guest:

  sudo ./qemu-system-ppc64 -name migrate_qemu -boot strict=on --enable-
  kvm -device nec-usb-xhci,id=usb,bus=pci.0,addr=0xf -device spapr-
  vscsi,id=scsi0,reg=0x2000 -smp 1,maxcpus=4,sockets=4,cores=1,threads=1
  --machine pseries,accel=kvm,usb=off,dump-guest-core=off -m
  4G,slots=32,maxmem=32G -drive
  file=/home/danielhb/vm_imgs/ub1710.qcow2,format=qcow2,if=none,id
  =drive-virtio-disk0,cache=none -device virtio-blk-
  pci,scsi=off,bus=pci.0,addr=0x2,drive=drive-virtio-disk0,id=virtio-
  disk0,bootindex=1 -nographic

  
  - guest information: Ubuntu 17.10 ppc64el:

  root@ubuntu1710:~# uname -a
  Linux ubuntu1710 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
  root@ubuntu1710:~# 

  
  - Problem: hotplugging a LMB generates a guest kernel Oops:

  root@ubuntu1710:~# QEMU 2.9.90 monitor - type 'help' for more information
  (qemu) 
  (qemu) object_add memory-backend-ram,id=ram1,size=1G
  (qemu) device_add pc-dimm,id=dimm1,memdev=ram1
  (qemu) [  126.850952] kernel BUG at 
/build/linux-S1V_3d/linux-4.11.0/mm/memory_hotplug.c:2185!
  [  126.851285] Oops: Exception in kernel mode, sig: 5 [#1]
  [  126.851428] SMP NR_CPUS=2048 
  [  126.851428] NUMA 
  [  126.851546] pSeries
  [  126.851714] Modules linked in: vmx_crypto ib_iser rdma_cm iw_cm ib_cm 
ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi 
crc32c_vpmsum virtio_blk
  [  126.852447] CPU: 0 PID: 5 Comm: kworker/u8:0 Not tainted 4.11.0-10-generic 
#15-Ubuntu
  [  126.852656] Workqueue: pseries hotplug workque pseries_hp_work_fn
  [  126.852828] task: c000fea8 task.stack: c000fe118000
  [  126.853000] NIP: c0350268 LR: c03501e0 CTR: 

  [  126.853190] REGS: c000fe11b780 TRAP: 0700   Not tainted  
(4.11.0-10-generic)
  [  126.853390] MSR: 8282b033 
  [  126.853396]   CR: 42002422  XER: 2000
  [  126.853672] CFAR: c03501e4 SOFTE: 1 
  [  126.853672] GPR00: c03501e0 c000fe11ba00 c149eb00 
0001 
  [  126.853672] GPR04: c000f9901480 c000ffe21c00 003e 
0003 
  [  126.853672] GPR08: 0002 0003 0003 
303078302d303030 
  [  126.853672] GPR12: 2200 cfb8 c0110008 
c000fe1810c0 
  [  126.853672] GPR16: c000fe050ea8 0010 c000fc30 
c000fea0 
  [  126.853672] GPR20: c000f951a1a4 0004 0001 
0010 
  [  126.853672] GPR24: 0001 c000f951a1a0 0004 
 
  [  126.853672] GPR28:  0001 1000 
00014000 
  [  126.855221] NIP [c0350268] remove_memory+0xf8/0x100
  [  126.855338] LR [c03501e0] remove_memory+0x70/0x100
  [  126.855453] Call Trace:
  [  126.855520] [c000fe11ba00] [c03501e0] remove_memory+0x70/0x100 
(unreliable)
  [  126.855684] [c000fe11ba40] [c00b0880] dlpar_add_lmb+0x370/0x3f0
  [  126.855822] [c000fe11bb20] [c00b174c] dlpar_memory+0x7cc/0xd20
  [  126.855959] [c000fe11bbf0] [c00a9af8] 
handle_dlpar_errorlog+0xa8/0x170
  [  126.856118] [c000fe11bc60] [c00a9c54] 
pseries_hp_work_fn+0x94/0xa0
  [  126.856275] [c000fe11bc90] [c01071d0] 
process_one_work+0x2b0/0x5a0
  [  126.856430] [c000fe11bd20] [c0107568] worker_thread+0xa8/0x670
  [  126.856563] [c000fe11bdc0] [c0110164] kthread+0x164/0x1b0
  [  126.856695] [c000

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1712345

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

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

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

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

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

Title:
  sort ABI files with C.UTF-8 locale

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever we update the ABI files, the files may be sorted in a
  different order, even though their contents are the same. That happens
  because the system updating the ABI files may use a different locale
  than the one that was used previously.

  Always using the C.UTF-8 locale should fix that.

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

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

[Kernel-packages] [Bug 1696852] Re: [SRU][Zesty] arm64: Add support for handling memory corruption

[Manoj Iyer]

ubuntu@awrep4:~/mce-test/cases/function/hwpoison$ uname -a 
Linux awrep4 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:04 UTC 2017 
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@awrep4:~/mce-test/cases/function/hwpoison$

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

Title:
  [SRU][Zesty] arm64: Add support for handling memory corruption

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

Bug description:
  [Impact]
  Enable memory corruption handling for arm64

  [Test]
  run mce-test mce-test/cases/function/hwpoison

  [Fix]
  [0] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1376052.html
  [1] https://www.spinics.net/lists/arm-kernel/msg581657.html
  [1] https://lkml.org/lkml/2017/4/7/486
  [2] https://lkml.org/lkml/2017/4/5/402

  Jonathan (Zhixiong) Zhang (2):
    arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling
    arm64: kconfig: allow support for memory failure handling

  Punit Agrawal (2):
    arm64: hugetlb: Fix huge_pte_offset to return poisoned page table
  entries
    arm64: mm: Update perf accounting to handle poison faults

   arch/arm64/Kconfig   |  1 +
   arch/arm64/include/asm/pgtable.h |  2 +-
   arch/arm64/mm/fault.c| 90 

   arch/arm64/mm/hugetlbpage.c  | 29 +
   4 files changed, 67 insertions(+), 55 deletions(-)

  [Regression Potential]
  Changes are confined to ARM64 architecture. Detailed test results are posted 
to this bug as comments.

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

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

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Thadeu Lima de Souza Cascardo]

Hi, hbathini.

Why is it needed to restart kdump-tools after a DLPAR? Does it refer to
a memory hotplug operation? What is LTC bug #150353? Is it mirrored to
launchpad already?

Thank you very much.
Cascardo.

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

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de 
Souza Cascardo (cascardo)

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04.2: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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

[Kernel-packages] [Bug 1696852] Re: [SRU][Zesty] arm64: Add support for handling memory corruption

[Manoj Iyer]

ubuntu@awrep4:~/mce-test/cases/function/hwpoison$ sudo ./run_hugepage.sh

***
Pay attention:

This is the functional test for huge page support of HWPoison.
***

Num of Executed Test Case: 42   Num of Failed Case: 14

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

Title:
  [SRU][Zesty] arm64: Add support for handling memory corruption

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

Bug description:
  [Impact]
  Enable memory corruption handling for arm64

  [Test]
  run mce-test mce-test/cases/function/hwpoison

  [Fix]
  [0] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1376052.html
  [1] https://www.spinics.net/lists/arm-kernel/msg581657.html
  [1] https://lkml.org/lkml/2017/4/7/486
  [2] https://lkml.org/lkml/2017/4/5/402

  Jonathan (Zhixiong) Zhang (2):
    arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling
    arm64: kconfig: allow support for memory failure handling

  Punit Agrawal (2):
    arm64: hugetlb: Fix huge_pte_offset to return poisoned page table
  entries
    arm64: mm: Update perf accounting to handle poison faults

   arch/arm64/Kconfig   |  1 +
   arch/arm64/include/asm/pgtable.h |  2 +-
   arch/arm64/mm/fault.c| 90 

   arch/arm64/mm/hugetlbpage.c  | 29 +
   4 files changed, 67 insertions(+), 55 deletions(-)

  [Regression Potential]
  Changes are confined to ARM64 architecture. Detailed test results are posted 
to this bug as comments.

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

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

[Kernel-packages] [Bug 1696852] Re: [SRU][Zesty] arm64: Add support for handling memory corruption

[Manoj Iyer]

ubuntu@awrep4:~/mce-test/cases/function/hwpoison$ sudo ./run_soft.sh

***
Pay attention:

This test is soft mode of HWPoison functional test.
***



Running tsoft (simple soft offline test)
PASS: ./tsoft

Running tsoftinj (soft offline test on various types of pages)
anonymous
anonymous
private, diskbacked
./helpers.sh: line 28: 12471 Bus error   (core dumped) ./tsoftinj
FAIL: ./tsoftinj returned with failure.

Running random_offline (random soft offline test for 60 seconds)
ERROR: No soft offlining support in kernel
PASS: ./random_offline -t 60
Unpoisoning.
WARNING: hwpoison page counter is broken.
HardwareCorrupted: 8 kB

Num of Executed Test Case: 3Num of Failed Case: 1


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

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

Title:
  [SRU][Zesty] arm64: Add support for handling memory corruption

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

Bug description:
  [Impact]
  Enable memory corruption handling for arm64

  [Test]
  run mce-test mce-test/cases/function/hwpoison

  [Fix]
  [0] https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1376052.html
  [1] https://www.spinics.net/lists/arm-kernel/msg581657.html
  [1] https://lkml.org/lkml/2017/4/7/486
  [2] https://lkml.org/lkml/2017/4/5/402

  Jonathan (Zhixiong) Zhang (2):
    arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling
    arm64: kconfig: allow support for memory failure handling

  Punit Agrawal (2):
    arm64: hugetlb: Fix huge_pte_offset to return poisoned page table
  entries
    arm64: mm: Update perf accounting to handle poison faults

   arch/arm64/Kconfig   |  1 +
   arch/arm64/include/asm/pgtable.h |  2 +-
   arch/arm64/mm/fault.c| 90 

   arch/arm64/mm/hugetlbpage.c  | 29 +
   4 files changed, 67 insertions(+), 55 deletions(-)

  [Regression Potential]
  Changes are confined to ARM64 architecture. Detailed test results are posted 
to this bug as comments.

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

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

[Kernel-packages] [Bug 1705447] Re: misleading kernel warning skb_warn_bad_offload during checksum calculation

[Kleber Sacilotto de Souza]

Hi @malikons,

Would you be able to verify the fix with the xenial and zesty kernels on
-proposed?

Thanks.

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

Title:
  misleading kernel warning skb_warn_bad_offload during checksum
  calculation

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

Bug description:
  Even when the packet says checksum calculation is unnecessary the
  kernel will still check the checksum and display a warning that the
  checksum is bad.

  This has been fixed upstream in Kernel 4.11 by commit id:
  b2504a5dbef3305ef41988ad270b0e8ec289331c

  We have reports of Ubuntu 16.04 virtual machines (with ip forward
  enabled) displaying these warnings:

  
  [10480.074664] [ cut here ]
  [10480.074667] WARNING: CPU: 1 PID: 0 at 
/build/linux-hwe-X3pKE5/linux-hwe-4.8.0/net/core/dev.c:2444 
skb_warn_bad_offload+0xd1/0x120
  [10480.074669] docker0: caps=(0x0400ffbb78e9, 0x) 
len=2962 data_len=2834 gso_size=1448 gso_type=5 ip_summed=1
  [10480.074670] Modules linked in: veth nfsv3 nfs_acl rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic usbhid hid virtio_scsi psmouse virtio_net 
pata_acpi floppy
  [10480.074695] CPU: 1 PID: 0 Comm: swapper/1 Tainted: PW  O
4.8.0-52-generic #55~16.04.1-Ubuntu
  [10480.074696] Hardware name: Nutanix AHV, BIOS seabios-1.7.5-11.el6 
04/01/2014
  [10480.074697]  0286 ec176c2ae03bc036 8beef5643870 
b7a2e7b3
  [10480.074699]  8beef56438c0  8beef56438b0 
b768314b
  [10480.074702]  098cb84fba80 8bed61f82000 8bee9915c000 
0005
  [10480.074704] Call Trace:
  [10480.074704][] dump_stack+0x63/0x90
  [10480.074708]  [] __warn+0xcb/0xf0
  [10480.074710]  [] warn_slowpath_fmt+0x5f/0x80
  [10480.074713]  [] ? ___ratelimit+0xa2/0xf0
  [10480.074714]  [] skb_warn_bad_offload+0xd1/0x120
  [10480.074716]  [] __skb_gso_segment+0xd8/0x140
  [10480.074717]  [] validate_xmit_skb+0x14f/0x2a0
  [10480.074719]  [] __dev_queue_xmit+0x322/0x6d0
  [10480.074720]  [] ? nf_nat_ipv4_fn+0x1a6/0x230 
[nf_nat_ipv4]
  [10480.074723]  [] dev_queue_xmit+0x10/0x20
  [10480.074725]  [] ip_finish_output2+0x292/0x380
  [10480.074726]  [] ? ipv4_confirm+0x7d/0x100 
[nf_conntrack_ipv4]
  [10480.074728]  [] ip_finish_output+0x132/0x1d0
  [10480.074729]  [] ? nf_hook_slow+0x73/0xd0
  [10480.074731]  [] ip_output+0x6e/0xf0
  [10480.074733]  [] ? 
__ip_flush_pending_frames.isra.40+0x90/0x90
  [10480.074736]  [] ip_forward_finish+0x43/0x70
  [10480.074738]  [] ip_forward+0x384/0x480
  [10480.074739]  [] ? ip_frag_mem+0x50/0x50
  [10480.074741]  [] ip_rcv_finish+0x11b/0x400
  [10480.074743]  [] ip_rcv+0x28b/0x3c0
  [10480.074744]  [] ? inet_del_offload+0x40/0x40
  [10480.074746]  [] __netif_receive_skb_core+0x524/0xab0
  [10480.074747]  [] ? kmem_cache_alloc+0xd7/0x1b0
  [10480.074749]  [] ? __build_skb+0x2a/0xe0
  [10480.074751]  [] __netif_receive_skb+0x18/0x60
  [10480.074753]  [] netif_receive_skb_internal+0x32/0xa0
  [10480.074754]  [] napi_gro_receive+0xcd/0x120
  [10480.074756]  [] virtnet_receive+0x1c3/0x970 [virtio_net]
  [10480.074758]  [] ? update_cfs_rq_load_avg+0x1f9/0x4c0
  [10480.074760]  [] virtnet_poll+0x1d/0x80 [virtio_net]
  [10480.074762]  [] net_rx_action+0x238/0x380
  [10480.074764]  [] __do_softirq+0xf6/0x280
  [10480.074765]  [] irq_exit+0xa3/0xb0
  [10480.074766]  [] do_IRQ+0x54/0xd0
  [10480.074768]  [] common_interrupt+0x82/0x82
  [10480.074768][] ? native_safe_halt+0x6/0x10
  [10480.074772]  [] default_idle+0x1e/0xd0
  [10480.074774]  [] arch_cpu_idle+0xf/0x20
  [10480.074775]  [] default_idle_call+0x2a/0x40
  [10480.074776]  [] cpu_startup_entry+0x2ea/0x350
  [10480.074778]  [] start_secondary+0x151/0x190
  [10480.074781] ---[ end trace 3a9bd18de5564b05 ]---

  
  We have recompiled your latest 16.04.2 kernel with this patch and confirmed 
that this warning does not happen. Could you please consider including this fix 
in your next 16.04 LTS release?

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

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

[Kernel-packages] [Bug 1703430] Re: Set CONFIG_SATA_HIGHBANK=y on armhf

[Kleber Sacilotto de Souza]

Hi @danbnicholson,

Would you be able to verify the fix with the xenial and zesty kernels on
-proposed?

Thank you.

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

Title:
  Set CONFIG_SATA_HIGHBANK=y on armhf

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: CONFIG_SATA_HIGHBANK was changed from y to m after trusty,
  with no justification appearing in the git history. This can cause
  problems booting on some systems.

  Fix: Change the option back to y.

  Regression Potential: Minimal, as this only switches a driver from
  being a module to being built-in, and the driver will only be used if
  the device appears in a platform's device tree.

  ---

  Sometime between trusty and xenial, CONFIG_SATA_HIGHBANK was changed
  from y to m. I believe the change was in utopic, but it's hard to
  tell.

  This makes booting on Calxeda Highbank systems pretty difficult since
  you can't get to the root filesystem on a SATA disk unless you were
  smart enough to have initramfs-tools include the sata_highbank module.
  On a clean install, you'd need to know to drop out of the installer,
  and rebuild the initramfs appropriately.

  Any chance that could be changed back to y for armhf?

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

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

[Kernel-packages] [Bug 1712168] Re: Linux 4.12 refuses to load self-signed modules under Secure Boot with properly enrolled keys

[Seth Forshee]

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

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

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

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

Title:
  Linux 4.12 refuses to load self-signed modules under Secure Boot with
  properly enrolled keys

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Since version 4.12, Linux refuses to load my self-signed VirtualBox
  modules.

  $ lsb_release -d
  Description:  Ubuntu Artful Aardvark (development branch)

  $ uname -rvm
  4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:26:42 UTC 2017 x86_64

  $ sudo modprobe -v vboxdrv
  insmod /lib/modules/4.12.0-11-generic/misc/vboxdrv.ko 
  modprobe: ERROR: could not insert 'vboxdrv': Required key not available

  
  I've followed [this guide](https://askubuntu.com/a/768310/65926) to import 
the key an sign the modules. It worked until kernel 4.11.

  
  The key is properly enrolled:

  $ sudo mokutil --test-key .mok/mok-eric-carvalho.der 
  .mok/mok-eric-carvalho.der is already enrolled

  
  I think this happens because the kernel was built without 
CONFIG_MODULE_SIG_UEFI:

  $ ls -1 /boot/config-*
  /boot/config-4.11.0-13-generic
  /boot/config-4.12.0-11-generic

  $ grep CONFIG_MODULE_SIG_UEFI /boot/config-*
  /boot/config-4.11.0-13-generic:CONFIG_MODULE_SIG_UEFI=y

  
  Same problem with kernel 4.12.0-12.13 from the proposed repository.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-11-generic 4.12.0-11.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carvalho   3077 F pulseaudio
   /dev/snd/controlC0:  carvalho   3077 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Mon Aug 21 15:37:56 2017
  HibernationDevice: RESUME=UUID=8766d3eb-a19c-403c-829a-ff5fa7878e87
  InstallationDate: Installed on 2016-12-15 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161214)
  MachineType: LENOVO 80JE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed 
root=UUID=ca49cfac-7b28-4152-bf45-006806f69224 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-11-generic N/A
   linux-backports-modules-4.12.0-11-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B0CNA0WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 4A1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G40-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrB0CNA0WW:bd09/30/2016:svnLENOVO:pn80JE:pvrLenovoG40-80:rvnLENOVO:rnLancer4A1:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoG40-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80JE
  dmi.product.version: Lenovo G40-80
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

[Ionut Lenghel]

The same happens on 4.4.0-20 kernel.

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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

[Kernel-packages] [Bug 1696570] Re: [SRU][Zesty] Add UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64

[Manoj Iyer]

ubuntu@awrep4:~$ dmesg | grep -i -E 'hest|ghes|edac|hardware'
[0.00] ACPI: HEST 0x08EC 000288 (v01 QCOM   QDF2400  
0001 INTL 20150515)
[0.620910] HEST: Table parsing has been initialized.
[4.178101] EDAC MC: Ver: 3.0.0
[5.636210] ghes_edac: This EDAC driver relies on BIOS to enumerate memory 
and get error reports.
[5.644811] ghes_edac: Unfortunately, not all BIOSes reflect the memory 
layout correctly.
[5.652965] ghes_edac: So, the end result of using this driver varies from 
vendor to vendor.
[5.661385] ghes_edac: If you find incorrect reports, please contact your 
hardware vendor
[5.669545] ghes_edac: to correct its BIOS.
[5.673711] ghes_edac: This system has 12 DIMM sockets.
[5.679105] EDAC MC0: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.688460] EDAC MC1: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.697918] EDAC MC2: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.707375] EDAC MC3: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.716838] EDAC MC4: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.726342] GHES: APEI firmware first mode is enabled by APEI bit and WHEA 
_OSC.
[7.020635] qcom-emac QCOM8070:00 eth0: hardware id 64.1, hardware version 
1.3.0
ubuntu@awrep4:~$

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

Title:
  [SRU][Zesty] Add UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64

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

Bug description:
  [Impact]
  Adds UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64.

  [Test]
  Run mce-test for testing RAS features.

  [Fix]
  In maintainer (Will Deacon's) tree 
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=for-next/ras-apei

  [V17,01/11] acpi: apei: read ack upon ghes record consumption
  [V17,02/11] ras: acpi/apei: cper: add support for generic data v3 structure
  [V17,03/11] cper: add timestamp print to CPER status printing
  [V17,04/11] efi: parse ARM processor error
  [V17,05/11] arm64: exception: handle Synchronous External Abort
  [V17,06/11] acpi: apei: handle SEA notification type for ARMv8
  [V17,07/11] acpi: apei: panic OS with fatal error status block
  [V17,08/11] efi: print unrecognized CPER section
  [V17,09/11] ras: acpi / apei: generate trace event for unrecognized CPER 
section
  [V17,10/11] trace, ras: add ARM processor error trace event
  [V17,11/11] arm/arm64: KVM: add guest SEA support

  [Regression Potential]
  Patches deal with updates for RAS features on ARM64 with minor impact to 
generic code.Kernel was boot tested on ARM64, AMD64 and Power8 and no 
regressions were found.

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

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

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

[bugproxy]

--- Comment From dougm...@us.ibm.com 2017-08-22 09:22 EDT---
Can we get some answers as to why CFQ is the default scheduler? It seems like 
the expedient fix is to change the default to "deadline".

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be desirable to run HTX somewhere other than the conso

[Kernel-packages] [Bug 1712345] [NEW] sort ABI files with C.UTF-8 locale

[Thadeu Lima de Souza Cascardo]

Public bug reported:

Whenever we update the ABI files, the files may be sorted in a different
order, even though their contents are the same. That happens because the
system updating the ABI files may use a different locale than the one
that was used previously.

Always using the C.UTF-8 locale should fix that.

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

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

Title:
  sort ABI files with C.UTF-8 locale

Status in linux package in Ubuntu:
  New

Bug description:
  Whenever we update the ABI files, the files may be sorted in a
  different order, even though their contents are the same. That happens
  because the system updating the ABI files may use a different locale
  than the one that was used previously.

  Always using the C.UTF-8 locale should fix that.

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

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

[Kernel-packages] [Bug 1706141] Re: [ARM64] config EDAC_GHES=y depends on EDAC_MM_EDAC=y

[Manoj Iyer]

ubuntu@awrep4:~$ uname -a 
Linux awrep4 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:04 UTC 2017 
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@awrep4:~$ 


ubuntu@awrep4:~$ dmesg | grep -i -E "edac|hest|ghes"
[0.00] ACPI: HEST 0x08EC 000288 (v01 QCOM   QDF2400  
0001 INTL 20150515)
[0.620910] HEST: Table parsing has been initialized.
[4.178101] EDAC MC: Ver: 3.0.0
[5.636210] ghes_edac: This EDAC driver relies on BIOS to enumerate memory 
and get error reports.
[5.644811] ghes_edac: Unfortunately, not all BIOSes reflect the memory 
layout correctly.
[5.652965] ghes_edac: So, the end result of using this driver varies from 
vendor to vendor.
[5.661385] ghes_edac: If you find incorrect reports, please contact your 
hardware vendor
[5.669545] ghes_edac: to correct its BIOS.
[5.673711] ghes_edac: This system has 12 DIMM sockets.
[5.679105] EDAC MC0: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.688460] EDAC MC1: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.697918] EDAC MC2: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.707375] EDAC MC3: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.716838] EDAC MC4: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
[5.726342] GHES: APEI firmware first mode is enabled by APEI bit and WHEA 
_OSC.
ubuntu@awrep4:~$ 

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

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

Title:
  [ARM64] config EDAC_GHES=y depends on EDAC_MM_EDAC=y

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

Bug description:
  [Impact]
  In configs Zesty and Artful, EDAC_MM_EDAC is set to =m, this disables 
EDAC_GHES. Customers using RAS on ARM64 may want this functionality.

  According to RAS expert at QTI. EDAC_GHES is essential for ARMv8.0
  Server systems, as it enables firmware-first error handling of memory
  and CPU errors. Due to a lack of standard RAS architecture (or machine
  check architecture equivalent) on ARMv8.0 systems, APEI/GHES is the
  only mechanism available for reporting hardware errors (e.g. memory
  and CPU errors). This enables reporting of hardware errors, and also
  helps enable memory fault recovery mechanisms to extend the life of
  the system by offlining pages when recoverable uncorrected errors are
  encountered. Note that other ARM vendors will be going in this
  direction for hardware error handling.

  [Test]
  Test kernel available in 
https://launchpad.net/~centriq-team/+archive/ubuntu/lp1706141

  Boot the kernel and check dmesg for the following:
  $ dmesg | grep -i -E "edac|hest|ghes"
  [0.00] ACPI: HEST 0x0916 000288 (v01 QCOM   QDF2400  
0001 INTL 20150515)
  [0.620278] HEST: Table parsing has been initialized.
  [4.178298] EDAC MC: Ver: 3.0.0
  [5.664499] ghes_edac: This EDAC driver relies on BIOS to enumerate memory 
and get error reports.
  [5.673371] ghes_edac: Unfortunately, not all BIOSes reflect the memory 
layout correctly.
  [5.681542] ghes_edac: So, the end result of using this driver varies from 
vendor to vendor.
  [5.689972] ghes_edac: If you find incorrect reports, please contact your 
hardware vendor
  [5.698142] ghes_edac: to correct its BIOS.
  [5.702320] ghes_edac: This system has 12 DIMM sockets.
  [5.707717] EDAC MC0: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
  [5.717264] EDAC MC1: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
  [5.726806] EDAC MC2: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
  [5.736344] EDAC MC3: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
  [5.745883] EDAC MC4: Giving out device to module ghes_edac.c controller 
ghes_edac: DEV ghes (INTERRUPT)
  [5.755469] GHES: APEI firmware first mode is enabled by APEI bit and WHEA 
_OSC.

  [Fix]
  1. Apply RAS patch series submitted for SRU in Bug #1696570
  2. Set config option EDAC_MM_EDAC=y for ARM64, this will automatically set 
EDAC_GHES=y
  3. Remove edac_core from
  debian.master/abi//arm64/generic.modules

  [Regression Potential]
  The config change is limited to ARM64 architecture, and does not impact any 
other architecture. Potential for regressions is low.

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

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

[Kernel-packages] [Bug 1709738] Re: xfstest sanity checks 17 fails on data-hole-data inside page

[Joseph Salisbury]

Thanks for testing the upstream kernel.  Since the bug is fixed in
4.13-rc4, we should be able to perform a "Reverse" bisect to identify
the commit that fixes the bug.

We first need to identify the last kernel version that had the bug and
the first kernel version that did knot.

Can you test the following kernel:
4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1



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

** Changed in: ubuntu-power-systems
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Joseph Salisbury (jsalisbury)

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

Title:
  xfstest sanity checks 17 fails on  data-hole-data inside page

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Problem Description
  
  xfstests fails with Metadata corruption at leaf on ext4 filesystem

  Environment
  --
  Kernel Build:  4.12.1-041201-generic
  System Name : ltc-test-ci2
  Model  : 8247-22L
  Platform:  PowerNV ( P8 )
  Issue observed in P9 also.

  Uname output
  ---
  # uname -a
  Linux ltc-test-ci2 4.12.1-041201-generic #201707121132 SMP Wed Jul 12 
17:03:25 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:
  
  1. Create a loop device with ext4 filesystem
  2. git clone git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git; cd 
xfstests-dev
  3. make
  4. Create a local.config for running with created loop device
  5. Run xfstests-dev test  : ./check tests/ext4/445

  generic/445  [failed, exit status 1] - output mismatch (see 
/root/harish/xfstests-dev/results//generic/445.out.bad)
  --- tests/generic/445.out   2017-07-13 06:04:36.244322946 -0400
  +++ /root/harish/xfstests-dev/results//generic/445.out.bad  2017-07-14 
02:49:06.540352923 -0400
  @@ -1,2 +1,3 @@
   QA output created by 445
  -Silence is golden
  +seek sanity check failed!
  +(see /root/harish/xfstests-dev/results//generic/445.full for details)
  ...
  (Run 'diff -u tests/generic/445.out 
/root/harish/xfstests-dev/results//generic/445.out.bad'  to see the entire diff)

  
  Nothing observed in dmesg.

  Full log is attached.

  Note: Issue is also observed on distro kernel - 4.11.0-10-generic.

  It needs to have two disks you run the test on. Make sure you create
  those directories before running the test.

  # cat local.config
  export TEST_DEV=/dev/loop0
  export TEST_DIR=/mnt/test
  export SCRATCH_DEV=/dev/loop1
  export SCRATCH_MNT=/mnt/scratch

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

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

[Kernel-packages] [Bug 1707663] Re: include scsi_debug module on linux-image package

[Kleber Sacilotto de Souza]

Confirmed that the scsi_debug module is now included on linux-
image-4.4.0-1028-gke_4.4.0-1028.28 and linux-
image-4.4.0-1032-aws_4.4.0-1032.41 and the systemd ADT testcase is now
passing:

linux-aws 4.4.0-1032.41:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/s/systemd/20170816_190917_c32ed@/log.gz

linux-gke 4.4.0-1028.28:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/s/systemd/20170816_172840_bd0d5@/log.gz

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

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

Title:
  include scsi_debug module on linux-image package

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

Bug description:
  The systemd autopkgtest 'storage' testcase needs to load the
  scsi_debug module to perform its tests. The testcase is currently
  failing on the following custom kernels:

  * linux-aws: doesn't ship the scsi_debug module
  * linux-gke: ships the scsi_debug module on the linux-image-extra-*-gke 
module, however the package is not installed by autopkgtest since it's not 
installed by the linux-image-gke meta-package.

  linux-aws (4.4.0-1027.36) -
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  xenial/xenial/amd64/s/systemd/20170731_111630_98aef@/log.gz

  linux-gke (4.4.0-1023.23) -
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  xenial/xenial/amd64/s/systemd/20170731_111633_b6dbe@/log.gz

  One solution would be to include the scsi_debug.ko module on the
  linux-aws and linux-gke linux-image package so it would be available
  for the testcase. The module is very small (130KB on gke), it won't be
  automatically loaded on the system and it doesn't affect the normal
  operation when loaded.

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

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

[Kernel-packages] [Bug 1709784] Re: KVM on 16.04.3 throws an error

[Joseph Salisbury]

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => 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/1709784

Title:
  KVM on 16.04.3 throws an error

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Invalid

Bug description:
  Problem Description
  
  KVM on Ubuntu 16.04.3 throws an error when used
   
  ---uname output---
  Linux bastion-1 4.4.0-89-generic #112-Ubuntu SMP Mon Jul 31 19:37:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type =  8348-21C Habanero 
   
  ---Steps to Reproduce---
   Install 16.04.3

  install KVM like:

  apt-get install libvirt-bin qemu qemu-slof qemu-system qemu-utils

  then exit and log back in so virsh will work without sudo

  then run my spawn script

  $ cat spawn.sh
  #!/bin/bash

  img=$1
  qemu-system-ppc64 \
  -machine pseries,accel=kvm,usb=off -cpu host -m 512 \
  -display none -nographic \
  -net nic -net user \
  -drive "file=$img"

  with a freshly downloaded ubuntu cloud image

  sudo ./spawn.sh xenial-server-cloudimg-ppc64el-disk1.img

  And I get nothing on the output.

  and errors in dmesg

  
  ubuntu@bastion-1:~$ [  340.180295] Facility 'TM' unavailable, exception at 
0xd000148b7f10, MSR=90009033
  [  340.180399] Oops: Unexpected facility unavailable exception, sig: 6 [#1]
  [  340.180513] SMP NR_CPUS=2048 NUMA PowerNV
  [  340.180547] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables kvm_hv kvm binfmt_misc joydev input_leds 
mac_hid opal_prd ofpart cmdlinepart powernv_flash ipmi_powernv ipmi_msghandler 
mtd at24 uio_pdrv_genirq uio ibmpowernv powernv_rng vmx_crypto ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath 
linear mlx4_en hid_generic usbhid hid uas usb_storage ast i2c_algo_bit bnx2x 
ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mlx4_core drm 
ahci vxlan libahci ip6_udp_tunnel udp_tunnel mdio libcrc32c
  [  340.181331] CPU: 46 PID: 5252 Comm: qemu-system-ppc Not tainted 
4.4.0-89-generic #112-Ubuntu
  [  340.181382] task: c01e34c30b50 ti: c01e34ce4000 task.ti: 
c01e34ce4000
  [  340.181432] NIP: d000148b7f10 LR: d00014822a14 CTR: 
d000148b7e40
  [  340.181475] REGS: c01e34ce77b0 TRAP: 0f60   Not tainted  
(4.4.0-89-generic)
  [  340.181519] MSR: 90009033   CR: 22024848  
XER: 
  [  340.181629] CFAR: d000148b7ea4 SOFTE: 1 
  GPR00: d00014822a14 c01e34ce7a30 d000148cc018 c01e37bc 
  GPR04: c01db9ac c01e34ce7bc0   
  GPR08: 0001 c01e34c30b50 0001 d000148278f8 
  GPR12: d000148b7e40 cfb5b500  001f 
  GPR16: 3fff91c3 0080 3fffa8e34390 3fff9242f200 
  GPR20: 3fff92430010 01001de5c030 3fff9242eb60 100c1ff0 
  GPR24: 3fffc91fe990 3fff91c10028  c01e37bc 
  GPR28:  c01db9ac c01e37bc c01db9ac 
  [  340.182315] NIP [d000148b7f10] kvmppc_vcpu_run_hv+0xd0/0xff0 [kvm_hv]
  [  340.182357] LR [d00014822a14] kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182394] Call Trace:
  [  340.182413] [c01e34ce7a30] [c01e34ce7ab0] 0xc01e34ce7ab0 
(unreliable)
  [  340.182468] [c01e34ce7b70] [d00014822a14] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
  [  340.182522] [c01e34ce7ba0] [d0001481f674] 
kvm_arch_vcpu_ioctl_run+0x64/0x170 [kvm]
  [  340.182581] [c01e34ce7be0] [d00014813918] 
kvm_vcpu_ioctl+0x528/0x7b0 [kvm]
  [  340.182634] [c01e34ce7d40] [c02fffa0] do_vfs_ioctl+0x480/0x7d0
  [  340.182678] [c01e34ce7de0] [c03003c4] SyS_ioctl+0xd4/0xf0
  [  340.182723] [c01e34ce7e30] [c0009204] system_call+0x38/0xb4
  [  340.182766] Instruction dump:
  [  340.182788] e92d02a0 e9290a50 e9290108 792a07e3 41820058 e92d02a0 e9290a50 
e9290108 
  [  340.182863] 7927e8a4 78e71f87 40820ed8 e92d02a0 <7d4022a6> f9490ee8 
e92d02a0 7d4122a6 
  [  340.182938] ---[ end trace bc5080cb7d18f102 ]---
  [  340.276202] 

  
  This was with the latest ubuntu cloud image. I get the same thing when trying 
to use virt-install with an ISO image. 

  I have no way of loading a KVM on 16.04.3

  == Comment: #2 - Ja

[Kernel-packages] [Bug 1707663] Re: include scsi_debug module on linux-image package

[Kleber Sacilotto de Souza]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

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

Title:
  include scsi_debug module on linux-image package

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

Bug description:
  The systemd autopkgtest 'storage' testcase needs to load the
  scsi_debug module to perform its tests. The testcase is currently
  failing on the following custom kernels:

  * linux-aws: doesn't ship the scsi_debug module
  * linux-gke: ships the scsi_debug module on the linux-image-extra-*-gke 
module, however the package is not installed by autopkgtest since it's not 
installed by the linux-image-gke meta-package.

  linux-aws (4.4.0-1027.36) -
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  xenial/xenial/amd64/s/systemd/20170731_111630_98aef@/log.gz

  linux-gke (4.4.0-1023.23) -
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  xenial/xenial/amd64/s/systemd/20170731_111633_b6dbe@/log.gz

  One solution would be to include the scsi_debug.ko module on the
  linux-aws and linux-gke linux-image package so it would be available
  for the testcase. The module is very small (130KB on gke), it won't be
  automatically loaded on the system and it doesn't affect the normal
  operation when loaded.

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

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

[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

[Joseph Salisbury]

Can you see if the issue was happening back in 4.4.0-20:

https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/9583414

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Kai-Heng Feng]

Use the one I built should be recent enough.

You can still get one from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.13-rc6/

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/20/2

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Steve Roberts]

Appreciate all your efforts Kai-Heng

Where do I get the latest mainline kernel ?

Thanks, Steve

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/20/2017
  dmi.bios.vendor: American Me

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Steve Roberts]

Unfortunately still no joy

Aug 21 18:02:54 phs08 kernel: [0.00] Linux version 4.13.0-6-generic 
(root@linux) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)) 
#7~lp1705748 SMP Fri Aug 18 17:09:21 CST 2017 (Ubuntu 
4.13.0-6.7~lp1705748-generic 4.13.0-rc5)
Aug 21 18:02:54 phs08 kernel: [0.00] Command line: 
BOOT_IMAGE=/vmlinuz-4.13.0-6-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro
...
Mon Aug 21 19:55:03 BST 2017: performing suspend
Tue Aug 22 02:17:23 BST 2017: Awake.

Aug 22 02:21:36 phs08 kernel: [ 6999.857721] nvme nvme0: controller is down; 
will reset: CSTS=0x, PCI_STATUS=0x
Aug 22 02:21:36 phs08 kernel: [ 6999.901881] print_req_error: I/O error, dev 
nvme0n1, sector 137284824
Aug 22 02:21:36 phs08 kernel: [ 6999.901892] BTRFS error (device nvme0n1p5): 
bdev /dev/nvme0n1p5 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Aug 22 02:21:36 phs08 kernel: [ 6999.901933] print_req_error: I/O error, dev 
nvme0n1, sector 137286408
Aug 22 02:21:36 phs08 kernel: [ 6999.901937] BTRFS error (device nvme0n1p5): 
bdev /dev/nvme0n1p5 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
Aug 22 02:21:36 phs08 kernel: [ 6999.901970] print_req_error: I/O error, dev 
nvme0n1, sector 137296616
Aug 22 02:21:36 phs08 kernel: [ 6999.901974] BTRFS error (device nvme0n1p5): 
bdev /dev/nvme0n1p5 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
Aug 22 02:21:36 phs08 kernel: [ 6999.902007] print_req_error: I/O error, dev 
nvme0n1, sector 137284312
Aug 22 02:21:36 phs08 kernel: [ 6999.902010] BTRFS error (device nvme0n1p5): 
bdev /dev/nvme0n1p5 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
Aug 22 02:21:36 phs08 kernel: [ 6999.945333] pci_raw_set_power_state: 5 
callbacks suppressed
Aug 22 02:21:36 phs08 kernel: [ 6999.945338] nvme :01:00.0: Refused to 
change power state, currently in D3
Aug 22 02:21:36 phs08 kernel: [ 6999.945503] nvme nvme0: Removing after probe 
failure status: -19

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3

[Kernel-packages] [Bug 1708399] Re: kernel panic -not syncing: Fatal exception: panic_on_oops

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Incomplete => New

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

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]00029c0f 00c42001ea00 0001 
0001
  [477085.705554]00c42001c5c8 00c42082c1a0 02aa2666325e 

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

[bugproxy]

--- Comment From y...@cn.ibm.com 2017-08-22 05:08 EDT---
I haven't seen the test kernel package yet. Any update?

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

Title:
  kernel panic -not syncing: Fatal exception: panic_on_oops

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - QI YE  - 2017-08-02 04:11:25 ==
  ---Problem Description---
  Ubuntu got kernel panic

  ---uname output---
  #110-Ubuntu SMP Tue Jul 18 12:56:43 UTC 2017 s390x s390x s390x GNU/Linux
   
  ---Debugger Data---
  PID: 10991  TASK: 19872a0e8 CPU: 2   COMMAND: "hyperkube"
   LOWCORE INFO:
-psw  : 0x0004c0018000 0x00115fa6
-function : pcpu_delegate at 115fa6
-prefix   : 0x7fe42000
-cpu timer: 0x7ffab2827828aa50
-clock cmp: 0xd2eb8b31445e4200
-general registers:
   0x0004e001 0x001283b6
   0xc001 0x8380fcb8
   0x00115f9e 0x0056f6e2
   0x0004 0x00cf9070
   0x0001f3bfc000 0x00112fd8
   0x0001c72bb400 0x0002
   0x7fffc000 0x007c9ef0
   0x00115f9e 0x8380fc18
-access registers:
   0x03ff 0x7910 00 00
   00 00 00 00
   00 00 00 00
   00 00 00 00
-control registers:
   0x14066a12 0x7e6d81c7
   0x00011140 00
   0x2aef 0x0400
   0x5000 0x7e6d81c7
   00 00
   00 00
   00 0x00cfc007
   0xdb00 0x00011280
-floating point registers:
   0x409c7e258000 0x401de4e0
   00 0x3fd24407ab0e073a
   0x3ff0 0x3fee
   0x3fef218f8a7a41a0 0x3fee
   0x0080 00
   0x03ff7f80 0x02aa4940e9e0
   0xd401 0x03ffe81fe110
   00 0x03fff2cfe638

   #0 [8380fc78] smp_find_processor_id at 1160f8
   #1 [8380fc90] machine_kexec at 1135d4
   #2 [8380fcb8] crash_kexec at 1fbb8a
   #3 [8380fd88] panic at 27d0e0
   #4 [8380fe28] die at 1142cc
   #5 [8380fe90] do_low_address at 12215e
   #6 [8380fea8] pgm_check_handler at 7c2ab4
   PSW:  070520018000 02aa267e0e42 (user space)
   GPRS:   02aa2c4fd690 0001
 02aa2c4fd690 03ff7fffee38  0002
 00029c0f 00c42001ea00 0001 0001
 00c42001c5c8 00c42082c1a0 02aa2666325e 03ff7fffed90 
   
  Contact Information = Chee Ye / y...@cn.ibm.com 
   
  Stack trace output:
   no
   
  Oops output:
   [43200.761465] docker0: port 10(vethb9132e9) entered forwarding state
  [50008.560926] hrtimer: interrupt took 1698076 ns
  [123483.768984] systemd[1]: apt-daily.timer: Adding 7h 34min 22.582204s 
random time.
  [123483.930058] systemd[1]: apt-daily.timer: Adding 2h 18min 14.857162s 
random time.
  [123484.064879] systemd[1]: apt-daily.timer: Adding 10h 46min 2.301756s 
random time.
  [123484.824760] systemd[1]: apt-daily.timer: Adding 6h 16min 22.178655s 
random time.
  [153113.703126] conntrack: generic helper won't handle protocol 47. Please 
consider loading the specific helper module.
  [477085.704538] Low-address protection: 0004 ilc:2 [#1] SMP
  [477085.704551] Modules linked in: xt_physdev veth xt_recent xt_comment 
xt_mark xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo 
iptable_nat nf_nat_ipv4 xt_addrtype nf_nat br_netfilter bridge stp llc aufs 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack iptable_filter ip_tables x_tables ghash_s390 prng 
aes_s390 des_s390 des_generic sha512_s390 qeth_l2 sha256_s390 qeth sha1_s390 
qdio sha_common ccwgroup vmur dasd_eckd_mod dasd_mod
  [477085.705522] CPU: 2 PID: 10991 Comm: hyperkube Not tainted 
4.4.0-87-generic #110-Ubuntu
  [477085.705525] task: 00019872a0e8 ti: 8380c000 task.ti: 
8380c000
  [477085.705529] User PSW : 070520018000 02aa267e0e42
  [477085.705532]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
EA:3
  User GPRS:   02aa2c4fd690 
0001
  [477085.705539]02aa2c4fd690 03ff7fffee38  
0002
  [477085.705553]00029c0f 00c42001ea00 0001 
0001
  [477085.705554]00c42001c5c8 00c42082c1a0 02aa2666325e 
00

[Kernel-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services

[Chris Valean]

The same happens on 4.4.0-40 kernel, I think this goes with comment #6.

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

Title:
  [Hyper-V] LIS daemons fail to start after disable/re-enable VM
  integration services

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

Bug description:
  Issue description: Hyper-V daemons fail to start after disable/re-
  enable VM integration services.

  Platform: host independent
  Affected daemons - KVP, FCOPY and VSS.

  Distribution name and release: Ubuntu 16.04, Ubuntu 17.04
  Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 
4.10.0-19-generic (for Ubuntu 17.04)

  Repro rate: 100%

  Steps to reproduce:
  1.Start VM with Guest Services enabled (FCopy daemon starts automatically)
  2.Go to File > Settings > Integration Services, uncheck Guest Services 
and apply (FCopy daemon will stop at this point)
  3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running).
  This is the issue. systemd monitors for the service and if we have the hook 
for the Guest Service, it tries to start the daemon again.
  systemd attempt to start any of the LIS daemons will fail, but manually 
executing the daemon binary, it will start the daemon.

  Additional Info:
  - the steps above can be repro'd with KVP / Data Exchange integration service 
as well.
  - Manually starting hv_fcopy_daemon works fine.
  - other distros (RHEL) does not have this behavior, the LIS daemons are 
started automatically by systemd once we re-enable the integration service.

  On the upstream kernel and the upstream hv daemons, these messages are 
recorded in syslog, once we re-enable the Guest service:
  HV_FCOPY: pread failed: Bad file descriptor
  systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: hv-fcopy-daemon.service: Unit entered failed state.
  systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'.

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

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