[Kernel-packages] [Bug 1682711] Re: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used

[Chris Cheney]

I sent a follow up email to Lenovo but don't expect to hear back from
them until sometime after next Monday.

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

Title:
  PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force /
  setpci used

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is somewhat similar in issue to lp#1377596.

  I have a "Lenovo ThinkCentre m900 Tiny" with an "Intel 600p" NVMe
  drive in it.

  As far as I can tell from dissembling the FADT PCIe ASPM is not set to
  disabled but the ports are not enabled in UEFI during boot.

  I also notice that the PCIe ASPM debug files are not in sysfs like
  they normally are ie: link_state

  I tried running the following manually but I think it must not be
  enough as the NVMe drive does not run any cooler as it does in a
  system with known working ASPM.

  setpci -s 00:1b.0 0x50.B=0x3
  setpci -s 00:1c.0 0x50.B=0x3
  setpci -s 01:00.0 0x80.B=0x3
  setpci -s 02:00.0 0x50.B=0x3

  I noticed via lspci that the root ports say ASPM not supported even
  though the FADT doesn't have them disabled. Is that the reason its
  still not working and how do I work around that issue?

  Also is there something specific I can tell Lenovo to do to fix this
  issue on their end, if it can't be worked around in Linux? I have an
  open case with them via the UEFI engineering team but so far its been
  slow going since I don't have anything concrete to tell them to fix.

  ===

  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1) (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: [40] 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 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
  LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, 
Exit Latency L0s <1us, L1 <16us
  ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt+ ABWMgmt-
  SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
  Slot #0, PowerLimit 25.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: Range ABC, TimeoutDis+, LTR+, 
OBFF Not Supported ARIFwd+
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Disabled 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: -3.5dB, 
EqualizationComplete+, EqualizationPhase1+
   EqualizationPhase2+, EqualizationPhase3+, 
LinkEqualizationRequest-
  Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Address: fee00218  Data: 
  Capabilities: [90] Subsystem: Lenovo Sunrise Point-H PCI Root Port
  Capabilities: [a0] Power Management version 3
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
  Capabilities: [100 v1] Advanced Error Reporting
  UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES- TLP- 

[Kernel-packages] [Bug 1682041] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 20, failed: 1

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/ms10-35-mcdivittB0-kernel__4.4.0-74.95__2017-04-14_04-17-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1682041] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 20, failed: 1

[Brad Figg]

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/ms10-34-mcdivittB0-kernel__4.4.0-74.95__2017-04-14_04-16-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1682711] Re: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used

[Chris Cheney]

Talking to Matthew Garrett on irc he said that he thinks this may only
be fixable via an UEFI change.

04:33 < ccheney> anyone know if it is possible to change a setting in LnkCap on 
a pci device? My pcie ports apparently have 'ASPM not supported' set and I need 
to turn it on somehow
04:33 < ccheney> its on a skylake system
04:35 < mjg59> ccheney: It's set by either the firmware or the chipset itself
04:35 < ccheney> the FADT doesn't have aspm disabled but its not enabled on the 
ports or the devices, setpci seems to be able to turn it on for LnkCtl but 
LnkCap seems to be overriding it?
04:35 < mjg59> lnkcap represents what the link is capable of
04:35 < ccheney> mjg59: is there anyway to force enable it afterwards via 
initrd (similar to acpi replacement tables) or something like that?
04:35 < mjg59> ccheney: Nope
04:35 < ccheney> ugh :(
04:35 < mjg59> Not that I know of

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

Title:
  PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force /
  setpci used

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is somewhat similar in issue to lp#1377596.

  I have a "Lenovo ThinkCentre m900 Tiny" with an "Intel 600p" NVMe
  drive in it.

  As far as I can tell from dissembling the FADT PCIe ASPM is not set to
  disabled but the ports are not enabled in UEFI during boot.

  I also notice that the PCIe ASPM debug files are not in sysfs like
  they normally are ie: link_state

  I tried running the following manually but I think it must not be
  enough as the NVMe drive does not run any cooler as it does in a
  system with known working ASPM.

  setpci -s 00:1b.0 0x50.B=0x3
  setpci -s 00:1c.0 0x50.B=0x3
  setpci -s 01:00.0 0x80.B=0x3
  setpci -s 02:00.0 0x50.B=0x3

  I noticed via lspci that the root ports say ASPM not supported even
  though the FADT doesn't have them disabled. Is that the reason its
  still not working and how do I work around that issue?

  Also is there something specific I can tell Lenovo to do to fix this
  issue on their end, if it can't be worked around in Linux? I have an
  open case with them via the UEFI engineering team but so far its been
  slow going since I don't have anything concrete to tell them to fix.

  ===

  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1) (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: [40] 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 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
  LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, 
Exit Latency L0s <1us, L1 <16us
  ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt+ ABWMgmt-
  SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
  Slot #0, PowerLimit 25.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: Range ABC, TimeoutDis+, LTR+, 
OBFF Not Supported ARIFwd+
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Disabled 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: -3.5dB, 
EqualizationComplete+, EqualizationPhase1+
   EqualizationPhase2+, EqualizationPhase3+, 

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force /
  setpci used

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is somewhat similar in issue to lp#1377596.

  I have a "Lenovo ThinkCentre m900 Tiny" with an "Intel 600p" NVMe
  drive in it.

  As far as I can tell from dissembling the FADT PCIe ASPM is not set to
  disabled but the ports are not enabled in UEFI during boot.

  I also notice that the PCIe ASPM debug files are not in sysfs like
  they normally are ie: link_state

  I tried running the following manually but I think it must not be
  enough as the NVMe drive does not run any cooler as it does in a
  system with known working ASPM.

  setpci -s 00:1b.0 0x50.B=0x3
  setpci -s 00:1c.0 0x50.B=0x3
  setpci -s 01:00.0 0x80.B=0x3
  setpci -s 02:00.0 0x50.B=0x3

  I noticed via lspci that the root ports say ASPM not supported even
  though the FADT doesn't have them disabled. Is that the reason its
  still not working and how do I work around that issue?

  Also is there something specific I can tell Lenovo to do to fix this
  issue on their end, if it can't be worked around in Linux? I have an
  open case with them via the UEFI engineering team but so far its been
  slow going since I don't have anything concrete to tell them to fix.

  ===

  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1) (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: [40] 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 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
  LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, 
Exit Latency L0s <1us, L1 <16us
  ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt+ ABWMgmt-
  SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
  Slot #0, PowerLimit 25.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: Range ABC, TimeoutDis+, LTR+, 
OBFF Not Supported ARIFwd+
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Disabled 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: -3.5dB, 
EqualizationComplete+, EqualizationPhase1+
   EqualizationPhase2+, EqualizationPhase3+, 
LinkEqualizationRequest-
  Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Address: fee00218  Data: 
  Capabilities: [90] Subsystem: Lenovo Sunrise Point-H PCI Root Port
  Capabilities: [a0] Power Management version 3
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
  Capabilities: [100 v1] Advanced Error Reporting
  UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES- TLP- FCP- CmpltTO- 

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1682712

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

Title:
  Laptop lid is always reported as closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Livefan S1 laptop lid is _always_ reported as closed.

  
  #cat /proc/acpi/button/lid/LID0/state 
  state:  closed

  #lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  `acpi_listen` doesn't detect any events

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

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

[Kernel-packages] [Bug 1650752] Re: Thinkpad Yoga 13 fails to suspend after update to 4.8.0.30.39

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Thinkpad Yoga 13 fails to suspend after update to  4.8.0.30.39

Status in linux package in Ubuntu:
  Expired

Bug description:
  It suspends then automatically resumes a few seconds later. Latest
  kernel update brings back screen auto-rotate feature, but also breaks
  suspend. Not sure if this is related. Previous few kernel releases had
  auto-rotate feature disabled, but suspend worked properly and did not
  resume from suspend automatically.

  [  737.222140] PM: Syncing filesystems ... done.
  [  737.233688] PM: Preparing system for sleep (mem)
  [  737.234034] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  737.236194] Double checking all user space processes after OOM killer 
disable... (elapsed 0.000 seconds) 
  [  737.236333] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) 
done.
  [  737.237252] PM: Suspending system (mem)
  [  737.237283] Suspending console(s) (use no_console_suspend to debug)
  [  737.404190] sd 0:0:0:0: [sda] Synchronizing SCSI cache
  [  737.406041] sd 0:0:0:0: [sda] Stopping disk
  [  738.065297] PM: suspend of devices complete after 827.881 msecs
  [  738.085132] PM: late suspend of devices complete after 19.829 msecs
  [  738.086363] xhci_hcd :00:14.0: System wakeup enabled by ACPI
  [  738.105461] PM: noirq suspend of devices complete after 20.326 msecs
  [  738.105897] ACPI: Preparing to enter system sleep state S3
  [  738.361104] ACPI : EC: EC stopped
  [  738.361105] PM: Saving platform NVS memory
  [  738.361121] Disabling non-boot CPUs ...
  [  738.361598] Broke affinity for irq 23
  [  738.361604] Broke affinity for irq 40
  [  738.361611] Broke affinity for irq 43
  [  738.363673] smpboot: CPU 1 is now offline
  [  738.386513] Broke affinity for irq 23
  [  738.386519] Broke affinity for irq 40
  [  738.386525] Broke affinity for irq 43
  [  738.386533] Broke affinity for irq 59
  [  738.387594] smpboot: CPU 2 is now offline
  [  738.418497] Broke affinity for irq 1
  [  738.418508] Broke affinity for irq 9
  [  738.418513] Broke affinity for irq 12
  [  738.418520] Broke affinity for irq 23
  [  738.418523] Broke affinity for irq 40
  [  738.418526] Broke affinity for irq 42
  [  738.418528] Broke affinity for irq 43
  [  738.418534] Broke affinity for irq 59
  [  738.419573] smpboot: CPU 3 is now offline
  [  738.440159] ACPI: Low-level resume complete
  [  738.440235] ACPI : EC: EC started
  [  738.440236] PM: Restoring platform NVS memory
  [  738.440625] Enabling non-boot CPUs ...
  [  738.463840] x86: Booting SMP configuration:
  [  738.463841] smpboot: Booting Node 0 Processor 1 APIC 0x1
  [  738.466739]  cache: parent cpu1 should not be sleeping
  [  738.466961] CPU1 is up
  [  738.487864] smpboot: Booting Node 0 Processor 2 APIC 0x2
  [  738.490555]  cache: parent cpu2 should not be sleeping
  [  738.490870] CPU2 is up
  [  738.535883] smpboot: Booting Node 0 Processor 3 APIC 0x3
  [  738.538658]  cache: parent cpu3 should not be sleeping
  [  738.539378] CPU3 is up
  [  738.549959] ACPI: Waking up from system sleep state S3
  [  739.483697] xhci_hcd :00:14.0: System wakeup disabled by ACPI
  [  739.483772] PM: noirq resume of devices complete after 32.141 msecs
  [  739.484169] PM: early resume of devices complete after 0.371 msecs
  [  739.487691] rtc_cmos 00:01: System wakeup disabled by ACPI
  [  739.488427] sd 0:0:0:0: [sda] Starting disk
  [  739.531853] xhci_hcd :00:14.0: port 4 resume PLC timeout
  [  739.547494] xhci_hcd :00:14.0: port 3 resume PLC timeout
  [  739.635640] usb 1-1.7: reset full-speed USB device number 3 using ehci-pci
  [  739.783794] usb 2-4: reset full-speed USB device number 2 using xhci_hcd
  [  739.802392] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [  739.802641] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  [  739.802643] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  [  739.802723] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
  [  739.802888] ata1.00: supports DRM functions and may not be fully accessible
  [  739.803249] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  [  739.803251] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  [  739.803272] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
  [  739.803357] ata1.00: supports DRM functions and may not be fully accessible
  [  739.803421] ata1.00: configured for UDMA/133
  [  739.823628] usb 1-1.8: reset full-speed USB device number 5 using ehci-pci
  [  740.043736] usb 2-6: reset high-speed USB device number 4 using xhci_hcd
  [  740.070524] psmouse serio1: 

[Kernel-packages] [Bug 1682711] Re: PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used

[Chris Cheney]

The setpci commands I used modified the LnkCtl option but not the LnkCap
values. I'm not sure but suspect that the LnkCap values are what are
causing the problem.

--

LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, Exit Latency L0s 
<1us, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

LnkCap: Port #7, Speed 8GT/s, Width x1, ASPM not supported, Exit Latency L0s 
<1us, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

vs

LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, Exit Latency L0s 
unlimited, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

LnkCap: Port #7, Speed 8GT/s, Width x1, ASPM not supported, Exit Latency L0s 
unlimited, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

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

