from:"Maciej"

Unfortunately I think the situation looks the same with mainline kernel.
Journalctl -b in attachment.

** Attachment added: "journalctl-mainline.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+attachment/5389364/+files/journalctl-mainline.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/1885573

Title:
  Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop's touchpad is not recognized by current linux kernel
  (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat
  /proc/bus/input/devices'.

  1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB)
  2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is 
ALPS, Elan or Synatics
  3. Problem occured for the first time during installation and then it 
continued after installation was complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrozwod1597 F pulseaudio
   /dev/snd/pcmC0D0p:   mrozwod1597 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 16:06:14 2020
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN14WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

Sorry, I followed vicaro's instructions first.

I booted your kernel without the parameters, adding journalctl -b from
it with in the attachment. If I need to check out anything else.

** Attachment added: "journalctl-customkernel.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+attachment/5389328/+files/journalctl-customkernel.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/1885573

Title:
  Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop's touchpad is not recognized by current linux kernel
  (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat
  /proc/bus/input/devices'.

  1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB)
  2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is 
ALPS, Elan or Synatics
  3. Problem occured for the first time during installation and then it 
continued after installation was complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrozwod1597 F pulseaudio
   /dev/snd/pcmC0D0p:   mrozwod1597 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 16:06:14 2020
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN14WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

I tested the provided unsigned image from #8, nothing changed.

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

Title:
  Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop's touchpad is not recognized by current linux kernel
  (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat
  /proc/bus/input/devices'.

  1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB)
  2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is 
ALPS, Elan or Synatics
  3. Problem occured for the first time during installation and then it 
continued after installation was complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrozwod1597 F pulseaudio
   /dev/snd/pcmC0D0p:   mrozwod1597 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 16:06:14 2020
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN14WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

journalctl -b in the attachment

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

Title:
  Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My laptop's touchpad is not recognized by current linux kernel
  (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat
  /proc/bus/input/devices'.

  1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB)
  2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is 
ALPS, Elan or Synatics
  3. Problem occured for the first time during installation and then it 
continued after installation was complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrozwod1597 F pulseaudio
   /dev/snd/pcmC0D0p:   mrozwod1597 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 16:06:14 2020
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN14WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

2020-07-02 Thread Maciej Rozwód

** Attachment added: "ACPI tables dump"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+attachment/5389147/+files/acpidump.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/1885573

Title:
  Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop's touchpad is not recognized by current linux kernel
  (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat
  /proc/bus/input/devices'.

  1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB)
  2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is 
ALPS, Elan or Synatics
  3. Problem occured for the first time during installation and then it 
continued after installation was complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrozwod1597 F pulseaudio
   /dev/snd/pcmC0D0p:   mrozwod1597 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 16:06:14 2020
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN14WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1885573] [NEW] Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

2020-06-29 Thread Maciej Rozwód

Public bug reported:

My laptop's touchpad is not recognized by current linux kernel
(5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat
/proc/bus/input/devices'.

1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB)
2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is 
ALPS, Elan or Synatics
3. Problem occured for the first time during installation and then it continued 
after installation was complete.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-39-generic 5.4.0-39.43
ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
Uname: Linux 5.4.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mrozwod1597 F pulseaudio
 /dev/snd/pcmC0D0p:   mrozwod1597 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 29 16:06:14 2020
InstallationDate: Installed on 2020-06-29 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20SM
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-39-generic N/A
 linux-backports-modules-5.4.0-39-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: DJCN14WW
dmi.board.name: LVAC/LVAD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ThinkBook 15-IIL
dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
dmi.product.family: Thinkbook 15-IIL
dmi.product.name: 20SM
dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
dmi.product.version: Lenovo ThinkBook 15-IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

** Attachment added: "devices dump"
   https://bugs.launchpad.net/bugs/1885573/+attachment/5388160/+files/devices

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

Title:
  Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop's touchpad is not recognized by current linux kernel
  (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat
  /proc/bus/input/devices'.

  1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB)
  2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is 
ALPS, Elan or Synatics
  3. Problem occured for the first time during installation and then it 
continued after installation was complete.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-39-generic 5.4.0-39.43
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mrozwod1597 F pulseaudio
   /dev/snd/pcmC0D0p:   mrozwod1597 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 29 16:06:14 2020
  InstallationDate: Installed on 2020-06-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20SM
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic 
root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-39-generic N/A
   linux-backports-modules-5.4.0-39-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN14WW
  dmi.board.name: LVAC/LVAD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL:
  dmi.product.family: Thinkbook 15-IIL
  dmi.product.name: 20SM
  dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL
  dmi.product.version: Lenovo ThinkBook 15-IIL
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list:

[Kernel-packages] [Bug 1883905] [NEW] Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL

2020-06-17 Thread Maciej Jedliński

Public bug reported:

Laptop is new, I bought it yesterday. I'm dual-booting Windows 10 and
Ubuntu 20.04. Touchpad works on Windows.

The touchpad does not show up in xinput --list and in the devices
(included in the attachment). Its manufacturer is Elantech, at least I
suppose it is, based on an output from acpidump which has shown:

27AD0: 54 59 01 70 0D 45 4C 41 4E 30 36 33 33 00 5F 48  TY.p.ELAN0633._H

on one line. If it is in fact my touchpad and its ID is 0633, then it is
not included in elan_i2c_core.c file in my ubuntu kernel source (IDs end
at 0632). I tried to modify it myself and compile a new, custom kernel,
but I am quite new to linux so I failed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-37-generic 5.4.0-37.41
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  maciek 3356 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 17 14:50:45 2020
InstallationDate: Installed on 2020-06-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera
 Bus 001 Device 002: ID 0b05:1844 ASUSTek Computer, Inc. ASUS WT205 Wireless 
Mouse
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81W8
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=9baf434c-2f39-433d-b9ec-ed69c897ef46 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-37-generic N/A
 linux-backports-modules-5.4.0-37-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DKCN26WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15IIL
dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:
dmi.product.family: IdeaPad S145-15IIL
dmi.product.name: 81W8
dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL
dmi.product.version: Lenovo IdeaPad S145-15IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1883905/+attachment/5384708/+files/devices

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

Title:
  Touchpad is not being detected by Ubuntu on Lenovo IdeaPad S145-15IIL

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop is new, I bought it yesterday. I'm dual-booting Windows 10 and
  Ubuntu 20.04. Touchpad works on Windows.

  The touchpad does not show up in xinput --list and in the devices
  (included in the attachment). Its manufacturer is Elantech, at least I
  suppose it is, based on an output from acpidump which has shown:

  27AD0: 54 59 01 70 0D 45 4C 41 4E 30 36 33 33 00 5F 48
  TY.p.ELAN0633._H

  on one line. If it is in fact my touchpad and its ID is 0633, then it
  is not included in elan_i2c_core.c file in my ubuntu kernel source
  (IDs end at 0632). I tried to modify it myself and compile a new,
  custom kernel, but I am quite new to linux so I failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maciek 3356 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 17 14:50:45 2020
  InstallationDate: Installed on 2020-06-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 002: ID 0b05:1844 ASUSTek Computer, Inc. ASUS WT205 Wireless 
Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81W8
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic

[Kernel-packages] [Bug 1848953] Re: Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working properly in Ubuntu 19.10

2020-06-12 Thread Maciej

I've found workaround, it was enough to disable n standard with "options
iwlwifi 11n_disable=1". Now I'm able to authenticate with any hotspot.

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

Title:
  Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working
  properly in Ubuntu 19.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a clean install of the latest Ubuntu, 19.10, but since the live usb, a 
bug appeared.
  I could not login to the 2.4 GHz Wifi network at home with the fresh 
installed Ubuntu, it says the password is wrong, but it is not.

  I have Dual Band Intel AC 3165 it seems. My card appears in the
  Additional Drivers list with the notice that the device is not
  working. I can connect the 5 GHz wifi, but not the 2.4 GHz. See the
  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  florin 1194 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 22:49:04 2019
  InstallationDate: Installed on 2019-10-19 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks TOSHIBA Web Camera - HD
   Bus 001 Device 006: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=0b07e060-55a5-4186-8670-bce4c230e596 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.sku: PSPUFE
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1848953] Re: Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working properly in Ubuntu 19.10

2020-06-11 Thread Maciej

Any updates on this one? I'm have the same issue with Intel Wifi 6 AX200
card. I can connect to 5GHz but for 2.4GHz I'm getting password prompt
over and over. 2.4GHz works fine on other devices.

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

Title:
  Intel wifi 3165 [8086:3165] subsystem id [8086:4010] not working
  properly in Ubuntu 19.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a clean install of the latest Ubuntu, 19.10, but since the live usb, a 
bug appeared.
  I could not login to the 2.4 GHz Wifi network at home with the fresh 
installed Ubuntu, it says the password is wrong, but it is not.

  I have Dual Band Intel AC 3165 it seems. My card appears in the
  Additional Drivers list with the notice that the device is not
  working. I can connect the 5 GHz wifi, but not the 2.4 GHz. See the
  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  florin 1194 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 22:49:04 2019
  InstallationDate: Installed on 2019-10-19 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5652 IMC Networks TOSHIBA Web Camera - HD
   Bus 001 Device 006: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TOSHIBA SATELLITE P50-C
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=0b07e060-55a5-4186-8670-bce4c230e596 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.50
  dmi.board.name: 06F4
  dmi.board.vendor: FF50
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.50:bd07/05/2017:svnTOSHIBA:pnSATELLITEP50-C:pvrPSPUFE-001009G6:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE P50-C
  dmi.product.sku: PSPUFE
  dmi.product.version: PSPUFE-001009G6
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1879630] Re: No sound output from HDMI audio

2020-05-28 Thread Maciej Borzecki

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

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

Title:
  No sound output from HDMI audio

Status in snapd:
  New
Status in linux-raspi package in Ubuntu:
  New

Bug description:
  There is no sound output from HDMI audio.

  System: Intel NUC7CJYH
  Image: 20200519.2

  Steps to reproduce:
  1. $ sudo snap install alsa-utils
  2. $ sudo amixer set Master 100 unmute
  3. $ sudo amixer set IEC958 100 unmute
  4. $ sudo speaker-test -c2 

  There is no sound output from HDMI audio.

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

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

[Kernel-packages] [Bug 1868894] Re: [uc18] docker overlayfs* seems broken

2020-04-06 Thread Maciej Borzecki

Ian proposed a PR with the change suggested by Jamie:
https://github.com/snapcore/snapd/pull/8426

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

Title:
  [uc18] docker overlayfs* seems broken

Status in snapd:
  Triaged
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  A customer recently reported that 'sudo docker run hello-world' fails
  on a pi3 or pi4 running UC18. Looking at the journal, the failure
  appears to be caused by an apparmor denial related docker's overlay2
  storage driver. I've tried both the unified and the Pi3 specific UC18
  images and both fail with the same error. The same command works fine
  on other devices running UC18 (I've tested multipass+macOS, and
  dragonboard), and also works on a Pi3b running our standard UC16
  image.

  Here are the details from the UC18 image.

  $ snap list
  core  16-2.43.3   8691stablecanonical✓  
core
  core18202001241673stablecanonical✓  
base
  docker18.09.9 427 stablecanonical✓  -
  pi18-127  18-pi canonical✓  
gadget
  pi-kernel 5.3.0-1019.21~18.04.1   104 18-pi canonical✓  
kernel
  snapd 2.43.3  6438stablecanonical✓  
snapd

  And here's the apparmor denial:

  Mar 24 19:38:55 localhost sudo[3095]:  awe : TTY=pts/0 ; PWD=/home/awe ; 
USER=root ; COMMAND=/snap/bin/docker run hello-world
  Mar 24 19:39:02 localhost audit[2932]: AVC apparmor="DENIED" operation="open" 
profile="snap.docker.dockerd" 
name="/system-data/var/snap/docker/common/var-lib-docker/overlay2/afce643d5ac2c31f46b8c867c35abea776166c6da199fab370c30af17d314fd7-init/diff/.dockerenv"
 pid=2932 comm="dockerd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  I've been told this may end up being something that gets worked around
  in snapd, however as this looks like a regression, I'm erring on the
  side of caution and filing this bug anyways.

  Please let me know if there's anything else I can provide.

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

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

[Kernel-packages] [Bug 1845180] Re: strace deadlock when tracing a trivial Go program

Despite waiting for 2h, apport-collect wasn't able to collect any useful
data.

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

