[Kernel-packages] [Bug 2036428] Re: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1

2023-09-20 Thread Alistair Cunningham
Thank you Daniel, I've opened bug #2036719 for this.

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

Title:
  Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1

Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  After upgrading linux-firmware to 20230915.gitdfa11466-0ubuntu1, my
  Intel AX201 Bluetooth controller is not available post-reboot.

  The device itself shows up here:

  $ lsusb | grep -i blue
  Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth

  But running e.g. `dmesg | grep -i bluetooth` returns no matches, and
  bluetoothctl finds no controllers.

  Reverting to the 20230323.gitbcdcfbcf-0ubuntu1.6 package restores full
  functionality.

  n.b. Possible duplicate of LP:2036348 - I am not in a position to
  confirm those symptoms yet, but will update later.

  Running mantic pre-release on amd64:

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

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


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


[Kernel-packages] [Bug 2036428] Re: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1

2023-09-20 Thread Alistair Cunningham
After upgrading to 20230919.git3672ccab-0ubuntu1, Bluetooth now works on
my laptop. However, my Sony WH-1000XM5 headphones are not working 100%.

Initially, they connected in mono mode only, and audio was completely
corrupt. I unpaired them and re-paired them.

Now they give good audio quality, but the first second or so of audio is
cut off when starting playing. The audio test in the Ubuntu sound
settings plays "t left" rather than "front left". If I then click on
right, it says "front right" correctly. If I close the audio test and
open it again, the same problem happens again. This didn't happen on
Ubuntu 23.04. Should I open another bug report for this?

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

Title:
  Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1

Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  After upgrading linux-firmware to 20230915.gitdfa11466-0ubuntu1, my
  Intel AX201 Bluetooth controller is not available post-reboot.

  The device itself shows up here:

  $ lsusb | grep -i blue
  Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth

  But running e.g. `dmesg | grep -i bluetooth` returns no matches, and
  bluetoothctl finds no controllers.

  Reverting to the 20230323.gitbcdcfbcf-0ubuntu1.6 package restores full
  functionality.

  n.b. Possible duplicate of LP:2036348 - I am not in a position to
  confirm those symptoms yet, but will update later.

  Running mantic pre-release on amd64:

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

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


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


[Kernel-packages] [Bug 2036580] [NEW] Bluetooth won't turn on after upgrade to 23.10

2023-09-19 Thread Alistair Cunningham
Public bug reported:

After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
click on the Unity gear wheel icon, then click on System Settings, then
on Bluetooth. The "Bluetooth" toggle is set to off, and the box on the
left says "Bluetooth is disabled". Clicking the toggle turns the toggle
on, but nothing else changes. The box on the left still says that
Bluetooth is disabled, and no Bluetooth icon shows on the menu bar
despite "Show Bluetooth status in the menu bar" being enabled.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: bluetooth 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 19 11:20:23 2023
InstallationDate: Installed on 2020-07-14 (1162 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
dmi.bios.date: 08/30/2022
dmi.bios.release: 1.28
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET38W (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:55 acl:0 sco:0 events:4 errors:0
TX bytes:15 acl:0 sco:0 commands:4 errors:0

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


** Tags: amd64 apport-bug mantic

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

Title:
  Bluetooth won't turn on after upgrade to 23.10

Status in bluez package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 23.04 to 23.10, Bluetooth won't turn on. I
  click on the Unity gear wheel icon, then click on System Settings,
  then on Bluetooth. The "Bluetooth" toggle is set to off, and the box
  on the left says "Bluetooth is disabled". Clicking the toggle turns
  the toggle on, but nothing else changes. The box on the left still
  says that Bluetooth is disabled, and no Bluetooth icon shows on the
  menu bar despite "Show Bluetooth status in the menu bar" being
  enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: bluetooth 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Sep 19 11:20:23 2023
  InstallationDate: Installed on 2020-07-14 (1162 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro loglevel=4 splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to mantic on 2023-09-16 (3 days ago)
  dmi.bios.date: 08/30/2022
  dmi.bios.release: 1.28
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET38W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET38W(1.28):bd08/30/2022:br1.28:efr1.15:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:

[Kernel-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-12-09 Thread Alistair Cunningham
Unfortunately it's not fixed. It doesn't happen every time, but perhaps
half the time. I haven't been able to determine any pattern.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Kernel-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-12-09 Thread Alistair Cunningham
Unfortunately it's not fixed. It doesn't happen every time, but perhaps
half the time. I haven't been able to determine any pattern.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Kernel-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-12-04 Thread Alistair Cunningham
This *appears* to be fixed in the latest Ubuntu 20.10 updates.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Kernel-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-12-04 Thread Alistair Cunningham
This *appears* to be fixed in the latest Ubuntu 20.10 updates.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Kernel-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list

2020-10-12 Thread Alistair Cunningham
This is still happening after upgrading to Ubuntu 20.10.

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

Title:
  Sony WH-1000XM3 headphones connect but don't appear in the audio
  devices list

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Kernel-packages] [Bug 1893655] [NEW] Headphones connect but don't appear as audio output

2020-08-31 Thread Alistair Cunningham
Public bug reported:

When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
laptop at Bluetooth level, but don't appear as an audio device. I have
to remove them in the Ubuntu Bluetooth settings, and then re-pair them,
every time. This is rather inconvenient. This started happening after
upgrading to Ubuntu 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
Uname: Linux 5.6.0-1021-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Unity:Unity7:ubuntu
Date: Mon Aug 31 14:48:53 2020
InstallationDate: Installed on 2020-07-14 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20U9CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET19W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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


** Tags: amd64 apport-bug focal

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

Title:
  Headphones connect but don't appear as audio output

Status in bluez package in Ubuntu:
  New

Bug description:
  When I switch on my Sony WH-1000XM3 headphones, they reconnect to my
  laptop at Bluetooth level, but don't appear as an audio device. I have
  to remove them in the Ubuntu Bluetooth settings, and then re-pair
  them, every time. This is rather inconvenient. This started happening
  after upgrading to Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19
  Uname: Linux 5.6.0-1021-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Aug 31 14:48:53 2020
  InstallationDate: Installed on 2020-07-14 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20U9CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem 
root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET19W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:AC:65:6D:04:AB  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1274806 acl:246 sco:0 events:180845 errors:0
TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0

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

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


[Kernel-packages] [Bug 1877829] [NEW] Won't reconnect to shared headphones

2020-05-10 Thread Alistair Cunningham
Public bug reported:

In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both my
laptop running Ubuntu, and my Android smartphone. The headphones would
pair with both, and I could simply re-enable the connection in Ubuntu or
Android to connect to the headphones if the other device had been using
the headphones last.

In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if my
Android phone was using the headphones last. I have to manually unpair
the headphones and re-pair them again. This is very inconvenient.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun May 10 15:44:22 2020
InstallationDate: Installed on 2017-08-16 (997 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HFCTO1WW
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET57W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET57W(1.36):bd11/29/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:20456 acl:96 sco:0 events:2692 errors:0
TX bytes:604938 acl:84 sco:0 commands:2573 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T23:41:27.085337

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


** Tags: amd64 apport-bug focal

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

Title:
  Won't reconnect to shared headphones

Status in bluez package in Ubuntu:
  New

Bug description:
  In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both
  my laptop running Ubuntu, and my Android smartphone. The headphones
  would pair with both, and I could simply re-enable the connection in
  Ubuntu or Android to connect to the headphones if the other device had
  been using the headphones last.

  In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if
  my Android phone was using the headphones last. I have to manually
  unpair the headphones and re-pair them again. This is very
  inconvenient.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 10 15:44:22 2020
  InstallationDate: Installed on 2017-08-16 (997 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HFCTO1WW
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET57W (1.36 )

[Kernel-packages] [Bug 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected

2019-12-31 Thread Alistair Cunningham
I can confirm that installing these packages onto Ubuntu 19.10 fixes the
problem for my Sony WH-1000XM3. Thank you very much Daniel!

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

Title:
  Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low
  quality headset mode and fails to switch to A2DP when selected

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

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

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


[Kernel-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected

2019-12-10 Thread Alistair Cunningham
Is anything happening with solving this?

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

Title:
  Bluetooth headphones/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

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

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


[Kernel-packages] [Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect

2019-11-28 Thread Alistair Cunningham
** Attachment added: "headphones"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+attachment/5308568/+files/headphones

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

Title:
   Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  *** This bug is the same as bug 1724919, but is NOT A DUPLICATE
  because that bug was closed because it was reported for Ubuntu 17.10,
  which is out of support. This bug is for newer versions, such as
  19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. ***

  On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov 28 13:28:52 2019
  InstallationDate: Installed on 2017-08-16 (833 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0
TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337

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

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


[Kernel-packages] [Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect

2019-11-28 Thread Alistair Cunningham
The only other Bluetooth headphones I've had access to recently were a
pair of Bose QC35 (1st generation). They showed up in the list of
visible BT devices, but my laptop couldn't connect to them at all,
despite numerous attempts. As a result, I bought the Sonys and got rid
of the Bose.

If you take a look at bug 1724919, you'll see that other people have the
same problem with other models of headphones.

Attached is a copy of /var/log/syslog since last boot, with minor
cleaning. Note that just after booting I wanted to use the headphones
for real, so I manually ran the attached 'headphones' script to
disconnect the headphones, reconnect them, and force A2DP mode. Then at
18:09:17, I deliberately recreated the bug by connecting the headphones,
and unsuccessfully trying to set A2DP in the sound settings.

** Attachment added: "syslog_cleaned.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+attachment/5308567/+files/syslog_cleaned.txt

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

Title:
   Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  *** This bug is the same as bug 1724919, but is NOT A DUPLICATE
  because that bug was closed because it was reported for Ubuntu 17.10,
  which is out of support. This bug is for newer versions, such as
  19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. ***

  On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov 28 13:28:52 2019
  InstallationDate: Installed on 2017-08-16 (833 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0
TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337

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

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


[Kernel-packages] [Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect

2019-11-28 Thread Alistair Cunningham
How do I run blueman after installing it?

$ blueman

Command 'blueman' not found, did you mean:

  command 'bluemon' from deb bluemon (1.4-7)

Try: sudo apt install 

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

Title:
   Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  *** This bug is the same as bug 1724919, but is NOT A DUPLICATE
  because that bug was closed because it was reported for Ubuntu 17.10,
  which is out of support. This bug is for newer versions, such as
  19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. ***

  On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov 28 13:28:52 2019
  InstallationDate: Installed on 2017-08-16 (833 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago)
  dmi.bios.date: 08/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET56W (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0
TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337

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

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


[Kernel-packages] [Bug 1854392] [NEW] Bluetooth headphones won't use A2DP on reconnect

2019-11-28 Thread Alistair Cunningham
Public bug reported:

*** This bug is the same as bug 1724919, but is NOT A DUPLICATE because
that bug was closed because it was reported for Ubuntu 17.10, which is
out of support. This bug is for newer versions, such as 19.10. PLEASE DO
NOT MARK THIS BUG AS A DUPLICATE. ***

On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair
using Bluetooth with no problems, and use A2DP by default. If I then
power off the headphones and power them back on, they reconnect but use
HSP/HFP and sound terrible. If I manually go into the sound settings,
A2DP is offered as an option, but selecting it doesn't take effect. The
headphones remain stuck in HSP/HFP mode.

Unpairing the headphones and re-pairing them again selects A2DP by
default, until the next time I switch the headphones off. Then they're
back to stuck in HSP/HFP until I unpair them once again. I therefore
need to unpair and re-pair them every time I want to use them, which is
a nuisance.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluez 5.50-0ubuntu4
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Nov 28 13:28:52 2019
InstallationDate: Installed on 2017-08-16 (833 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HFCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago)
dmi.bios.date: 08/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET56W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0
TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337

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


** Tags: amd64 apport-bug eoan

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

Title:
   Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  New

Bug description:
  *** This bug is the same as bug 1724919, but is NOT A DUPLICATE
  because that bug was closed because it was reported for Ubuntu 17.10,
  which is out of support. This bug is for newer versions, such as
  19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. ***

  On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov 28 13:28:52 2019
  InstallationDate: Installed on 2017-08-16 (833 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  

[Kernel-packages] [Bug 1850051] [NEW] Bluetooth headphones won't use A2DP on reconnect

2019-10-27 Thread Alistair Cunningham
Public bug reported:

On Ubuntu 19.04 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair
using Bluetooth with no problems, and use A2DP by default. If I then
power off the headphones and power them back on, they reconnect but use
HSP/HFP and sound terrible. If I manually go into the sound settings,
A2DP is offered as an option, but selecting it doesn't take effect. The
headphones remain stuck in HSP/HFP mode.

Unpairing the headphones and re-pairing them again selects A2DP by
default, until the next time I switch the headphones off. Then they're
back to stuck in HSP/HFP until I unpair them once again. I therefore
need to unpair and re-pair them every time I want to use them, which is
a nuisance.

I'm not sure which package is responsible for handling this, so am
reporting to for bluez since it provides /etc/bluetooth/main.conf. If
I'm wrong, please re-assign.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Oct 27 10:43:21 2019
InstallationDate: Installed on 2017-08-16 (801 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
 Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HFCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to eoan on 2019-10-04 (22 days ago)
dmi.bios.date: 08/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET56W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:59:71:8D:1A:16  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:730576 acl:159 sco:13734 events:3688 errors:0
TX bytes:2014957 acl:979 sco:13705 commands:2568 errors:0

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


** Tags: amd64 apport-bug eoan

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

Title:
  Bluetooth headphones won't use A2DP on reconnect

Status in bluez package in Ubuntu:
  New

Bug description:
  On Ubuntu 19.04 on my Thinkpad T470s, my Sony WH-1000XM3 headphones
  pair using Bluetooth with no problems, and use A2DP by default. If I
  then power off the headphones and power them back on, they reconnect
  but use HSP/HFP and sound terrible. If I manually go into the sound
  settings, A2DP is offered as an option, but selecting it doesn't take
  effect. The headphones remain stuck in HSP/HFP mode.

  Unpairing the headphones and re-pairing them again selects A2DP by
  default, until the next time I switch the headphones off. Then they're
  back to stuck in HSP/HFP until I unpair them once again. I therefore
  need to unpair and re-pair them every time I want to use them, which
  is a nuisance.

  I'm not sure which package is responsible for handling this, so am
  reporting to for bluez since it provides /etc/bluetooth/main.conf. If
  I'm wrong, please re-assign.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Oct 27 10:43:21 2019
  InstallationDate: Installed on 2017-08-16 (801 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
   Bus 001 Device 004: ID 8087:0a2b 

[Kernel-packages] [Bug 1849724] [NEW] Thinkpad T470s failure to suspend

2019-10-24 Thread Alistair Cunningham
Public bug reported:

Since upgrading to Ubuntu 19.10, my Thinkpad T470s sometimes refuses to
suspend.  This *appears* to happen if I've previously suspended it since
the last full reboot, though it's hard to be sure that this is always
the case. When it fails to suspend, the following is logged to kern.log:

Oct 24 12:09:42 localhost kernel: [15809.059931] Filesystems sync: 0.010 seconds
Oct 24 12:09:42 localhost kernel: [15809.060368] Freezing user space processes 
... (elapsed 0.004 seconds) done.
Oct 24 12:09:42 localhost kernel: [15809.065301] OOM killer disabled.
Oct 24 12:09:42 localhost kernel: [15809.065302] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
Oct 24 12:09:42 localhost kernel: [15809.066938] printk: Suspending console(s) 
(use no_console_suspend to debug)
Oct 24 12:09:42 localhost kernel: [15809.947126] e1000e: EEE TX LPI TIMER: 
0011
Oct 24 12:09:42 localhost kernel: [15809.954275] PM: pci_pm_suspend(): 
e1000e_pm_suspend+0x0/0x60 [e1000e] returns -2
Oct 24 12:09:42 localhost kernel: [15809.954277] PM: dpm_run_callback(): 
pci_pm_suspend+0x0/0x150 returns -2
Oct 24 12:09:42 localhost kernel: [15809.954278] PM: Device :00:1f.6 failed 
to suspend async: error -2
Oct 24 12:09:42 localhost kernel: [15809.989504] PM: Some devices failed to 
suspend, or early wake event detected
Oct 24 12:09:42 localhost kernel: [15810.747730] psmouse serio1: synaptics: 
queried max coordinates: x [..5676], y [..4762]
Oct 24 12:09:42 localhost kernel: [15810.782411] psmouse serio1: synaptics: 
queried min coordinates: x [1266..], y [1094..]
Oct 24 12:09:42 localhost kernel: [15810.893760] OOM killer enabled.
Oct 24 12:09:42 localhost kernel: [15810.893761] Restarting tasks ... 
Oct 24 12:09:42 localhost kernel: [15810.899483] mei_hdcp 
mei::b638ab7e-94e2-4ea2-a552-d1c54b627f04:01: bound :00:02.0 (ops
 i915_hdcp_component_ops [i915])
Oct 24 12:09:42 localhost kernel: [15810.907488] done.
Oct 24 12:09:42 localhost kernel: [15810.909513] thermal thermal_zone2: failed 
to read out thermal zone (-61)
Oct 24 12:09:42 localhost kernel: [15810.946024] PM: suspend exit
Oct 24 12:09:42 localhost kernel: [15811.200265] [drm] Reducing the compressed 
framebuffer size. This may lead to less power sa
vings than a non-reduced-size. Try to increase stolen memory size if available 
in BIOS.

This looks to me like a bug in the Intel ethernet driver. In dmesg, on
boot I see the following ethernet driver loaded:

[0.674440] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-19-generic 5.3.0-19.20
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alistair   2060 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Oct 24 15:51:11 2019
InstallationDate: Installed on 2017-08-16 (798 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HFCTO1WW
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-19-generic N/A
 linux-backports-modules-5.3.0-19-generic  N/A
 linux-firmware1.183
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-10-04 (20 days ago)
dmi.bios.date: 08/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET56W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug eoan

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

Title:
  Thinkpad T470s failure to suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 19.10, my Thinkpad 

[Kernel-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash

2018-04-09 Thread Alistair Cunningham
Just had a system hang on 18.04 due to this. The hangs are definitely
much rarer, but do happen.

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

Title:
  System hangs after iwlwifi firmware crash

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at
  unpredictable times. I have experienced probably 20 hangs. Once the
  system is hung no mouse movement, NumLock toggle, VT switch,
  Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any
  audio playing is stuck looping in the hardware buffer. The system is
  really stuck. Only the keyboard backlight is still responsive.

  The only correlation I have noticed is that the system only hangs if
  WiFi is enabled. This morning I experienced two hangs in ten minutes
  necessitating reboots. Having disabled WiFi the system has been stable
  since ~1100 (~5 hours).

  Often, I see a iwlwifi hardware reset in the logs before the system
  dies:

  /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi
  :02:00.0: Microcode SW error detected.  Restarting 0x8200.

  (apport has hopefully uploaded the full log, please lmk if not).
  Sometimes the message doesn't make it into the logs, and ext4
  truncates the file at the next mount.

  There seems to be no correlation with any messages immediately before
  the wifi chip dies. It doesn't seem to matter whether I'm at home or
  at work. I have wired ethernet at work simultaneously with wifi, but
  the wifi provides IPv6 so I would imagine most traffic uses wifi, so
  it's hard to say whether there's any effect of the traffic load on the
  probability of failure.

  Here is a sample of the firmware load:

  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi 
:02:00.0: enabling device ( -> 0002)
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi 
:02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi 
:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208

  02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

  Any help appreciated.

  Thanks,
  Bruce

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Oct 30 16:15:43 2017
  DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c]
  InstallationDate: Installed on 2016-09-09 (416 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP EliteBook 820 G3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.13
  dmi.board.name: 807C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.74
  dmi.chassis.asset.tag: 5CG6354JW5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash

2018-04-05 Thread Alistair Cunningham
On Ubuntu 18.04, the warnings in kern.log still happen, and a kernel
oops is reported, but the system doesn't hang.

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

Title:
  System hangs after iwlwifi firmware crash

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at
  unpredictable times. I have experienced probably 20 hangs. Once the
  system is hung no mouse movement, NumLock toggle, VT switch,
  Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any
  audio playing is stuck looping in the hardware buffer. The system is
  really stuck. Only the keyboard backlight is still responsive.

  The only correlation I have noticed is that the system only hangs if
  WiFi is enabled. This morning I experienced two hangs in ten minutes
  necessitating reboots. Having disabled WiFi the system has been stable
  since ~1100 (~5 hours).

  Often, I see a iwlwifi hardware reset in the logs before the system
  dies:

  /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi
  :02:00.0: Microcode SW error detected.  Restarting 0x8200.

  (apport has hopefully uploaded the full log, please lmk if not).
  Sometimes the message doesn't make it into the logs, and ext4
  truncates the file at the next mount.

  There seems to be no correlation with any messages immediately before
  the wifi chip dies. It doesn't seem to matter whether I'm at home or
  at work. I have wired ethernet at work simultaneously with wifi, but
  the wifi provides IPv6 so I would imagine most traffic uses wifi, so
  it's hard to say whether there's any effect of the traffic load on the
  probability of failure.

  Here is a sample of the firmware load:

  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi 
:02:00.0: enabling device ( -> 0002)
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi 
:02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi 
:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208

  02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

  Any help appreciated.

  Thanks,
  Bruce

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Oct 30 16:15:43 2017
  DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c]
  InstallationDate: Installed on 2016-09-09 (416 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP EliteBook 820 G3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.13
  dmi.board.name: 807C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.74
  dmi.chassis.asset.tag: 5CG6354JW5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash

2018-04-05 Thread Alistair Cunningham
Upon upgrading to Ubuntu 18.04 beta, which runs kernel 4.15.0-13-generic
and iwlwifi 8265 driver firmware 34.0.1, this problem seems to have gone
away.

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

Title:
  System hangs after iwlwifi firmware crash

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Kubuntu 17.10 my HP EliteBook 820 G3 hangs at
  unpredictable times. I have experienced probably 20 hangs. Once the
  system is hung no mouse movement, NumLock toggle, VT switch,
  Ctrl+Alt+Del, SysRq keys, SSH attempts have any effect whatsoever. Any
  audio playing is stuck looping in the hardware buffer. The system is
  really stuck. Only the keyboard backlight is still responsive.

  The only correlation I have noticed is that the system only hangs if
  WiFi is enabled. This morning I experienced two hangs in ten minutes
  necessitating reboots. Having disabled WiFi the system has been stable
  since ~1100 (~5 hours).

  Often, I see a iwlwifi hardware reset in the logs before the system
  dies:

  /var/log/syslog:Oct 30 11:49:30 fry kernel: [ 6529.550751] iwlwifi
  :02:00.0: Microcode SW error detected.  Restarting 0x8200.

  (apport has hopefully uploaded the full log, please lmk if not).
  Sometimes the message doesn't make it into the logs, and ext4
  truncates the file at the next mount.

  There seems to be no correlation with any messages immediately before
  the wifi chip dies. It doesn't seem to matter whether I'm at home or
  at work. I have wired ethernet at work simultaneously with wifi, but
  the wifi provides IPv6 so I would imagine most traffic uses wifi, so
  it's hard to say whether there's any effect of the traffic load on the
  probability of failure.

  Here is a sample of the firmware load:

  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.604743] iwlwifi 
:02:00.0: enabling device ( -> 0002)
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611790] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-33.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.611930] iwlwifi 
:02:00.0: Direct firmware load for iwlwifi-8000C-32.ucode failed with error 
-2
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.620028] iwlwifi 
:02:00.0: loaded firmware version 31.532993.0 op_mode iwlmvm
  /var/log/syslog.5.gz:Oct 24 15:37:26 fry kernel: [7.650972] iwlwifi 
:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208

  02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

  Any help appreciated.

  Thanks,
  Bruce

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Oct 30 16:15:43 2017
  DistUpgraded: 2017-10-15 14:47:25,517 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 520 [103c:807c]
  InstallationDate: Installed on 2016-09-09 (416 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP EliteBook 820 G3
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-15 (15 days ago)
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.13
  dmi.board.name: 807C
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.74
  dmi.chassis.asset.tag: 5CG6354JW5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook820G3:pvr:rvnHP:rn807C:rvrKBCVersion85.74:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 820 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

[Kernel-packages] [Bug 1728651] Re: System hangs after iwlwifi firmware crash

2018-03-31 Thread Alistair Cunningham
Am suffering from the same bug on a Thinkpad T470s with an Intel 8265
wifi chip running Ubuntu 17.10, Linux kernel 4.13.0-37-generic, and
iwlwifi 31.560484.0. There are multiple reports like the errors below in
kern.log. After a while, the machine completely locks up. Interestingly,
the system only seems to lock up when transferring files using Syncthing
or Resilio Sync.

Mar 31 15:36:50 albatross kernel: [66351.160529] iwlwifi :3a:00.0: 
Microcode SW error detected.  Restarting 0x8200.
Mar 31 15:36:50 albatross kernel: [66351.160659] iwlwifi :3a:00.0: Start 
IWL Error Log Dump:
Mar 31 15:36:50 albatross kernel: [66351.160661] iwlwifi :3a:00.0: Status: 
0x0200, count: 6
Mar 31 15:36:50 albatross kernel: [66351.160662] iwlwifi :3a:00.0: Loaded 
firmware version: 31.560484.0
Mar 31 15:36:50 albatross kernel: [66351.160664] iwlwifi :3a:00.0: 
0x0038 | BAD_COMMAND 
Mar 31 15:36:50 albatross kernel: [66351.160665] iwlwifi :3a:00.0: 
0x0220 | trm_hw_status0
Mar 31 15:36:50 albatross kernel: [66351.160667] iwlwifi :3a:00.0: 
0x | trm_hw_status1
Mar 31 15:36:50 albatross kernel: [66351.160668] iwlwifi :3a:00.0: 
0x0002495C | branchlink2
Mar 31 15:36:50 albatross kernel: [66351.160670] iwlwifi :3a:00.0: 
0x0003962E | interruptlink1
Mar 31 15:36:50 albatross kernel: [66351.160671] iwlwifi :3a:00.0: 
0x | interruptlink2
Mar 31 15:36:50 albatross kernel: [66351.160673] iwlwifi :3a:00.0: 
0x0065001C | data1
Mar 31 15:36:50 albatross kernel: [66351.160674] iwlwifi :3a:00.0: 
0x0066 | data2
Mar 31 15:36:50 albatross kernel: [66351.160675] iwlwifi :3a:00.0: 
0x0067 | data3
Mar 31 15:36:50 albatross kernel: [66351.160677] iwlwifi :3a:00.0: 
0x00016976 | beacon time
Mar 31 15:36:50 albatross kernel: [66351.160678] iwlwifi :3a:00.0: 
0x0398C5D9 | tsf low
Mar 31 15:36:50 albatross kernel: [66351.160680] iwlwifi :3a:00.0: 
0x0014 | tsf hi
Mar 31 15:36:50 albatross kernel: [66351.160681] iwlwifi :3a:00.0: 
0x | time gp1
Mar 31 15:36:50 albatross kernel: [66351.160682] iwlwifi :3a:00.0: 
0x000C98DD | time gp2
Mar 31 15:36:50 albatross kernel: [66351.160684] iwlwifi :3a:00.0: 
0x0001 | uCode revision type
Mar 31 15:36:50 albatross kernel: [66351.160685] iwlwifi :3a:00.0: 
0x001F | uCode version major
Mar 31 15:36:50 albatross kernel: [66351.160687] iwlwifi :3a:00.0: 
0x00088D64 | uCode version minor
Mar 31 15:36:50 albatross kernel: [66351.160688] iwlwifi :3a:00.0: 
0x0230 | hw version
Mar 31 15:36:50 albatross kernel: [66351.160689] iwlwifi :3a:00.0: 
0x00C89000 | board version
Mar 31 15:36:50 albatross kernel: [66351.160691] iwlwifi :3a:00.0: 
0x0065001C | hcmd
Mar 31 15:36:50 albatross kernel: [66351.160692] iwlwifi :3a:00.0: 
0x24022082 | isr0
Mar 31 15:36:50 albatross kernel: [66351.160694] iwlwifi :3a:00.0: 
0x | isr1
Mar 31 15:36:50 albatross kernel: [66351.160695] iwlwifi :3a:00.0: 
0x28201802 | isr2
Mar 31 15:36:50 albatross kernel: [66351.160697] iwlwifi :3a:00.0: 
0x004120C0 | isr3
Mar 31 15:36:50 albatross kernel: [66351.160698] iwlwifi :3a:00.0: 
0x | isr4
Mar 31 15:36:50 albatross kernel: [66351.160699] iwlwifi :3a:00.0: 
0x0A8A001C | last cmd Id
Mar 31 15:36:50 albatross kernel: [66351.160701] iwlwifi :3a:00.0: 
0x | wait_event
Mar 31 15:36:50 albatross kernel: [66351.160702] iwlwifi :3a:00.0: 
0x0094 | l2p_control
Mar 31 15:36:50 albatross kernel: [66351.160704] iwlwifi :3a:00.0: 
0x00018030 | l2p_duration
Mar 31 15:36:50 albatross kernel: [66351.160705] iwlwifi :3a:00.0: 
0x000F | l2p_mhvalid
Mar 31 15:36:50 albatross kernel: [66351.160706] iwlwifi :3a:00.0: 
0x0085 | l2p_addr_match
Mar 31 15:36:50 albatross kernel: [66351.160708] iwlwifi :3a:00.0: 
0x000D | lmpm_pmg_sel
Mar 31 15:36:50 albatross kernel: [66351.160709] iwlwifi :3a:00.0: 
0x13091828 | timestamp
Mar 31 15:36:50 albatross kernel: [66351.160711] iwlwifi :3a:00.0: 
0x8098 | flow_handler
Mar 31 15:36:50 albatross kernel: [66351.160777] iwlwifi :3a:00.0: Start 
IWL Error Log Dump:
Mar 31 15:36:50 albatross kernel: [66351.160779] iwlwifi :3a:00.0: Status: 
0x0200, count: 7
Mar 31 15:36:50 albatross kernel: [66351.160781] iwlwifi :3a:00.0: 
0x0070 | ADVANCED_SYSASSERT
Mar 31 15:36:50 albatross kernel: [66351.160782] iwlwifi :3a:00.0: 
0x | umac branchlink1
Mar 31 15:36:50 albatross kernel: [66351.160783] iwlwifi :3a:00.0: 
0xC0086950 | umac branchlink2
Mar 31 15:36:50 albatross kernel: [66351.160785] iwlwifi :3a:00.0: 
0xC00842BC | umac interruptlink1
Mar 31 15:36:50 albatross kernel: [66351.160786] iwlwifi :3a:00.0: 
0xC00842BC | umac interruptlink2
Mar 31 15:36:50 albatross kernel: [66351.160788] iwlwifi :3a:00.0: 
0x0800 | umac data1
Mar 31 15:36:50 albatross kernel: [66351.160789] iwlwifi :3a:00.0: 
0xC00842BC | umac data2

[Kernel-packages] [Bug 1191465] Re: Thinkpad sometimes won't suspend

2014-12-05 Thread Alistair Cunningham
I'm horrified that it has been well over a year between this problem
being reported and the first non-automated response from Ubuntu. Yes,
this problem still exists on Ubuntu 14.10, but I have managed to
implement a workaround. If I disable the Nvidia graphics card in BIOS,
and use the Intel graphics card instead, the problem goes away. This
means that I can't play games on the laptop, but given how appallingly
slow Ubuntu is to respond, I see no point in pursuing this bug report
any further. I'll probably have replaced the laptop before anything is
done about this. As far as I'm concerned, this bug report can be closed.

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

Title:
  Thinkpad sometimes won't suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've filed this bug against pm-utils as I'm not sure which package is
  the root cause of this. My apologies if it's really something else.
  Feel free to re-assign in this case.

  I have a Thinkpad T530 running Ubuntu 13.04 that will sometimes
  suspend, but sometimes won't. When it won't, the suspend LED flashes
  for a few seconds, then the battery LED flashes for a seconds, and the
  system returns to normal running. When this happens, no amount of
  trying to suspend seems to work, and the only option is to do a full
  shutdown. Here's the part of /var/log/kern.log that seems most
  appropriate:

  Jun 15 10:53:20 albatross kernel: [558688.602852] PM: Syncing filesystems ... 
done.
  Jun 15 10:53:25 albatross kernel: [558688.615862] Freezing user space 
processes ... (elapsed 0.01 seconds) done.
  Jun 15 10:53:25 albatross kernel: [558688.629715] Freezing remaining 
freezable tasks ... (elapsed 0.01 seconds) done.
  Jun 15 10:53:25 albatross kernel: [558688.645836] Suspending console(s) (use 
no_console_suspend to debug)
  Jun 15 10:53:25 albatross kernel: [558688.646018] sd 1:0:0:0: [sdb] 
Synchronizing SCSI cache
  Jun 15 10:53:25 albatross kernel: [558688.646115] sd 0:0:0:0: [sda] 
Synchronizing SCSI cache
  Jun 15 10:53:25 albatross kernel: [558688.646257] sd 1:0:0:0: [sdb] Stopping 
disk
  Jun 15 10:53:25 albatross kernel: [558688.663882] sd 0:0:0:0: [sda] Stopping 
disk
  Jun 15 10:53:25 albatross kernel: [558688.881041] e1000e :00:19.0: System 
wakeup enabled by ACPI
  Jun 15 10:53:25 albatross kernel: [558689.204873] thinkpad_acpi: unknown 
possible thermal alarm or keyboard event received
  Jun 15 10:53:25 albatross kernel: [558689.204876] thinkpad_acpi: unhandled 
HKEY event 0x6040
  Jun 15 10:53:25 albatross kernel: [558689.204878] thinkpad_acpi: please 
report the conditions when this event happened to
  ibm-acpi-de...@lists.sourceforge.net
  Jun 15 10:53:25 albatross kernel: [558689.205237] thinkpad_acpi: EC reports 
that Thermal Table has changed
  Jun 15 10:53:25 albatross kernel: [558689.336431] PM: suspend of devices 
complete after 691.807 msecs
  Jun 15 10:53:25 albatross kernel: [558689.336542] PM: late suspend of devices 
complete after 0.109 msecs
  Jun 15 10:53:25 albatross kernel: [558689.352427] ehci-pci :00:1d.0: 
System wakeup enabled by ACPI

  I've also attached the full kern.log from around that time. A few
  other details that may be of interest:

  root@albatross:~# uname -a
  Linux albatross 3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:24:54 UTC 2013 
i686 i686 i686 GNU/Linux
  root@albatross:~# lspci
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)
  00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset 
Family KT Controller (rev 04)
  00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 1 (rev c4)
  00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 2 (rev c4)
  00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 3 (rev c4)
  00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller 
(rev 04)
  00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port 
SATA 

[Kernel-packages] [Bug 1191465] Re: Thinkpad sometimes won't suspend

2014-12-05 Thread Alistair Cunningham
** Changed in: linux (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  Thinkpad sometimes won't suspend

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I've filed this bug against pm-utils as I'm not sure which package is
  the root cause of this. My apologies if it's really something else.
  Feel free to re-assign in this case.

  I have a Thinkpad T530 running Ubuntu 13.04 that will sometimes
  suspend, but sometimes won't. When it won't, the suspend LED flashes
  for a few seconds, then the battery LED flashes for a seconds, and the
  system returns to normal running. When this happens, no amount of
  trying to suspend seems to work, and the only option is to do a full
  shutdown. Here's the part of /var/log/kern.log that seems most
  appropriate:

  Jun 15 10:53:20 albatross kernel: [558688.602852] PM: Syncing filesystems ... 
done.
  Jun 15 10:53:25 albatross kernel: [558688.615862] Freezing user space 
processes ... (elapsed 0.01 seconds) done.
  Jun 15 10:53:25 albatross kernel: [558688.629715] Freezing remaining 
freezable tasks ... (elapsed 0.01 seconds) done.
  Jun 15 10:53:25 albatross kernel: [558688.645836] Suspending console(s) (use 
no_console_suspend to debug)
  Jun 15 10:53:25 albatross kernel: [558688.646018] sd 1:0:0:0: [sdb] 
Synchronizing SCSI cache
  Jun 15 10:53:25 albatross kernel: [558688.646115] sd 0:0:0:0: [sda] 
Synchronizing SCSI cache
  Jun 15 10:53:25 albatross kernel: [558688.646257] sd 1:0:0:0: [sdb] Stopping 
disk
  Jun 15 10:53:25 albatross kernel: [558688.663882] sd 0:0:0:0: [sda] Stopping 
disk
  Jun 15 10:53:25 albatross kernel: [558688.881041] e1000e :00:19.0: System 
wakeup enabled by ACPI
  Jun 15 10:53:25 albatross kernel: [558689.204873] thinkpad_acpi: unknown 
possible thermal alarm or keyboard event received
  Jun 15 10:53:25 albatross kernel: [558689.204876] thinkpad_acpi: unhandled 
HKEY event 0x6040
  Jun 15 10:53:25 albatross kernel: [558689.204878] thinkpad_acpi: please 
report the conditions when this event happened to
  ibm-acpi-de...@lists.sourceforge.net
  Jun 15 10:53:25 albatross kernel: [558689.205237] thinkpad_acpi: EC reports 
that Thermal Table has changed
  Jun 15 10:53:25 albatross kernel: [558689.336431] PM: suspend of devices 
complete after 691.807 msecs
  Jun 15 10:53:25 albatross kernel: [558689.336542] PM: late suspend of devices 
complete after 0.109 msecs
  Jun 15 10:53:25 albatross kernel: [558689.352427] ehci-pci :00:1d.0: 
System wakeup enabled by ACPI

  I've also attached the full kern.log from around that time. A few
  other details that may be of interest:

  root@albatross:~# uname -a
  Linux albatross 3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:24:54 UTC 2013 
i686 i686 i686 GNU/Linux
  root@albatross:~# lspci
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
PCI Express Root Port (rev 09)
  00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)
  00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset 
Family KT Controller (rev 04)
  00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 1 (rev c4)
  00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 2 (rev c4)
  00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 3 (rev c4)
  00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller 
(rev 04)
  00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port 
SATA Controller [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus 
Controller (rev 04)
  01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [NVS 5400M] (rev 
a1)
  01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio 
Controller (rev a1)
  02:00.0 System peripheral: Ricoh Co Ltd PCIe SDXC/MMC Host Controller (rev 08)
  02:00.3 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 PCIe IEEE 1394 Controller 
(rev 04)
  03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 
[Taylor Peak]