Title:
  PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force /
  setpci used

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is somewhat similar in issue to lp#1377596.

  I have a "Lenovo ThinkCentre m900 Tiny" with an "Intel 600p" NVMe
  drive in it.

  As far as I can tell from dissembling the FADT PCIe ASPM is not set to
  disabled but the ports are not enabled in UEFI during boot.

  I also notice that the PCIe ASPM debug files are not in sysfs like
  they normally are ie: link_state

  I tried running the following manually but I think it must not be
  enough as the NVMe drive does not run any cooler as it does in a
  system with known working ASPM.

  setpci -s 00:1b.0 0x50.B=0x3
  setpci -s 00:1c.0 0x50.B=0x3
  setpci -s 01:00.0 0x80.B=0x3
  setpci -s 02:00.0 0x50.B=0x3

  I noticed via lspci that the root ports say ASPM not supported even
  though the FADT doesn't have them disabled. Is that the reason its
  still not working and how do I work around that issue?

  Also is there something specific I can tell Lenovo to do to fix this
  issue on their end, if it can't be worked around in Linux? I have an
  open case with them via the UEFI engineering team but so far its been
  slow going since I don't have anything concrete to tell them to fix.

  ===

  00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1) (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: [40] 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 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
  LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, 
Exit Latency L0s <1us, L1 <16us
  ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt+ ABWMgmt-
  SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
  Slot #0, PowerLimit 25.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: Range ABC, TimeoutDis+, LTR+, 
OBFF Not Supported ARIFwd+
  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Disabled ARIFwd-
  LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- 

[Kernel-packages] [Bug 1682711] [NEW] PCIe ASPM disabled even when enabled in FADT and pcie_aspm=force / setpci used

[Chris Cheney]

Public bug reported:

This is somewhat similar in issue to lp#1377596.

I have a "Lenovo ThinkCentre m900 Tiny" with an "Intel 600p" NVMe drive
in it.

As far as I can tell from dissembling the FADT PCIe ASPM is not set to
disabled but the ports are not enabled in UEFI during boot.

I also notice that the PCIe ASPM debug files are not in sysfs like they
normally are ie: link_state

I tried running the following manually but I think it must not be enough
as the NVMe drive does not run any cooler as it does in a system with
known working ASPM.

setpci -s 00:1b.0 0x50.B=0x3
setpci -s 00:1c.0 0x50.B=0x3
setpci -s 01:00.0 0x80.B=0x3
setpci -s 02:00.0 0x50.B=0x3

I noticed via lspci that the root ports say ASPM not supported even
though the FADT doesn't have them disabled. Is that the reason its still
not working and how do I work around that issue?

Also is there something specific I can tell Lenovo to do to fix this
issue on their end, if it can't be worked around in Linux? I have an
open case with them via the UEFI engineering team but so far its been
slow going since I don't have anything concrete to tell them to fix.

===

00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev 
f1) (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: [40] 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 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, 
Exit Latency L0s <1us, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ DLActive+ 
BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 25.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: Range ABC, TimeoutDis+, LTR+, OBFF 
Not Supported ARIFwd+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Disabled 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: -3.5dB, 
EqualizationComplete+, EqualizationPhase1+
 EqualizationPhase2+, EqualizationPhase3+, 
LinkEqualizationRequest-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00218  Data: 
Capabilities: [90] Subsystem: Lenovo Sunrise Point-H PCI Root Port
Capabilities: [a0] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Advanced Error Reporting
UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [140 v1] Access Control Services
ACSCap: SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd- 
EgressCtrl- DirectTrans-
ACSCtl: SrcValid- TransBlk- ReqRedir- 

[Kernel-packages] [Bug 1682712] Re: Laptop lid is always reported as closed

[Alex]

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

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

Title:
  Laptop lid is always reported as closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Livefan S1 laptop lid is _always_ reported as closed.

  
  #cat /proc/acpi/button/lid/LID0/state 
  state:  closed

  #lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  `acpi_listen` doesn't detect any events

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

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

[Kernel-packages] [Bug 1682712] [NEW] Laptop lid is always reported as closed

[Alex]

Public bug reported:

On Livefan S1 laptop lid is _always_ reported as closed.


#cat /proc/acpi/button/lid/LID0/state 
state:  closed

#lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

`acpi_listen` doesn't detect any events

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

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

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

Title:
  Laptop lid is always reported as closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Livefan S1 laptop lid is _always_ reported as closed.

  
  #cat /proc/acpi/button/lid/LID0/state 
  state:  closed

  #lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  `acpi_listen` doesn't detect any events

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

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

[Kernel-packages] [Bug 1682041] fozzie (i386) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/fozzie__4.4.0-74.95__2017-04-14_03-18-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1671278] Re: Xorg freeze

[Michael Richey]

You guys work fast!

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Freezes the screen and locks the computer, needing to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar  8 20:40:04 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-11-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.10.0-9-generic, x86_64: installed
   virtualbox, 5.1.14, 4.10.0-11-generic, x86_64: installed
  GpuHangFrequency: Continuously
  GpuHangReproducibility: I don't know
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G98M [GeForce 9300M GS] [1028:02bb]
  InstallationDate: Installed on 2014-01-10 (1153 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: Dell Inc. Vostro 1320
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-11-generic 
root=UUID=5189c31e-9b68-4026-a657-b0d301136218 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0R235J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd09/10/2009:svnDellInc.:pnVostro1320:pvrNull:rvnDellInc.:rn0R235J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1320
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.75-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1

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

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

[Kernel-packages] [Bug 1682041] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/ms10-35-mcdivittB0-kernel__4.4.0-74.95__2017-04-14_03-52-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1682041] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/ms10-34-mcdivittB0-kernel__4.4.0-74.95__2017-04-14_03-51-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1682184] Re: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2

[Jeffery Painter]

I installed v4.10.8 and left stress running on for about an hour.  Just
got back and the system has been stable for the past 5 hours without any
failures.

painter@merlin:~$ uname -a
Linux merlin 4.10.8-041008-generic #201703310531 SMP Fri Mar 31 09:33:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

painter@merlin:~$ uptime
 23:46:02 up  5:07,  1 user,  load average: 0.19, 0.08, 0.01

Leaving tomorrow morning on vacation, so if you want me to test anything
else, it will have to be when I get back next Monday.

Thanks!
Jeff

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

Title:
  Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu
  17.04-beta2

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

Bug description:
  
  Apologies in advance if this is not the right place to file the bug, but I 
have been running Ubuntu 17.04-beta2 for 2 days now and have had a kernel bug 
cause system lock up twice now requiring a hard reboot. Only apps open were 
Chrome and Thunderbird.

  root@merlin:/var/log# lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  root@merlin:/var/log# uname -a
  Linux merlin 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz

  System: Dell XPS 8900 (default setup) booting from
  ata1.00: ATA-9: Samsung SSD 850 EVO 250GB, EMT01B6Q, max UDMA/133


  Apr 12 12:23:48 merlin kernel: [ 8390.993645] [ cut here 
]
  Apr 12 12:23:48 merlin kernel: [ 8390.993655] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
  Apr 12 12:23:48 merlin kernel: [ 8390.993661] invalid opcode:  [#1] SMP
  Apr 12 12:23:48 merlin kernel: [ 8390.993665] Modules linked in: rfcomm 
joydev input_leds pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) cmac 
vboxdrv(OE) bnep usblp hid_logitech_hidpp snd_hda_codec_hdmi hid_logitech_dj 
uas usb_storage btusb btrtl usbhid snd_usb_audio snd_usbmidi_lib uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media 
snd_hda_codec_realtek snd_hda_codec_generic dell_wmi sparse_keymap 
snd_hda_intel snd_hda_codec snd_hda_core dell_smbios snd_hwdep snd_pcm 
snd_seq_midi snd_seq_midi_event intel_rapl snd_rawmidi dcdbas 
x86_pkg_temp_thermal intel_powerclamp coretemp nvidia_uvm(POE) snd_seq 
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul snd_seq_device 
ghash_clmulni_intel pcbc aesni_intel snd_timer aes_x86_64 crypto_simd 
glue_helper cryptd intel_cstate intel_rapl_perf snd soundcore
  Apr 12 12:23:48 merlin kernel: [ 8390.993735]  serio_raw hci_uart btbcm btqca 
btintel bluetooth mei_me mei wmi shpchp intel_pch_thermal acpi_als kfifo_buf 
industrialio intel_lpss_acpi mac_hid intel_lpss acpi_pad parport_pc ppdev lp 
parport ip_tables x_tables autofs4 dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea 
sysfillrect e1000e sysimgblt fb_sys_fops psmouse drm ahci ptp pps_core libahci 
video pinctrl_sunrisepoint i2c_hid pinctrl_intel hid fjes
  Apr 12 12:23:48 merlin kernel: [ 8390.993790] CPU: 2 PID: 4607 Comm: JS 
Helper Tainted: P   OE   4.10.0-19-generic #21-Ubuntu
  Apr 12 12:23:48 merlin kernel: [ 8390.993793] Hardware name: Dell Inc. XPS 
8900/0XJ8C4, BIOS 2.0.3 09/18/2015
  Apr 12 12:23:48 merlin kernel: [ 8390.993798] task: 9e46d69a2e00 
task.stack: bb5d4603c000
  Apr 12 12:23:48 merlin kernel: [ 8390.993809] RIP: 
0010:__migration_entry_wait+0x16a/0x180
  Apr 12 12:23:48 merlin kernel: [ 8390.993813] RSP: :bb5d4603fd68 
EFLAGS: 00010246
  Apr 12 12:23:48 merlin kernel: [ 8390.993818] RAX: 0017c0048078 RBX: 
e73757462bf0 RCX: e73757462bf0
  Apr 12 12:23:48 merlin kernel: [ 8390.993822] RDX: 0001 RSI: 
9e46d18af800 RDI: e73756614000
  Apr 12 12:23:48 merlin kernel: [ 8390.993825] RBP: bb5d4603fd80 R08: 
9e47458645c0 R09: 9e47458645c0
  Apr 12 12:23:48 merlin kernel: [ 8390.993829] R10: 7f59927000c8 R11: 
0206 R12: e73756614000
  Apr 12 12:23:48 merlin kernel: [ 8390.993832] R13: 3e598500 R14: 
bb5d4603fe30 R15: 9e46d1a3be10
  Apr 12 12:23:48 merlin kernel: [ 8390.993837] FS:  7f59774fa700() 
GS:9e476548() knlGS:
  Apr 12 12:23:48 merlin kernel: [ 8390.993841] CS:  0010 DS:  ES:  
CR0: 80050033
  Apr 12 12:23:48 merlin kernel: [ 8390.993844] CR2: 7f593df00018 CR3: 
0005d6951000 CR4: 003406e0
  Apr 12 12:23:48 merlin kernel: [ 8390.993848] DR0:  DR1: 
 DR2: 
  Apr 12 12:23:48 merlin kernel: [ 8390.993852] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Apr 12 12:23:48 merlin kernel: [ 8390.993854] Call Trace:
  Apr 12 

[Kernel-packages] [Bug 1682704] [NEW] nvme controller is down will reset (regression in zesty on XPS laptop)

[Mike C. Fletcher]

Public bug reported:

I've just upgraded a Dell XPS 15" (9550, early 2016 model) with a
Samsung NVME drive. Machine was stable under Kubuntu 16.10 with the same
drive. After the upgrade to Zesty I've now seen 3 hard lockups (machine
loses root fs) with the following message printed:

nvme controller is down will reset

there are also messages printed to the virtual console reporting failure
to write to the underlying disk from the home-directory encfs.

Linux tass 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 17.04 (Kubuntu)

dmesg about nvme:
[1.748864] nvme nvme0: pci function :04:00.0
[1.864553]  nvme0n1: p1 p2 p3 p4 p5 p6
[2.961181] EXT4-fs (nvme0n1p6): mounted filesystem with ordered data mode. 
Opts: (null)
[4.172546] EXT4-fs (nvme0n1p6): re-mounted. Opts: errors=remount-ro

NVME cli shows 57 errors in the error-log, all seeming to be invalid
field or invalid namespace. Not sure if that's since boot or since
machine creation.

Smartctrl shows...
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.10.0-19-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:   PM951 NVMe SAMSUNG 512GB
Serial Number:  S29PNXAH142328
Firmware Version:   BXV77D0Q
PCI Vendor/Subsystem ID:0x144d
IEEE OUI Identifier:0x002538
Controller ID:  1
Number of Namespaces:   1
Namespace 1 Size/Capacity:  512,110,190,592 [512 GB]
Namespace 1 Utilization:365,503,283,200 [365 GB]
Namespace 1 Formatted LBA Size: 512
Local Time is:  Thu Apr 13 23:21:32 2017 EDT
Firmware Updates (0x06):3 Slots
Optional Admin Commands (0x0017):   Security Format Frmw_DL *Other*
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Maximum Data Transfer Size: 32 Pages

Supported Power States
St Op Max   Active Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 + 6.00W   --0  0  0  05   5
 1 + 4.20W   --1  1  1  1   30  30
 2 + 3.10W   --2  2  2  2  100 100
 3 -   0.0700W   --3  3  3  3  5005000
 4 -   0.0050W   --4  4  4  4 2000   22000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 + 512   0 0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0x)
Critical Warning:   0x00
Temperature:35 Celsius
Available Spare:100%
Available Spare Threshold:  50%
Percentage Used:0%
Data Units Read:2,724,346 [1.39 TB]
Data Units Written: 6,568,756 [3.36 TB]
Host Read Commands: 52,921,997
Host Write Commands:157,530,880
Controller Busy Time:   1,349
Power Cycles:   831
Power On Hours: 5,358
Unsafe Shutdowns:   46
Media and Data Integrity Errors:0
Error Information Log Entries:  57

Error Information (NVMe Log 0x01, max 64 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc  LBA  NSIDVS
  0 57 0  0x0004  0x4016  0x0000 1 -
  1 56 0  0x0004  0x4016  0x0000 1 -
  2 55 0  0x0004  0x4016  0x0000 1 -
  3 54 0  0x0004  0x4016  0x0000 1 -
  4 53 0  0x0004  0x4016  0x0000 1 -
  5 52 0  0x0004  0x4016  0x0000 1 -
  6 51 0  0x0004  0x4016  0x0000 1 -
  7 50 0  0x0004  0x4016  0x0000 1 -
  8 49 0  0x001f  0x4004  0x0000 0 -
  9 48 0  0x001e  0x4004  0x0000 0 -
 10 47 0  0x001f  0x4004  0x0000 0 -
 11 46 0  0x001e  0x4004  0x0000 0 -
 12 45 0  0x001f  0x4004  0x0000 0 -
 13 44 0  0x001e  0x4004  0x0000 0 -
 14 43 0  0x  0x4016  0x0000 1 -
 15 42 0  0x0004  0x4016  0x0000 1 -
... (41 entries not shown)

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

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

Title:
  nvme controller is down will reset (regression in zesty on XPS laptop)

Status in linux-signed package in Ubuntu:
  New

Bug description:
  I've just upgraded a 

Re: [Kernel-packages] [Bug 1610979] Re: Call Trace disabling IRQ 17, affects USB mouse

[js1]

I have done irqpoll in the past, and it didn't help.  I will try again
with 4.10.10.

On Thu, Apr 13, 2017 at 11:58 AM, Kai-Heng Feng
 wrote:
> Did you see the message "[ 795.982336] irq 17: nobody cared (try booting with 
> the "irqpoll" option)
> "?
>
> Can you try to boot with kernel parameter "irqpoll"?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1610979
>
> Title:
>   Call Trace disabling IRQ 17, affects USB mouse
>
> Status in linux package in Ubuntu:
>   Expired
>
> Bug description:
>   [  477.964736] Call Trace:
>   [  477.964738][] dump_stack+0x63/0x90
>   [  477.964750]  [] __report_bad_irq+0x33/0xc0
>   [  477.964753]  [] note_interrupt+0x247/0x290
>   [  477.964756]  [] handle_irq_event_percpu+0x167/0x1d0
>   [  477.964758]  [] handle_irq_event+0x3e/0x60
>   [  477.964761]  [] handle_fasteoi_irq+0x96/0x150
>   [  477.964765]  [] handle_irq+0x1a/0x30
>   [  477.964769]  [] do_IRQ+0x4b/0xd0
>   [  477.964772]  [] common_interrupt+0x82/0x82
>   [  477.964773][] ? mwait_idle+0x76/0x180
>   [  477.964780]  [] arch_cpu_idle+0xf/0x20
>   [  477.964784]  [] default_idle_call+0x2a/0x40
>   [  477.964786]  [] cpu_startup_entry+0x2f1/0x350
>   [  477.964790]  [] start_secondary+0x154/0x190
>   [  477.964792] handlers:
>   [  477.964796] [] usb_hcd_irq
>   [  477.964798] [] usb_hcd_irq
>   [  477.964802] [] ata_bmdma_interrupt
>   [  477.964804] Disabling IRQ #17
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: linux-image-4.4.0-31-generic 4.4.0-31.50
>   ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
>   Uname: Linux 4.4.0-31-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  js13126 F pulseaudio
>   Date: Mon Aug  8 09:47:58 2016
>   HibernationDevice: RESUME=UUID=62dbd34f-d371-4ae5-8687-e061a2ff9ec0
>   InstallationDate: Installed on 2016-04-24 (105 days ago)
>   InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
> (20160420.1)
>   ProcEnviron:
>TERM=xterm
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcFB:
>
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
> root=UUID=1ac1bc6f-01e2-4f75-8a7c-3c2586ae7d6a ro
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-4.4.0-31-generic N/A
>linux-backports-modules-4.4.0-31-generic  N/A
>linux-firmware1.157.2
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 07/15/2009
>   dmi.bios.vendor: Intel Corp.
>   dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: DP35DP
>   dmi.board.vendor: Intel Corporation
>   dmi.board.version: AAD81073-209
>   dmi.chassis.type: 3
>   dmi.modalias: 
> dmi:bvnIntelCorp.:bvrDPP3510J.86A.0572.2009.0715.2346:bd07/15/2009:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-209:cvn:ct3:cvr:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1610979/+subscriptions