Title:
  strace deadlock when tracing a trivial Go program

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Intially found when running snapd integration test suite on Arch on
  5.2.x kernels. The problem was reproduced on daily eoan cloud images
  with kernel Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 (as reported in
  /proc/version_signature)

  Stracing trivial Go binary results in a deadlock when both strace and
  the binary being traced end up in D state.

  Example code:

  ```
  package main

  import (
  "os"
  "syscall"
  )

  func main() {
  syscall.Exec("/bin/echo", []string{"/bin/echo", "Hello"}, os.Environ())
  }
  ```

  $ go build exec.go
  $ while true; do echo '- go'; strace -f -e 'execve' ./exec 2>/dev/null ; done
  ..
  Hello
  - go
  Hello
  - go
  Hello
  - go
  ^C

  At which point strace does not react to ^C. This can only be unlocked
  by issuing SIGKILL to either strace or the binary being traced.

  Process list:

    PID TTY  STAT   TIME COMMAND
    808 ?Ss 0:00 sshd: guest [priv]
   1003 ?S  0:01  \_ sshd: guest@pts/0,pts/1,pts/2
   1038 pts/0Ss 0:00  \_ -bash
  23473 pts/0D+ 0:00  |   \_ strace -f -e execve ./exec
  23476 pts/0Dl+0:00  |   \_ ./exec

  The dump of blocked kernel tasks:

  [  414.886023] sysrq: Show Blocked State
  [  414.886695]   taskPC stack   pid father
  [  414.886739] strace  D0 23473   1038 0x
  [  414.886741] Call Trace:
  [  414.886747]  __schedule+0x2b9/0x6c0
  [  414.886748]  schedule+0x42/0xb0
  [  414.886750]  schedule_preempt_disabled+0xe/0x10
  [  414.886751]  __mutex_lock.isra.0+0x182/0x4f0
  [  414.886752]  __mutex_lock_killable_slowpath+0x13/0x20
  [  414.886754]  mutex_lock_killable+0x2e/0x40
  [  414.886756]  mm_access+0x27/0xa0
  [  414.886758]  process_vm_rw_core.isra.0+0x10f/0x590
  [  414.886760]  ? __switch_to_asm+0x40/0x70
  [  414.886761]  ? __switch_to_asm+0x34/0x70
  [  414.886762]  ? __switch_to_asm+0x34/0x70
  [  414.886763]  ? __switch_to_asm+0x40/0x70
  [  414.886764]  ? reschedule_interrupt+0xa/0x20
  [  414.886767]  ? __check_object_size+0x4d/0x150
  [  414.886770]  ? _copy_from_user+0x3e/0x60
  [  414.886772]  ? rw_copy_check_uvector+0x62/0x110
  [  414.886774]  ? __check_object_size+0x4d/0x150
  [  414.886774]  ? _copy_from_user+0x3e/0x60
  [  414.886776]  process_vm_rw+0x106/0x130
  [  414.886778]  ? common_file_perm+0x5e/0x110
  [  414.886780]  ? vfs_write+0x173/0x1a0
  [  414.886781]  ? ksys_write+0x67/0xe0
  [  414.886782]  __x64_sys_process_vm_readv+0x2b/0x30
  [  414.886785]  do_syscall_64+0x5a/0x130
  [  414.886786]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  414.886788] RIP: 0033:0x7fa7b90ec19e
  [  414.886794] Code: Bad RIP value.
  [  414.886794] RSP: 002b:7ffc293ab9f8 EFLAGS: 0246 ORIG_RAX: 
0136
  [  414.886796] RAX: ffda RBX: 7ffc293aba90 RCX: 
7fa7b90ec19e
  [  414.886796] RDX: 0001 RSI: 7ffc293aba00 RDI: 
5bb5
  [  414.886797] RBP: 00c8a010 R08: 0001 R09: 

  [  414.886797] R10: 7ffc293aba10 R11: 0246 R12: 
1000
  [  414.886797] R13: 1000 R14: 5bb5 R15: 

  [  414.886799] execD0 23476  23473 0x80004003
  [  414.886800] Call Trace:
  [  414.886802]  __schedule+0x2b9/0x6c0
  [  414.886803]  schedule+0x42/0xb0
  [  414.886805]  de_thread+0x1c3/0x480
  [  414.886806]  flush_old_exec+0x2a/0x260
  [  414.886808]  ? load_elf_phdrs+0x70/0xb0
  [  414.886809]  load_elf_binary+0x344/0x11e0
  [  414.886810]  ? get_user_pages_remote+0x146/0x230
  [  414.886811]  ? get_acl+0x1d/0x120
  [  414.886813]  ? ima_bprm_check+0x87/0xb0
  [  414.886814]  search_binary_handler+0x8b/0x1c0
  [  414.886816]  __do_execve_file.isra.0+0x4fe/0x860
  [  414.886817]  __x64_sys_execve+0x39/0x50
  [  414.886818]  do_syscall_64+0x5a/0x130
  [  414.886820]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  414.886820] RIP: 0033:0x459ffb
  [  414.886821] Code: Bad RIP value.
  [  414.886822] RSP: 002b:00c82e40 EFLAGS: 0206 ORIG_RAX: 
003b
  [  414.886822] RAX: ffda RBX:  RCX: 
00459ffb
  [  414.886823] RDX: 00c98000 RSI: 00c96000 RDI: 
00c8a010
  [  414.886823] RBP: 00c82ed0 R08:  R09: 

  [  414.886824] R10:  R11: 0206 R12: 
00c9a848
  [  414.886824] R13: 085b R14: 00c9a848 R15: 
00c980b0

  A patch was proposed on LKML back in 2016

[Kernel-packages] [Bug 1845180] Re: strace deadlock when tracing a trivial Go program

** Attachment added: "Trivial piece of Go code"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845180/+attachment/5290927/+files/exec.go

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

Title:
  strace deadlock when tracing a trivial Go program

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Intially found when running snapd integration test suite on Arch on
  5.2.x kernels. The problem was reproduced on daily eoan cloud images
  with kernel Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 (as reported in
  /proc/version_signature)

  Stracing trivial Go binary results in a deadlock when both strace and
  the binary being traced end up in D state.

  Example code:

  ```
  package main

  import (
  "os"
  "syscall"
  )

  func main() {
  syscall.Exec("/bin/echo", []string{"/bin/echo", "Hello"}, os.Environ())
  }
  ```

  $ go build exec.go
  $ while true; do echo '- go'; strace -f -e 'execve' ./exec 2>/dev/null ; done
  ..
  Hello
  - go
  Hello
  - go
  Hello
  - go
  ^C

  At which point strace does not react to ^C. This can only be unlocked
  by issuing SIGKILL to either strace or the binary being traced.

  Process list:

    PID TTY  STAT   TIME COMMAND
    808 ?Ss 0:00 sshd: guest [priv]
   1003 ?S  0:01  \_ sshd: guest@pts/0,pts/1,pts/2
   1038 pts/0Ss 0:00  \_ -bash
  23473 pts/0D+ 0:00  |   \_ strace -f -e execve ./exec
  23476 pts/0Dl+0:00  |   \_ ./exec

  The dump of blocked kernel tasks:

  [  414.886023] sysrq: Show Blocked State
  [  414.886695]   taskPC stack   pid father
  [  414.886739] strace  D0 23473   1038 0x
  [  414.886741] Call Trace:
  [  414.886747]  __schedule+0x2b9/0x6c0
  [  414.886748]  schedule+0x42/0xb0
  [  414.886750]  schedule_preempt_disabled+0xe/0x10
  [  414.886751]  __mutex_lock.isra.0+0x182/0x4f0
  [  414.886752]  __mutex_lock_killable_slowpath+0x13/0x20
  [  414.886754]  mutex_lock_killable+0x2e/0x40
  [  414.886756]  mm_access+0x27/0xa0
  [  414.886758]  process_vm_rw_core.isra.0+0x10f/0x590
  [  414.886760]  ? __switch_to_asm+0x40/0x70
  [  414.886761]  ? __switch_to_asm+0x34/0x70
  [  414.886762]  ? __switch_to_asm+0x34/0x70
  [  414.886763]  ? __switch_to_asm+0x40/0x70
  [  414.886764]  ? reschedule_interrupt+0xa/0x20
  [  414.886767]  ? __check_object_size+0x4d/0x150
  [  414.886770]  ? _copy_from_user+0x3e/0x60
  [  414.886772]  ? rw_copy_check_uvector+0x62/0x110
  [  414.886774]  ? __check_object_size+0x4d/0x150
  [  414.886774]  ? _copy_from_user+0x3e/0x60
  [  414.886776]  process_vm_rw+0x106/0x130
  [  414.886778]  ? common_file_perm+0x5e/0x110
  [  414.886780]  ? vfs_write+0x173/0x1a0
  [  414.886781]  ? ksys_write+0x67/0xe0
  [  414.886782]  __x64_sys_process_vm_readv+0x2b/0x30
  [  414.886785]  do_syscall_64+0x5a/0x130
  [  414.886786]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  414.886788] RIP: 0033:0x7fa7b90ec19e
  [  414.886794] Code: Bad RIP value.
  [  414.886794] RSP: 002b:7ffc293ab9f8 EFLAGS: 0246 ORIG_RAX: 
0136
  [  414.886796] RAX: ffda RBX: 7ffc293aba90 RCX: 
7fa7b90ec19e
  [  414.886796] RDX: 0001 RSI: 7ffc293aba00 RDI: 
5bb5
  [  414.886797] RBP: 00c8a010 R08: 0001 R09: 

  [  414.886797] R10: 7ffc293aba10 R11: 0246 R12: 
1000
  [  414.886797] R13: 1000 R14: 5bb5 R15: 

  [  414.886799] execD0 23476  23473 0x80004003
  [  414.886800] Call Trace:
  [  414.886802]  __schedule+0x2b9/0x6c0
  [  414.886803]  schedule+0x42/0xb0
  [  414.886805]  de_thread+0x1c3/0x480
  [  414.886806]  flush_old_exec+0x2a/0x260
  [  414.886808]  ? load_elf_phdrs+0x70/0xb0
  [  414.886809]  load_elf_binary+0x344/0x11e0
  [  414.886810]  ? get_user_pages_remote+0x146/0x230
  [  414.886811]  ? get_acl+0x1d/0x120
  [  414.886813]  ? ima_bprm_check+0x87/0xb0
  [  414.886814]  search_binary_handler+0x8b/0x1c0
  [  414.886816]  __do_execve_file.isra.0+0x4fe/0x860
  [  414.886817]  __x64_sys_execve+0x39/0x50
  [  414.886818]  do_syscall_64+0x5a/0x130
  [  414.886820]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  414.886820] RIP: 0033:0x459ffb
  [  414.886821] Code: Bad RIP value.
  [  414.886822] RSP: 002b:00c82e40 EFLAGS: 0206 ORIG_RAX: 
003b
  [  414.886822] RAX: ffda RBX:  RCX: 
00459ffb
  [  414.886823] RDX: 00c98000 RSI: 00c96000 RDI: 
00c8a010
  [  414.886823] RBP: 00c82ed0 R08:  R09: 

  [  414.886824] R10:  R11: 0206 R12: 
00c9a848
  [  414.886824] R13: 085b R14: 00c9a848 R15: 
00c980b0

  A patch was proposed on LKML back in 2016

[Kernel-packages] [Bug 1845180] Re: strace deadlock when tracing a trivial Go program

Blocked kernel tasks as reported by echo w > /proc/sysrq-trigger

** Attachment added: "Blocked kernel tasks"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845180/+attachment/5290929/+files/blocked.state

** Description changed:

  Intially found when running snapd integration test suite on Arch on
  5.2.x kernels. The problem was reproduced on daily eoan cloud images
  with kernel Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 (as reported in
  /proc/version_signature)
  
  Stracing trivial Go binary results in a deadlock when both strace and
  the binary being traced end up in D state.
  
  Example code:
  
  ```
  package main
  
  import (
- "os"
- "syscall"
+ "os"
+ "syscall"
  )
  
  func main() {
- syscall.Exec("/bin/echo", []string{"/bin/echo", "Hello"}, os.Environ())
+ syscall.Exec("/bin/echo", []string{"/bin/echo", "Hello"}, os.Environ())
  }
  ```
  
  $ go build exec.go
  $ while true; do echo '- go'; strace -f -e 'execve' ./exec 2>/dev/null ; done
  ..
  Hello
  - go
  Hello
  - go
  Hello
  - go
  ^C
  
- 
- At which point strace does not react to ^C. This can only be unlocked by 
issuing SIGKILL to either strace or the binary being traced.
+ At which point strace does not react to ^C. This can only be unlocked by
+ issuing SIGKILL to either strace or the binary being traced.
  
  Process list:
  
-   PID TTY  STAT   TIME COMMAND
-   808 ?Ss 0:00 sshd: guest [priv]
-  1003 ?S  0:01  \_ sshd: guest@pts/0,pts/1,pts/2
-  1038 pts/0Ss 0:00  \_ -bash
+   PID TTY  STAT   TIME COMMAND
+   808 ?Ss 0:00 sshd: guest [priv]
+  1003 ?S  0:01  \_ sshd: guest@pts/0,pts/1,pts/2
+  1038 pts/0Ss 0:00  \_ -bash
  23473 pts/0D+ 0:00  |   \_ strace -f -e execve ./exec
  23476 pts/0Dl+0:00  |   \_ ./exec
  
  The dump of blocked kernel tasks:
  
  [  414.886023] sysrq: Show Blocked State
  [  414.886695]   taskPC stack   pid father
  [  414.886739] strace  D0 23473   1038 0x
  [  414.886741] Call Trace:
  [  414.886747]  __schedule+0x2b9/0x6c0
  [  414.886748]  schedule+0x42/0xb0
  [  414.886750]  schedule_preempt_disabled+0xe/0x10
  [  414.886751]  __mutex_lock.isra.0+0x182/0x4f0
  [  414.886752]  __mutex_lock_killable_slowpath+0x13/0x20
  [  414.886754]  mutex_lock_killable+0x2e/0x40
  [  414.886756]  mm_access+0x27/0xa0
  [  414.886758]  process_vm_rw_core.isra.0+0x10f/0x590
  [  414.886760]  ? __switch_to_asm+0x40/0x70
  [  414.886761]  ? __switch_to_asm+0x34/0x70
  [  414.886762]  ? __switch_to_asm+0x34/0x70
  [  414.886763]  ? __switch_to_asm+0x40/0x70
  [  414.886764]  ? reschedule_interrupt+0xa/0x20
  [  414.886767]  ? __check_object_size+0x4d/0x150
  [  414.886770]  ? _copy_from_user+0x3e/0x60
  [  414.886772]  ? rw_copy_check_uvector+0x62/0x110
  [  414.886774]  ? __check_object_size+0x4d/0x150
  [  414.886774]  ? _copy_from_user+0x3e/0x60
  [  414.886776]  process_vm_rw+0x106/0x130
  [  414.886778]  ? common_file_perm+0x5e/0x110
  [  414.886780]  ? vfs_write+0x173/0x1a0
  [  414.886781]  ? ksys_write+0x67/0xe0
  [  414.886782]  __x64_sys_process_vm_readv+0x2b/0x30
  [  414.886785]  do_syscall_64+0x5a/0x130
  [  414.886786]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  414.886788] RIP: 0033:0x7fa7b90ec19e
  [  414.886794] Code: Bad RIP value.
  [  414.886794] RSP: 002b:7ffc293ab9f8 EFLAGS: 0246 ORIG_RAX: 