-- 
Jiann-Ming Su
"I have to decide between two equally frightening options.
 If I wanted to do that, I'd vote." --Duckman
"The system's broke, Hank.  The election baby has peed in
the bath water.  You got to throw 'em both out."  --Dale Gribble
"Those who vote decide nothing.
Those who count the votes decide everything.”  --Joseph Stalin

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

Title:
  Call Trace disabling IRQ 17, affects USB mouse

Status in linux package in Ubuntu:
  Expired

Bug description:
  [  477.964736] Call Trace:
  [  477.964738][] dump_stack+0x63/0x90
  [  477.964750]  [] __report_bad_irq+0x33/0xc0
  [  477.964753]  [] note_interrupt+0x247/0x290
  [  477.964756]  [] handle_irq_event_percpu+0x167/0x1d0
  [  477.964758]  [] handle_irq_event+0x3e/0x60
  [  477.964761]  [] handle_fasteoi_irq+0x96/0x150
  [  477.964765]  [] handle_irq+0x1a/0x30
  [  477.964769]  [] do_IRQ+0x4b/0xd0
  [  477.964772]  [] common_interrupt+0x82/0x82
  [  477.964773][] ? mwait_idle+0x76/0x180
  [  477.964780]  [] arch_cpu_idle+0xf/0x20
  [  477.964784]  [] default_idle_call+0x2a/0x40
  [  477.964786]  [] cpu_startup_entry+0x2f1/0x350
  [  477.964790]  [] start_secondary+0x154/0x190
  [  477.964792] handlers:
  [  477.964796] [] usb_hcd_irq
  [  477.964798] [] usb_hcd_irq
  [  477.964802] [] ata_bmdma_interrupt
  [  477.964804] Disabling IRQ #17

  

[Kernel-packages] [Bug 1676747] Re: Enable lspcon on i915

[Shih-Yuan Lee]

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

Title:
  Enable lspcon on i915

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Some new machine comes with both HDMI and DP (not DP over TB), in this
  case, lspcon support is required to make HDMI work.

  The patch series cover letter has  more information:
  https://patchwork.freedesktop.org/series/4756/

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

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

[Kernel-packages] [Bug 1680513] Re: Migrating KSM page causes the VM lock up as the KSM page merging list is too large

[Gavin Guo]

** Description changed:

+ [Impact]
  After numad is enabled and there are several VMs running on the same
  host machine(host kernel version: 4.4.0-72-generic #93), the
  softlockup messages can be observed inside the VMs' dmesg.
  
  First, the crashdump was captured when the symptom was observed. At
  the first glance, it looks like an IPI lost issue. The numad process
  initiates a migration of memory, and as part of this, needs to flush
  the TLB cache of another CPU. When the crash dump was taken, that
- other CPU has the TLB flush pending, but not executed. 
+ other CPU has the TLB flush pending, but not executed.
  
  The numad kernel task is holding a semaphore lock mmap_sem(for the
  VM's memory) to do the migration, and the tasks that actually end up
  being blocked are other virtual CPUs for the same VM. These tasks need
  to access or make changes to the memory map for the VM because of the
  VM page fault, but cannot acquire the semaphore lock.
  
  However, the original thoughts on the root cause (unhandled IPI or csd
  lock issue) are incorrect.
  
- 
  We originally suspected an issue with a lost IPI (inter processor
  interrupt) that performs remote CPU cache flushes during page
  migration, or a known issue with the "csd" lock used to synchronize
  the remote CPU cache flush.  A lost IPI would be a function of the
  system firmware or chipset (it is not a CPU issue), but the known csd
- issue is hardware independent. 
+ issue is hardware independent.
  
  Gavin created the hotfix kernel with changes in the csd_lock_wait
  function that would time out if the unlock never happens (the end
  result of either cause), and print messages to the console when that
- timeout occurred. The messages look like: 
+ timeout occurred. The messages look like:
  
  csd_lock_wait called %d times
  
  csd: Detected non-responsive CSD lock (#%d) on CPU#%02d, waiting
  %Ld.%03Ld secs for CPU#%02d
  
  However, the VMs are still experiencing the hangs, but the
  csd_lock_wait timeout is not happening. This suggests that the csd
  lock / lost IPI is not the actual cause.
  
  In the crash dump, the numad task has induced a migration, and the
- stack is as follows: 
+ stack is as follows:
  
- #1 [885f8fb4fb78] smp_call_function_many 
- #2 [885f8fb4fbc0] native_flush_tlb_others 
- #3 [885f8fb4fc08] flush_tlb_page 
- #4 [885f8fb4fc30] ptep_clear_flush 
- #5 [885f8fb4fc60] try_to_unmap_one 
- #6 [885f8fb4fcd0] rmap_walk_ksm 
- #7 [885f8fb4fd28] rmap_walk 
- #8 [885f8fb4fd80] try_to_unmap 
- #9 [885f8fb4fdc8] migrate_pages 
- #10 [885f8fb4fe80] do_migrate_pages 
- 
+ #1 [885f8fb4fb78] smp_call_function_many
+ #2 [885f8fb4fbc0] native_flush_tlb_others
+ #3 [885f8fb4fc08] flush_tlb_page
+ #4 [885f8fb4fc30] ptep_clear_flush
+ #5 [885f8fb4fc60] try_to_unmap_one
+ #6 [885f8fb4fcd0] rmap_walk_ksm
+ #7 [885f8fb4fd28] rmap_walk
+ #8 [885f8fb4fd80] try_to_unmap
+ #9 [885f8fb4fdc8] migrate_pages
+ #10 [885f8fb4fe80] do_migrate_pages
  
  The frame #1 is actually in the csd_lock_wait function mentioned
  above, but the compiler has optimized that call and it does not appear
- in the stack. 
+ in the stack.
  
  What happens here is that do_migrate_pages (frame #10) acquires the
  semaphore that everything else is waiting for (and that eventually
  produce the hang warnings), and it holds that semaphore for the
  duration of the page migration.  This strongly suggests that this
  single do_migrate_pages call is taking in excess of 10 seconds, and if
  the csd lock is not stuck, then something else within its call path is
- not functioning correctly. 
+ not functioning correctly.
  
  We originally suspected that the lost IPI/csd lock hang was
  responsible for the hung task timeouts, but in the absence of the csd
- warning messages, the cause presumably lies elsewhere. 
+ warning messages, the cause presumably lies elsewhere.
  
  A KSM function appears in frame #6; this is the function that will
- search out the merged pages to handle them for the migration. 
+ search out the merged pages to handle them for the migration.
  
- Gavin have tried to disassemble the code and finally find the 
+ Gavin have tried to disassemble the code and finally find the
  stable_node->hlist is as long as 2306920 entries:
  
- rmap_item list(stable_node->hlist): 
- stable_node: 0x881f836ba000 stable_node->hlist->first = 
0x883f3e5746b0 
+ rmap_item list(stable_node->hlist):
+ stable_node: 0x881f836ba000 stable_node->hlist->first = 0x883f3e5746b0
  
- struct hlist_head { 
- [0] struct hlist_node *first; 
- } 
- struct hlist_node { 
- [0] struct hlist_node *next; 
- [8] struct hlist_node **pprev; 
- } 
+ struct hlist_head {
+ [0] struct hlist_node *first;
+ }
+ struct hlist_node {
+ [0] struct hlist_node *next;
+ [8] struct hlist_node **pprev;
+ }
  
  crash> list hlist_node.next 0x883f3e5746b0 > rmap_item.lst
  
- $ wc -l rmap_item.lst 
+ $ wc -l 

[Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Andrei Aldea]

Got sound working folks. See the repository for the new updated install
script (it's at the top of the description).

Only things not working perfectly now are Sleep (my script makes it so
the screen just shuts down to save some power) and SD card. Cheers!

https://github.com/Grippentech/Asus-E200HA-Linux-Post-Install-Script

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

[Kernel-packages] [Bug 1682041] fozzie (amd64) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/fozzie__4.4.0-74.95__2017-04-14_02-06-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Eric Joslyn]

@Marc Singer.  The new 4.10.3 kernel seems to work ok in my Gigabyte
AB350 Gaming 3. No need for acpi=off, and all 16 cores show up in the
system monitor. Is there anything specific that I can test?

I originally compiled the latest 4.11 rc6 kernel out of sheer curiosity.
I wanted to see what was default for the amd gpio option (it was
active). Once I had the code, I thought what the heck, might as well
compile it.

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

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

[NancyHsu]

Reply to comment #32.
We didn't remember what kernel version we were running with the kernel in 
comment #16.

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1682041] fozzie (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/fozzie__4.4.0-74.95__2017-04-14_01-42-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1682041] fozzie (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-lowlatency/fozzie__4.4.0-74.95__2017-04-14_01-19-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1682041] fozzie (i386) - tests ran: 19, failed: 1

[Brad Figg]

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/fozzie__4.4.0-74.95__2017-04-14_00-06-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1384297] Re: After system resume, Intel i915 graphics hangs

[spike speigel]

I get this on my Dell XPS 13 9360:

$ uname -a
Linux blackhole 4.10.0-19-generic #21~16.04.1-Ubuntu SMP Fri Apr 7 08:20:02 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial


I cannot switch terminals to try and recover.  Blank screen.  Must reboot.  Not 
good.

** Tags added: xenial

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

Title:
  After system resume, Intel i915 graphics hangs

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Won't Fix

Bug description:
  [ 3871.551684] WARNING: CPU: 2 PID: 2161 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:5997 
intel_display_power_put+0x14c/0x160 [i915]()
  [ 3871.551686] Modules linked in: ctr ccm ec_sys dm_crypt intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul arc4 ghash_clmulni_intel rfcomm dm_multipath scsi_dh bnep 
aesni_intel iwlmvm hid_multitouch aes_x86_64 mac80211 lrw gf128mul glue_helper 
ablk_helper cryptd snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi 
snd_hda_codec_generic nfsd rtsx_pci_ms snd_hda_intel auth_rpcgss 
snd_hda_controller nfs_acl btusb memstick joydev snd_hda_codec nfs lockd 
snd_hwdep bluetooth snd_seq_midi snd_seq_midi_event sunrpc snd_rawmidi 
snd_soc_rt5640 6lowpan_iphc fscache snd_soc_rl6231 cfg80211 snd_seq 
snd_soc_core snd_compress binfmt_misc snd_pcm_dmaengine snd_pcm snd_seq_device 
tpm_infineon snd_timer lpc_ich dw_dmac dw_dmac_core i2c_hid 8250_dw 
i2c_designware_platform
  [ 3871.551704]  i2c_designware_core snd shpchp snd_soc_sst_acpi mei_me mei 
spi_pxa2xx_platform mac_hid soundcore serio_raw parport_pc ppdev lp parport 
btrfs xor raid6_pq dm_mirror dm_region_hash dm_log mmc_block usbhid hid 
rtsx_pci_sdmmc i915 i2c_algo_bit rtsx_pci psmouse ahci drm_kms_helper r8169 
libahci mii drm wmi sdhci_acpi video sdhci
  [ 3871.551717] CPU: 2 PID: 2161 Comm: unity-system-co Tainted: GW I   
3.16.0-23-generic #30-Ubuntu
  [ 3871.551718] Hardware name: System76, IncDarter 
UltraThin/Darter UltraThin, BIOS 4.6.5 10/28/2013
  [ 3871.551719]  0009 8800d70efae0 8177fcbc 

  [ 3871.551721]  8800d70efb18 8106fd8d 88021008002c 
000b
  [ 3871.551722]  880210088520 8802106c3000 88021008 
8800d70efb28
  [ 3871.551724] Call Trace:
  [ 3871.551729]  [] dump_stack+0x45/0x56
  [ 3871.551732]  [] warn_slowpath_common+0x7d/0xa0
  [ 3871.551734]  [] warn_slowpath_null+0x1a/0x20
  [ 3871.551742]  [] intel_display_power_put+0x14c/0x160 
[i915]
  [ 3871.551754]  [] 
modeset_update_crtc_power_domains+0x204/0x210 [i915]
  [ 3871.551765]  [] 
haswell_modeset_global_resources+0xe/0x10 [i915]
  [ 3871.551775]  [] __intel_set_mode+0x5fa/0xab0 [i915]
  [ 3871.551785]  [] intel_set_mode+0x16/0x30 [i915]
  [ 3871.551794]  [] intel_crtc_set_config+0xa4a/0xda0 [i915]
  [ 3871.551804]  [] drm_mode_set_config_internal+0x61/0xe0 
[drm]
  [ 3871.551813]  [] drm_framebuffer_remove+0xe1/0x140 [drm]
  [ 3871.551822]  [] drm_mode_rmfb+0xdf/0x110 [drm]
  [ 3871.551828]  [] drm_ioctl+0x1df/0x680 [drm]
  [ 3871.551831]  [] ? dentry_free+0x34/0x40
  [ 3871.551833]  [] ? __dentry_kill+0x17a/0x200
  [ 3871.551835]  [] ? dput+0x180/0x1c0
  [ 3871.551837]  [] ? mntput+0x24/0x40
  [ 3871.551838]  [] do_vfs_ioctl+0x2c8/0x4a0
  [ 3871.551840]  [] ? fput+0xe/0x10
  [ 3871.551842]  [] ? task_work_run+0xbc/0xf0
  [ 3871.551843]  [] SyS_ioctl+0x81/0xa0
  [ 3871.551845]  [] system_call_fastpath+0x1a/0x1f

  [ 3871.551854] WARNING: CPU: 2 PID: 2161 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:6001 
intel_display_power_put+0xf9/0x160 [i915]()
  [ 3871.551854] Modules linked in: ctr ccm ec_sys dm_crypt intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul arc4 ghash_clmulni_intel rfcomm dm_multipath scsi_dh bnep 
aesni_intel iwlmvm hid_multitouch aes_x86_64 mac80211 lrw gf128mul glue_helper 
ablk_helper cryptd snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi 
snd_hda_codec_generic nfsd rtsx_pci_ms snd_hda_intel auth_rpcgss 
snd_hda_controller nfs_acl btusb memstick joydev snd_hda_codec nfs lockd 
snd_hwdep bluetooth snd_seq_midi snd_seq_midi_event sunrpc snd_rawmidi 
snd_soc_rt5640 6lowpan_iphc fscache snd_soc_rl6231 cfg80211 snd_seq 
snd_soc_core snd_compress binfmt_misc snd_pcm_dmaengine snd_pcm snd_seq_device 
tpm_infineon snd_timer lpc_ich dw_dmac dw_dmac_core i2c_hid 8250_dw 
i2c_designware_platform
  [ 3871.551872]  i2c_designware_core snd shpchp snd_soc_sst_acpi mei_me mei 
spi_pxa2xx_platform mac_hid soundcore serio_raw parport_pc ppdev lp parport 
btrfs xor raid6_pq dm_mirror dm_region_hash dm_log mmc_block usbhid hid 

[Kernel-packages] [Bug 1673564] Re: ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on

[David Daney]

The Experimental patch in comment #9, although it seems to prevent the
hang under some workloads, puts the code in the wrong function.  We
really think it should be at the end of __vgic_v3_save_state()

We will have a revised patch after some further testing.

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

Title:
  ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
  vhost=on

Status in edk2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a followup of an earlier thread/bug that we have narrowed down
  to an incompatibility/issue with vhost support in qemu-efi. Without
  vhost=on qemu seems to be working fine.

  I have tested several edk2 firmwares:
  - xenial
  - zesty
  - Fedora: 
ftp://195.220.108.108/linux/fedora-secondary/development/rawhide/Everything/aarch64/os/Packages/e/edk2-aarch64-20170209git296153c5-2.fc26.noarch.rpm

  I have also tested with different guests:
  - cirros: 
https://download.cirros-cloud.net/daily/20161201/cirros-d161201-aarch64-disk.img
  - ubuntu xenial: 
https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-arm64-uefi1.img

  The test steps are simple enough. A tap device is needed, qemu-kvm,
  qemu-efi need to be installed. The UEFI iamge is run as shown in the
  launch.sh script, the tap device is used in vhost=on mode.

  Also note that the QEMU_EFI.fd binary needs to be padded up to 64M:
  dd if=/dev/zero of=AAVMF_CODE.fd bs=1M count=64
  dd if=QEMU_EFI.fd of=AAVMF_CODE.fd conv=notrunc

  
  The result was always the same, the node crashing with soft-lockups when qemu 
was attempting to boot the kernel.

  I will attach all the relevant information shortly.

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

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

[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[spike speigel]

** Tags added: xenial

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1673564] Re: ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on

[Ubuntu Foundations Team Bug Bot]

The attachment "Experimental workaround" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
  vhost=on

Status in edk2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a followup of an earlier thread/bug that we have narrowed down
  to an incompatibility/issue with vhost support in qemu-efi. Without
  vhost=on qemu seems to be working fine.

  I have tested several edk2 firmwares:
  - xenial
  - zesty
  - Fedora: 
ftp://195.220.108.108/linux/fedora-secondary/development/rawhide/Everything/aarch64/os/Packages/e/edk2-aarch64-20170209git296153c5-2.fc26.noarch.rpm

  I have also tested with different guests:
  - cirros: 
https://download.cirros-cloud.net/daily/20161201/cirros-d161201-aarch64-disk.img
  - ubuntu xenial: 
https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-arm64-uefi1.img

  The test steps are simple enough. A tap device is needed, qemu-kvm,
  qemu-efi need to be installed. The UEFI iamge is run as shown in the
  launch.sh script, the tap device is used in vhost=on mode.

  Also note that the QEMU_EFI.fd binary needs to be padded up to 64M:
  dd if=/dev/zero of=AAVMF_CODE.fd bs=1M count=64
  dd if=QEMU_EFI.fd of=AAVMF_CODE.fd conv=notrunc

  
  The result was always the same, the node crashing with soft-lockups when qemu 
was attempting to boot the kernel.

  I will attach all the relevant information shortly.

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

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

[Kernel-packages] [Bug 1682041] fozzie (amd64) - tests ran: 19, failed: 0

[Brad Figg]

tests ran:  19, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/fozzie__4.4.0-74.95__2017-04-13_22-56-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1681566] Re: nvidia-375 DKMS module not recompiled on upgrade to 17.04

[Brian Murray]

I found some of those attachments I mentioned:

$ for log in $(find . -name VarLogDistupgradeApttermlog.txt); do grep -H 
"Building for.*4.8" $log; done
./bug-1646551/VarLogDistupgradeApttermlog.txt:Building for 4.4.0-47-generic and 
4.8.0-27-generic
./bug-1646551/VarLogDistupgradeApttermlog.txt:Building for 4.4.0-47-generic and 
4.8.0-27-generic
./bug-1646551/VarLogDistupgradeApttermlog.txt:Building for 4.4.0-47-generic and 
4.8.0-27-generic
./bug-1646551/VarLogDistupgradeApttermlog.txt:Building for 4.4.0-47-generic and 
4.8.0-27-generic
./bug-1646551/VarLogDistupgradeApttermlog.txt:Building for 4.4.0-47-generic and 
4.8.0-27-generic
./bug-1637466/VarLogDistupgradeApttermlog.txt:Building for 4.4.0-43-generic and 
4.8.0-22-generic
./bug-1670785/VarLogDistupgradeApttermlog.txt:Building for 4.4.0-38-generic and 
4.8.0-17-generic
./bug-1648952/VarLogDistupgradeApttermlog.txt:Building for 4.4.0-47-generic and 
4.8.0-27-generic

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

Title:
  nvidia-375 DKMS module not recompiled on upgrade to 17.04

Status in dkms package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Invalid
Status in dkms source package in Zesty:
  Fix Released
Status in nvidia-graphics-drivers-375 source package in Zesty:
  Invalid
Status in ubuntu-release-upgrader source package in Zesty:
  Invalid
Status in virtualbox source package in Zesty:
  Invalid

Bug description:
  When upgrading from 16.10 to 17.04 using `update-manager -d`, the
  `nvidia-375` DKMS modules are not compiled for the new kernel.

  The result is that the user must run `apt install --reinstall
  nvidia-375` and reboot.

  To reproduce this:

  - Clean install of 16.10 on a system with NVIDIA graphics
  - Install `nvidia-375`
  - Run `update-manager -d`, complete all steps, then reboot
  - You will be unable to login until running `apt install --reinstall 
nvidia-375`

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1682331/+attachment/4861621/+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/1682331

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

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

[frk-az]

apport information

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

Title:
  Cannot get lowest brightness with kernel 4.4.0-53-generic

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.

  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I
  used to run this command:

  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes

  I have always used intel_backlight instead of dell_backlight because
  it gives much more steps.

  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to
  the brightness levels I used to get with the same command. In fact,
  using a value of 0 with older kernels, the backlight is turned off.

  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That
  is how I realized that the problem was the kernel.

  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...

  Some system information:

  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena

  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v:
  A14 date: 05/13/2013

  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB

  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel

  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight

  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.

  Thanks for your time, Frk.

  P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  betops 6791 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.1
  HibernationDevice: RESUME=UUID=923be72b-35a8-4997-b31a-e6072b9d4a29
  InstallationDate: Installed on 2017-02-05 (66 days ago)
  InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213
  MachineType: Dell Inc. Inspiron 5520
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=ef4672c3-b0ed-47f3-a6b6-28e4e1e22d44 ro acpi_backlight=vendor 
intel_pstate=enable acpi_osi= acpi_irq_balance
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-53-generic N/A
   linux-backports-modules-4.4.0-53-generic  N/A
   linux-firmware1.157.8
  Tags:  serena serena
  Uname: Linux 4.4.0-53-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: False
  dmi.bios.date: 05/13/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 04G65K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/13/2013:svnDellInc.:pnInspiron5520:pvrA14:rvnDellInc.:rn04G65K:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.name: Inspiron 5520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1682331] Re: Cannot get lowest brightness with kernel 4.4.0-53-generic

[frk-az]

apport information

** Description changed:

- I have been using kernel 3.16/3.19 in my Dell Laptop for a long time
- with Linux Mint 17 and previous versions and the problem here had never
+ I have been using kernel 3.16 in my Dell Laptop for a long time with
+ Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.
  
  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I used
  to run this command:
  
- # ie: Set lowest possible backlight brightness 
+ # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes
  
  I have always used intel_backlight instead of dell_backlight because it
  gives much more steps.
  
  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to the
  brightness levels I used to get with the same command. In fact, using a
  value of 0 with older kernels, the backlight is turned off.
  
  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That is
  how I realized that the problem was the kernel.
  
  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...
  
  Some system information:
  
  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
-Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena
+    Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena
  
  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v: A14
  date: 05/13/2013
  
  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB
  
- Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller 
-Display Server: X.org 1.18.4 driver: intel
+ Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
+    Display Server: X.org 1.18.4 driver: intel
  
  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight
  
  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.
  
  Thanks for your time, Frk.
  
  P.S. I have also asked about this issue without luck here =>
  https://goo.gl/TVzH7z

** Tags added: apport-collected serena

** Description changed:

  I have been using kernel 3.16 in my Dell Laptop for a long time with
  Linux Mint 17 and previous versions and the problem here had never
  happened until LM18.
  
  Very often I set the lowest possible brightness, for example at night,
  or while I am flying for many hours. Using values from 0 to 4882 I used
  to run this command:
  
  # ie: Set lowest possible backlight brightness
  echo 0 > /sys/class/backlight/intel_backlight/brightnes
  
  I have always used intel_backlight instead of dell_backlight because it
  gives much more steps.
  
  Well now with kernel 4.4.0-53-generic it actually decreases the
  brightness but at night it is still very high even at 0 compared to the
  brightness levels I used to get with the same command. In fact, using a
  value of 0 with older kernels, the backlight is turned off.
  
  Just for testing, I have booted my laptop with Debian Live kernel
  3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to
  reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That is
  how I realized that the problem was the kernel.
  
  Does anyone know if with newer kernels > 3.19 this is a well-known and
  tolerated behavior? Maybe the kernel code for intel_backlight was
  modified and ended up with this problem...
  
  Some system information:
  
  System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 
18.1 Serena
  
  Machine:   System: Dell product: Inspiron 5520 v: A14 Bios: Dell v: A14
  date: 05/13/2013
  
  CPU:   Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB
  
  Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller
     Display Server: X.org 1.18.4 driver: intel
  
  $ ls /sys/class/backlight/
  dell_backlight  intel_backlight
  
  Also I always use the acpi_backlight=vendor kernel parameter and I can
  confirm that by changing its value, the problem persists.
  
  Thanks for your time, Frk.
  
- P.S. I have also asked about this issue without luck here =>
- https://goo.gl/TVzH7z
+ P.S. I have also asked about this issue without luck here => 
https://goo.gl/TVzH7z
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  betops 6791 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ 

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Julio Alves]

Didn't work in my AB350 Gaming 3 with Ubuntu 16.04, I get a lot of
"unexpected irq trap at vector 07" without acpi=off before system
freezes.

I've also tried other kernels, from 4.8 to 4.10, to no avail.

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1667416] Re: PowerNV: No rate limit for kernel error "KVM can't copy data from"

[Mikhail S Medvedev]

I have triggered the error while using kernel image from proposed
repository:

2017-04-13 21:55:41.868 | Selected version '4.8.0.48.60' 
(Ubuntu:16.10/yakkety-proposed [ppc64el]) for 'linux-image-generic'
$ uname -a
Linux mmedvede-test-ratelimit-pkvmci8401 4.8.0-48-generic #51-Ubuntu SMP Wed 
Apr 12 12:59:15 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

And confirmed that the printk is now ratelimited. From kernel log:

[ 1725.561053] kvmppc_mmu_book3s_64_xlate: 282675 callbacks suppressed
[ 1725.561057] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561068] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561078] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561088] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561099] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561109] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561119] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561130] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561140] KVM: Can't copy data from 0x3fff8b7bbc80!
[ 1725.561150] KVM: Can't copy data from 0x3fff8b7bbc80!


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

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

Title:
  PowerNV: No rate limit for kernel error "KVM can't copy data from"

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

Bug description:
  == Comment: #0 - MIKHAIL S. MEDVEDEV  - 2017-02-03 
14:40:58 ==
  ---Problem Description---
  I am experiencing a problem with KVM on Power with a symptom of "KVM can't 
copy data" message being spammed to kern.log at about 10 messages a second. 
Apart from original problem that triggers the error, the printk is a problem on 
its own. System might run out of space for logs, and would have high CPU load 
caused by journald.

  This bug is to address an absence of rate limiter on printk at
  
https://github.com/torvalds/linux/blob/f64e8084c94bb0449177364856d8117e2f14c4c0/arch/powerpc/kvm/book3s_64_mmu.c#L268

  Maybe wrapping the printk in printk_ratelimit() is all that is
  required?

  if(printk_ratelimit()){
 printk("KVM can't copy");
  }
   
  Contact Information = Mikhail Medvedev / mmedv...@us.ibm.com, Rafael Folco / 
rfo...@br.ibm.com 
   
  ---uname output---
  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 = KVM guest on P8 8247 21L  
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Deploy OpenStack with devstack
  2. Run simultaneously between 4 and 6 instances of a script that
  - boots a VM (openstack server create)
  - immediately creates the backup of the VM (openstack server backup 
create)

  This is not a very good way to reproduce it. I am still unable to
  reproduce the problem just by using libvirt and qemu.

  
  == Comment: #5 - VIPIN K. PARASHAR  - 2017-02-07 
09:42:31 ==

  From kernel logs
  ===

  [852719.001593] KVM can't copy data from 0x3fff86683c80!
  [852719.001614] KVM can't copy data from 0x3fff86683c80!
  [852719.001617] KVM can't copy data from 0x3fff66a83c80!
  [852719.001624] KVM can't copy data from 0x3fff86683c80!
  [852719.001634] KVM can't copy data from 0x3fff86683c80!
  [852719.001637] KVM can't copy data from 0x3fff66a83c80!
  [852719.001645] KVM can't copy data from 0x3fff86683c80!
  [852719.001655] KVM can't copy data from 0x3fff86683c80!
  [852719.001658] KVM can't copy data from 0x3fff66a83c80!
  [852719.001665] KVM can't copy data from 0x3fff86683c80!
  [852719.001668] KVM can't copy data from 0x3fff66a83c80!
  [852719.001678] KVM can't copy data from 0x3fff66a83c80!
  [852719.001686] KVM can't copy data from 0x3fff86683c80!

  
  "KVM can't copy data from" error is being logged at very high rate
  by kernel. rate limiting this error should fix this issue.

  
  == Comment: #20 - VIPIN K. PARASHAR  - 2017-02-23 