0136
  [  414.886796] RAX: ffda RBX: 7ffc293aba90 RCX: 
7fa7b90ec19e
  [  414.886796] RDX: 0001 RSI: 7ffc293aba00 RDI: 
5bb5
  [  414.886797] RBP: 00c8a010 R08: 0001 R09: 

  [  414.886797] R10: 7ffc293aba10 R11: 0246 R12: 
1000
  [  414.886797] R13: 1000 R14: 5bb5 R15: 

  [  414.886799] execD0 23476  23473 0x80004003
  [  414.886800] Call Trace:
  [  414.886802]  __schedule+0x2b9/0x6c0
  [  414.886803]  schedule+0x42/0xb0
  [  414.886805]  de_thread+0x1c3/0x480
  [  414.886806]  flush_old_exec+0x2a/0x260
  [  414.886808]  ? load_elf_phdrs+0x70/0xb0
  [  414.886809]  load_elf_binary+0x344/0x11e0
  [  414.886810]  ? get_user_pages_remote+0x146/0x230
  [  414.886811]  ? get_acl+0x1d/0x120
  [  414.886813]  ? ima_bprm_check+0x87/0xb0
  [  414.886814]  search_binary_handler+0x8b/0x1c0
  [  414.886816]  __do_execve_file.isra.0+0x4fe/0x860
  [  414.886817]  __x64_sys_execve+0x39/0x50
  [  414.886818]  do_syscall_64+0x5a/0x130
  [  414.886820]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  414.886820] RIP: 0033:0x459ffb
  [  414.886821] Code: Bad RIP value.
  [  414.886822] RSP: 002b:00c82e40 EFLAGS: 0206 ORIG_RAX: 
003b
  [  414.886822] RAX: ffda RBX:  RCX: 
00459ffb
  [  414.886823] RDX: 00c98000 RSI: 00c96000 RDI: 
00c8a010
  [  414.886823] RBP: 00c82ed0

[Kernel-packages] [Bug 1845180] Re: strace deadlock when tracing a trivial Go program

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845180/+attachment/5290928/+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/1845180

Title:
  strace deadlock when tracing a trivial Go program

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Intially found when running snapd integration test suite on Arch on
  5.2.x kernels. The problem was reproduced on daily eoan cloud images
  with kernel Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 (as reported in
  /proc/version_signature)

  Stracing trivial Go binary results in a deadlock when both strace and
  the binary being traced end up in D state.

  Example code:

  ```
  package main

  import (
  "os"
  "syscall"
  )

  func main() {
  syscall.Exec("/bin/echo", []string{"/bin/echo", "Hello"}, os.Environ())
  }
  ```

  $ go build exec.go
  $ while true; do echo '- go'; strace -f -e 'execve' ./exec 2>/dev/null ; done
  ..
  Hello
  - go
  Hello
  - go
  Hello
  - go
  ^C

  At which point strace does not react to ^C. This can only be unlocked
  by issuing SIGKILL to either strace or the binary being traced.

  Process list:

    PID TTY  STAT   TIME COMMAND
    808 ?Ss 0:00 sshd: guest [priv]
   1003 ?S  0:01  \_ sshd: guest@pts/0,pts/1,pts/2
   1038 pts/0Ss 0:00  \_ -bash
  23473 pts/0D+ 0:00  |   \_ strace -f -e execve ./exec
  23476 pts/0Dl+0:00  |   \_ ./exec

  The dump of blocked kernel tasks:

  [  414.886023] sysrq: Show Blocked State
  [  414.886695]   taskPC stack   pid father
  [  414.886739] strace  D0 23473   1038 0x
  [  414.886741] Call Trace:
  [  414.886747]  __schedule+0x2b9/0x6c0
  [  414.886748]  schedule+0x42/0xb0
  [  414.886750]  schedule_preempt_disabled+0xe/0x10
  [  414.886751]  __mutex_lock.isra.0+0x182/0x4f0
  [  414.886752]  __mutex_lock_killable_slowpath+0x13/0x20
  [  414.886754]  mutex_lock_killable+0x2e/0x40
  [  414.886756]  mm_access+0x27/0xa0
  [  414.886758]  process_vm_rw_core.isra.0+0x10f/0x590
  [  414.886760]  ? __switch_to_asm+0x40/0x70
  [  414.886761]  ? __switch_to_asm+0x34/0x70
  [  414.886762]  ? __switch_to_asm+0x34/0x70
  [  414.886763]  ? __switch_to_asm+0x40/0x70
  [  414.886764]  ? reschedule_interrupt+0xa/0x20
  [  414.886767]  ? __check_object_size+0x4d/0x150
  [  414.886770]  ? _copy_from_user+0x3e/0x60
  [  414.886772]  ? rw_copy_check_uvector+0x62/0x110
  [  414.886774]  ? __check_object_size+0x4d/0x150
  [  414.886774]  ? _copy_from_user+0x3e/0x60
  [  414.886776]  process_vm_rw+0x106/0x130
  [  414.886778]  ? common_file_perm+0x5e/0x110
  [  414.886780]  ? vfs_write+0x173/0x1a0
  [  414.886781]  ? ksys_write+0x67/0xe0
  [  414.886782]  __x64_sys_process_vm_readv+0x2b/0x30
  [  414.886785]  do_syscall_64+0x5a/0x130
  [  414.886786]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  414.886788] RIP: 0033:0x7fa7b90ec19e
  [  414.886794] Code: Bad RIP value.
  [  414.886794] RSP: 002b:7ffc293ab9f8 EFLAGS: 0246 ORIG_RAX: 
0136
  [  414.886796] RAX: ffda RBX: 7ffc293aba90 RCX: 
7fa7b90ec19e
  [  414.886796] RDX: 0001 RSI: 7ffc293aba00 RDI: 
5bb5
  [  414.886797] RBP: 00c8a010 R08: 0001 R09: 

  [  414.886797] R10: 7ffc293aba10 R11: 0246 R12: 
1000
  [  414.886797] R13: 1000 R14: 5bb5 R15: 

  [  414.886799] execD0 23476  23473 0x80004003
  [  414.886800] Call Trace:
  [  414.886802]  __schedule+0x2b9/0x6c0
  [  414.886803]  schedule+0x42/0xb0
  [  414.886805]  de_thread+0x1c3/0x480
  [  414.886806]  flush_old_exec+0x2a/0x260
  [  414.886808]  ? load_elf_phdrs+0x70/0xb0
  [  414.886809]  load_elf_binary+0x344/0x11e0
  [  414.886810]  ? get_user_pages_remote+0x146/0x230
  [  414.886811]  ? get_acl+0x1d/0x120
  [  414.886813]  ? ima_bprm_check+0x87/0xb0
  [  414.886814]  search_binary_handler+0x8b/0x1c0
  [  414.886816]  __do_execve_file.isra.0+0x4fe/0x860
  [  414.886817]  __x64_sys_execve+0x39/0x50
  [  414.886818]  do_syscall_64+0x5a/0x130
  [  414.886820]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  414.886820] RIP: 0033:0x459ffb
  [  414.886821] Code: Bad RIP value.
  [  414.886822] RSP: 002b:00c82e40 EFLAGS: 0206 ORIG_RAX: 
003b
  [  414.886822] RAX: ffda RBX:  RCX: 
00459ffb
  [  414.886823] RDX: 00c98000 RSI: 00c96000 RDI: 
00c8a010
  [  414.886823] RBP: 00c82ed0 R08:  R09: 

  [  414.886824] R10:  R11: 0206 R12: 
00c9a848
  [  414.886824] R13: 085b R14: 00c9a848 R15: 
00c980b0

  A patch was proposed on LKML back in 2016

[Kernel-packages] [Bug 1845180] [NEW] strace deadlock when tracing a trivial Go program

Public bug reported:

Intially found when running snapd integration test suite on Arch on
5.2.x kernels. The problem was reproduced on daily eoan cloud images
with kernel Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 (as reported in
/proc/version_signature)

Stracing trivial Go binary results in a deadlock when both strace and
the binary being traced end up in D state.

Example code:

```
package main

import (
"os"
"syscall"
)

func main() {
syscall.Exec("/bin/echo", []string{"/bin/echo", "Hello"}, os.Environ())
}
```

$ go build exec.go
$ while true; do echo '- go'; strace -f -e 'execve' ./exec 2>/dev/null ; done
..
Hello
- go
Hello
- go
Hello
- go
^C

At which point strace does not react to ^C. This can only be unlocked by
issuing SIGKILL to either strace or the binary being traced.

Process list:

  PID TTY  STAT   TIME COMMAND
  808 ?Ss 0:00 sshd: guest [priv]
 1003 ?S  0:01  \_ sshd: guest@pts/0,pts/1,pts/2
 1038 pts/0Ss 0:00  \_ -bash
23473 pts/0D+ 0:00  |   \_ strace -f -e execve ./exec
23476 pts/0Dl+0:00  |   \_ ./exec

The dump of blocked kernel tasks:

[  414.886023] sysrq: Show Blocked State
[  414.886695]   taskPC stack   pid father
[  414.886739] strace  D0 23473   1038 0x
[  414.886741] Call Trace:
[  414.886747]  __schedule+0x2b9/0x6c0
[  414.886748]  schedule+0x42/0xb0
[  414.886750]  schedule_preempt_disabled+0xe/0x10
[  414.886751]  __mutex_lock.isra.0+0x182/0x4f0
[  414.886752]  __mutex_lock_killable_slowpath+0x13/0x20
[  414.886754]  mutex_lock_killable+0x2e/0x40
[  414.886756]  mm_access+0x27/0xa0
[  414.886758]  process_vm_rw_core.isra.0+0x10f/0x590
[  414.886760]  ? __switch_to_asm+0x40/0x70
[  414.886761]  ? __switch_to_asm+0x34/0x70
[  414.886762]  ? __switch_to_asm+0x34/0x70
[  414.886763]  ? __switch_to_asm+0x40/0x70
[  414.886764]  ? reschedule_interrupt+0xa/0x20
[  414.886767]  ? __check_object_size+0x4d/0x150
[  414.886770]  ? _copy_from_user+0x3e/0x60
[  414.886772]  ? rw_copy_check_uvector+0x62/0x110
[  414.886774]  ? __check_object_size+0x4d/0x150
[  414.886774]  ? _copy_from_user+0x3e/0x60
[  414.886776]  process_vm_rw+0x106/0x130
[  414.886778]  ? common_file_perm+0x5e/0x110
[  414.886780]  ? vfs_write+0x173/0x1a0
[  414.886781]  ? ksys_write+0x67/0xe0
[  414.886782]  __x64_sys_process_vm_readv+0x2b/0x30
[  414.886785]  do_syscall_64+0x5a/0x130
[  414.886786]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  414.886788] RIP: 0033:0x7fa7b90ec19e
[  414.886794] Code: Bad RIP value.
[  414.886794] RSP: 002b:7ffc293ab9f8 EFLAGS: 0246 ORIG_RAX: 
0136
[  414.886796] RAX: ffda RBX: 7ffc293aba90 RCX: 7fa7b90ec19e
[  414.886796] RDX: 0001 RSI: 7ffc293aba00 RDI: 5bb5
[  414.886797] RBP: 00c8a010 R08: 0001 R09: 
[  414.886797] R10: 7ffc293aba10 R11: 0246 R12: 1000
[  414.886797] R13: 1000 R14: 5bb5 R15: 
[  414.886799] execD0 23476  23473 0x80004003
[  414.886800] Call Trace:
[  414.886802]  __schedule+0x2b9/0x6c0
[  414.886803]  schedule+0x42/0xb0
[  414.886805]  de_thread+0x1c3/0x480
[  414.886806]  flush_old_exec+0x2a/0x260
[  414.886808]  ? load_elf_phdrs+0x70/0xb0
[  414.886809]  load_elf_binary+0x344/0x11e0
[  414.886810]  ? get_user_pages_remote+0x146/0x230
[  414.886811]  ? get_acl+0x1d/0x120
[  414.886813]  ? ima_bprm_check+0x87/0xb0
[  414.886814]  search_binary_handler+0x8b/0x1c0
[  414.886816]  __do_execve_file.isra.0+0x4fe/0x860
[  414.886817]  __x64_sys_execve+0x39/0x50
[  414.886818]  do_syscall_64+0x5a/0x130
[  414.886820]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  414.886820] RIP: 0033:0x459ffb
[  414.886821] Code: Bad RIP value.
[  414.886822] RSP: 002b:00c82e40 EFLAGS: 0206 ORIG_RAX: 
003b
[  414.886822] RAX: ffda RBX:  RCX: 00459ffb
[  414.886823] RDX: 00c98000 RSI: 00c96000 RDI: 00c8a010
[  414.886823] RBP: 00c82ed0 R08:  R09: 
[  414.886824] R10:  R11: 0206 R12: 00c9a848
[  414.886824] R13: 085b R14: 00c9a848 R15: 00c980b0