12:01:26 ==
  Fix for this is submitted to PowerPC mailing list 
  and is available at below location:

  https://patchwork.ozlabs.org/patch/728831/

  It reads:

  "KVM: PPC: Book3S: Ratelimit copy data failure error messages"

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

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

[Leonardo Varuzza]

I tested the kernel from Marc Singer in my Gigabyte X370 Gamming K7 with
Ryzen 1700 and everything is working (typing it right now from the
system).

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1651005] Re: Unidentified Trackpad Synaptics

[Dmitry Torokhov]

** Bug watch added: Linux Kernel Bug Tracker #190301
   http://bugzilla.kernel.org/190301

** Also affects: linux via
   http://bugzilla.kernel.org/190301
   Importance: Unknown
   Status: Unknown

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

Title:
  Unidentified Trackpad Synaptics

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

Bug description:
  I recently purchased a Sager NP8152-S / Clevo 650RP6 on which I am dual 
booting.
  See http://www.clevo.com/clevo_prodetail.asp?id=958=en

  The trackpad is not detected. xinput does not display a trackpad
  device nor is the device listed in cat /proc/bus/input/devices which
  is uploaded as a file entitled devices.

  The trackpad device is a Synaptics SMBus TouchPad.

  Please let me know if I incorrectly reported this bug as it is my
  first for Ubuntu. I followed the instructions listed on
  https://wiki.ubuntu.com/DebuggingTouchpadDetection in the section
  called "In case your Touchpad doesn't work at all (No response from
  the Touchpad)".

  Thank you!

  


  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-generic 4.8.0.30.39
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cmuell89   2587 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Dec 18 17:52:04 2016
  HibernationDevice: RESUME=UUID=a7e110fa-7d4d-4b96-8681-fb7acbb406a9
  InstallationDate: Installed on 2016-12-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc.
   Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65xRP
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed 
root=UUID=49d81fc1-d0a2-493f-9a49-c2a533f8d0a6 ro quiet splash i8042.nomux 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-30-generic N/A
   linux-backports-modules-4.8.0-30-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago)
  dmi.bios.date: 11/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08LS2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65xRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08LS2:bd11/11/2016:svnNotebook:pnP65xRP:pvrNotApplicable:rvnNotebook:rnP65xRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65xRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1682660/+attachment/4861579/+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/1682660

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

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

[hellslinger]

apport information

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Complex 11t
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cytrix Technology

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

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

[Kernel-packages] [Bug 1682660] Re: Portait mode rotation on 2-in-1 is upside down

[hellslinger]

apport information

** Tags added: apport-collected zesty

** Description changed:

- Rotation worked in 16.10 after installing mainline 4.10.8 kernel to
- enable  kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait
- mode, screen is upside down in either physical direction. Landscape is
- correct orientation for both physical directions.zz
+ Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
+ --- 
+ ApportVersion: 2.20.4-0ubuntu4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
+  /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.04
+ HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
+ InstallationDate: Installed on 2016-10-13 (182 days ago)
+ InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
+ MachineType: Cytrix Technology Complex 11t
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-19-generic N/A
+  linux-backports-modules-4.10.0-19-generic  N/A
+  linux-firmware 1.164
+ Tags:  zesty
+ Uname: Linux 4.10.0-19-generic x86_64
+ UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/10/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 5.011
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: Complex 11t
+ dmi.board.vendor: Cytrix Technology
+ dmi.board.version: To be filled by O.E.M.
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd10/10/2015:svnCytrixTechnology:pnComplex11t:pvrTobefilledbyO.E.M.:rvnCytrixTechnology:rnComplex11t:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
+ dmi.product.name: Complex 11t
+ dmi.product.version: To be filled by O.E.M.
+ dmi.sys.vendor: Cytrix Technology

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to enable  
kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait mode, screen 
is upside down in either physical direction. Landscape is correct orientation 
for both physical directions.zz
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hellslinger   2088 F pulseaudio
   /dev/snd/controlC1:  hellslinger   2088 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=481e3b77-59a2-4488-94ab-2cc05064cab5
  InstallationDate: Installed on 2016-10-13 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Cytrix Technology Complex 11t
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=1b233e45-df88-48f6-ad76-9b3665db0ac9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-19-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.011
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Complex 11t
  dmi.board.vendor: Cytrix Technology
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To 

[Kernel-packages] [Bug 1682665] Re: [Hyper-V] PCI passthrough fixes for 32 or more CPUs

[jack carter]

Facebook customer service 1-(850)-366-6203 Facebook Customer Service
1-850-366-6203 Number!!@,New York,USA Facebook customer service
1-850-366-6203 Facebook Customer Service Number!!@ Facebook customer
service 1-850-366-6203 Facebook Customer Service Number!!@ Facebook
customer service 1-850-366-6203 Facebook Customer Service Number!!@
Facebook customer service Facebook Customer Service Number Facebook
Number Facebook customer service Facebook customer service Facebook
customer service FACEBOOK 24 hour contact number, FACEBOOK customer
support contact number, FACEBOOK customer service contact number,
FACEBOOK official number, FACEBOOK official contact number, FACEBOOK 850
contact number, FACEBOOK toll free number, 850 number for FACEBOOK
support, FACEBOOK 24/7 support phone number FACEBOOK support phone
number,FACEBOOK support phone number,FACEBOOK help phone number,
FACEBOOK technical support number.FACEBOOK support number, Facebook
customer service, FACEBOOK tech support number, FACEBOOK customer
support number, FACEBOOK customer support phone number, FACEBOOK
customer service phone number, FACEBOOK customer service phone number,
FACEBOOK support phone number.Help@Call 1-850-366-6203/.FACEBOOK 24/7
support phone number,FACEBOOK telephone number for support? call
1850-366-6203@./FACEBOOK contact number, FACEBOOK contact phone number,
FACEBOOK contact telephone number telephone number for FACEBOOK online
support,FACEBOOK official support number,FACEBOOK official
number,FACEBOOK official phone number,phone number for FACEBOOK support
FACEBOOK 24/7 support phone number FACEBOOK support number,FACEBOOK
telephone number for support " = FACEBOOK Contact Number 1 850 366 6203
= FACEBOOK Customer Service phone number,FACEBOOK helpline phone number
here. Describe FACEBOOK help desk phone number,FACEBOOK helpline phone
number here. FACEBOOK Payroll support phone number, 1-850-366-6203
FACEBOOK tech support number Call, 1-850-366-6203 for all type help by
FACEBOOK tech support phone number, 1850-366-6203 Intuit FACEBOOK Tech
Support Phone Number, 1850-366-6203 FACEBOOK Help Desk Phone Number,
1850-366-6203 FACEBOOK tech support number, FACEBOOK technical support
phone number, 1850-366-6203 @ Facebook customer service, 1850-366-6203
FACEBOOK technical support number, 1850-366-6203 FACEBOOK support phone
number, 1850-366-6203 FACEBOOK technical support, FACEBOOK Customer
Service Phone Number, FACEBOOK Customer Service Number, FACEBOOK
Customer Support Phone Number, FACEBOOK Customer Support Number,
FACEBOOK Customer Service Helpline Number, FACEBOOK Customer Care
Number, FACEBOOK support team phone number, FACEBOOK help number-
FACEBOOK Helpline Number; FACEBOOK help phone number-FACEBOOK Helpline
Number, FACEBOOK Tech Support Toll free Number, FACEBOOK Support
Telephone Number, FACEBOOK Tech Support Telephone number, FACEBOOK Tech
Support contact number, FACEBOOK support contact number, FACEBOOK
technical support contact number. Call, FACEBOOK tech support phone
number, Intuit FACEBOOK Tech Support Phone Number, FACEBOOK Help Desk
Phone Number, FACEBOOK tech support number, FACEBOOK technical support
phone number, Facebook customer service, FACEBOOK technical support
number == FACEBOOK Contact Phone Number 1 850 366 6203 Toll free Number
== FACEBOOK support phone number. It is very popular toll free number
which payroll vide by FACEBOOK technical support, FACEBOOK Customer
Service Phone Number, FACEBOOK Customer Service Number, FACEBOOK
Customer Support Phone Number, FACEBOOK Customer Support Number,
FACEBOOK Customer Service Helpline Number, FACEBOOK Customer Care
Number, FACEBOOK support team phone number. Call, FACEBOOK tech support
phone number, Intuit FACEBOOK Tech Support Phone Number, FACEBOOK Help
Desk Phone Number, FACEBOOK tech support number, FACEBOOK technical
support phone number, Facebook customer service, FACEBOOK technical
support number, FACEBOOK support phone number, FACEBOOK technical
support, FACEBOOK Customer Service Phone Number, FACEBOOK Customer
Service Number, FACEBOOK Customer Support Phone Number, FACEBOOK
Customer Support Number, FACEBOOK Customer Service Helpline Number,
FACEBOOK Customer Care Number, FACEBOOK support team phone number,
FACEBOOK help number-FACEBOOK Helpline Number; FACEBOOK help phone
number, FACEBOOK Helpline Number, FACEBOOK Tech Support Toll free
Number, FACEBOOK Support Telephone Number, FACEBOOK Tech Support
Telephone number, FACEBOOK Tech Support contact number, FACEBOOK support
contact number, FACEBOOK technical support contact number, FACEBOOK
support phone number, FACEBOOK support phone number. FACEBOOK customer
support phone number FACEBOOK Support Helpline Number, FACEBOOK contact
number FACEBOOK tech support phone number FACEBOOK support team phone
number FACEBOOK contact number 1850-366-6203 FACEBOOK technical help
telephone number, FACEBOOK technical help contact number, FACEBOOK
technical support contact number, FACEBOOK contact number, FACEBOOK
contact 

[Kernel-packages] [Bug 1682665] Re: [Hyper-V] PCI passthrough fixes for 32 or more CPUs

[Joshua R. Poulson]

These should all apply to 4.4, 4.8, and 4.10

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

Title:
  [Hyper-V] PCI passthrough fixes for 32 or more CPUs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following set of patches are needed for SR-IOV on larger VM sizes
  on Hyper-V, especially with more than 32 CPUs. Some of these patches
  were already pulled in as SAUCE for SR-IOV in Azure previously.

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=22e2495b76dbe398540faf355a541b10faad33b9

  Merge branch 'pci/host-hv' into next
  * pci/host-hv:
PCI: hv: Allocate interrupt descriptors with GFP_ATOMIC
PCI: hv: Specify CPU_AFFINITY_ALL for MSI affinity when >= 32 CPUs
PCI: hv: Lock PCI bus on device eject
PCI: hv: Properly handle PCI bus remove

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

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

[Kernel-packages] [Bug 1682665] Re: [Hyper-V] PCI passthrough fixes for 32 or more CPUs

[jack carter]

Facebook customer service 1-(850)-366-6203 Facebook Customer Service
1-850-366-6203 Number!!@,New York,USA Facebook customer service
1-850-366-6203 Facebook Customer Service Number!!@ Facebook customer
service 1-850-366-6203 Facebook Customer Service Number!!@ Facebook
customer service 1-850-366-6203 Facebook Customer Service Number!!@
Facebook customer service Facebook Customer Service Number Facebook
Number Facebook customer service Facebook customer service Facebook
customer service FACEBOOK 24 hour contact number, FACEBOOK customer
support contact number, FACEBOOK customer service contact number,
FACEBOOK official number, FACEBOOK official contact number, FACEBOOK 850
contact number, FACEBOOK toll free number, 850 number for FACEBOOK
support, FACEBOOK 24/7 support phone number FACEBOOK support phone
number,FACEBOOK support phone number,FACEBOOK help phone number,
FACEBOOK technical support number.FACEBOOK support number, Facebook
customer service, FACEBOOK tech support number, FACEBOOK customer
support number, FACEBOOK customer support phone number, FACEBOOK
customer service phone number, FACEBOOK customer service phone number,
FACEBOOK support phone number.Help@Call 1-850-366-6203/.FACEBOOK 24/7
support phone number,FACEBOOK telephone number for support? call
1850-366-6203@./FACEBOOK contact number, FACEBOOK contact phone number,
FACEBOOK contact telephone number telephone number for FACEBOOK online
support,FACEBOOK official support number,FACEBOOK official
number,FACEBOOK official phone number,phone number for FACEBOOK support
FACEBOOK 24/7 support phone number FACEBOOK support number,FACEBOOK
telephone number for support " = FACEBOOK Contact Number 1 850 366 6203
= FACEBOOK Customer Service phone number,FACEBOOK helpline phone number
here. Describe FACEBOOK help desk phone number,FACEBOOK helpline phone
number here. FACEBOOK Payroll support phone number, 1-850-366-6203
FACEBOOK tech support number Call, 1-850-366-6203 for all type help by
FACEBOOK tech support phone number, 1850-366-6203 Intuit FACEBOOK Tech
Support Phone Number, 1850-366-6203 FACEBOOK Help Desk Phone Number,
1850-366-6203 FACEBOOK tech support number, FACEBOOK technical support
phone number, 1850-366-6203 @ Facebook customer service, 1850-366-6203
FACEBOOK technical support number, 1850-366-6203 FACEBOOK support phone
number, 1850-366-6203 FACEBOOK technical support, FACEBOOK Customer
Service Phone Number, FACEBOOK Customer Service Number, FACEBOOK
Customer Support Phone Number, FACEBOOK Customer Support Number,
FACEBOOK Customer Service Helpline Number, FACEBOOK Customer Care
Number, FACEBOOK support team phone number, FACEBOOK help number-
FACEBOOK Helpline Number; FACEBOOK help phone number-FACEBOOK Helpline
Number, FACEBOOK Tech Support Toll free Number, FACEBOOK Support
Telephone Number, FACEBOOK Tech Support Telephone number, FACEBOOK Tech
Support contact number, FACEBOOK support contact number, FACEBOOK
technical support contact number. Call, FACEBOOK tech support phone
number, Intuit FACEBOOK Tech Support Phone Number, FACEBOOK Help Desk
Phone Number, FACEBOOK tech support number, FACEBOOK technical support
phone number, Facebook customer service, FACEBOOK technical support
number == FACEBOOK Contact Phone Number 1 850 366 6203 Toll free Number
== FACEBOOK support phone number. It is very popular toll free number
which payroll vide by FACEBOOK technical support, FACEBOOK Customer
Service Phone Number, FACEBOOK Customer Service Number, FACEBOOK
Customer Support Phone Number, FACEBOOK Customer Support Number,
FACEBOOK Customer Service Helpline Number, FACEBOOK Customer Care
Number, FACEBOOK support team phone number. Call, FACEBOOK tech support
phone number, Intuit FACEBOOK Tech Support Phone Number, FACEBOOK Help
Desk Phone Number, FACEBOOK tech support number, FACEBOOK technical
support phone number, Facebook customer service, FACEBOOK technical
support number, FACEBOOK support phone number, FACEBOOK technical
support, FACEBOOK Customer Service Phone Number, FACEBOOK Customer
Service Number, FACEBOOK Customer Support Phone Number, FACEBOOK
Customer Support Number, FACEBOOK Customer Service Helpline Number,
FACEBOOK Customer Care Number, FACEBOOK support team phone number,
FACEBOOK help number-FACEBOOK Helpline Number; FACEBOOK help phone
number, FACEBOOK Helpline Number, FACEBOOK Tech Support Toll free
Number, FACEBOOK Support Telephone Number, FACEBOOK Tech Support
Telephone number, FACEBOOK Tech Support contact number, FACEBOOK support
contact number, FACEBOOK technical support contact number, FACEBOOK
support phone number, FACEBOOK support phone number. FACEBOOK customer
support phone number FACEBOOK Support Helpline Number, FACEBOOK contact
number FACEBOOK tech support phone number FACEBOOK support team phone
number FACEBOOK contact number 1850-366-6203 FACEBOOK technical help
telephone number, FACEBOOK technical help contact number, FACEBOOK
technical support contact number, FACEBOOK contact number, FACEBOOK
contact 

[Kernel-packages] [Bug 1682041] fozzie (i386) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/fozzie__4.4.0-74.95__2017-04-13_22-33-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1682184] Re: Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu 17.04-beta2

[Jeffery Painter]

So far I have test v4.10.2, v4.10.4 and v4.10.6 - each time running
Thunderbird, Chrome, RhythmBox, Eclipse and then starting up stress to
push a system load (20-25 minutes each).  I originally saw some funky
performance within the first few minutes with the kernel that started
this thread, but so far I haven't seen any issues.

I will test v4.10.8 next and see if it breaks.

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

Title:
  Kernel bug 4.10.0-19-generic causing lockup and crash on Ubuntu
  17.04-beta2

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

Bug description:
  
  Apologies in advance if this is not the right place to file the bug, but I 
have been running Ubuntu 17.04-beta2 for 2 days now and have had a kernel bug 
cause system lock up twice now requiring a hard reboot. Only apps open were 
Chrome and Thunderbird.

  root@merlin:/var/log# lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  root@merlin:/var/log# uname -a
  Linux merlin 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz

  System: Dell XPS 8900 (default setup) booting from
  ata1.00: ATA-9: Samsung SSD 850 EVO 250GB, EMT01B6Q, max UDMA/133


  Apr 12 12:23:48 merlin kernel: [ 8390.993645] [ cut here 
]
  Apr 12 12:23:48 merlin kernel: [ 8390.993655] kernel BUG at 
/build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
  Apr 12 12:23:48 merlin kernel: [ 8390.993661] invalid opcode:  [#1] SMP
  Apr 12 12:23:48 merlin kernel: [ 8390.993665] Modules linked in: rfcomm 
joydev input_leds pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) cmac 
vboxdrv(OE) bnep usblp hid_logitech_hidpp snd_hda_codec_hdmi hid_logitech_dj 
uas usb_storage btusb btrtl usbhid snd_usb_audio snd_usbmidi_lib uvcvideo 
videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media 
snd_hda_codec_realtek snd_hda_codec_generic dell_wmi sparse_keymap 
snd_hda_intel snd_hda_codec snd_hda_core dell_smbios snd_hwdep snd_pcm 
snd_seq_midi snd_seq_midi_event intel_rapl snd_rawmidi dcdbas 
x86_pkg_temp_thermal intel_powerclamp coretemp nvidia_uvm(POE) snd_seq 
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul snd_seq_device 
ghash_clmulni_intel pcbc aesni_intel snd_timer aes_x86_64 crypto_simd 
glue_helper cryptd intel_cstate intel_rapl_perf snd soundcore
  Apr 12 12:23:48 merlin kernel: [ 8390.993735]  serio_raw hci_uart btbcm btqca 
btintel bluetooth mei_me mei wmi shpchp intel_pch_thermal acpi_als kfifo_buf 
industrialio intel_lpss_acpi mac_hid intel_lpss acpi_pad parport_pc ppdev lp 
parport ip_tables x_tables autofs4 dm_mirror dm_region_hash dm_log 
nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) drm_kms_helper syscopyarea 
sysfillrect e1000e sysimgblt fb_sys_fops psmouse drm ahci ptp pps_core libahci 
video pinctrl_sunrisepoint i2c_hid pinctrl_intel hid fjes
  Apr 12 12:23:48 merlin kernel: [ 8390.993790] CPU: 2 PID: 4607 Comm: JS 
Helper Tainted: P   OE   4.10.0-19-generic #21-Ubuntu
  Apr 12 12:23:48 merlin kernel: [ 8390.993793] Hardware name: Dell Inc. XPS 
8900/0XJ8C4, BIOS 2.0.3 09/18/2015
  Apr 12 12:23:48 merlin kernel: [ 8390.993798] task: 9e46d69a2e00 
task.stack: bb5d4603c000
  Apr 12 12:23:48 merlin kernel: [ 8390.993809] RIP: 
0010:__migration_entry_wait+0x16a/0x180
  Apr 12 12:23:48 merlin kernel: [ 8390.993813] RSP: :bb5d4603fd68 
EFLAGS: 00010246
  Apr 12 12:23:48 merlin kernel: [ 8390.993818] RAX: 0017c0048078 RBX: 
e73757462bf0 RCX: e73757462bf0
  Apr 12 12:23:48 merlin kernel: [ 8390.993822] RDX: 0001 RSI: 
9e46d18af800 RDI: e73756614000
  Apr 12 12:23:48 merlin kernel: [ 8390.993825] RBP: bb5d4603fd80 R08: 
9e47458645c0 R09: 9e47458645c0
  Apr 12 12:23:48 merlin kernel: [ 8390.993829] R10: 7f59927000c8 R11: 
0206 R12: e73756614000
  Apr 12 12:23:48 merlin kernel: [ 8390.993832] R13: 3e598500 R14: 
bb5d4603fe30 R15: 9e46d1a3be10
  Apr 12 12:23:48 merlin kernel: [ 8390.993837] FS:  7f59774fa700() 
GS:9e476548() knlGS:
  Apr 12 12:23:48 merlin kernel: [ 8390.993841] CS:  0010 DS:  ES:  
CR0: 80050033
  Apr 12 12:23:48 merlin kernel: [ 8390.993844] CR2: 7f593df00018 CR3: 
0005d6951000 CR4: 003406e0
  Apr 12 12:23:48 merlin kernel: [ 8390.993848] DR0:  DR1: 
 DR2: 
  Apr 12 12:23:48 merlin kernel: [ 8390.993852] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Apr 12 12:23:48 merlin kernel: [ 8390.993854] Call Trace:
  Apr 12 12:23:48 merlin kernel: [ 8390.993863]  migration_entry_wait+0x74/0x80
  Apr 12 12:23:48 merlin kernel: [ 8390.993871]  do_swap_page+0x5b3/0x770
  

[Kernel-packages] [Bug 1682665] [NEW] [Hyper-V] PCI passthrough fixes for 32 or more CPUs

[Joshua R. Poulson]

Public bug reported:

The following set of patches are needed for SR-IOV on larger VM sizes on
Hyper-V, especially with more than 32 CPUs. Some of these patches were
already pulled in as SAUCE for SR-IOV in Azure previously.

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=22e2495b76dbe398540faf355a541b10faad33b9

Merge branch 'pci/host-hv' into next
* pci/host-hv:
  PCI: hv: Allocate interrupt descriptors with GFP_ATOMIC
  PCI: hv: Specify CPU_AFFINITY_ALL for MSI affinity when >= 32 CPUs
  PCI: hv: Lock PCI bus on device eject
  PCI: hv: Properly handle PCI bus remove

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

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

Title:
  [Hyper-V] PCI passthrough fixes for 32 or more CPUs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following set of patches are needed for SR-IOV on larger VM sizes
  on Hyper-V, especially with more than 32 CPUs. Some of these patches
  were already pulled in as SAUCE for SR-IOV in Azure previously.

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=22e2495b76dbe398540faf355a541b10faad33b9

  Merge branch 'pci/host-hv' into next
  * pci/host-hv:
PCI: hv: Allocate interrupt descriptors with GFP_ATOMIC
PCI: hv: Specify CPU_AFFINITY_ALL for MSI affinity when >= 32 CPUs
PCI: hv: Lock PCI bus on device eject
PCI: hv: Properly handle PCI bus remove

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

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

[Kernel-packages] [Bug 1682665] Re: [Hyper-V] PCI passthrough fixes for 32 or more CPUs

[jack carter]

Facebook customer service 1-(850)-366-6203 Facebook Customer Service
1-850-366-6203 Number!!@,New York,USA Facebook customer service
1-850-366-6203 Facebook Customer Service Number!!@ Facebook customer
service 1-850-366-6203 Facebook Customer Service Number!!@ Facebook
customer service 1-850-366-6203 Facebook Customer Service Number!!@
Facebook customer service Facebook Customer Service Number Facebook
Number Facebook customer service Facebook customer service Facebook
customer service FACEBOOK 24 hour contact number, FACEBOOK customer
support contact number, FACEBOOK customer service contact number,
FACEBOOK official number, FACEBOOK official contact number, FACEBOOK 850
contact number, FACEBOOK toll free number, 850 number for FACEBOOK
support, FACEBOOK 24/7 support phone number FACEBOOK support phone
number,FACEBOOK support phone number,FACEBOOK help phone number,
FACEBOOK technical support number.FACEBOOK support number, Facebook
customer service, FACEBOOK tech support number, FACEBOOK customer
support number, FACEBOOK customer support phone number, FACEBOOK
customer service phone number, FACEBOOK customer service phone number,
FACEBOOK support phone number.Help@Call 1-850-366-6203/.FACEBOOK 24/7
support phone number,FACEBOOK telephone number for support? call
1850-366-6203@./FACEBOOK contact number, FACEBOOK contact phone number,
FACEBOOK contact telephone number telephone number for FACEBOOK online
support,FACEBOOK official support number,FACEBOOK official
number,FACEBOOK official phone number,phone number for FACEBOOK support
FACEBOOK 24/7 support phone number FACEBOOK support number,FACEBOOK
telephone number for support " = FACEBOOK Contact Number 1 850 366 6203
= FACEBOOK Customer Service phone number,FACEBOOK helpline phone number
here. Describe FACEBOOK help desk phone number,FACEBOOK helpline phone
number here. FACEBOOK Payroll support phone number, 1-850-366-6203
FACEBOOK tech support number Call, 1-850-366-6203 for all type help by
FACEBOOK tech support phone number, 1850-366-6203 Intuit FACEBOOK Tech
Support Phone Number, 1850-366-6203 FACEBOOK Help Desk Phone Number,
1850-366-6203 FACEBOOK tech support number, FACEBOOK technical support
phone number, 1850-366-6203 @ Facebook customer service, 1850-366-6203
FACEBOOK technical support number, 1850-366-6203 FACEBOOK support phone
number, 1850-366-6203 FACEBOOK technical support, FACEBOOK Customer
Service Phone Number, FACEBOOK Customer Service Number, FACEBOOK
Customer Support Phone Number, FACEBOOK Customer Support Number,
FACEBOOK Customer Service Helpline Number, FACEBOOK Customer Care
Number, FACEBOOK support team phone number, FACEBOOK help number-
FACEBOOK Helpline Number; FACEBOOK help phone number-FACEBOOK Helpline
Number, FACEBOOK Tech Support Toll free Number, FACEBOOK Support
Telephone Number, FACEBOOK Tech Support Telephone number, FACEBOOK Tech
Support contact number, FACEBOOK support contact number, FACEBOOK
technical support contact number. Call, FACEBOOK tech support phone
number, Intuit FACEBOOK Tech Support Phone Number, FACEBOOK Help Desk
Phone Number, FACEBOOK tech support number, FACEBOOK technical support
phone number, Facebook customer service, FACEBOOK technical support
number == FACEBOOK Contact Phone Number 1 850 366 6203 Toll free Number
== FACEBOOK support phone number. It is very popular toll free number
which payroll vide by FACEBOOK technical support, FACEBOOK Customer
Service Phone Number, FACEBOOK Customer Service Number, FACEBOOK
Customer Support Phone Number, FACEBOOK Customer Support Number,
FACEBOOK Customer Service Helpline Number, FACEBOOK Customer Care
Number, FACEBOOK support team phone number. Call, FACEBOOK tech support
phone number, Intuit FACEBOOK Tech Support Phone Number, FACEBOOK Help
Desk Phone Number, FACEBOOK tech support number, FACEBOOK technical
support phone number, Facebook customer service, FACEBOOK technical
support number, FACEBOOK support phone number, FACEBOOK technical
support, FACEBOOK Customer Service Phone Number, FACEBOOK Customer
Service Number, FACEBOOK Customer Support Phone Number, FACEBOOK
Customer Support Number, FACEBOOK Customer Service Helpline Number,
FACEBOOK Customer Care Number, FACEBOOK support team phone number,
FACEBOOK help number-FACEBOOK Helpline Number; FACEBOOK help phone
number, FACEBOOK Helpline Number, FACEBOOK Tech Support Toll free
Number, FACEBOOK Support Telephone Number, FACEBOOK Tech Support
Telephone number, FACEBOOK Tech Support contact number, FACEBOOK support
contact number, FACEBOOK technical support contact number, FACEBOOK
support phone number, FACEBOOK support phone number. FACEBOOK customer
support phone number FACEBOOK Support Helpline Number, FACEBOOK contact
number FACEBOOK tech support phone number FACEBOOK support team phone
number FACEBOOK contact number 1850-366-6203 FACEBOOK technical help
telephone number, FACEBOOK technical help contact number, FACEBOOK
technical support contact number, FACEBOOK contact number, FACEBOOK
contact 

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1682660

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to
  enable  kxcjk_1013 i2c driver. Now in 17.04, when rotating to a
  portrait mode, screen is upside down in either physical direction.
  Landscape is correct orientation for both physical directions.zz

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

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

[Kernel-packages] [Bug 1682660] Re: Portait mode rotation on 2-in-1 is upside down

[Jeremy Bicha]

** Project changed: ubuntu-gnome => linux (Ubuntu)

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

Title:
  Portait mode rotation on 2-in-1 is upside down

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Rotation worked in 16.10 after installing mainline 4.10.8 kernel to
  enable  kxcjk_1013 i2c driver. Now in 17.04, when rotating to a
  portrait mode, screen is upside down in either physical direction.
  Landscape is correct orientation for both physical directions.zz

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

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

[Kernel-packages] [Bug 331675] Re: try it

[Uli Schroeder]

Greetings,