A patch was proposed on LKML back in 2016
https://lore.kernel.org/patchwork/patch/719314/ but it was not accepted
into mainline.

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

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1845180/+attachment/5290926/+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/1845180

Title:
  strace deadlock when tracing a trivial Go program

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Intially found when running snapd

[Kernel-packages] [Bug 1826516] [NEW] bluetooh mouse lag when use bluetooth hedphones

2019-04-26 Thread Maciej Witman

Public bug reported:

I have Microsoft Sculpt Comfort Mouse (bluettoh) and it works.
When i connect my bluetooth heaset (plantronics PLT 50) mouse cursor lags 
terribly.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
Uname: Linux 5.0.9-050009-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 26 09:19:08 2019
InstallationDate: Installed on 2018-12-22 (124 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20LW000YPB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.9-050009-generic 
root=UUID=74c51606-28cc-4d8f-91ac-c1d0dfd082c3 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET54W (1.31 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LW000YPB
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET54W(1.31):bd01/21/2019:svnLENOVO:pn20LW000YPB:pvrThinkPadL580:rvnLENOVO:rn20LW000YPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L580
dmi.product.name: 20LW000YPB
dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
dmi.product.version: ThinkPad L580
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:21:6B:EA:3C:5F  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:21050738 acl:78587 sco:377825 events:21982 errors:0
TX bytes:19896288 acl:159 sco:377811 commands:5333 errors:0
mtime.conffile..etc.bluetooth.input.conf: 2019-04-15T07:00:56.250208

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


** Tags: amd64 apport-bug cosmic third-party-packages

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

Title:
  bluetooh mouse lag when use bluetooth hedphones

Status in bluez package in Ubuntu:
  New

Bug description:
  I have Microsoft Sculpt Comfort Mouse (bluettoh) and it works.
  When i connect my bluetooth heaset (plantronics PLT 50) mouse cursor lags 
terribly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 09:19:08 2019
  InstallationDate: Installed on 2018-12-22 (124 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20LW000YPB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.9-050009-generic 
root=UUID=74c51606-28cc-4d8f-91ac-c1d0dfd082c3 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET54W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LW000YPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET54W(1.31):bd01/21/2019:svnLENOVO:pn20LW000YPB:pvrThinkPadL580:rvnLENOVO:rn20LW000YPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L580
  dmi.product.name: 20LW000YPB
  dmi.product.sku: LENOVO_MT_20LW_BU_Think_FM_ThinkPad L580
  dmi.product.version: ThinkPad L580
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:21:6B:EA:3C:5F  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:21050738 acl:78587 sco:377825 events:21982 errors:0
TX bytes:19896288 acl:159 sco:377811 commands:5333 errors:0
  mtime.conffile..etc.bluetooth.input.conf: 2019-04-15T07:00:56.250208

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

-- 
Mailing list: https://launchpad.net/~kernel-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 AMD Ryzen / Gigabyte GA-AB350-gaming-3

2017-03-13 Thread Maciej Dziardziel

Huang YangWen: can you attach result of those command:

ls -l /sys/bus/acpi/devices/
sudo lspci -vvnn


I wonder what the differences between motherboards are. I suspect Gigabyte has 
something other boards don't have.

-- 
You 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 AMD Ryzen / Gigabyte GA-AB350-gaming-3

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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

2017-03-11 Thread Maciej Dziardziel

> Maciej, do you have any suggestions if there is no previous OS
installed?

You may try to boot with those options:

acpi=off quiet loglevel=3

(just acpi=off might be enough). That should get you through
installation.

-- 
You 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 AMD Ryzen / Gigabyte GA-AB350-gaming-3

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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

2017-03-10 Thread Maciej Dziardziel

I've found a workaround (requires compiling own kernel, tested on 4.11
and r4.11rc1):

When configuring kernel (I used make menuconfig) disable following
things:

Everything under device drivers/gpio support, especially:
memory mapped files/amd promontory support (GPIO_AMDPT)
and pci gpio expanders / amd 8111 gpio driver (GPIO_AMD8111)
but I've turned of everything to make sure nothing is using gpio.

device drivers / pin controllers / amd gpio pin control (PINCTRL_AMD)

Perhaps only one of them could be really necessary, but I didn't tested
that.

System boots normally, no problems with journald and no weird messages
from dmesg.

-- 
You 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 AMD Ryzen / Gigabyte GA-AB350-gaming-3

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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

2017-03-09 Thread Maciej Dziardziel

The issue had nothing to do with upgrades, its the same problem on 16.10 as 
well as on 17.04.
I've tested it on my system and on live ubuntu on usb. 

I've tried to use mainline kernel and the problem is still there.

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

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

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

Title:
  System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

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 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

2017-03-09 Thread Maciej Dziardziel

apport information

** Tags added: apport-collected zesty

** Description changed:

  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

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

Title:
  System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

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
  [

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

2017-03-09 Thread Maciej Dziardziel

I've added appport info

-- 
You 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 AMD Ryzen / Gigabyte GA-AB350-gaming-3

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 1671360] [NEW] System doesn't boot properly on AMD Ryzen / Gigabyte GA-AB350-gaming-3

2017-03-08 Thread Maciej Dziardziel

Public bug reported:

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.

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

** Attachment added: "kernel config, lspci, dmesg messages and other info I 
could get"
   https://bugs.launchpad.net/bugs/1671360/+attachment/4834330/+files/report.tgz

-- 
You 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 AMD Ryzen / Gigabyte GA-AB350-gaming-3

Status in linux package in Ubuntu:
  Incomplete

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

[Kernel-packages] [Bug 1614789] [NEW] zfs.target should not require zfs-share.service

2016-08-18 Thread Maciej Puzio

Public bug reported:

Currently package zfsutils-linux contains systemd target file 
/lib/systemd/system/zfs.target that specifies following dependencies:
Requires=zfs-mount.service
Requires=zfs-share.service
Wants=zed.service

zfs-share.service is not essential in setups where file sharing is not
used, or when it is configured without the use of the zfs utility. The
user may therefore choose to mask this service. However, doing so has an
unexpected and confusing effect, preventing zfs from starting on boot at
all. This is because zfs.target is the only zfs-related unit that is
wanted by multi-user.target, and if one of its required services is
masked, zfs.target is skipped, together with zfs-mount.service. A
solution is to replace "Requires=zfs-share.service" with "Wants=zfs-
share.service".

Steps to reproduce:
systemctl mask zfs-share.service
reboot

Expected results:
Module zfs is loaded
zfs-mount.service is active and ZFS filesystems are mounted
ZFS filesystems are not shared

Observed results:
Module zfs is not loaded
ZFS filesystems are not mounted
zpool status produces an error:
"The ZFS modules are not loaded.
Try running '/sbin/modprobe zfs' as root to load them."

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

$ apt-cache policy zfsutils-linux
zfsutils-linux:
  Installed: 0.6.5.6-0ubuntu10

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

** Package changed: autofs (Ubuntu) => zfs-linux (Ubuntu)

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

Title:
  zfs.target should not require zfs-share.service

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Currently package zfsutils-linux contains systemd target file 
/lib/systemd/system/zfs.target that specifies following dependencies:
  Requires=zfs-mount.service
  Requires=zfs-share.service
  Wants=zed.service

  zfs-share.service is not essential in setups where file sharing is not
  used, or when it is configured without the use of the zfs utility. The
  user may therefore choose to mask this service. However, doing so has
  an unexpected and confusing effect, preventing zfs from starting on
  boot at all. This is because zfs.target is the only zfs-related unit
  that is wanted by multi-user.target, and if one of its required
  services is masked, zfs.target is skipped, together with zfs-
  mount.service. A solution is to replace "Requires=zfs-share.service"
  with "Wants=zfs-share.service".

  Steps to reproduce:
  systemctl mask zfs-share.service
  reboot

  Expected results:
  Module zfs is loaded
  zfs-mount.service is active and ZFS filesystems are mounted
  ZFS filesystems are not shared

  Observed results:
  Module zfs is not loaded
  ZFS filesystems are not mounted
  zpool status produces an error:
  "The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them."

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu10

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

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

[Kernel-packages] [Bug 1559716] [NEW] sometimes it works and sometimes it doesn't work

2016-03-20 Thread Maciej Kollo

Public bug reported:

fresh 64-bit 16.04 Installation on HP Compaq 6720s. The drivers for BCM4311 
802.11b/g was working with 14.04 and 15.10 ubuntu version. For 16.04 it is 
sometimes working and sometime it doesn't work. Even if it is direct by the 
modem it is not connecting to the modem. It is as it is not scanning.
Ubuntu Xenial Xerus (development branch)
Release: 16.04
unable to locate package pkgname
should the driver be updated?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 20 15:23:19 2016
InstallationDate: Installed on 2016-03-01 (18 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  sometimes it works and sometimes it doesn't work

Status in bcmwl package in Ubuntu:
  New

Bug description:
  fresh 64-bit 16.04 Installation on HP Compaq 6720s. The drivers for BCM4311 
802.11b/g was working with 14.04 and 15.10 ubuntu version. For 16.04 it is 
sometimes working and sometime it doesn't work. Even if it is direct by the 
modem it is not connecting to the modem. It is as it is not scanning.
  Ubuntu Xenial Xerus (development branch)
  Release: 16.04
  unable to locate package pkgname
  should the driver be updated?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 20 15:23:19 2016
  InstallationDate: Installed on 2016-03-01 (18 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1350480] Re: [REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB devices plugged in

2014-09-10 Thread Maciej Puzio

Joseph, thank you for pointing my attention to this bug. On my hardware
(bug 1330530) the problem is not reproducible with kernel 3.13.y, so
unfortunately I can neither confirm nor deny whether your test kernel
fixes it. However, I would very much like to see the patch being
backported to 3.2.y. i.e. Precise. I already tested the patch (modified
to keep find_trb_seg) with the upstream (kernel.org) stable 3.2 kernel,
and can confirm it fixes the regression.

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

Title:
  [REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with
  USB devices plugged in

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Precise:
  In Progress
Status in “linux” source package in Trusty:
  In Progress
Status in “linux” source package in Utopic:
  In Progress

Bug description:
  The latest kernel update in Ubuntu 14.04 LTS (3.13.0-32.57) renders
  our Intel NUCs unbootable, when we cold boot and have USB devices
  (keyboard, mouse, USB/Ethernet adapter) connected.

  The 3.13.0-24.47 kernel does not exhibit this behavior.

  Our particular NUCs have the i5-3427U processor, which is the
  D53427RKE board (DC53427HYE kit).

  These reports seem to be related:
  http://support.sundtek.com/index.php/topic,1600.0.html
  http://en.it-usenet.org/thread/19505/17700/
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1400 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=37e4ff56-b945-4604-a94d-557bdf83e0b2
  InstallationDate: Installed on 2014-07-30 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=c0597da2-7d4a-4340-b85a-c7f96d8262d7 ro
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/25/2013
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RKPPT10H.86A.0017.2013.0425.1251
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D53427RKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G87790-403
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0017.2013.0425.1251:bd04/25/2013:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87790-403:cvn:ct3:cvr:

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

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

[Kernel-packages] [Bug 1333229] Re: USB 3.0 regression after upgrading to 3.2.0-64 kernel

2014-09-05 Thread Maciej Puzio

The patch has been added to the upstream mainline kernel 3.17-rc3, and
to the 3.16-stable tree. Please see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330530/comments/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/1333229

Title:
  USB 3.0 regression after upgrading to 3.2.0-64 kernel

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 3.2.0-64 kernel wireless mouse stopped working but 
keyboard still works
  Problem occurred with next Wireless Kit (keyboard+mouse):
  04f2:1123 Chicony Electronics Co., Ltd Asus Wireless Keyboard and Mouse
  04f2:0836 Chicony Electronics Co., Ltd Pleomax Wireless Keyboard and Mouse

  from dmesg:
  # dmesg |grep generic-usb
  [3.043949] generic-usb 0003:04F2:0963.0001: input,hidraw0: USB HID v1.11 
Keyboard [Chicony 2.4G Multimedia Wireless Kit] on usb-:00:12.0-3/input0
  [3.059228] generic-usb 0003:04F2:0963.0002: input,hiddev0,hidraw1: USB 
HID v1.11 Mouse [Chicony 2.4G Multimedia Wireless Kit] on 
usb-:00:12.0-3/input1
  [  635.024628] generic-usb 0003:04F2:0836.0003: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  655.024520] generic-usb: probe of 0003:04F2:0836.0004 failed with error 
-110
  [  680.024656] generic-usb: probe of 0003:04F2:0836.0005 failed with error 
-110
  [  686.324531] generic-usb 0003:04F2:0836.0006: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  706.324634] generic-usb: probe of 0003:04F2:0836.0007 failed with error 
-110
  [  731.328465] generic-usb: probe of 0003:04F2:0836.0008 failed with error 
-110
  [  732.155547] generic-usb 0003:04F2:0836.0009: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  752.156459] generic-usb: probe of 0003:04F2:0836.000A failed with error 
-110
  [  777.156718] generic-usb: probe of 0003:04F2:0836.000B failed with error 
-110
  [ 1236.880527] generic-usb 0003:04F2:0836.000C: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [ 1256.880712] generic-usb: probe of 0003:04F2:0836.000D failed with error 
-110
  [ 1281.880705] generic-usb: probe of 0003:04F2:0836.000E failed with error 
-110

  With 3.2.0-63 kernel all works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-64-generic-pae 3.2.0-64.97
  ProcVersionSignature: Ubuntu 3.2.0-64.97-generic-pae 3.2.59
  Uname: Linux 3.2.0-64-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 45'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'SB'/'HDA ATI SB at 0xfeb4 irq 16'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,104384ff,00100100'
 Controls  : 18
 Simple ctrls  : 10
  Date: Mon Jun 23 14:48:34 2014
  HibernationDevice: RESUME=UUID=f22f0450-8574-4bb3-9992-fde733b437eb
  MachineType: ASUSTeK Computer INC. ET2012A
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-64-generic-pae 
root=UUID=8e8ca8ab-ae5e-41bc-b008-7a15a613d9e0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-64-generic-pae N/A
   linux-backports-modules-3.2.0-64-generic-pae  N/A
   linux-firmware1.79.14
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0306
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: ET2012A
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.01G

[Kernel-packages] [Bug 1330530] Re: [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller

2014-09-05 Thread Maciej Puzio

The patch has been somewhat reworked and added to the upstream mainline kernel 
3.17-rc3, and to the 3.16-stable tree.
https://lkml.org/lkml/2014/8/29/386
http://www.spinics.net/lists/stable/msg59724.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/1330530

Title:
  [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3
  controller

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  With a Dell Vostro 430, the HighPoint RocketU 1144C USB 3.0 controller, Areca 
ARC-5040 USB 3.0 RAID enclosure connected to it, and the following conditions 
are met:
  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  An error loop during boot contains the following messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  I've attached a file generated by apport-cli -f -p linux --save
  filename.apport .

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

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

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

[Kernel-packages] [Bug 1333229] Re: USB 3.0 regression after upgrading to 3.2.0-64 kernel

2014-07-18 Thread Maciej Puzio

Problem has been identified and patch created. Please see the following link 
for details:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330530/comments/15

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

Title:
  USB 3.0 regression after upgrading to 3.2.0-64 kernel

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 3.2.0-64 kernel wireless mouse stopped working but 
keyboard still works
  Problem occurred with next Wireless Kit (keyboard+mouse):
  04f2:1123 Chicony Electronics Co., Ltd Asus Wireless Keyboard and Mouse
  04f2:0836 Chicony Electronics Co., Ltd Pleomax Wireless Keyboard and Mouse

  from dmesg:
  # dmesg |grep generic-usb
  [3.043949] generic-usb 0003:04F2:0963.0001: input,hidraw0: USB HID v1.11 
Keyboard [Chicony 2.4G Multimedia Wireless Kit] on usb-:00:12.0-3/input0
  [3.059228] generic-usb 0003:04F2:0963.0002: input,hiddev0,hidraw1: USB 
HID v1.11 Mouse [Chicony 2.4G Multimedia Wireless Kit] on 
usb-:00:12.0-3/input1
  [  635.024628] generic-usb 0003:04F2:0836.0003: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  655.024520] generic-usb: probe of 0003:04F2:0836.0004 failed with error 
-110
  [  680.024656] generic-usb: probe of 0003:04F2:0836.0005 failed with error 
-110
  [  686.324531] generic-usb 0003:04F2:0836.0006: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  706.324634] generic-usb: probe of 0003:04F2:0836.0007 failed with error 
-110
  [  731.328465] generic-usb: probe of 0003:04F2:0836.0008 failed with error 
-110
  [  732.155547] generic-usb 0003:04F2:0836.0009: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  752.156459] generic-usb: probe of 0003:04F2:0836.000A failed with error 
-110
  [  777.156718] generic-usb: probe of 0003:04F2:0836.000B failed with error 
-110
  [ 1236.880527] generic-usb 0003:04F2:0836.000C: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [ 1256.880712] generic-usb: probe of 0003:04F2:0836.000D failed with error 
-110
  [ 1281.880705] generic-usb: probe of 0003:04F2:0836.000E failed with error 
-110

  With 3.2.0-63 kernel all works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-64-generic-pae 3.2.0-64.97
  ProcVersionSignature: Ubuntu 3.2.0-64.97-generic-pae 3.2.59
  Uname: Linux 3.2.0-64-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 45'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'SB'/'HDA ATI SB at 0xfeb4 irq 16'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,104384ff,00100100'
 Controls  : 18
 Simple ctrls  : 10
  Date: Mon Jun 23 14:48:34 2014
  HibernationDevice: RESUME=UUID=f22f0450-8574-4bb3-9992-fde733b437eb
  MachineType: ASUSTeK Computer INC. ET2012A
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-64-generic-pae 
root=UUID=8e8ca8ab-ae5e-41bc-b008-7a15a613d9e0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-64-generic-pae N/A
   linux-backports-modules-3.2.0-64-generic-pae  N/A
   linux-firmware1.79.14
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0306
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: ET2012A
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.01G

[Kernel-packages] [Bug 1330530] Re: [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller

2014-07-18 Thread Maciej Puzio

Julius Werner, the author of the commit in question, has found the problem and 
created a patch. The problem is in the place that I identified, but specific 
regression-triggering details are different that I originally thought. The 
patch is available here:
https://lkml.org/lkml/2014/7/8/571

I tested this patch and can confirm that it fixes the regression in kernel 
3.2.x. Newer kernels have not been affected by the regression, as it is masked 
by another code change that has not been backported to 3.2. Here is the link 
for the discussion:
http://thread.gmane.org/gmane.linux.usb.general/110685

As I understand it, we are now waiting for Julius' patch to be pulled to
the mainline kernel.

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

Title:
  [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3
  controller

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  With a Dell Vostro 430, the HighPoint RocketU 1144C USB 3.0 controller, Areca 
ARC-5040 USB 3.0 RAID enclosure connected to it, and the following conditions 
are met:
  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  An error loop during boot contains the following messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  I've attached a file generated by apport-cli -f -p linux --save
  filename.apport .

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

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

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

[Kernel-packages] [Bug 1330530] Re: [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller

2014-07-01 Thread Maciej Puzio

I think that I may have found the bug, and since the newest upstream kernel 
3.16.0-rc3 has the affected code essentially unmodified, I contacted the 
maintainer of the XHCI driver and the author of the problematic commit. I also 
asked for help on linux-usb kernel mailing list:
http://permalink.gmane.org/gmane.linux.usb.general/110685
http://www.spinics.net/lists/linux-usb/msg109949.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/1330530

Title:
  [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3
  controller

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  With a Dell Vostro 430, the HighPoint RocketU 1144C USB 3.0 controller, Areca 
ARC-5040 USB 3.0 RAID enclosure connected to it, and the following conditions 
are met:
  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  An error loop during boot contains the following messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  I've attached a file generated by apport-cli -f -p linux --save
  filename.apport .

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

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

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

[Kernel-packages] [Bug 1330530] Re: [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller

2014-06-26 Thread Maciej Puzio

Christopher, due to the nature of this bug, I cannot perform the reverse
bisect. I explained it already in comment #8. Just to be clearer: the
regression has not been fixed upstream. There is no 3.x kernel branch
which would contain the regression and the subsequent fix. The
regression either is not there at all (all branches except 3.2), or
remains unfixed (3.2). Thus I have no target for the bisection.

On somewhat happier news, I have spent last few days debugging the
kernel, and I got some results. Specifically, I have a patch that fixes
regression on 3.2.0-64 running on a particular hardware. The patch is
rather ugly, and will probably cause problems on other hardware, but at
least it shows some direction.

I will gladly discuss this matter, but I will need a little more
attention shown by Ubuntu maintainers. Each of my posts corresponds to
many hours of my work, and while I am grateful for any attention, its
current level does not permit a constructive dialogue. I am very sorry
to say this, and I mean no offense, but I will put more effort into
writing here only when I see a chance that someone will read it.

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

** Tags removed: kernel-fixed-upstream-3.16-rc1 needs-reverse-bisect

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

Title:
  [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3
  controller

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  With a Dell Vostro 430, the HighPoint RocketU 1144C USB 3.0 controller, Areca 
ARC-5040 USB 3.0 RAID enclosure connected to it, and the following conditions 
are met:
  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  An error loop during boot contains the following messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  I've attached a file generated by apport-cli -f -p linux --save
  filename.apport .

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

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

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

[Kernel-packages] [Bug 1333229] Re: USB 3.0 regression after upgrading to 3.2.0-64 kernel

2014-06-25 Thread Maciej Puzio

This is interesting:
[ 4650.205313] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep f3133600
[ 4650.205329] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep f313362c

I am getting the same errors with most USB 3.0 devices that I tried. These 
errors come after a ~15 second delay, and this repeats in a loop for 18 
minutes. Some other errors may also be thrown, usually related to udev or 
various timeouts.
However, with the USB3 SD reader that I tested, the errors came only once 
during boot, with only ~15 second total delay, and the boot then proceeded 
successfully, although the device subsequently did not work. This matches your 
observations.

This all suggests that we are experiencing the same root problem..

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

Title:
  USB 3.0 regression after upgrading to 3.2.0-64 kernel

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 3.2.0-64 kernel wireless mouse stopped working but 
keyboard still works
  Problem occurred with next Wireless Kit (keyboard+mouse):
  04f2:1123 Chicony Electronics Co., Ltd Asus Wireless Keyboard and Mouse
  04f2:0836 Chicony Electronics Co., Ltd Pleomax Wireless Keyboard and Mouse

  from dmesg:
  # dmesg |grep generic-usb
  [3.043949] generic-usb 0003:04F2:0963.0001: input,hidraw0: USB HID v1.11 
Keyboard [Chicony 2.4G Multimedia Wireless Kit] on usb-:00:12.0-3/input0
  [3.059228] generic-usb 0003:04F2:0963.0002: input,hiddev0,hidraw1: USB 
HID v1.11 Mouse [Chicony 2.4G Multimedia Wireless Kit] on 
usb-:00:12.0-3/input1
  [  635.024628] generic-usb 0003:04F2:0836.0003: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  655.024520] generic-usb: probe of 0003:04F2:0836.0004 failed with error 
-110
  [  680.024656] generic-usb: probe of 0003:04F2:0836.0005 failed with error 
-110
  [  686.324531] generic-usb 0003:04F2:0836.0006: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  706.324634] generic-usb: probe of 0003:04F2:0836.0007 failed with error 
-110
  [  731.328465] generic-usb: probe of 0003:04F2:0836.0008 failed with error 
-110
  [  732.155547] generic-usb 0003:04F2:0836.0009: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  752.156459] generic-usb: probe of 0003:04F2:0836.000A failed with error 
-110
  [  777.156718] generic-usb: probe of 0003:04F2:0836.000B failed with error 
-110
  [ 1236.880527] generic-usb 0003:04F2:0836.000C: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [ 1256.880712] generic-usb: probe of 0003:04F2:0836.000D failed with error 
-110
  [ 1281.880705] generic-usb: probe of 0003:04F2:0836.000E failed with error 
-110

  With 3.2.0-63 kernel all works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-64-generic-pae 3.2.0-64.97
  ProcVersionSignature: Ubuntu 3.2.0-64.97-generic-pae 3.2.59
  Uname: Linux 3.2.0-64-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 45'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'SB'/'HDA ATI SB at 0xfeb4 irq 16'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,104384ff,00100100'
 Controls  : 18
 Simple ctrls  : 10
  Date: Mon Jun 23 14:48:34 2014
  HibernationDevice: RESUME=UUID=f22f0450-8574-4bb3-9992-fde733b437eb
  MachineType: ASUSTeK Computer INC. ET2012A
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-64-generic-pae 
root=UUID=8e8ca8ab-ae5e-41bc-b008-7a15a613d9e0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code

[Kernel-packages] [Bug 1330530] Re: [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller

2014-06-24 Thread Maciej Puzio

** Tags removed: needs-reverse-bisect

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

Title:
  [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3
  controller

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  With a Dell Vostro 430, the HighPoint RocketU 1144C USB 3.0 controller, Areca 
ARC-5040 USB 3.0 RAID enclosure connected to it, and the following conditions 
are met:
  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  An error loop during boot contains the following messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  I've attached a file generated by apport-cli -f -p linux --save
  filename.apport .

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

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

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

[Kernel-packages] [Bug 1333229] Re: USB 3.0 regression after upgrading to 3.2.0-64 kernel

2014-06-24 Thread Maciej Puzio

Roman, compared to bugs 1330530 and 1328984, you have a similar USB 3.0
controller: ASM1042 (this bug) vs ASM1042A (other bugs). So this may be
the same issue. Would you be able to test the regression with other USB
devices?

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

Title:
  USB 3.0 regression after upgrading to 3.2.0-64 kernel

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 3.2.0-64 kernel wireless mouse stopped working but 
keyboard still works
  Problem occurred with next Wireless Kit (keyboard+mouse):
  04f2:1123 Chicony Electronics Co., Ltd Asus Wireless Keyboard and Mouse
  04f2:0836 Chicony Electronics Co., Ltd Pleomax Wireless Keyboard and Mouse

  from dmesg:
  # dmesg |grep generic-usb
  [3.043949] generic-usb 0003:04F2:0963.0001: input,hidraw0: USB HID v1.11 
Keyboard [Chicony 2.4G Multimedia Wireless Kit] on usb-:00:12.0-3/input0
  [3.059228] generic-usb 0003:04F2:0963.0002: input,hiddev0,hidraw1: USB 
HID v1.11 Mouse [Chicony 2.4G Multimedia Wireless Kit] on 
usb-:00:12.0-3/input1
  [  635.024628] generic-usb 0003:04F2:0836.0003: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  655.024520] generic-usb: probe of 0003:04F2:0836.0004 failed with error 
-110
  [  680.024656] generic-usb: probe of 0003:04F2:0836.0005 failed with error 
-110
  [  686.324531] generic-usb 0003:04F2:0836.0006: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  706.324634] generic-usb: probe of 0003:04F2:0836.0007 failed with error 
-110
  [  731.328465] generic-usb: probe of 0003:04F2:0836.0008 failed with error 
-110
  [  732.155547] generic-usb 0003:04F2:0836.0009: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  752.156459] generic-usb: probe of 0003:04F2:0836.000A failed with error 
-110
  [  777.156718] generic-usb: probe of 0003:04F2:0836.000B failed with error 
-110
  [ 1236.880527] generic-usb 0003:04F2:0836.000C: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [ 1256.880712] generic-usb: probe of 0003:04F2:0836.000D failed with error 
-110
  [ 1281.880705] generic-usb: probe of 0003:04F2:0836.000E failed with error 
-110

  With 3.2.0-63 kernel all works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-64-generic-pae 3.2.0-64.97
  ProcVersionSignature: Ubuntu 3.2.0-64.97-generic-pae 3.2.59
  Uname: Linux 3.2.0-64-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 45'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'SB'/'HDA ATI SB at 0xfeb4 irq 16'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,104384ff,00100100'
 Controls  : 18
 Simple ctrls  : 10
  Date: Mon Jun 23 14:48:34 2014
  HibernationDevice: RESUME=UUID=f22f0450-8574-4bb3-9992-fde733b437eb
  MachineType: ASUSTeK Computer INC. ET2012A
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-64-generic-pae 
root=UUID=8e8ca8ab-ae5e-41bc-b008-7a15a613d9e0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-64-generic-pae N/A
   linux-backports-modules-3.2.0-64-generic-pae  N/A
   linux-firmware1.79.14
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0306
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: ET2012A
  dmi.board.vendor: ASUSTeK

[Kernel-packages] [Bug 1333229] Re: USB 3.0 regression after upgrading to 3.2.0-64 kernel

2014-06-24 Thread Maciej Puzio

I'm trying to find similarities between this bug and the bugs I reported. 
Speaking about the devices mentioned above, but only those that cause problems:
1. Is any a USB 3.0 device?
2. If you boot with any of the problematic devices plugged in, do you 
experience boot problems of any kind (stuck, long delay, dropped to boot 
console, etc.)?
3. Does any of the problematic devices work after you give it sufficient time 
(in my testing, most devices would work after being plugged in for 18 minutes). 
4. Do the error messages differ among problematic devices?
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/1333229

Title:
  USB 3.0 regression after upgrading to 3.2.0-64 kernel

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 3.2.0-64 kernel wireless mouse stopped working but 
keyboard still works
  Problem occurred with next Wireless Kit (keyboard+mouse):
  04f2:1123 Chicony Electronics Co., Ltd Asus Wireless Keyboard and Mouse
  04f2:0836 Chicony Electronics Co., Ltd Pleomax Wireless Keyboard and Mouse

  from dmesg:
  # dmesg |grep generic-usb
  [3.043949] generic-usb 0003:04F2:0963.0001: input,hidraw0: USB HID v1.11 
Keyboard [Chicony 2.4G Multimedia Wireless Kit] on usb-:00:12.0-3/input0
  [3.059228] generic-usb 0003:04F2:0963.0002: input,hiddev0,hidraw1: USB 
HID v1.11 Mouse [Chicony 2.4G Multimedia Wireless Kit] on 
usb-:00:12.0-3/input1
  [  635.024628] generic-usb 0003:04F2:0836.0003: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  655.024520] generic-usb: probe of 0003:04F2:0836.0004 failed with error 
-110
  [  680.024656] generic-usb: probe of 0003:04F2:0836.0005 failed with error 
-110
  [  686.324531] generic-usb 0003:04F2:0836.0006: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  706.324634] generic-usb: probe of 0003:04F2:0836.0007 failed with error 
-110
  [  731.328465] generic-usb: probe of 0003:04F2:0836.0008 failed with error 
-110
  [  732.155547] generic-usb 0003:04F2:0836.0009: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [  752.156459] generic-usb: probe of 0003:04F2:0836.000A failed with error 
-110
  [  777.156718] generic-usb: probe of 0003:04F2:0836.000B failed with error 
-110
  [ 1236.880527] generic-usb 0003:04F2:0836.000C: input,hidraw2: USB HID v1.11 
Keyboard [Chicony Samsung 2.4GHz Transceiver] on usb-:05:00.0-2/input0
  [ 1256.880712] generic-usb: probe of 0003:04F2:0836.000D failed with error 
-110
  [ 1281.880705] generic-usb: probe of 0003:04F2:0836.000E failed with error 
-110

  With 3.2.0-63 kernel all works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-64-generic-pae 3.2.0-64.97
  ProcVersionSignature: Ubuntu 3.2.0-64.97-generic-pae 3.2.59
  Uname: Linux 3.2.0-64-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: SB [HDA ATI SB], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 45'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'SB'/'HDA ATI SB at 0xfeb4 irq 16'
 Mixer name : 'Realtek ALC269VB'
 Components : 'HDA:10ec0269,104384ff,00100100'
 Controls  : 18
 Simple ctrls  : 10
  Date: Mon Jun 23 14:48:34 2014
  HibernationDevice: RESUME=UUID=f22f0450-8574-4bb3-9992-fde733b437eb
  MachineType: ASUSTeK Computer INC. ET2012A
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-64-generic-pae 
root=UUID=8e8ca8ab-ae5e-41bc-b008-7a15a613d9e0 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-64-generic-pae N/A
   linux-backports-modules-3.2.0-64-generic-pae  N/A

[Kernel-packages] [Bug 1330530] Re: [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller

2014-06-23 Thread Maciej Puzio

After testing this thoroughly, I am confident to say that the regression is 
caused by commit usb: xhci: Prefer endpoint context dequeue pointer over 
stopped_trb. In ubuntu-precise git repository this is commit 
f04e4b02bce3a0ce19f9673bbefde9b8c624c00a.
However, an equivalent commit is part of mainline kernel v3.16-rc1, where it 
does not cause problems. My guess is that this commit revealed a bug hidden 
somewhere else, in a code that was modified since kernel 3.2.

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

Title:
  [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3
  controller

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  With a Dell Vostro 430, the HighPoint RocketU 1144C USB 3.0 controller, Areca 
ARC-5040 USB 3.0 RAID enclosure connected to it, and the following conditions 
are met:
  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  An error loop during boot contains the following messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  I've attached a file generated by apport-cli -f -p linux --save
  filename.apport .

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

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

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

[Kernel-packages] [Bug 1330530] Re: [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller

2014-06-20 Thread Maciej Puzio

I bisected commits between Ubuntu-3.2.0-63.95 and Ubuntu-3.2.0-64.97,
and arrived at a specific xhci-related commit. However, manual
modification of the relevant file to revert the effects of this commit
yielded a kernel that still suffered from a regression. Further
complicating the matter is the fact that the the code in question is
modified by two commits.

Since I was not able to verify the result of bisection, I am not posting
it, to avoid confusion. Next week I will further debug the code, and
post here when I get conclusive results.

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

Title:
  [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3
  controller

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  With a Dell Vostro 430, the HighPoint RocketU 1144C USB 3.0 controller, Areca 
ARC-5040 USB 3.0 RAID enclosure connected to it, and the following conditions 
are met:
  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  An error loop during boot contains the following messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  I've attached a file generated by apport-cli -f -p linux --save
  filename.apport .

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

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

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

[Kernel-packages] [Bug 1328984] Re: [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card

2014-06-19 Thread Maciej Puzio

tl;dr: This bug report is a duplicate of bug 1330530.

I am going to focus my efforts on bug 1330530, and I do not intend to do
any work on this bug report until bug 1330530 is resolved. This is
because doing the same work twice is not a good use of time and effort
of anybody involved. Please do not change the status to incomplete, and
do not request same steps or actions as for bug 1330530. Instead, please
mark this bug as a duplicate of 1330530. This will focus everybody's
attention on the problem and minimize confusion. Thank you.

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

Title:
  [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with
  USB3 controller card

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64
  resulted in unbootable system on two machines. Further testing
  revealed that kernel fails while initializing HighPoint RocketU 1144C
  USB 3.0 controller. This is a PCIe x4 add-in card that contains four
  USB 3.0 ports, each equipped with its own controller. The card did and
  does work without any problems with kernel 3.2.0-63 and earlier. Prior
  to installing kernel 3.2.0-64 there were neither hardware nor software
  problems with either of the machines.

  Steps to reproduce:
  apt-get dist-upgrade
  sync
  reboot
  Result: system fails to boot.

  The workaround is to revert to kernel 3.2.0-63 or to remove the
  RocketU card.

  Hardware description (same on both machines):
  Dell PowerEdge R510
  PERC6/i RAID controller
  64GB RAM DDR3 ECC registered
  Dual CPU: Intel Xeon X5660 2.80GHz
  HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA

  Operating system (identical on both machines):
  Ubuntu 12.04.4 LTS
  Linux 3.2.0-64-generic x86_64

  Drives:
  sda - logical drive on PERC6/i, OS
  sdb - logical drive on PERC6/i, data
  sdc - Areca 5040 external RAID connected by USB3 to RocketU card
  sdd - Areca 5040 external RAID connected by USB3 to RocketU card
  sde - Areca 5040 external RAID connected by USB3 to RocketU card

  Symptoms:
  System boots normally until initialization of Areca drives connected to the 
RocketU card. The following messages are displayed on screen when booting 
without quiet and with debug options. These are last messages of a typical 
part of the boot sequence. Following it is a ~2 minute lag when no messages are 
displayed.

  [Please note that no trace of the boot progress gets recorded in
  system logs, and messages on screen scroll very fast. I had to record
  the boot progress with a high framerate camera, and even so some
  messages scrolled too fast and were not recorded. The following is a
  manual transcript of fragments of these videos; please forgive
  inevitable typos.]

  [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5  PQ: 0 ANSI: 5
  [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0
  [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
  [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 
TB/19.0 TiB)
  [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3  PQ: 0 ANSI: 5
  [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0
  [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
  [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 
TB/19.0 TiB)
  [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7  PQ: 0 ANSI: 5
  [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0
  [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16).
  [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 
TB/16.3 TiB)
  [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 
46874620k

  After a two minute delay, the following messages appear in an infinite
  loop.  Please note that these messages appear in a somewhat random
  sequence, and not all messages appear on every boot. The only thing
  that works at this point is Ctrl-Alt-Delete.

  udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774]
  udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776]
  udevd[529]: timeout: killing '/sbin/modprobe -bv 
input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642]
  udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655]
  udevd[508]: timeout: killing '/sbin/modprobe -bv 
pci:v80864342Esvsdbc00sc00i00' [512]
  udevd[494]: timeout: killing '/sbin/modprobe -bv 
input:b0019vp0001e-r0,1,k74,ramlsfw' [771]
  udevd[699]: timeout: killing '/sbin/modprobe -bv 
dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rm00HDP0:rvr002:cvnDellInc.:ct23:cvr:'
 [708]
  udevd[529]: timeout: killing

[Kernel-packages] [Bug 1330530] Re: [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller

2014-06-19 Thread Maciej Puzio

I have tested 28 mainline kernels from 9 branches currently maintained
(3.2, 3.4, 3.10, 3.11, 3.12, 3.13, 3.14, 3.15, 3.16), focusing on those
that were built around the time the problematic commit was introduced
(May-June 2014). The bug appears to affect the 3.2 branch exclusively.
Thus I will now try to forward bisect commits from 3.2.58 (last good) to
3.2.59 (first bad).

Just for reference, here are results of my testing. Bad means that bug was 
reproducible in the given kernel, good that it was not.
3.2.58 good
3.2.59 bad
3.2.60 bad
3.4.89 good
3.4.90 good
3.4.91 good
3.4.92 good
3.4.93 good
3.4.94 good
3.10.44 good
3.11.10.11 good
3.13.22 good
3.13.11 good
3.13.11.1 good
3.13.11.2 good
3.13.11.3 good
3.14.8 good
3.15-rc1 good
3.15-rc2 good
3.15-rc3 good
3.15-rc4 good
3.15-rc5 good
3.15-rc6 good
3.15-rc7 good
3.15-rc8 good
3.15 good
3.15.1 good
3.16-rc1 good

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

Title:
  [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3
  controller

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  With a Dell Vostro 430, the HighPoint RocketU 1144C USB 3.0 controller, Areca 
ARC-5040 USB 3.0 RAID enclosure connected to it, and the following conditions 
are met:
  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  An error loop during boot contains the following messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  I've attached a file generated by apport-cli -f -p linux --save
  filename.apport .

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

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

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

[Kernel-packages] [Bug 1328984] Re: [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card

2014-06-18 Thread Maciej Puzio

I have tested kernels 3.16.0-031600rc1-generic and 3.2.60-030260-generic. On 
the former, the problem does not appear, on the latter, the bug is replicated 
with similar symptoms as on 3.2.0-64. I used a flash drive with a vanilla 
Ubuntu 12.04 desktop install for all tests. To summarize kernels tested so far:
Good kernels: 3.2.0-63, 3.16.0-031600rc1
Bad kernels: 3.2.0-64, 3.2.60-030260

I also tested this issue on three additional machines, and the results
were the same. So I have now five different hardware configurations
(including one from bug 1330530) that are affected by this problem and
show very similar symptoms. In fact, I was not able to find a computer
that would not replicate this regression. If we also take into account
Bard Hemmer's hardware, we can reasonably conclude that the issue is not
related to motherboard/chipset/CPU/BIOS. It is however related to
HighPoint RocketU 1144C add-in adapter that I used in all my tests.

I would like to note that symptoms are similar on various hardware, but
not identical. The errors are generally similar (xhci, udev, modprobe),
but it appears that timing differences cause the issue to occur at
different parts of the boot process, depending on the hardware. So far I
have seen:

1. Dropping to initramfs shell in the middle of the boot (Gave up
waiting for root device. ... ALERT! [boot drive] does not exist!
Dropping to shell!)

2. An error loop preventing system to boot (as described in this
report). In this case I am not sure whether this is an infinite loop, or
if the system would boot after a long delay.

3. Boot is delayed by 18 minutes, during which time numerous errors are
thrown. After 18 minutes, OS boots fine.

4. System boots to text console, rather than the graphical login screen.
It is possible to log on to the console. Within seconds, xhci and/or
udev errors start appearing in the syslog. After two minutes, screen
goes blank, and the console seems unresponsive for another 16 minutes.
Following that, the graphical login screen appears, and from this point
system behaves fine.

5. As in 4, but after two minutes in the text console, incomplete
graphical login screen appears. Password box is missing and the
background is not fully loaded. After another 16 minutes, login screen
loads missing parts, and system behaves OK. In this case it is possible
to switch between text and graphical consoles during these 16 minutes,
but the graphical console becomes a purple empty screen after the
switch.

It is also worth noting that symptoms are highly dependent on the
external device(s) attached to RocketU's ports. Here is a summary:

1. No device connected to RocletU adapter - no problems during boot
2. USB3 flash drives (tested two models) - no problems during boot
3. Areca ARC-5040 enclosure - bug is triggered
4. WD MyPassport 2TB US 3.0 drive - bug is triggered
5. Transcend USB 3.0 SD card reader (TS-RDF5K) - bug is triggered with 
different symptoms: only a small delay (~15 seconds) and small number of xhci 
errors occur during boot, but the device does not work when OS is fully booted.

All the above devices work fine with good kernels. Note that I tested
three RocketU controllers and five Areca enclosures, to rule out the
possibility of a hardware problem on these devices.

With a variety of hardware reliably triggering the bug on bad kernels,
while working fine with good kernels, I think it is fully
substantiated to consider this regression as not hardware-dependent
(apart from the RocketU controller). I am changing tags as Christopher
requested in comment #13, but I would like to ask that this bug is
marked as duplicate of bug 1330530. That would allow me to debug the
issue on my test machines, which would be substantially easier than
doing it on production servers. I would prefer not to touch these
servers until the fix is released and verified on test computers.

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.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/1328984

Title:
  [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with
  USB3 controller card

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64
  resulted in unbootable system on two machines. Further testing
  revealed that kernel fails while initializing HighPoint RocketU 1144C
  USB 3.0 controller. This is a PCIe x4 add-in card that contains four
  USB 3.0 ports, each equipped with its own controller. The card did and
  does work without any problems with kernel 3.2.0-63 and earlier. Prior
  to installing kernel 3.2.0-64 there were neither hardware nor software
  problems with either of the machines.

  Steps to reproduce:
  apt-get dist-upgrade
  sync
  reboot
  Result: system fails to boot.

  The workaround is to revert to kernel 3.2.0-63 or to remove the
  RocketU card.

[Kernel-packages] [Bug 1328984] Re: [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card

2014-06-18 Thread Maciej Puzio

** Tags removed: kernel-fixed-upstream-3.16
** Tags added: kernel-fixed-upstream-3.16-rc1

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

Title:
  [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with
  USB3 controller card

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64
  resulted in unbootable system on two machines. Further testing
  revealed that kernel fails while initializing HighPoint RocketU 1144C
  USB 3.0 controller. This is a PCIe x4 add-in card that contains four
  USB 3.0 ports, each equipped with its own controller. The card did and
  does work without any problems with kernel 3.2.0-63 and earlier. Prior
  to installing kernel 3.2.0-64 there were neither hardware nor software
  problems with either of the machines.

  Steps to reproduce:
  apt-get dist-upgrade
  sync
  reboot
  Result: system fails to boot.

  The workaround is to revert to kernel 3.2.0-63 or to remove the
  RocketU card.

  Hardware description (same on both machines):
  Dell PowerEdge R510
  PERC6/i RAID controller
  64GB RAM DDR3 ECC registered
  Dual CPU: Intel Xeon X5660 2.80GHz
  HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA

  Operating system (identical on both machines):
  Ubuntu 12.04.4 LTS
  Linux 3.2.0-64-generic x86_64

  Drives:
  sda - logical drive on PERC6/i, OS
  sdb - logical drive on PERC6/i, data
  sdc - Areca 5040 external RAID connected by USB3 to RocketU card
  sdd - Areca 5040 external RAID connected by USB3 to RocketU card
  sde - Areca 5040 external RAID connected by USB3 to RocketU card

  Symptoms:
  System boots normally until initialization of Areca drives connected to the 
RocketU card. The following messages are displayed on screen when booting 
without quiet and with debug options. These are last messages of a typical 
part of the boot sequence. Following it is a ~2 minute lag when no messages are 
displayed.

  [Please note that no trace of the boot progress gets recorded in
  system logs, and messages on screen scroll very fast. I had to record
  the boot progress with a high framerate camera, and even so some
  messages scrolled too fast and were not recorded. The following is a
  manual transcript of fragments of these videos; please forgive
  inevitable typos.]

  [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5  PQ: 0 ANSI: 5
  [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0
  [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
  [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 
TB/19.0 TiB)
  [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3  PQ: 0 ANSI: 5
  [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0
  [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
  [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 
TB/19.0 TiB)
  [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7  PQ: 0 ANSI: 5
  [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0
  [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16).
  [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 
TB/16.3 TiB)
  [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 
46874620k

  After a two minute delay, the following messages appear in an infinite
  loop.  Please note that these messages appear in a somewhat random
  sequence, and not all messages appear on every boot. The only thing
  that works at this point is Ctrl-Alt-Delete.

  udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774]
  udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776]
  udevd[529]: timeout: killing '/sbin/modprobe -bv 
input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642]
  udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655]
  udevd[508]: timeout: killing '/sbin/modprobe -bv 
pci:v80864342Esvsdbc00sc00i00' [512]
  udevd[494]: timeout: killing '/sbin/modprobe -bv 
input:b0019vp0001e-r0,1,k74,ramlsfw' [771]
  udevd[699]: timeout: killing '/sbin/modprobe -bv 
dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rm00HDP0:rvr002:cvnDellInc.:ct23:cvr:'
 [708]
  udevd[529]: timeout: killing '/sbin/modprobe -bv 
input:b0003v0557p2261e0110-e0,1,2,3,4,k71,72,73,74,77,80,82,83,85,86,87,88,89,8A,8B,8C,8E,8F,90,96,98,9B,9C,9E,9F,A1,A3,A4,A5,A6,A7,A8,A9,AB,AC,AD,AE,B1,B2,B5,CE,CF,D0,D1,D2,D4,D8,D9,DB,E4,EA,EB,F1,100,161,162,166,16A,16E,172,174,176,178,179,17A,17B,17C,17D,17F,180,182,182,185,188,189,18C,18D,18E,18F,190,191,192,193,195,198,199,19A,1A9,1A1,1A2,1A3,1A4,1A5,1A6,1A7,1A8,1A9,1AA,1AB,1AC,1AD,1AE,1B0,1B1,1B7,1BA,r6,a20,m4,lsfw'
 [1678]

  After pressing Ctrl-Alt-Delete, the above messages continue to

[Kernel-packages] [Bug 1328984] Re: [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card

2014-06-18 Thread Maciej Puzio

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

Title:
  [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with
  USB3 controller card

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  A routine system update of Ubuntu 12.04 LTS to kernel 3.2.0-64
  resulted in unbootable system on two machines. Further testing
  revealed that kernel fails while initializing HighPoint RocketU 1144C
  USB 3.0 controller. This is a PCIe x4 add-in card that contains four
  USB 3.0 ports, each equipped with its own controller. The card did and
  does work without any problems with kernel 3.2.0-63 and earlier. Prior
  to installing kernel 3.2.0-64 there were neither hardware nor software
  problems with either of the machines.

  Steps to reproduce:
  apt-get dist-upgrade
  sync
  reboot
  Result: system fails to boot.

  The workaround is to revert to kernel 3.2.0-63 or to remove the
  RocketU card.

  Hardware description (same on both machines):
  Dell PowerEdge R510
  PERC6/i RAID controller
  64GB RAM DDR3 ECC registered
  Dual CPU: Intel Xeon X5660 2.80GHz
  HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA

  Operating system (identical on both machines):
  Ubuntu 12.04.4 LTS
  Linux 3.2.0-64-generic x86_64

  Drives:
  sda - logical drive on PERC6/i, OS
  sdb - logical drive on PERC6/i, data
  sdc - Areca 5040 external RAID connected by USB3 to RocketU card
  sdd - Areca 5040 external RAID connected by USB3 to RocketU card
  sde - Areca 5040 external RAID connected by USB3 to RocketU card

  Symptoms:
  System boots normally until initialization of Areca drives connected to the 
RocketU card. The following messages are displayed on screen when booting 
without quiet and with debug options. These are last messages of a typical 
part of the boot sequence. Following it is a ~2 minute lag when no messages are 
displayed.

  [Please note that no trace of the boot progress gets recorded in
  system logs, and messages on screen scroll very fast. I had to record
  the boot progress with a high framerate camera, and even so some
  messages scrolled too fast and were not recorded. The following is a
  manual transcript of fragments of these videos; please forgive
  inevitable typos.]

  [5.621523] scsi 5:0:0:0: Direct-Access Areca Areca5  PQ: 0 ANSI: 5
  [5.622896] sd 5:0:0:0: Attached scsi generic sg4 type 0
  [5.623230] sd 5:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
  [5.623668] sd 5:0:0:0: [sdc] 41015622144 512-byte logical blocks: (20.9 
TB/19.0 TiB)
  [5.741152] scsi 6:0:0:0: Direct-Access Areca Areca3  PQ: 0 ANSI: 5
  [5.744003] sd 6:0:0:0: Attached scsi generic sg5 type 0
  [5.744545] sd 6:0:0:0: [sdd] Very big device. Trying to use READ CAPACITY(16).
  [5.744980] sd 6:0:0:0: [sdd] 41015622144 512-byte logical blocks: (20.9 
TB/19.0 TiB)
  [6.004526] scsi76:0:0:0: Direct-Access Areca Areca7  PQ: 0 ANSI: 5
  [6.006121] sd 7:0:0:0: Attached scsi generic sg6 type 0
  [6.006488] sd 7:0:0:0: [sde] Very big device. Trying to use READ CAPACITY(16).
  [6.006834] sd 7:0:0:0: [sde] 35156217552 512-byte logical blocks: (17.9 
TB/16.3 TiB)
  [7.133091] Adding 46874620k swap on /dev/sda3. Priority: -1 extents:1 across 
46874620k

  After a two minute delay, the following messages appear in an infinite
  loop.  Please note that these messages appear in a somewhat random
  sequence, and not all messages appear on every boot. The only thing
  that works at this point is Ctrl-Alt-Delete.

  udevd[632]: timeout: killing '/sbin/modprobe -bv acpi:ACPI000D:PMP0C01:' [774]
  udevd[703]: timeout: killing '/sbin/modprobe -bv acpi:PMP0C014:' [776]
  udevd[529]: timeout: killing '/sbin/modprobe -bv 
input:b0003v0557p2261e0110-e0,1,2,3,4,k110,111,112,r8,a0,1,m4,lsfw' [1642]
  udevd[630]: timeout: killing '/sbin/modprobe -bv serio:ty06pr00id00ex00' [655]
  udevd[508]: timeout: killing '/sbin/modprobe -bv 
pci:v80864342Esvsdbc00sc00i00' [512]
  udevd[494]: timeout: killing '/sbin/modprobe -bv 
input:b0019vp0001e-r0,1,k74,ramlsfw' [771]
  udevd[699]: timeout: killing '/sbin/modprobe -bv 
dmi:bvnDellInc.:bvr1.12.0:bd07/26/2013:svnDellInc.:pnPowerEdgeR510:pvr:rvnDellInc.:rm00HDP0:rvr002:cvnDellInc.:ct23:cvr:'
 [708]
  udevd[529]: timeout: killing '/sbin/modprobe -bv 
input:b0003v0557p2261e0110-e0,1,2,3,4,k71,72,73,74,77,80,82,83,85,86,87,88,89,8A,8B,8C,8E,8F,90,96,98,9B,9C,9E,9F,A1,A3,A4,A5,A6,A7,A8,A9,AB,AC,AD,AE,B1,B2,B5,CE,CF,D0,D1,D2,D4,D8,D9,DB,E4,EA,EB,F1,100,161,162,166,16A,16E,172,174,176,178,179,17A,17B,17C,17D,17F,180,182,182,185,188,189,18C,18D,18E,18F,190,191,192,193,195,198,199,19A,1A9,1A1,1A2,1A3,1A4,1A5,1A6,1A7,1A8,1A9,1AA,1AB,1AC,1AD,1AE,1B0,1B1,1B7,1BA,r6,a20,m4,lsfw'
 [1678]

  After pressing Ctrl-Alt-Delete, the above messages continue to appear
  for a few

[Kernel-packages] [Bug 1330530] Re: [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller

2014-06-17 Thread Maciej Puzio

I have tested the mainline kernel 3.2.60, and was able to reproduce the 
problem, with exactly the same symptoms as with kernel 3.2.0-64 (3.2.59).
Kernel URL: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.60-precise/

I also tested Western Digital My Passport 2TB USB 3.0 drive (Part#
WDBY8L0020BBL). This drive is causing the same problems as Areca
ARC-5040 (with kernels 3.2.0-64 and 3.2.60). No problems with kernel
3.16.0-031600rc1. Thus I have two USB3 devices that trigger the bug. As
of now, the only constant element required for the bug to appear is
HighPoint RocketU 1144C USB3 controller.

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

Title:
  [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3
  controller

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  With a Dell Vostro 430, the HighPoint RocketU 1144C USB 3.0 controller, Areca 
ARC-5040 USB 3.0 RAID enclosure connected to it, and the following conditions 
are met:
  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  An error loop during boot contains the following messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  I've attached a file generated by apport-cli -f -p linux --save
  filename.apport .

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

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

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

[Kernel-packages] [Bug 1330530] [NEW] Regression: Kernel 3.2.0-64 problems with USB3 controller

Public bug reported:

This bug report is a follow-up to bug 1328984, describing a successful
attempt to replicate that bug on another hardware. As advised, I am
opening a new bug to avoid mixing information related to two hardware
configurations.

Conditions triggering this bug:
As the original bug (1328984) was encountered on machines that are production 
servers, I attempted to replicate in on another machine that could be entirely 
devoted to testing this issue. I equipped this computer with the same USB3 
hardware as the servers, that is the HighPoint RocketU 1144C USB 3.0 controller 
and Areca ARC-5040 USB 3.0 RAID enclosure connected to it. I was able to 
replicate the problem with ease, provided that all three following conditions 
were met:

1. System booted kernel 3.2.0-64,
2. HighPoint RocketU 1144C controller was installed,
3. Areca ARC-5040 was connected to that controller.

The problem did not appear if I booted an older kernel (e.g. 3.2.0-63),
or if Areca enclosure was not attached, or if it was attached using
another interface (USB2 or eSATA). The problem was also absent if I
replaced the Areca enclosure with another USB3 device (a flash drive).
The test machine's motherboard did not have a built-in USB3 controller,
but I performed an additional test on yet another computer, equipped
with a NEC USB3 controller. That test was done with kernel 3.2.0-64 and
the Areca enclosure, and did not replicate the problem. Thus I assume
that it is the combination of the RocketU controller and a specific USB3
device that triggers kernel regression. In the original bug report
(1328984) Bard Hemmer reported that he encountered a similar trouble
with  Western Digital My Passport 2TB USB 3.0 external drive. I happen
to own this exact model, and I intend to test it as soon as possible.

Symptoms:
The symptoms on the test machine are somewhat different than those occurring on 
the production servers. The error loop during boot contains the following 
messages:
[   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
[   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
[   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

Similar effects happen if Areca enclosure is hot-plugged to the working
system. In such a case OS boots fine (as the enclosure is absent during
boot). After plugging the Areca, the drive is unavailable for 18
minutes, during which time numerous errors as above are logged. After 18
minutes elapse, drive is mounted and behaves normally.

Hardware:
Dell Vostro 430
CPU: Intel Core i7-860
RAM: 16GB DDR3 unbuffered non-ECC
Add-on card: HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA

Software:
Ubuntu 3.2.0-64.97-generic 3.2.59 x86_64

Note about apport collection:
Due to problems described in bug 1328984, relevant to this setup as well, I am 
unable to run apport tools to submit system information. For this reason, I am 
attaching a file generated by apport-cli -f -p linux --save filename.apport

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

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

Title:
  Regression: Kernel 3.2.0-64 problems with USB3 controller

Status in “linux” package in Ubuntu:
  New

Bug description:
  This bug report is a follow-up to bug 1328984, describing a successful
  attempt to replicate that bug on another hardware. As advised, I am
  opening a new bug to avoid mixing information related to two hardware
  configurations.

  Conditions triggering this bug:
  As the original bug (1328984) was encountered on machines that are production 
servers, I attempted to replicate in on another machine that could be entirely 
devoted to testing this issue. I equipped this computer with the same USB3 
hardware as the servers, that is the HighPoint RocketU 1144C USB 3.0 controller 
and Areca ARC-5040 USB 3.0 RAID enclosure connected to it. I was able to 
replicate the problem with ease, provided that all three following conditions 
were met:

  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3

[Kernel-packages] [Bug 1330530] Re: Regression: Kernel 3.2.0-64 problems with USB3 controller

** Attachment added: Result of apport-cli

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330530/+attachment/4132664/+files/bug1330530.apport

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

Title:
Regression: Kernel 3.2.0-64 problems with USB3 controller

Status in “linux” package in Ubuntu:
Incomplete

Bug description:
This bug report is a follow-up to bug 1328984, describing a successful
attempt to replicate that bug on another hardware. As advised, I am
opening a new bug to avoid mixing information related to two hardware
configurations.

Conditions triggering this bug:
As the original bug (1328984) was encountered on machines that are production
servers, I attempted to replicate in on another machine that could be entirely
devoted to testing this issue. I equipped this computer with the same USB3
hardware as the servers, that is the HighPoint RocketU 1144C USB 3.0 controller
and Areca ARC-5040 USB 3.0 RAID enclosure connected to it. I was able to
replicate the problem with ease, provided that all three following conditions
were met:

1. System booted kernel 3.2.0-64,
2. HighPoint RocketU 1144C controller was installed,
3. Areca ARC-5040 was connected to that controller.

The problem did not appear if I booted an older kernel (e.g.
3.2.0-63), or if Areca enclosure was not attached, or if it was
attached using another interface (USB2 or eSATA). The problem was also
absent if I replaced the Areca enclosure with another USB3 device (a
flash drive). The test machine's motherboard did not have a built-in
USB3 controller, but I performed an additional test on yet another
computer, equipped with a NEC USB3 controller. That test was done with
kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
problem. Thus I assume that it is the combination of the RocketU
controller and a specific USB3 device that triggers kernel regression.
In the original bug report (1328984) Bard Hemmer reported that he
encountered a similar trouble with Western Digital My Passport 2TB
USB 3.0 external drive. I happen to own this exact model, and I intend
to test it as soon as possible.

Symptoms:
The symptoms on the test machine are somewhat different than those occurring
on the production servers. The error loop during boot contains the following
messages:
[ 34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
[ 34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with
disabled ep 88042102e000
[ 34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with
disabled ep 88042102e040
This continues for about 18 minutes, after which the filesystem on the Areca
drive is mounted, and boot process continues successfully, as if nothing had
happened. Afterwards the affected drive works seemingly fine, although I
experienced some system instability, causing a total system freeze. At this
point I am not sure if this instability is related to the problem at hand.

Similar effects happen if Areca enclosure is hot-plugged to the
working system. In such a case OS boots fine (as the enclosure is
absent during boot). After plugging the Areca, the drive is
unavailable for 18 minutes, during which time numerous errors as above
are logged. After 18 minutes elapse, drive is mounted and behaves
normally.

Hardware:
Dell Vostro 430
CPU: Intel Core i7-860
RAM: 16GB DDR3 unbuffered non-ECC
Add-on card: HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA

Software:
Ubuntu 3.2.0-64.97-generic 3.2.59 x86_64

Note about apport collection:
Due to problems described in bug 1328984, relevant to this setup as well, I
am unable to run apport tools to submit system information. For this reason, I
am attaching a file generated by apport-cli -f -p linux --save filename.apport

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

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

[Kernel-packages] [Bug 1330530] Re: Regression: Kernel 3.2.0-64 problems with USB3 controller

A few notes regarding the contents of the apport file submitted above:
1. Times logged in syslog are incorrect and do not reflect the 18-minute delay. 
It appears that rsyslog is started after the delay and logs its startup time, 
not the real time of events.
2. Nouveau segfaults are not related to this bug report, and were occurring in 
older kernels as well.

As this bug has been replicated on various hardware, affects more than
one user, and requested system information has been provided, I am
changing status to 'confirmed'. When the nature of this problem is
better understood, this bug may possibly be marked as a duplicate of bug
1328984.

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

Title:
  Regression: Kernel 3.2.0-64 problems with USB3 controller

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  This bug report is a follow-up to bug 1328984, describing a successful
  attempt to replicate that bug on another hardware. As advised, I am
  opening a new bug to avoid mixing information related to two hardware
  configurations.

  Conditions triggering this bug:
  As the original bug (1328984) was encountered on machines that are production 
servers, I attempted to replicate in on another machine that could be entirely 
devoted to testing this issue. I equipped this computer with the same USB3 
hardware as the servers, that is the HighPoint RocketU 1144C USB 3.0 controller 
and Areca ARC-5040 USB 3.0 RAID enclosure connected to it. I was able to 
replicate the problem with ease, provided that all three following conditions 
were met:

  1. System booted kernel 3.2.0-64,
  2. HighPoint RocketU 1144C controller was installed,
  3. Areca ARC-5040 was connected to that controller.

  The problem did not appear if I booted an older kernel (e.g.
  3.2.0-63), or if Areca enclosure was not attached, or if it was
  attached using another interface (USB2 or eSATA). The problem was also
  absent if I replaced the Areca enclosure with another USB3 device (a
  flash drive). The test machine's motherboard did not have a built-in
  USB3 controller, but I performed an additional test on yet another
  computer, equipped with a NEC USB3 controller. That test was done with
  kernel 3.2.0-64 and the Areca enclosure, and did not replicate the
  problem. Thus I assume that it is the combination of the RocketU
  controller and a specific USB3 device that triggers kernel regression.
  In the original bug report (1328984) Bard Hemmer reported that he
  encountered a similar trouble with  Western Digital My Passport 2TB
  USB 3.0 external drive. I happen to own this exact model, and I intend
  to test it as soon as possible.

  Symptoms:
  The symptoms on the test machine are somewhat different than those occurring 
on the production servers. The error loop during boot contains the following 
messages:
  [   34.084469] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
  [   34.101825] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e000
  [   34.101918] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with 
disabled ep 88042102e040
  This continues for about 18 minutes, after which the filesystem on the Areca 
drive is mounted, and boot process continues successfully, as if nothing had 
happened. Afterwards the affected drive works seemingly fine, although I 
experienced some system instability, causing a total system freeze. At this 
point I am not sure if this instability is related to the problem at hand.

  Similar effects happen if Areca enclosure is hot-plugged to the
  working system. In such a case OS boots fine (as the enclosure is
  absent during boot). After plugging the Areca, the drive is
  unavailable for 18 minutes, during which time numerous errors as above
  are logged. After 18 minutes elapse, drive is mounted and behaves
  normally.

  Hardware:
  Dell Vostro 430
  CPU: Intel Core i7-860
  RAM: 16GB DDR3 unbuffered non-ECC
  Add-on card: HighPoint RocketU 1144C 4-Port USB 3.0 PCIe 2.0 x4 HBA

  Software:
  Ubuntu 3.2.0-64.97-generic 3.2.59 x86_64

  Note about apport collection:
  Due to problems described in bug 1328984, relevant to this setup as well, I 
am unable to run apport tools to submit system information. For this reason, I 
am attaching a file generated by apport-cli -f -p linux --save filename.apport

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

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

[Kernel-packages] [Bug 1328984] Re: [Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails to boot with USB3 controller card