Have  you ever tried that stuff before?  It's something gorgeous, just  take a 
look http://comprehensive.rebelselector.com/c4c5

ulischroeder

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

Title:
  package linux-image-2.6.28-8-generic 2.6.28-8.24 failed to
  install/upgrade: subprocess post-installation script returned error
  exit status 2 (ImportError: No module named NvidiaDetector)

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-common package in Ubuntu:
  Confirmed

Bug description:
  The update did not install properly which cause this crash.

  ProblemType: Package
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ErrorMessage: subprocess post-installation script returned error exit status 2
  Lsusb:
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: linux-image-2.6.28-8-generic 2.6.28-8.24
  ProcCmdLine: User Name=UUID=912d04b0-77a4-4248-b6fc-3bbeb95e317d ro quiet 
splash
  ProcVersionSignature: Ubuntu 2.6.28-8.24-generic
  SourcePackage: linux
  Title: package linux-image-2.6.28-8-generic 2.6.28-8.24 failed to 
install/upgrade: subprocess post-installation script returned error exit status 
2

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

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

[Kernel-packages] [Bug 1682660] [NEW] Portait mode rotation on 2-in-1 is upside down

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Rotation worked in 16.10 after installing mainline 4.10.8 kernel to
enable  kxcjk_1013 i2c driver. Now in 17.04, when rotating to a portrait
mode, screen is upside down in either physical direction. Landscape is
correct orientation for both physical directions.zz

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

-- 
Portait mode rotation on 2-in-1 is upside down
https://bugs.launchpad.net/bugs/1682660
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 1682041] fozzie (amd64) - tests ran: 1, failed: 0

[Brad Figg]

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-74.95-generic/fozzie__4.4.0-74.95__2017-04-13_22-10-00/results-index.html

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

Title:
  linux: 4.4.0-74.95 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682042
  derivatives: 1682043,1682045,1682047,1682048
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682041/+subscriptions

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Philipp Ludwig]

I fixed the problem by installing xserver-xorg-input-all.

Since this pulls in xserver-xorg-input-evdev, I suspect that this was
the problem, as this package was not installed. It must have been
somehow uninstalled during the upgrade.

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1594939] Re: Sound over bluetooth is stuttering

[Tomislav]

#1594591 might be related.

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

Title:
  Sound over bluetooth is stuttering

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I am using a Meizu Pro 5 device with Ubuntu 15.04 (r110).

  Problem description:
  When paired with a bluetooth receiver (tested with 'Bose Soundlink Colour' 
and 'Philips AEA2700') the sound is very laggy and stuttering a lot.

  Apart from the stuttering where there is no sound at all for short
  periods of time you can also hear, that the sound is stretched and
  squeezed sometimes (maybe to compensate the lags).

  The stuttering is a lot worse, when the system-settings-app is open
  and searching for bt-devices.

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

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

[Kernel-packages] [Bug 1594591] Re: Bluetooth audio isn't working properly!

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Bluetooth audio isn't working properly!

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset is connected fine but the sound keeps stuttering,
  then the sound completely disappears! I noticed that it only happens
  when wifi is enabled!

  I'm using Ubuntu 16.04 LTS | Broadcom driver

  ps: it works quite well with windows 10.

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

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

[Kernel-packages] [Bug 1594591] Re: Bluetooth audio isn't working properly!

[Tomislav]

I encounter sound over bluetooth stuttering as well. Ubuntu 14.04,
bluetooth in A2DP mode. I get the vague feeling that the stuttering gets
worse when the system is active, but sometimes it's the CPU, sometimes
the WiFi...sometimes no obvious reason.

I'm 3m away from a receiver in line of sight, FWIW.

Also, issue #1594939 sounds like it might be related.

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

Title:
  Bluetooth audio isn't working properly!

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  My bluetooth headset is connected fine but the sound keeps stuttering,
  then the sound completely disappears! I noticed that it only happens
  when wifi is enabled!

  I'm using Ubuntu 16.04 LTS | Broadcom driver

  ps: it works quite well with windows 10.

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1682649

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

Title:
  cheese error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  camera was working, but changed effects and now it comes up with error :
  There was an error playing video from the webcam

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cheese 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr 14 00:17:12 2017
  InstallationDate: Installed on 2017-04-13 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: VMware, Inc. VMware Virtual Platform
  RelatedPackageVersions:
   cheese3.24.0-0ubuntu1
   cheese-common 3.24.0-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 008: ID 046d:092f Logitech, Inc. QuickCam Express Plus
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

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

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Philipp Ludwig]

I can confirm this bug.

Using 16.04 everything worked fine; after upgrading to 16.10, mouse and
keyboard stopped working.

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse

[Philipp Ludwig]

I should probably mention that the keyboard works fine in recovery mode,
so I suspect it has something to do with X.

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

Title:
  after starting ubuntu 16.10 -- no keyboard, no mouse

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  After starting Ubuntu 16.10 keyboard and mouse are dead. Since it
  works with an older kernel but not with the latest one, I'd assume the
  newer kernel does not initialize the devices the right way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  4 15:27:52 2016
  InstallationDate: Installed on 2012-12-12 (1391 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic 
root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1682632] Re: systemd blocked and times out

[Walker Sampson]

Cannot run 'apport-collect 1682632' as file system is read only and the
program is not installed.

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

Title:
  systemd blocked and times out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  At boot I consistently get the error message:

  "INFO: task systemd-udevd:179 blocked for more than 120 seconds."

  This is under 16.04 on a Dell Optiplex 9020. See the attached image
  for a full call trace when booting in Recovery Mode.

  I want the system to boot to the GUI, but it instead stalls at
  repeating this error message. Eventually it dumps onto the command
  line as a read-only system.

  cat /proc/version_signature is Ubuntu 4.8.0-42.45~16.04.1 generic
  4.8.17

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

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

[Kernel-packages] [Bug 1682649] [NEW] cheese error

[dzobro]

Public bug reported:

camera was working, but changed effects and now it comes up with error :
There was an error playing video from the webcam

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: cheese 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Fri Apr 14 00:17:12 2017
InstallationDate: Installed on 2017-04-13 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: VMware, Inc. VMware Virtual Platform
RelatedPackageVersions:
 cheese3.24.0-0ubuntu1
 cheese-common 3.24.0-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 008: ID 046d:092f Logitech, Inc. QuickCam Express Plus
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

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


** Tags: amd64 apport-bug gstreamer-error 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/1682649

Title:
  cheese error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  camera was working, but changed effects and now it comes up with error :
  There was an error playing video from the webcam

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: cheese 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Apr 14 00:17:12 2017
  InstallationDate: Installed on 2017-04-13 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: VMware, Inc. VMware Virtual Platform
  RelatedPackageVersions:
   cheese3.24.0-0ubuntu1
   cheese-common 3.24.0-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 008: ID 046d:092f Logitech, Inc. QuickCam Express Plus
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

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

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

[Kernel-packages] [Bug 1667527] Re: [Hyper-V] pci-hyperv: Use device serial number as PCI domain

[Simon Xiao]

** Changed in: linux (Ubuntu Yakkety)
   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/1667527

Title:
  [Hyper-V] pci-hyperv: Use device serial number as PCI domain

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 Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This allows PCI domain numbers starts with 1, and also unique
  on the same VM. So names, such as VF NIC names, that include
  domain number as part of the name, can be shorter than that
  based on part of bus UUID previously. The new names will also
  stay same for VMs created with copied VHD and same number of
  devices.

  This is needed for SR-IOV in Azure.

  This is Bjorn's tree for 4.11 here:
  https://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/commit/?h=pci
  /host-hv=4a9b0933bdfcd85da840284bf5a0eb17b654b9c2

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

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

[Kernel-packages] [Bug 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself

[Joseph Salisbury]

Thanks for the feedback, Josh.

SRU requests submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-April/083633.html
https://lists.ubuntu.com/archives/kernel-team/2017-April/083635.html

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

Title:
  [Hyper-V] hv: util: move waiting for release to hv_utils_transport
  itself

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

Bug description:
  We are observing call traces with the -73 and -74 proposed kernels
  that look like this:

  [  240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
  [  240.412299]   Not tainted 4.4.0-73-generic #94-Ubuntu
  [  240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  240.420217] kworker/14:1D 8804e6f23b68 0   179  2 
0x
  [  240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
  [  240.420236]  8804e6f23b68 000181f9 8804ed944600 
8804e6fe3800
  [  240.420241]  8804e6f24000 c0187a48 c0187a40 
8804e6fe3800
  [  240.420243]  8804ea196800 8804e6f23b80 81837845 
7fff
  [  240.420245] Call Trace:
  [  240.420254]  [] schedule+0x35/0x80
  [  240.420256]  [] schedule_timeout+0x1b5/0x270
  [  240.420260]  [] ? kfree+0x13a/0x150
  [  240.420264]  [] ? kfree_const+0x22/0x30
  [  240.420268]  [] ? kobject_release+0x94/0x190
  [  240.420270]  [] ? kobject_put+0x27/0x50
  [  240.420272]  [] wait_for_completion+0xb3/0x140
  [  240.420276]  [] ? wake_up_q+0x70/0x70
  [  240.420284]  [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
  [  240.420288]  [] util_remove+0x21/0x40 [hv_utils]
  [  240.420294]  [] vmbus_remove+0x27/0x30 [hv_vmbus]
  [  240.420301]  [] __device_release_driver+0xa1/0x150
  [  240.420303]  [] device_release_driver+0x23/0x30
  [  240.420306]  [] bus_remove_device+0x101/0x170
  [  240.420308]  [] device_del+0x139/0x270
  [  240.420310]  [] device_unregister+0x1e/0x60
  [  240.420313]  [] vmbus_device_unregister+0x1f/0x50 
[hv_vmbus]
  [  240.420316]  [] vmbus_onoffer_rescind+0x91/0xb0 
[hv_vmbus]
  [  240.420324]  [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
  [  240.420327]  [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
  [  240.420331]  [] process_one_work+0x165/0x480
  [  240.420335]  [] worker_thread+0x4b/0x4c0
  [  240.420338]  [] ? process_one_work+0x480/0x480
  [  240.420341]  [] ? process_one_work+0x480/0x480
  [  240.420345]  [] kthread+0xd8/0xf0
  [  240.420347]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  240.420350]  [] ret_from_fork+0x3f/0x70
  [  240.420352]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  317.360035] serial8250: too much work for irq3

  The following commit should fix this issue:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398

  Waiting for release_event in all three drivers introduced issues on release
  as on_reset() hook is not always called. E.g. if the device was never
  opened we will never get the completion.

  Move the waiting code to hvutil_transport_destroy() and make sure it is
  only called when the device is open. hvt->lock serialization should
  guarantee the absence of races.

  Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
  Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing 
issue")
  Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing 
issue")

  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Signed-off-by: Vitaly Kuznetsov 
  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: Greg Kroah-Hartman 

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

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

[Kernel-packages] [Bug 1670518] Re: [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

[Simon Xiao]

The issue has been fixed with those patches.

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

Title:
  [Hyper-V] Missing PCI patches breaking SR-IOV hot remove

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 Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  Looks like the rebase work missed some prerequisite patches in
  drivers/pci/host/pci-hyperv.c

  (Needed for SR-IOV in Azure on lts-xenial, HWE, and custom)

  commit 0de8ce3ee8e38cc66683438f715c79a2cc69539e
  Author: Long Li 
  Date:   Tue Nov 8 14:04:38 2016 -0800

  PCI: hv: Allocate physically contiguous hypercall params buffer

  hv_do_hypercall() assumes that we pass a segment from a physically
  contiguous buffer.  A buffer allocated on the stack may not work if
  CONFIG_VMAP_STACK=y is set.

  Use kmalloc() to allocate this buffer.

  
  commit 542ccf4551fa019a8ae9dfb7c8cd7e73a3d7e614
  Author: Tobias Klauser 
  Date:   Mon Oct 31 12:04:09 2016 +0100

  PCI: hv: Make unnecessarily global IRQ masking functions static

  Make hv_irq_mask() and hv_irq_unmask() static as they are only used in
  pci-hyperv.c

  This fixes a sparse warning.

  commit e74d2ebdda33b3bdd1826b5b92e9aa45bdf92bb3
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:19:52 2016 +

  PCI: hv: Delete the device earlier from hbus->children for hot-
  remove

  After we send a PCI_EJECTION_COMPLETE message to the host, the host will
  immediately send us a PCI_BUS_RELATIONS message with
  relations->device_count == 0, so pci_devices_present_work(), running on
  another thread, can find the being-ejected device, mark the
  hpdev->reported_missing to true, and run list_move_tail()/list_del() for
  the device -- this races hv_eject_device_work() -> list_del().

  Move the list_del() in hv_eject_device_work() to an earlier place, i.e.,
  before we send PCI_EJECTION_COMPLETE, so later the
  pci_devices_present_work() can't see the device.

  
  commit 17978524a636d007e6b929304ae3eb5ea0371019
  Author: Dexuan Cui 
  Date:   Thu Nov 10 07:18:47 2016 +

  PCI: hv: Fix hv_pci_remove() for hot-remove

  1. We don't really need such a big on-stack buffer when sending the
  teardown_packet: vmbus_sendpacket() here only uses sizeof(struct
  pci_message).

  2. In the hot-remove case (PCI_EJECT), after we send PCI_EJECTION_COMPLETE
  to the host, the host will send a RESCIND_CHANNEL message to us and the
  host won't access the per-channel ringbuffer any longer, so we needn't 
send
  PCI_RESOURCES_RELEASED/PCI_BUS_D0EXIT to the host, and we shouldn't expect
  the host's completion message of PCI_BUS_D0EXIT, which will never come.

  3. We should send PCI_BUS_D0EXIT after
  hv_send_resources_released().

  Signed-off-by: Dexuan Cui 
  Signed-off-by: Bjorn Helgaas 
  Reviewed-by: Jake Oshins 
  Acked-by: K. Y. Srinivasan 
  CC: Haiyang Zhang 
  CC: Vitaly Kuznetsov 

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

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

[Kernel-packages] [Bug 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself

[Joshua R. Poulson]

Those commits are in the payload for
https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1670544
which is in proposed right now.

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

Title:
  [Hyper-V] hv: util: move waiting for release to hv_utils_transport
  itself

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

Bug description:
  We are observing call traces with the -73 and -74 proposed kernels
  that look like this:

  [  240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
  [  240.412299]   Not tainted 4.4.0-73-generic #94-Ubuntu
  [  240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  240.420217] kworker/14:1D 8804e6f23b68 0   179  2 
0x
  [  240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
  [  240.420236]  8804e6f23b68 000181f9 8804ed944600 
8804e6fe3800
  [  240.420241]  8804e6f24000 c0187a48 c0187a40 
8804e6fe3800
  [  240.420243]  8804ea196800 8804e6f23b80 81837845 
7fff
  [  240.420245] Call Trace:
  [  240.420254]  [] schedule+0x35/0x80
  [  240.420256]  [] schedule_timeout+0x1b5/0x270
  [  240.420260]  [] ? kfree+0x13a/0x150
  [  240.420264]  [] ? kfree_const+0x22/0x30
  [  240.420268]  [] ? kobject_release+0x94/0x190
  [  240.420270]  [] ? kobject_put+0x27/0x50
  [  240.420272]  [] wait_for_completion+0xb3/0x140
  [  240.420276]  [] ? wake_up_q+0x70/0x70
  [  240.420284]  [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
  [  240.420288]  [] util_remove+0x21/0x40 [hv_utils]
  [  240.420294]  [] vmbus_remove+0x27/0x30 [hv_vmbus]
  [  240.420301]  [] __device_release_driver+0xa1/0x150
  [  240.420303]  [] device_release_driver+0x23/0x30
  [  240.420306]  [] bus_remove_device+0x101/0x170
  [  240.420308]  [] device_del+0x139/0x270
  [  240.420310]  [] device_unregister+0x1e/0x60
  [  240.420313]  [] vmbus_device_unregister+0x1f/0x50 
[hv_vmbus]
  [  240.420316]  [] vmbus_onoffer_rescind+0x91/0xb0 
[hv_vmbus]
  [  240.420324]  [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
  [  240.420327]  [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
  [  240.420331]  [] process_one_work+0x165/0x480
  [  240.420335]  [] worker_thread+0x4b/0x4c0
  [  240.420338]  [] ? process_one_work+0x480/0x480
  [  240.420341]  [] ? process_one_work+0x480/0x480
  [  240.420345]  [] kthread+0xd8/0xf0
  [  240.420347]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  240.420350]  [] ret_from_fork+0x3f/0x70
  [  240.420352]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  317.360035] serial8250: too much work for irq3

  The following commit should fix this issue:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398

  Waiting for release_event in all three drivers introduced issues on release
  as on_reset() hook is not always called. E.g. if the device was never
  opened we will never get the completion.

  Move the waiting code to hvutil_transport_destroy() and make sure it is
  only called when the device is open. hvt->lock serialization should
  guarantee the absence of races.

  Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
  Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing 
issue")
  Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing 
issue")

  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Signed-off-by: Vitaly Kuznetsov 
  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: Greg Kroah-Hartman 

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

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

[Kernel-packages] [Bug 1682034] rumford (amd64) - tests ran: 64, failed: 0

[Brad Figg]

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-48.51-generic/rumford__4.8.0-48.51__2017-04-13_20-36-00/results-index.html

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

Title:
  linux: 4.8.0-48.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1682037
  derivatives: 1682038
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1682034/+subscriptions

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

[Kernel-packages] [Bug 1673564] Re: ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on

[David Daney]

We are testing this patch, it is not a definitive solution at this
point, but we would like to get wider testing on it to see if it helps
for this bug.

** Patch added: "Experimental workaround"
   
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1673564/+attachment/4861520/+files/kvm-hang.patch

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

Title:
  ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
  vhost=on

Status in edk2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a followup of an earlier thread/bug that we have narrowed down
  to an incompatibility/issue with vhost support in qemu-efi. Without
  vhost=on qemu seems to be working fine.

  I have tested several edk2 firmwares:
  - xenial
  - zesty
  - Fedora: 
ftp://195.220.108.108/linux/fedora-secondary/development/rawhide/Everything/aarch64/os/Packages/e/edk2-aarch64-20170209git296153c5-2.fc26.noarch.rpm

  I have also tested with different guests:
  - cirros: 
https://download.cirros-cloud.net/daily/20161201/cirros-d161201-aarch64-disk.img
  - ubuntu xenial: 
https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-arm64-uefi1.img

  The test steps are simple enough. A tap device is needed, qemu-kvm,
  qemu-efi need to be installed. The UEFI iamge is run as shown in the
  launch.sh script, the tap device is used in vhost=on mode.

  Also note that the QEMU_EFI.fd binary needs to be padded up to 64M:
  dd if=/dev/zero of=AAVMF_CODE.fd bs=1M count=64
  dd if=QEMU_EFI.fd of=AAVMF_CODE.fd conv=notrunc

  
  The result was always the same, the node crashing with soft-lockups when qemu 
was attempting to boot the kernel.

  I will attach all the relevant information shortly.

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

-- 
Mailing list: https://launchpad.net/~kernel-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] [NEW] IPR driver causes multipath to fail paths/stuck IO on Medium Errors

[bugproxy]

Public bug reported:

---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
> http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=785a470496d8e0a32e3d39f376984eb2c98ca5b3

Please apply to 17.04 and 16.04.

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.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-153445 severity-critical 
targetmilestone-inin16043

** Tags added: architecture-ppc64le bugnameltc-153445 severity-critical
targetmilestone-inin16043

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  ---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
  > 
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=785a470496d8e0a32e3d39f376984eb2c98ca5b3

  Please apply to 17.04 and 16.04.

  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 1682644] [NEW] IPR driver causes multipath to fail paths/stuck IO on Medium Errors

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---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
> http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=785a470496d8e0a32e3d39f376984eb2c98ca5b3

Please apply to 17.04 and 16.04.

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.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-153445 severity-critical 
targetmilestone-inin16043
-- 
IPR driver causes multipath to fail paths/stuck IO on Medium Errors
https://bugs.launchpad.net/bugs/1682644
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 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself

[Joseph Salisbury]

The three commits that introduced this bug have not landed in
Yakkety(4.8).  That's because 4.8 is EOL upstream and no longer gets
upstream stable updates.

Will yakkety still needed commit e9c18ae6eb2b?  The requested commit applied 
and built fine. 
 
Yakkety will not get the following three updates unless they come in from 
another Ubuntu specific bug, which I don't think exists:

  - Drivers: hv: util: kvp: Fix a rescind processing issue
  - Drivers: hv: util: Fcopy: Fix a rescind processing issue
  - Drivers: hv: util: Backup: Fix a rescind processing issue

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

Title:
  [Hyper-V] hv: util: move waiting for release to hv_utils_transport
  itself

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

Bug description:
  We are observing call traces with the -73 and -74 proposed kernels
  that look like this:

  [  240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
  [  240.412299]   Not tainted 4.4.0-73-generic #94-Ubuntu
  [  240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  240.420217] kworker/14:1D 8804e6f23b68 0   179  2 
0x
  [  240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
  [  240.420236]  8804e6f23b68 000181f9 8804ed944600 
8804e6fe3800
  [  240.420241]  8804e6f24000 c0187a48 c0187a40 
8804e6fe3800
  [  240.420243]  8804ea196800 8804e6f23b80 81837845 
7fff
  [  240.420245] Call Trace:
  [  240.420254]  [] schedule+0x35/0x80
  [  240.420256]  [] schedule_timeout+0x1b5/0x270
  [  240.420260]  [] ? kfree+0x13a/0x150
  [  240.420264]  [] ? kfree_const+0x22/0x30
  [  240.420268]  [] ? kobject_release+0x94/0x190
  [  240.420270]  [] ? kobject_put+0x27/0x50
  [  240.420272]  [] wait_for_completion+0xb3/0x140
  [  240.420276]  [] ? wake_up_q+0x70/0x70
  [  240.420284]  [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
  [  240.420288]  [] util_remove+0x21/0x40 [hv_utils]
  [  240.420294]  [] vmbus_remove+0x27/0x30 [hv_vmbus]
  [  240.420301]  [] __device_release_driver+0xa1/0x150
  [  240.420303]  [] device_release_driver+0x23/0x30
  [  240.420306]  [] bus_remove_device+0x101/0x170
  [  240.420308]  [] device_del+0x139/0x270
  [  240.420310]  [] device_unregister+0x1e/0x60
  [  240.420313]  [] vmbus_device_unregister+0x1f/0x50 
[hv_vmbus]
  [  240.420316]  [] vmbus_onoffer_rescind+0x91/0xb0 
[hv_vmbus]
  [  240.420324]  [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
  [  240.420327]  [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
  [  240.420331]  [] process_one_work+0x165/0x480
  [  240.420335]  [] worker_thread+0x4b/0x4c0
  [  240.420338]  [] ? process_one_work+0x480/0x480
  [  240.420341]  [] ? process_one_work+0x480/0x480
  [  240.420345]  [] kthread+0xd8/0xf0
  [  240.420347]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  240.420350]  [] ret_from_fork+0x3f/0x70
  [  240.420352]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  317.360035] serial8250: too much work for irq3

  The following commit should fix this issue:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398

  Waiting for release_event in all three drivers introduced issues on release
  as on_reset() hook is not always called. E.g. if the device was never
  opened we will never get the completion.

  Move the waiting code to hvutil_transport_destroy() and make sure it is
  only called when the device is open. hvt->lock serialization should
  guarantee the absence of races.

  Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
  Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing 
issue")
  Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing 
issue")

  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Signed-off-by: Vitaly Kuznetsov 
  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: Greg Kroah-Hartman 

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1682632

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

Title:
  systemd blocked and times out

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  At boot I consistently get the error message:

  "INFO: task systemd-udevd:179 blocked for more than 120 seconds."

  This is under 16.04 on a Dell Optiplex 9020. See the attached image
  for a full call trace when booting in Recovery Mode.

  I want the system to boot to the GUI, but it instead stalls at
  repeating this error message. Eventually it dumps onto the command
  line as a read-only system.

  cat /proc/version_signature is Ubuntu 4.8.0-42.45~16.04.1 generic
  4.8.17

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

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

[Kernel-packages] [Bug 1641393] Re: 'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S Fresh install

[Mo B]

Hi, I am experiencing a similar issue with the new Lenovo Yoga 720 15"
that just came out (April 2017)


As far as I can tell the touchpad is not detected. I have tried all of the 
option suggested above to no avail. Please let me know if I should file a new 
bug or if I can provide any additional troubleshooting information. Thanks.

$ xinput --list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Wacom HID 50FE Finger id=11   [slave  pointer  (2)]
⎜   ↳ Logitech G300s Optical Gaming Mouse   id=15   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Power Button  id=9[slave  keyboard (3)]
↳ EasyCameraid=10   [slave  keyboard (3)]
↳ Ideapad extra buttons id=12   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=13   [slave  keyboard (3)]
↳ Logitech G300s Optical Gaming Mouse   id=14   [slave  keyboard (3)]

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

Title:
  'Elan Touchpad' not detected in Ubuntu 16.04.1 Gigabyte P57K-965-603S
  Fresh install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of Ubuntu 16.04.1 (July 27 2016, downloaded
  November 13 2016 from the official site) on the above machine, the
  Elan touchpad was not detected at all.  An external mouse works
  perfectly.

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

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

[Kernel-packages] [Bug 1682561] Re: [Hyper-V] hv: util: move waiting for release to hv_utils_transport itself

[Simon Xiao]

It is fixed in the test kernel http://kernel.ubuntu.com/~jsalisbury/lp1682561/.
Please submit the SRU request.

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

Title:
  [Hyper-V] hv: util: move waiting for release to hv_utils_transport
  itself

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

Bug description:
  We are observing call traces with the -73 and -74 proposed kernels
  that look like this:

  [  240.408061] INFO: task kworker/14:1:179 blocked for more than 120 seconds.
  [  240.412299]   Not tainted 4.4.0-73-generic #94-Ubuntu
  [  240.415546] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  240.420217] kworker/14:1D 8804e6f23b68 0   179  2 
0x
  [  240.420229] Workqueue: hv_vmbus_con vmbus_onmessage_work [hv_vmbus]
  [  240.420236]  8804e6f23b68 000181f9 8804ed944600 
8804e6fe3800
  [  240.420241]  8804e6f24000 c0187a48 c0187a40 
8804e6fe3800
  [  240.420243]  8804ea196800 8804e6f23b80 81837845 
7fff
  [  240.420245] Call Trace:
  [  240.420254]  [] schedule+0x35/0x80
  [  240.420256]  [] schedule_timeout+0x1b5/0x270
  [  240.420260]  [] ? kfree+0x13a/0x150
  [  240.420264]  [] ? kfree_const+0x22/0x30
  [  240.420268]  [] ? kobject_release+0x94/0x190
  [  240.420270]  [] ? kobject_put+0x27/0x50
  [  240.420272]  [] wait_for_completion+0xb3/0x140
  [  240.420276]  [] ? wake_up_q+0x70/0x70
  [  240.420284]  [] hv_kvp_deinit+0x4f/0x60 [hv_utils]
  [  240.420288]  [] util_remove+0x21/0x40 [hv_utils]
  [  240.420294]  [] vmbus_remove+0x27/0x30 [hv_vmbus]
  [  240.420301]  [] __device_release_driver+0xa1/0x150
  [  240.420303]  [] device_release_driver+0x23/0x30
  [  240.420306]  [] bus_remove_device+0x101/0x170
  [  240.420308]  [] device_del+0x139/0x270
  [  240.420310]  [] device_unregister+0x1e/0x60
  [  240.420313]  [] vmbus_device_unregister+0x1f/0x50 
[hv_vmbus]
  [  240.420316]  [] vmbus_onoffer_rescind+0x91/0xb0 
[hv_vmbus]
  [  240.420324]  [] vmbus_onmessage+0x33/0xa0 [hv_vmbus]
  [  240.420327]  [] vmbus_onmessage_work+0x21/0x30 [hv_vmbus]
  [  240.420331]  [] process_one_work+0x165/0x480
  [  240.420335]  [] worker_thread+0x4b/0x4c0
  [  240.420338]  [] ? process_one_work+0x480/0x480
  [  240.420341]  [] ? process_one_work+0x480/0x480
  [  240.420345]  [] kthread+0xd8/0xf0
  [  240.420347]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  240.420350]  [] ret_from_fork+0x3f/0x70
  [  240.420352]  [] ? kthread_create_on_node+0x1e0/0x1e0
  [  317.360035] serial8250: too much work for irq3

  The following commit should fix this issue:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c18ae6eb2b312f16c63e34b43ea23926daa398

  Waiting for release_event in all three drivers introduced issues on release
  as on_reset() hook is not always called. E.g. if the device was never
  opened we will never get the completion.

  Move the waiting code to hvutil_transport_destroy() and make sure it is
  only called when the device is open. hvt->lock serialization should
  guarantee the absence of races.

  Fixes: 5a66fecbf6aa ("Drivers: hv: util: kvp: Fix a rescind processing issue")
  Fixes: 20951c7535b5 ("Drivers: hv: util: Fcopy: Fix a rescind processing 
issue")
  Fixes: d77044d142e9 ("Drivers: hv: util: Backup: Fix a rescind processing 
issue")

  Reported-by: Dexuan Cui 
  Tested-by: Dexuan Cui 
  Signed-off-by: Vitaly Kuznetsov 
  Signed-off-by: K. Y. Srinivasan 
  Signed-off-by: Greg Kroah-Hartman 

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

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