[Kernel-packages] [Bug 1881462] Re: Brightness settings don't work on Lenovo Ideapad 5 15ARE05

[Paul]

The kernel fix by updating to 5.7 from mainline does work for me. I get
the same result as @Simon,  brightness change from 50-100% is working. A
proper fix would be nice because 50% brightness is in my opinion still
too bright in a dark environment.

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

Title:
  Brightness settings don't work on Lenovo Ideapad 5 15ARE05

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installation, the notebook brighness buttons change brightness
  settings, but settings are not applied on the screen.

  In the log files I can see something like this:
  Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0.
  amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or 
address
  amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or 
address
  Failed to get backlight or LED device 'backlight:acpi_video0': No such device

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sun May 31 10:43:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev ce) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Renoir [17aa:381b]
  InstallationDate: Installed on 2020-05-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YQ
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=94ab3768-11c5-4582-9374-578128353e38 ro quiet splash 
amdgpu.exp_hw_support=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E7CN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05:
  dmi.product.family: IdeaPad 5 15ARE05
  dmi.product.name: 81YQ
  dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05
  dmi.product.version: IdeaPad 5 15ARE05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881462/+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 1875916] Re: upgrading to 4.15.0-99-generic breaks the sound and the trackpad

[Paul]

I can confirm #52.

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

Title:
  upgrading to 4.15.0-99-generic breaks the sound and the trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using kubuntu LTS 18.04.
  This morning I was promped to update the kernel to the 4.15.0-99-generic. 

  After the upgrade I did not manage to get any sound. I checked
  everything, pavucontrol, alsamix, everything was in order, the streams
  showed as if they were playing, however I couldn't get any sound from
  the speakers headphones and I could not get any sound recorded either.

  I then rebooted with the previous version of the Kernel, and have my sound 
back without doing anything at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba
  InstallationDate: Installed on 2019-01-29 (455 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   wlp108s0  no wireless extensions.
  MachineType: Dell Inc. Latitude 7390 2-in-1
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-99-generic N/A
   linux-backports-modules-4.15.0-99-generic  N/A
   linux-firmware 1.173.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0YNG30
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7390 2-in-1
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916/+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 1866879] Re: Failure to boot on linux-image-5.3.0-40-generic

[Paul]

I upgraded/updated to `5.3.0-42-generic` and now it boots without me
having to change anything in grub.

I've attached `journalctl -b` in case this is of help.

All the best
Paul

** Attachment added: "journalctl -b"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+attachment/5339448/+files/journalctl-42.txt

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

Title:
  Failure to boot on linux-image-5.3.0-40-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu on the laptop, rebooted and everything was fine. I
  did an upgrade to all packages and found that when I rebooted, it
  fails to load.

  I found out that a workaround is to select linux-
  image-5.3.0-18-generic in grub which leads me to think that the issue
  is related to the upgrade of the linux-image 5.3.0 package.

  To be clear, linux-image-5.3.0-18-generic works but linux-
  image-5.3.0-40-generic does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paul   2027 F pulseaudio
   /dev/snd/controlC0:  paul   2027 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 18:25:57 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+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 1689408]

[Paul]

(In reply to Timothy Arceri from comment #8)
> Is this working for you now?

I've since removed linux from the system and handed it down to a family
member, so it's not possible for me to test anymore. However I would
expect the bug would have been fixed by now, according to the current
RadeonFeature support table.

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1689408/+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 1689408] Re: System hang when utilising OpenGL 4.5 features

[Paul]

Fix status is unknown and untested, it may not be fixed at all, I simply
lack the hardware to actually test it.

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1689408/+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 1801540] Re: Microphone distorted sound on ALC892

[Paul]

Thanks Fred, it worked for me !

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

Title:
  Microphone distorted sound on ALC892

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

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540] Re: Microphone distorted sound on ALC892

[Paul]

I have exactly the same problem, and I also have an MSI B350 am4
motherboard...

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

Title:
  Microphone distorted sound on ALC892

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

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1688143] Re: Stop disabling bluetooth!

[Paul]

Wait what? I never set it to launchpad-integration, it was originally
kdebluetooth as bluez doesn't show when you search for bluetooth
packages...

Is bluez part of bluetoothd and what kubuntu uses?

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

Title:
  Stop disabling bluetooth!

Status in bluez package in Ubuntu:
  New

Bug description:
  Randomly after resuming from sleep, restarting, logging in or opening
  the screen on a laptop, bluetooth gets disabled. This is a major
  problem for bluetooth peripheral users as it can cause the system to
  be unusable without having to use a non-bluetooth peripheral just to
  re-enable bluetooth.

  This is completely unrelated to bluetooth discovery, of which is
  normally disabled in this use-case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688143/+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 1689408] [NEW] System hang when utilising OpenGL 4.5 features

[Paul]

Public bug reported:

I've found this to be easily reproducible via unigine's heaven
benchmark, which uses tessellation and other features extensively.
Simply creating a OpenGL 4.5 context will not trigger the hang, and you
must explicitly request an OGL 4+ context as the default will only be
3.0.

On a successful trigger, the screen may flicker on and off a few times
and eventually hang completely on a black screen, there's no way to
recover the system from this state bar a power cycle (ie hold the power
button).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-20-generic 4.10.0-20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  paulh  1405 F pulseaudio
 /dev/snd/controlC0:  paulh  1405 F pulseaudio
CurrentDesktop: KDE
Date: Tue May  9 09:14:09 2017
InstallationDate: Installed on 2017-01-05 (123 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
MachineType: HP HP Notebook
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-20-generic N/A
 linux-backports-modules-4.10.0-20-generic  N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
dmi.bios.date: 10/29/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.1C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8133
dmi.board.vendor: HP
dmi.board.version: KBC Version 98.0E
dmi.chassis.asset.tag: 5CG6124XBK
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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

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


** Tags: amd64 apport-bug zesty

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

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  

[Kernel-packages] [Bug 1689408] Re: System hang when utilising OpenGL 4.5 features

[Paul]

The default is ignored however if the game requires tessellation or
other 4+ features, which is pretty much every big game released in the
past few years...

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/+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 1689408] Re: System hang when utilising OpenGL 4.5 features

[Paul]

https://bugs.freedesktop.org/show_bug.cgi?id=100995

** Bug watch added: freedesktop.org Bugzilla #100995
   https://bugs.freedesktop.org/show_bug.cgi?id=100995

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

Title:
  System hang when utilising OpenGL 4.5 features

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  I've found this to be easily reproducible via unigine's heaven
  benchmark, which uses tessellation and other features extensively.
  Simply creating a OpenGL 4.5 context will not trigger the hang, and
  you must explicitly request an OGL 4+ context as the default will only
  be 3.0.

  On a successful trigger, the screen may flicker on and off a few times
  and eventually hang completely on a black screen, there's no way to
  recover the system from this state bar a power cycle (ie hold the
  power button).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh  1405 F pulseaudio
   /dev/snd/controlC0:  paulh  1405 F pulseaudio
  CurrentDesktop: KDE
  Date: Tue May  9 09:14:09 2017
  InstallationDate: Installed on 2017-01-05 (123 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=a5482167-6676-4a1a-b150-a86255560de6 ro rhgb quiet 
resume=/dev/sda6/swapfile resume_offset=7673856 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (24 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689408/+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 1881462] Re: Brightness settings don't work on Lenovo Ideapad 5 15ARE05

[Paul]

I updated now to kernel 5.7.9 and brightness can now be reduced to less
than 50%. Only thing I noted is that setting brightness to zero does not
turn off the screen as it is when running windows on the machine.

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

Title:
  Brightness settings don't work on Lenovo Ideapad 5 15ARE05

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installation, the notebook brighness buttons change brightness
  settings, but settings are not applied on the screen.

  In the log files I can see something like this:
  Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0.
  amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or 
address
  amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or 
address
  Failed to get backlight or LED device 'backlight:acpi_video0': No such device

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sun May 31 10:43:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev ce) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Renoir [17aa:381b]
  InstallationDate: Installed on 2020-05-29 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YQ
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=94ab3768-11c5-4582-9374-578128353e38 ro quiet splash 
amdgpu.exp_hw_support=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E7CN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 15ARE05
  dmi.modalias: 
dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05:
  dmi.product.family: IdeaPad 5 15ARE05
  dmi.product.name: 81YQ
  dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05
  dmi.product.version: IdeaPad 5 15ARE05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881462/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Paul]

How do we get the Kernel maintainers to approve the remaining patches? I
thought it might be fixed in 20.10 (KUbuntu), but it is not. I would
think there is at least one kernel approver within Canonical? If not,
who do I get in touch to talk about 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/1838151

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1685564] [NEW] swapops.h bug causes soft lockup, takes down entire network stack

[Paul]

Public bug reported:

Unlocked the computer to find Thunderbird in an infinite loop and the
system barely usable, with no networking. ifconfig and netstat -r both
locked up without returning data. Apport would not complete until after
a reboot, so I collected some log output (attached).

At the time of the bug, Ubuntu had been running for about 15 hours since
the last software suspend.

kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
invalid opcode:  [#1] SMP
Modules linked in: nls_iso8859_1 uas usb_storage ccm rfcomm cmac bnep ipheth 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
videodev media btusb btrtl btbcm hid_generic btintel hid_multitouch bluetooth 
usbhid binfmt_misc asus_nb_wmi asus_wmi sparse_keymap intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_rt5640 kvm_intel 
snd_soc_rl6231 snd_soc_core kvm snd_compress ac97_bus irqbypass arc4 
snd_pcm_dmaengine crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_seq_midi pcbc snd_seq_midi_event aesni_intel aes_x86_64 
snd_hda_codec_conexant crypto_simd snd_hda_codec_hdmi glue_helper 
snd_hda_codec_generic snd_rawmidi cryptd iwlmvm intel_cstate intel_rapl_perf 
snd_hda_intel mac80211 snd_seq snd_hda_codec joydev snd_hda_core input_leds 
snd_hwdep serio_raw
 snd_seq_device intel_pch_thermal iwlwifi snd_pcm mei_me 
processor_thermal_device cfg80211 intel_soc_dts_iosf mei shpchp snd_timer 
lpc_ich snd soundcore dw_dmac dw_dmac_core snd_soc_sst_acpi snd_soc_sst_match 
elan_i2c 8250_dw i2c_designware_platform i2c_designware_core int3406_thermal 
spi_pxa2xx_platform int3402_thermal int340x_thermal_zone tpm_crb 
int3400_thermal acpi_thermal_rel asus_wireless mac_hid acpi_pad parport_pc 
ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq i915 
i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt 
fb_sys_fops ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid fjes
CPU: 1 PID: 4223 Comm: thunderbird Not tainted 4.10.0-19-generic #21-Ubuntu
Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS UX303LAB.210 
08/25/2015 
task: 8aef08471680 task.stack: b3c7099a
RIP: 0010:__migration_entry_wait+0x16a/0x180 
RSP: :b3c7099a3d68 EFLAGS: 00010246
RAX: 000fc0048078 RBX: d9d08a9c67f0 RCX: d9d08a9c67f0
RDX: 0001 RSI: 8aeee719f800 RDI: d9d08187c000
RBP: b3c7099a3d80 R08: 8aeefeabf440 R09: 8aeefeabf440
R10: 7f18117000c8 R11: 0206 R12: d9d08187c000
R13: 3e061f00 R14: b3c7099a3e30 R15: 8aee8b0633e8
FS:  7f1812b43740() GS:8aef5ec8() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7f17e0500018 CR3: 00028fbb3000 CR4: 003406e0
Call Trace:
 migration_entry_wait+0x74/0x80
 do_swap_page+0x5b3/0x770
 handle_mm_fault+0x873/0x1360
 __do_page_fault+0x23e/0x4e0
 do_page_fault+0x22/0x30
 page_fault+0x28/0x30
RIP: 0033:0x5627064df06c
RSP: 002b:7ffc33c899b0 EFLAGS: 00010203
RAX:  RBX: 7f1811700040 RCX: 7f18119b6137
RDX: 0008 RSI: 8000 RDI: 7f17e0514000
RBP: 7f17e050 R08: 7f18117000c8 R09: 
R10: 7f18117000c8 R11: 0206 R12: 0200
R13: 7f18117000c8 R14: 0013 R15: 0008
Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 
8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c 
fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb
RIP: __migration_entry_wait+0x16a/0x180 RSP: b3c7099a3d68

# uname -a
Linux freedom 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
# cat /proc/version_signature
Ubuntu 4.10.0-19.21-generic 4.10.8

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1418 F pulseaudio
  pmj1986 F pulseaudio
 /dev/snd/controlC1:  gdm1418 F pulseaudio
  pmj1986 F pulseaudio
Date: Sun Apr 23 09:56:20 2017
HibernationDevice: RESUME=UUID=d572808f-6762-4035-abbc-22fab43c88a5
InstallationDate: Installed on 2016-12-02 (141 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
MachineType: ASUSTeK COMPUTER INC. UX303LAB
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-19-generic 
root=UUID=795346fb-c6f2-478b-88c6-363f7317e849 ro rootflags=subvol=@ quiet 
splash acpi_osi= vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 

[Kernel-packages] [Bug 1685564] Re: swapops.h bug causes soft lockup, takes down entire network stack

[Paul]

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685564/+attachment/4866644/+files/syslog

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

Title:
  swapops.h bug causes soft lockup, takes down entire network stack

Status in linux package in Ubuntu:
  New

Bug description:
  Unlocked the computer to find Thunderbird in an infinite loop and the
  system barely usable, with no networking. ifconfig and netstat -r both
  locked up without returning data. Apport would not complete until
  after a reboot, so I collected some log output (attached).

  At the time of the bug, Ubuntu had been running for about 15 hours
  since the last software suspend.

  kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
  invalid opcode:  [#1] SMP
  Modules linked in: nls_iso8859_1 uas usb_storage ccm rfcomm cmac bnep ipheth 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
videodev media btusb btrtl btbcm hid_generic btintel hid_multitouch bluetooth 
usbhid binfmt_misc asus_nb_wmi asus_wmi sparse_keymap intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_rt5640 kvm_intel 
snd_soc_rl6231 snd_soc_core kvm snd_compress ac97_bus irqbypass arc4 
snd_pcm_dmaengine crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_seq_midi pcbc snd_seq_midi_event aesni_intel aes_x86_64 
snd_hda_codec_conexant crypto_simd snd_hda_codec_hdmi glue_helper 
snd_hda_codec_generic snd_rawmidi cryptd iwlmvm intel_cstate intel_rapl_perf 
snd_hda_intel mac80211 snd_seq snd_hda_codec joydev snd_hda_core input_leds 
snd_hwdep serio_raw
   snd_seq_device intel_pch_thermal iwlwifi snd_pcm mei_me 
processor_thermal_device cfg80211 intel_soc_dts_iosf mei shpchp snd_timer 
lpc_ich snd soundcore dw_dmac dw_dmac_core snd_soc_sst_acpi snd_soc_sst_match 
elan_i2c 8250_dw i2c_designware_platform i2c_designware_core int3406_thermal 
spi_pxa2xx_platform int3402_thermal int340x_thermal_zone tpm_crb 
int3400_thermal acpi_thermal_rel asus_wireless mac_hid acpi_pad parport_pc 
ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq i915 
i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt 
fb_sys_fops ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid fjes
  CPU: 1 PID: 4223 Comm: thunderbird Not tainted 4.10.0-19-generic #21-Ubuntu
  Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS UX303LAB.210 
08/25/2015 
  task: 8aef08471680 task.stack: b3c7099a
  RIP: 0010:__migration_entry_wait+0x16a/0x180 
  RSP: :b3c7099a3d68 EFLAGS: 00010246
  RAX: 000fc0048078 RBX: d9d08a9c67f0 RCX: d9d08a9c67f0
  RDX: 0001 RSI: 8aeee719f800 RDI: d9d08187c000
  RBP: b3c7099a3d80 R08: 8aeefeabf440 R09: 8aeefeabf440
  R10: 7f18117000c8 R11: 0206 R12: d9d08187c000
  R13: 3e061f00 R14: b3c7099a3e30 R15: 8aee8b0633e8
  FS:  7f1812b43740() GS:8aef5ec8() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f17e0500018 CR3: 00028fbb3000 CR4: 003406e0
  Call Trace:
   migration_entry_wait+0x74/0x80
   do_swap_page+0x5b3/0x770
   handle_mm_fault+0x873/0x1360
   __do_page_fault+0x23e/0x4e0
   do_page_fault+0x22/0x30
   page_fault+0x28/0x30
  RIP: 0033:0x5627064df06c
  RSP: 002b:7ffc33c899b0 EFLAGS: 00010203
  RAX:  RBX: 7f1811700040 RCX: 7f18119b6137
  RDX: 0008 RSI: 8000 RDI: 7f17e0514000
  RBP: 7f17e050 R08: 7f18117000c8 R09: 
  R10: 7f18117000c8 R11: 0206 R12: 0200
  R13: 7f18117000c8 R14: 0013 R15: 0008
  Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 
8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c 
fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb
  RIP: __migration_entry_wait+0x16a/0x180 RSP: b3c7099a3d68

  # uname -a
  Linux freedom 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  # cat /proc/version_signature
  Ubuntu 4.10.0-19.21-generic 4.10.8

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1418 F pulseaudio
pmj1986 F pulseaudio
   /dev/snd/controlC1:  gdm1418 F pulseaudio
pmj1986 F pulseaudio
  Date: Sun Apr 23 09:56:20 2017
  HibernationDevice: RESUME=UUID=d572808f-6762-4035-abbc-22fab43c88a5
  InstallationDate: Installed on 2016-12-02 (141 day

[Kernel-packages] [Bug 1685564] Re: swapops.h bug causes soft lockup, takes down entire network stack

[Paul]

** Attachment added: "lspci-vvnn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685564/+attachment/4866645/+files/lspci-vvnn.log

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

Title:
  swapops.h bug causes soft lockup, takes down entire network stack

Status in linux package in Ubuntu:
  New

Bug description:
  Unlocked the computer to find Thunderbird in an infinite loop and the
  system barely usable, with no networking. ifconfig and netstat -r both
  locked up without returning data. Apport would not complete until
  after a reboot, so I collected some log output (attached).

  At the time of the bug, Ubuntu had been running for about 15 hours
  since the last software suspend.

  kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
  invalid opcode:  [#1] SMP
  Modules linked in: nls_iso8859_1 uas usb_storage ccm rfcomm cmac bnep ipheth 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
videodev media btusb btrtl btbcm hid_generic btintel hid_multitouch bluetooth 
usbhid binfmt_misc asus_nb_wmi asus_wmi sparse_keymap intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_rt5640 kvm_intel 
snd_soc_rl6231 snd_soc_core kvm snd_compress ac97_bus irqbypass arc4 
snd_pcm_dmaengine crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_seq_midi pcbc snd_seq_midi_event aesni_intel aes_x86_64 
snd_hda_codec_conexant crypto_simd snd_hda_codec_hdmi glue_helper 
snd_hda_codec_generic snd_rawmidi cryptd iwlmvm intel_cstate intel_rapl_perf 
snd_hda_intel mac80211 snd_seq snd_hda_codec joydev snd_hda_core input_leds 
snd_hwdep serio_raw
   snd_seq_device intel_pch_thermal iwlwifi snd_pcm mei_me 
processor_thermal_device cfg80211 intel_soc_dts_iosf mei shpchp snd_timer 
lpc_ich snd soundcore dw_dmac dw_dmac_core snd_soc_sst_acpi snd_soc_sst_match 
elan_i2c 8250_dw i2c_designware_platform i2c_designware_core int3406_thermal 
spi_pxa2xx_platform int3402_thermal int340x_thermal_zone tpm_crb 
int3400_thermal acpi_thermal_rel asus_wireless mac_hid acpi_pad parport_pc 
ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq i915 
i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt 
fb_sys_fops ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid fjes
  CPU: 1 PID: 4223 Comm: thunderbird Not tainted 4.10.0-19-generic #21-Ubuntu
  Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS UX303LAB.210 
08/25/2015 
  task: 8aef08471680 task.stack: b3c7099a
  RIP: 0010:__migration_entry_wait+0x16a/0x180 
  RSP: :b3c7099a3d68 EFLAGS: 00010246
  RAX: 000fc0048078 RBX: d9d08a9c67f0 RCX: d9d08a9c67f0
  RDX: 0001 RSI: 8aeee719f800 RDI: d9d08187c000
  RBP: b3c7099a3d80 R08: 8aeefeabf440 R09: 8aeefeabf440
  R10: 7f18117000c8 R11: 0206 R12: d9d08187c000
  R13: 3e061f00 R14: b3c7099a3e30 R15: 8aee8b0633e8
  FS:  7f1812b43740() GS:8aef5ec8() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f17e0500018 CR3: 00028fbb3000 CR4: 003406e0
  Call Trace:
   migration_entry_wait+0x74/0x80
   do_swap_page+0x5b3/0x770
   handle_mm_fault+0x873/0x1360
   __do_page_fault+0x23e/0x4e0
   do_page_fault+0x22/0x30
   page_fault+0x28/0x30
  RIP: 0033:0x5627064df06c
  RSP: 002b:7ffc33c899b0 EFLAGS: 00010203
  RAX:  RBX: 7f1811700040 RCX: 7f18119b6137
  RDX: 0008 RSI: 8000 RDI: 7f17e0514000
  RBP: 7f17e050 R08: 7f18117000c8 R09: 
  R10: 7f18117000c8 R11: 0206 R12: 0200
  R13: 7f18117000c8 R14: 0013 R15: 0008
  Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 
8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c 
fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb
  RIP: __migration_entry_wait+0x16a/0x180 RSP: b3c7099a3d68

  # uname -a
  Linux freedom 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  # cat /proc/version_signature
  Ubuntu 4.10.0-19.21-generic 4.10.8

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1418 F pulseaudio
pmj1986 F pulseaudio
   /dev/snd/controlC1:  gdm1418 F pulseaudio
pmj1986 F pulseaudio
  Date: Sun Apr 23 09:56:20 2017
  HibernationDevice: RESUME=UUID=d572808f-6762-4035-abbc-22fab43c88a5
  InstallationDate: Installed on 201

[Kernel-packages] [Bug 1685564] Re: swapops.h bug causes soft lockup, takes down entire network stack

[Paul]

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685564/+attachment/4866646/+files/dmesg.log

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

Title:
  swapops.h bug causes soft lockup, takes down entire network stack

Status in linux package in Ubuntu:
  New

Bug description:
  Unlocked the computer to find Thunderbird in an infinite loop and the
  system barely usable, with no networking. ifconfig and netstat -r both
  locked up without returning data. Apport would not complete until
  after a reboot, so I collected some log output (attached).

  At the time of the bug, Ubuntu had been running for about 15 hours
  since the last software suspend.

  kernel BUG at /build/linux-Fk60NP/linux-4.10.0/include/linux/swapops.h:129!
  invalid opcode:  [#1] SMP
  Modules linked in: nls_iso8859_1 uas usb_storage ccm rfcomm cmac bnep ipheth 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
videodev media btusb btrtl btbcm hid_generic btintel hid_multitouch bluetooth 
usbhid binfmt_misc asus_nb_wmi asus_wmi sparse_keymap intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_rt5640 kvm_intel 
snd_soc_rl6231 snd_soc_core kvm snd_compress ac97_bus irqbypass arc4 
snd_pcm_dmaengine crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_seq_midi pcbc snd_seq_midi_event aesni_intel aes_x86_64 
snd_hda_codec_conexant crypto_simd snd_hda_codec_hdmi glue_helper 
snd_hda_codec_generic snd_rawmidi cryptd iwlmvm intel_cstate intel_rapl_perf 
snd_hda_intel mac80211 snd_seq snd_hda_codec joydev snd_hda_core input_leds 
snd_hwdep serio_raw
   snd_seq_device intel_pch_thermal iwlwifi snd_pcm mei_me 
processor_thermal_device cfg80211 intel_soc_dts_iosf mei shpchp snd_timer 
lpc_ich snd soundcore dw_dmac dw_dmac_core snd_soc_sst_acpi snd_soc_sst_match 
elan_i2c 8250_dw i2c_designware_platform i2c_designware_core int3406_thermal 
spi_pxa2xx_platform int3402_thermal int340x_thermal_zone tpm_crb 
int3400_thermal acpi_thermal_rel asus_wireless mac_hid acpi_pad parport_pc 
ppdev lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq i915 
i2c_algo_bit drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt 
fb_sys_fops ahci drm libahci wmi sdhci_acpi video sdhci i2c_hid hid fjes
  CPU: 1 PID: 4223 Comm: thunderbird Not tainted 4.10.0-19-generic #21-Ubuntu
  Hardware name: ASUSTeK COMPUTER INC. UX303LAB/UX303LAB, BIOS UX303LAB.210 
08/25/2015 
  task: 8aef08471680 task.stack: b3c7099a
  RIP: 0010:__migration_entry_wait+0x16a/0x180 
  RSP: :b3c7099a3d68 EFLAGS: 00010246
  RAX: 000fc0048078 RBX: d9d08a9c67f0 RCX: d9d08a9c67f0
  RDX: 0001 RSI: 8aeee719f800 RDI: d9d08187c000
  RBP: b3c7099a3d80 R08: 8aeefeabf440 R09: 8aeefeabf440
  R10: 7f18117000c8 R11: 0206 R12: d9d08187c000
  R13: 3e061f00 R14: b3c7099a3e30 R15: 8aee8b0633e8
  FS:  7f1812b43740() GS:8aef5ec8() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f17e0500018 CR3: 00028fbb3000 CR4: 003406e0
  Call Trace:
   migration_entry_wait+0x74/0x80
   do_swap_page+0x5b3/0x770
   handle_mm_fault+0x873/0x1360
   __do_page_fault+0x23e/0x4e0
   do_page_fault+0x22/0x30
   page_fault+0x28/0x30
  RIP: 0033:0x5627064df06c
  RSP: 002b:7ffc33c899b0 EFLAGS: 00010203
  RAX:  RBX: 7f1811700040 RCX: 7f18119b6137
  RDX: 0008 RSI: 8000 RDI: 7f17e0514000
  RBP: 7f17e050 R08: 7f18117000c8 R09: 
  R10: 7f18117000c8 R11: 0206 R12: 0200
  R13: 7f18117000c8 R14: 0013 R15: 0008
  Code: ff ff ff 4c 89 e7 e8 96 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 
8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 0c 
fb f9 ff eb b8 4c 8d 60 ff 4c 8d 68 1b eb
  RIP: __migration_entry_wait+0x16a/0x180 RSP: b3c7099a3d68

  # uname -a
  Linux freedom 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  # cat /proc/version_signature
  Ubuntu 4.10.0-19.21-generic 4.10.8

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1418 F pulseaudio
pmj1986 F pulseaudio
   /dev/snd/controlC1:  gdm1418 F pulseaudio
pmj1986 F pulseaudio
  Date: Sun Apr 23 09:56:20 2017
  HibernationDevice: RESUME=UUID=d572808f-6762-4035-abbc-22fab43c88a5
  InstallationDate: Installed on 2016-12-02 (1

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Paul]

Just to clarify, the fixed kernel got released via both software update
and ISO right? I'm asking because if that's the case, my issue still
persists.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Yoga 3 11"
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Paul]

I tried to report this ages ago. The people at AskUbuntu shut my request
for help down.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects Acer Aspire E5-771G.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Paul]

Link to my report that got closed:
https://askubuntu.com/questions/939961/ubuntu-17-10-update-broke-my-bios

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects Acer Aspire E5-771G.

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Paul]

I didn't know that people couldn't see linked deleted asks, apologies
everyone. Here's a screenshot.

** Attachment added: "askubuntubiosissues.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+attachment/5025410/+files/askubuntubiosissues.png

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Committed
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Dell Insperion (with Insyde Software BIOS)

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Paul]

Just in case anyone is actually reading the comments before they post in
this bug. If you're unaffected, there's no need to post. Live your life
happily. That goes doubly if your device isn't even listed in the
initial bug post.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  SRU Justification

  Impact: Many users are reporting issues with bios corruption with
  17.10. This seems to stem from enabling the intel-spi-* drivers in the
  kernel, which don't appear to be ready for use on end-user machines.

  Fix: Disable this driver.

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (20/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  The bug also affects:
  Acer Aspire E5-771G
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Dell XPS 13 9350 I7.

  Bug may effect machines from any manufacturer that uses BIOS based on
  Insyde Software

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  Architecture: amd64
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[Paul]

For the love of all things holy, can someone tell me how to ban Lucy
Pahasta (Sidzen)?

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in linux-oem source package in Artful:
  Invalid
Status in linux package in openSUSE:
  New

Bug description:
  Description: An update to linux kernel on Ubuntu 17.10 that enabled
  the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
  Settings being not stored, USB Boot impossible and EFI entries read-
  only.

  Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
  affected machines still suffered from a broken BIOS.

  Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
  Linux and BIOS should be restored to a working state.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE
  Acer TravelMate B113
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Paul]

Hi, I've seen the solution that Anthony posted and I'm grateful, but I
have a few questions.

1/ If it's as simple as updating/replacing the kernel, why hasn't this
fix been rolled out as a system/software update?

2/ When is it likely to roll out as an update?

3/ a/ Has the download been updated with a non-broken kernel? b/ This
debacle has allowed a lot of system degradation to take place on my
system to the point that I need to reinstall 17.10, this doesn't seem to
be a possibility right now, or am I wrong?

4/ What changes have been implemented over at AskUbuntu to ensure that
users like myself who a/ test pre-release software are able to be
supported and b/ Do not have issues such as a report of a broken bios
dismissed/deleted before they're investigated adequately and escalated
and thus stem the issue ballooning into an issue of this magnitude in
the future?

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our ma

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Paul]

@ Steve Langasek (vorlon)
> I do not know what "system degradation" you refer to that would be related
> to this bug and would warrant a reinstallation. If you need to reinstall
> currently, the supported path is to install either Ubuntu 16.04 LTS or
> Ubuntu 17.04 and upgrade.

My browser has become disassociated with its launcher icon, my swap disk
has issues and I can't launch any Virtual Boxes. There's probably more,
these are all issues that I suspect a reinstall would solve. Also
downgrading isn't an option, hence all four questions that I asked.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Paul]

@ Paul Sladen (sladen)
There's no need to file bugs for those issues, I was merely attesting as to why 
I need to reinstall 17.10, which requires a working BIOS and a working ISO.

Though if you're able to answer the questions raised in #459, I'd
appreciate the answers.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-edge source package in Xenial:
  Fix Released
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
  drivers results in a serial flash that is read only in Intel Broadwell
  and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

  Symptoms:
   * BIOS settings cannot be saved
   * USB Boot impossible
   * EFI entries read-only.

  ---

  Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
  the kernel so it is not compiled with Intel SPI support. But previous
  affected machines still suffered from a broken BIOS.

  Repair: If you still can boot into Ubuntu, you can recover your BIOS
  with the following steps:

  1. Boot into Ubuntu
  2. Download 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  3. Install the downloaded package:
    $ sudo dpkg -i 
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
  4. Make sure the kernel is installed without any error. Once installed, 
reboot.
  5. At grub, choose the newly installed kernel. You can choose the "recovery" 
mode.
  6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
  7. In case your BIOS is not recovered, reboot to the new kernel, then reboot 
*once again* to the new kernel, do not enter BIOS settings before the reboot. 
After the second reboot, check BIOS.
  8. If your BIOS issue remains, download another kernel from 
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
 and use dpkg to install it, then repeat steps 4 to 6.

  After your BIOS is fixed, the kernel packages you just installed are
  no longer needed, you can remove it by running 'sudo dpkg -r linux-
  image-4.15.0-041500rc6-generic'.

  The patch used to build the linux v4.15 kernel in step 8 can be found
  at https://goo.gl/xUKJFR.

  ---

  Test Case: Fix has been verified by our HWE team on affected hardware.

  Regression Potential: Minimal, it's unlikely anyone is actually doing
  anything which requires this driver.

  ---

  Affected Machines:

  Lenovo B40-70
  Lenovo B50-70
  Lenovo B50-80
  Lenovo Flex-3
  Lenovo Flex-10
  Lenovo G40-30
  Lenovo G50-30
  Lenovo G50-70
  Lenovo G50-80
  Lenovo S20-30
  Lenovo U31-70
  Lenovo Y50-70
  Lenovo Y70-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo Yoga 2 11" - 20332
  Lenovo Z50-70
  Lenovo Z51-70
  Lenovo ideapad 100-15IBY

  Acer Aspire E5-771G
  Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
  Acer TravelMate B113
  Acer Swift SF314-52 (Fixed by 4.14.9)
  Toshiba Satellite S55T-B5233
  Toshiba Satellite L50-B-1R7
  Toshiba Satellite S50-B-13G
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  Acer Aspire E3-111-C0UM
  HP 14-r012la

  ---

  Affected serial flash devices by manufacturer part number, JEDEC ID 
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
  /* ESMT */
     f25l32pa, 0x8c2016
     f25l32qa, 0x8c4116
     f25l64qa, 0x8c4117
  /* GigaDevice */
     gd25q16, 0xc84015
     gd25q32, 0xc84016
     gd25lq32, 0xc86016
     gd25q64, 0xc84017
     gd25lq64c, 0xc86017
     gd25q128, 0xc84018
     gd25q256, 0xc84019
  /* Winbond */
     w25q16dw, 0xef6015
     w25q32dw, 0xef6016
     w25q64dw, 0xef6017
     w25q128fw, 0xef6018

  ---

  Original Description:

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+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 1555389] [NEW] system reboots after acpi error

[Paul]

Public bug reported:

system rebooting at least once per day after this error appears in
syslog

kernel: [2.786805] ACPI Warning: 0x1828-0x182f 
SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
kernel: [2.786814] ACPI Warning: 0x1c30-0x1c3f 
SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
kernel: [2.786817] ACPI Warning: 0x1c30-0x1c3f 
SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)
kernel: [2.786820] ACPI Warning: 0x1c00-0x1c2f 
SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
kernel: [2.786822] ACPI Warning: 0x1c00-0x1c2f 
SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)

any suggestions gratefully received

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-79-generic 3.13.0-79.123
ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
Uname: Linux 3.13.0-79-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-79-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CurrentDmesg:
 [   11.857681] init: plexmediaserver main process (986) terminated with status 
255
 [   11.857693] init: plexmediaserver main process ended, respawning
 [   15.156202] init: plymouth-upstart-bridge main process ended, respawning
Date: Thu Mar 10 00:03:10 2016
HibernationDevice: RESUME=/dev/mapper/ibiza--vg-swap_1
InstallationDate: Installed on 2014-07-26 (592 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
MachineType: Shuttle Inc. SZ87R
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic 
root=/dev/mapper/hostname--vg-root ro processor.nocst=1
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-79-generic N/A
 linux-backports-modules-3.13.0-79-generic  N/A
 linux-firmware 1.127.20
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.01
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FZ87
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.01:bd02/21/2014:svnShuttleInc.:pnSZ87R:pvrV1.0:rvnShuttleInc.:rnFZ87:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: SZ87R
dmi.product.version: V1.0
dmi.sys.vendor: Shuttle Inc.

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


** Tags: amd64 apport-bug trusty

** Attachment added: "output from ubuntu-bug"
   
https://bugs.launchpad.net/bugs/1555389/+attachment/4594423/+files/apport.linux-image-3.13.0-79-generic.pl_igwqt.apport

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

Title:
  system reboots after acpi error

Status in linux package in Ubuntu:
  New

Bug description:
  system rebooting at least once per day after this error appears in
  syslog

  kernel: [2.786805] ACPI Warning: 0x1828-0x182f 
SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
  kernel: [2.786814] ACPI Warning: 0x1c30-0x1c3f 
SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
  kernel: [2.786817] ACPI Warning: 0x1c30-0x1c3f 
SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)
  kernel: [2.786820] ACPI Warning: 0x1c00-0x1c2f 
SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
  kernel: [2.786822] ACPI Warning: 0x1c00-0x1c2f 
SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)

  any suggestions gratefully received

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-79-generic 3.13.0-79.123
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-79-generic.

[Kernel-packages] [Bug 1555389] Re: system reboots after acpi error

[Paul]

Hi Christopher,

Thanks for the prompt feedback. I was able to upgrade the bios but the
issue re-occurred 24 hours later.

As requested:

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2.05
01/04/2016

As far as I can tell there is no improvement, typically the problem
happens at least once every 24 hours.

Kind regards,
Paul

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

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

Title:
  system reboots after acpi error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  system rebooting at least once per day after this error appears in
  syslog

  kernel: [2.786805] ACPI Warning: 0x1828-0x182f 
SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
  kernel: [2.786814] ACPI Warning: 0x1c30-0x1c3f 
SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
  kernel: [2.786817] ACPI Warning: 0x1c30-0x1c3f 
SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)
  kernel: [2.786820] ACPI Warning: 0x1c00-0x1c2f 
SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
  kernel: [2.786822] ACPI Warning: 0x1c00-0x1c2f 
SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)

  any suggestions gratefully received

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-79-generic 3.13.0-79.123
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-79-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CurrentDmesg:
   [   11.857681] init: plexmediaserver main process (986) terminated with 
status 255
   [   11.857693] init: plexmediaserver main process ended, respawning
   [   15.156202] init: plymouth-upstart-bridge main process ended, respawning
  Date: Thu Mar 10 00:03:10 2016
  HibernationDevice: RESUME=/dev/mapper/ibiza--vg-swap_1
  InstallationDate: Installed on 2014-07-26 (592 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  MachineType: Shuttle Inc. SZ87R
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic 
root=/dev/mapper/hostname--vg-root ro processor.nocst=1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-79-generic N/A
   linux-backports-modules-3.13.0-79-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.01
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ87
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.01:bd02/21/2014:svnShuttleInc.:pnSZ87R:pvrV1.0:rvnShuttleInc.:rnFZ87:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: SZ87R
  dmi.product.version: V1.0
  dmi.sys.vendor: Shuttle Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555389/+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 1555389] Re: system reboots after acpi error

[Paul]

Thanks Christopher.
I'm going to test some new Crucial memory to rule that out - then will follow 
your suggestion r.e. upstream kernel.
Memtest doesn't reveal any errors but my Corsair isn't on the supported list so 
will test new Crucial memory for the next 48 hours to rule that out.
http://global.shuttle.com/news/productsSupportList?productId=1723

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

Title:
  system reboots after acpi error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  system rebooting at least once per day after this error appears in
  syslog

  kernel: [2.786805] ACPI Warning: 0x1828-0x182f 
SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
  kernel: [2.786814] ACPI Warning: 0x1c30-0x1c3f 
SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
  kernel: [2.786817] ACPI Warning: 0x1c30-0x1c3f 
SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)
  kernel: [2.786820] ACPI Warning: 0x1c00-0x1c2f 
SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
  kernel: [2.786822] ACPI Warning: 0x1c00-0x1c2f 
SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)

  any suggestions gratefully received

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-79-generic 3.13.0-79.123
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-79-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CurrentDmesg:
   [   11.857681] init: plexmediaserver main process (986) terminated with 
status 255
   [   11.857693] init: plexmediaserver main process ended, respawning
   [   15.156202] init: plymouth-upstart-bridge main process ended, respawning
  Date: Thu Mar 10 00:03:10 2016
  HibernationDevice: RESUME=/dev/mapper/ibiza--vg-swap_1
  InstallationDate: Installed on 2014-07-26 (592 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  MachineType: Shuttle Inc. SZ87R
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic 
root=/dev/mapper/hostname--vg-root ro processor.nocst=1
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-79-generic N/A
   linux-backports-modules-3.13.0-79-generic  N/A
   linux-firmware 1.127.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.01
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FZ87
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.01:bd02/21/2014:svnShuttleInc.:pnSZ87R:pvrV1.0:rvnShuttleInc.:rnFZ87:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: SZ87R
  dmi.product.version: V1.0
  dmi.sys.vendor: Shuttle Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555389/+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 1548587] Re: Ubuntu 15.10 VMWare guest won't show UI after upgrading to 4.2.0-30

[Paul]

I've just installed the update on 5 VMs and none of them would boot.

I've interrupted boot (by holding the Shift key whilst powering on the
VM) to bring up the Grub menu (it took several attempts to get it),
selected "Advanced options for Ubuntu", highlighted the previous kernel
("Ubuntu, with Linux 4.2.0-27-generic"), and booted.

Once the system came back up I logged in and did:

apt-get --purge remove  linux-image-4.2.0-30-generic linux-image-
extra-4.2.0-30-generic

My VM(s) will now reboot.

Looks like the new kernel is broke.

I'm running VMware Workstation Pro 12.1.0 build-3272444 on Windows 7
64-bit and my VMs are using open-vm-tools.

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

Title:
  Ubuntu 15.10 VMWare guest won't show UI after upgrading to 4.2.0-30

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed a fresh copy of Ubuntu 15.10 64-bit as a guest VM in
  VMWare Workstation 12.1.0.

  After installation, I am able to log into the system. I then ran the
  updater application to install the latest updates.

  After installing the updates and restarting, the system no longer
  shows any UI after booting. I am now faced with a black screen and a
  dash that does not blink. The system also does not respond to any
  inputs.

  I was able to get back into my system by holding shift to show the
  GRUB menu and boot using the 4.2.16 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548587/+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 1548587] Re: Ubuntu VMWare guest won't show UI after upgrading to 4.2.0-30.35, 3.19.0-51.57, 3.16.0-62.82

[Paul]

Thanks for putting in the effort to fix this - I'll check my VMs and
report back...

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

Title:
  Ubuntu VMWare guest won't show UI after upgrading to 4.2.0-30.35,
  3.19.0-51.57, 3.16.0-62.82

Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux-lts-wily source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  I installed a fresh copy of Ubuntu 15.10 64-bit as a guest VM in
  VMWare Workstation 12.1.0.

  After installation, I am able to log into the system. I then ran the
  updater application to install the latest updates.

  After installing the updates and restarting, the system no longer
  shows any UI after booting. I am now faced with a black screen and a
  dash that does not blink. The system also does not respond to any
  inputs.

  I was able to get back into my system by holding shift to show the
  GRUB menu and boot using the 4.2.16 kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548587/+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 1544737] [NEW] wireless does not work on aspire e15

[paul]

Public bug reported:

wireless could not be enabled

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Thu Feb 11 22:33:28 2016
InstallationDate: Installed on 2016-02-11 (0 days ago)
InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-lts-vivid
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  wireless does not work on aspire e15

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  wireless could not be enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Feb 11 22:33:28 2016
  InstallationDate: Installed on 2016-02-11 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1544737/+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 1355984] Re: Built in speakers do not work on iMac 14, 2 and iMac 14, 4

[Paul]

apport information

** Tags added: apport-collected trusty

** Description changed:

  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes
  
  
  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:
  
  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples
  
  The audio related parts of the output of # sudo lspci -vvnn is:
  
  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1355984/+attachment/4176504/+files/AlsaInfo.txt

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headp

[Kernel-packages] [Bug 1355984] BootDmesg.txt

[Paul]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1355984/+attachment/4176505/+files/BootDmesg.txt

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Lspci.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Lsusb.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] IwConfig.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] ProcEnviron.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] UdevDb.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] RfKill.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] WifiSyslog.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] ProcCpuinfo.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] ProcInterrupts.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] ProcModules.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] PulseList.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] UdevLog.txt

[Paul]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1355984/+attachment/4176518/+files/UdevLog.txt

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] CurrentDmesg.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] CRDA.txt

[Paul]

apport information

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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

Re: [Kernel-packages] [Bug 1355984] Re: Built in speakers do not work on iMac 14, 2 and iMac 14, 4

[Paul]

There are 2 internal speakers according to the system report in OSX.
Headphones work fine if I put a file with "options snd-hda-intel
model=imac27_122" in /etc/modprobe.dIt is the built in speakers that
don't work.  Headphone detection works.  If I open alsamixer and plug in
the headphones it mutes the speakers, when I unplug them it un-mutes the
speakers.  I just noticed something else interesting: I logged on to the
machine went to settings-->sound--test sound.  The test sounds "Front
Right" and "Front Left"  worked once then did not work again on subsequent
attempts there is no audio from applications and no volume adjust noise.
If I plug in the headphones I get all of the audio I am supposed to through
the headphones.


On Wed, Aug 13, 2014 at 1:03 AM, Raymond <1355...@bugs.launchpad.net> wrote:

> Node 0x0b [Pin Complex] wcaps 0x410101: Stereo
>   Control: name="Speaker Phantom Jack", index=0, device=0
>   Pincap 0x0050: OUT Balanced
>   Pin Default 0x90100112: [Fixed] Speaker at Int N/A
> Conn = Unknown, Color = Unknown
> DefAssociation = 0x1, Sequence = 0x2
> Misc = NO_PRESENCE
>   Pin-ctls: 0x00:
>   Delay: 1 samples
>   Connection: 1
>
> how many speaker since the node support balanced  mode ?
>
> speaker is muted by the driver when headphone is plugged
>
>
> control.17 {
> iface CARD
> name 'Headphone Jack'
> value true
> comment {
> access read
> type BOOLEAN
> count 1
> }
> }
>
> do you mean Jack detection of headphone in incorrect ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1355984
>
> Title:
>   Built in speakers do not work on iMac 14,2 and iMac 14,4
>
> Status in “alsa-driver” package in Ubuntu:
>   New
> Status in “linux” package in Ubuntu:
>   Incomplete
>
> Bug description:
>   No sound from internal speakers but OK from plugged in headphones.
> Running Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio
> (S/PDIF DigitalAudio output). Headphones appear to be using analogue
> output. Both loud and clear using OSX 10.9.4.
>   Have tried all fixes found on many Linux distro websites but no success.
> Also tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and
> Ubuntu 13.04, 13.10 (same problem as Xubuntu).
>   Have all PulseAudio utils installed, all devices are listed but only
> analogue volume meter shows outputs when playing but as above nothing from
> speakers.
>   AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at
> 00 but cannot be adjusted.
>   What is the problem? I sense there is a simple solution here, if only to
> ger the analogue output via the internal speakers.
>   This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier
> iMac which were solved simply using AlsaMixer.
>   That I have installed Ubuntu on my new iMac shows how much I prefer
> Linux to OSX, this small problem is spoiling my enjoyment of your great OS.
>   Thank you in anticipation.
>   Ed Hughes
>
>
>   I have the same issue on an iMac 14,2. I think the audio hardware in the
> iMac 14,2 and 14,4 is probably the same. To get the headphones to work I
> upgraded to the daily ALSA snapshot found here:
> https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
>   Neither the headphones or the internal speakers work with the default
> configuration so I did this: # echo "options snd-hda-intel
> model=imac27_122" >> /etc/modprobe.d/imac_local.conf followed by a reboot.
> This fix works on every other Mac I have tested so far, but for this
> machine it only fixes the headphone audio. The output of alsa-info.sh is
> here:
> http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a
> I have downloaded the HDA Analyzer tool but I can't seem to get the
> internal speakers to work correctly in any consistent way, although they do
> occasionally work correctly for a few seconds. I can consistently make
> sound come from the speakers if I chose VREF = 50 or 80 in Node[0x0d]pin
> but it sounds like I am using a much smaller lower quality speaker when I
> do that. Here is the text dump for that node configuration:
>
>   Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
> Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
> Amp-In vals: [0x00 0x00]
> Pincap 0x1764: IN Detect Balance
>   Vref caps: HIZ 50 GRD 80
> Pin Default 0x40f0: [N/A] Line Out at Ext N/A
>   Conn = Unknown, Color = Unknown
>   DefAssociation = 0xf, Sequence = 0x0
> Unsolicited: tag=0x00, enabled=0
> Power: setting=D0, actual=D0
> Delay: 1 samples
>
>   The audio related parts of the output of # sudo lspci -vvnn is:
>
>   00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series
> Chipset High Definition Audio Controller [8086:8c2

[Kernel-packages] [Bug 1355984] Re: Built in speakers do not work on iMac 14, 2 and iMac 14, 4

[Paul]

tag: 'kernel-bug-exists-upstream'

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Re: Built in speakers do not work on iMac 14, 2 and iMac 14, 4

[Paul]

I just installed the kernel that you linked and the issue still exists
in that kernel.  I also installed the latest v3.17 kernel [0].  The
issue exists in that kernel as well.  However, something appears to have
changed in these latest kernel builds.  If I go to system
preferences-->sound-->test sound, the "front right" and "front left"
test sounds consistently work and other sounds work while those sounds
are playing and sometimes for a few seconds after the test sounds play.
The line "options snd-hda-intel model=imac27_122" is still required in
/etc/modprobe.d/imac_local.conf for headphones to function and for this
limited/intermittent speaker functionality.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc1-utopic/

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Re: Built in speakers do not work on iMac 14, 2 and iMac 14, 4

[Paul]

tags: 'kernel-bug-exists-upstream'

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Re: Built in speakers do not work on iMac 14, 2 and iMac 14, 4

[Paul]

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

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Re: Built in speakers do not work on iMac 14, 2

[Paul]

Actually, headphone fix still works in v3.17-rc4-utopic.  My bad.

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

Title:
  Built in speakers do not work on iMac 14,2

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Fix Committed

Bug description:
  Xubuntu 14.04 on iMac 14,2 no sound from internal speakers. Loud and clear 
using OSX 10.9.4. Also tried installing Lubuntu (no sound at all) Linux Mint 16 
& 17 and Ubuntu 13.04, 13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.

  To get the headphones to work I upgraded to the daily ALSA snapshot
  found here: https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages

  The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:
  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
    Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
    Amp-In vals: [0x00 0x00]
    Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
    Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
    Unsolicited: tag=0x00, enabled=0
    Power: setting=D0, actual=D0
    Delay: 1 samples

  WORKAROUND for the headphones only: # echo "options snd-hda-intel
  model=imac27_122" >> /etc/modprobe.d/imac_local.conf followed by a
  reboot.

  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ladmin 1910 F pulseaudio
   /dev/snd/controlC0:  ladmin 1910 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-08-11 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Apple Inc. iMac14,2
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic.efi.signed 
root=UUID=2f77d057-5c9c-42d8-b2c0-18507f43420e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-33-generic N/A
   linux-backports-modules-3.13.0-33-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty trusty
  Uname: Linux 3.13.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM142.88Z.0118.B02.1403141302
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-27ADBB7B4CEE8E61
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-27ADBB7B4CEE8E61
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM142.88Z.0118.B02.1403141302:bd03/14/2014:svnAppleInc.:pniMac14,2:pvr1.0:rvnAppleInc.:rnMac-27ADBB7B4CEE8E61:rvriMac14,2:cvnAppleInc.:ct13:cvrMac-27ADBB7B4CEE8E61:
  dmi.product.name: iMac14,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Re: Built in speakers do not work on iMac 14, 2

[Paul]

I have been a bit busy but I finally got a chance to test this with some
newer kernels.  I tested v3.17-rc3-utopic and v3.17-rc4-utopic kernels.
Internal speakers still do not work and the headphone fix stopped
working in both of these kernels.

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

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

Title:
  Built in speakers do not work on iMac 14,2

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Fix Committed

Bug description:
  Xubuntu 14.04 on iMac 14,2 no sound from internal speakers. Loud and clear 
using OSX 10.9.4. Also tried installing Lubuntu (no sound at all) Linux Mint 16 
& 17 and Ubuntu 13.04, 13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.

  To get the headphones to work I upgraded to the daily ALSA snapshot
  found here: https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages

  The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:
  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
    Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
    Amp-In vals: [0x00 0x00]
    Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
    Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
    Unsolicited: tag=0x00, enabled=0
    Power: setting=D0, actual=D0
    Delay: 1 samples

  WORKAROUND for the headphones only: # echo "options snd-hda-intel
  model=imac27_122" >> /etc/modprobe.d/imac_local.conf followed by a
  reboot.

  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ladmin 1910 F pulseaudio
   /dev/snd/controlC0:  ladmin 1910 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-08-11 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Apple Inc. iMac14,2
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic.efi.signed 
root=UUID=2f77d057-5c9c-42d8-b2c0-18507f43420e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-33-generic N/A
   linux-backports-modules-3.13.0-33-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty trusty
  Uname: Linux 3.13.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM142.88Z.0118.B02.1403141302
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-27ADBB7B4CEE8E61
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-27ADBB7B4CEE8E61
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM142.88Z.0118.B02.1403141302:bd03/14/2014:svnAppleInc.:pniMac14,2:pvr1.0:rvnAppleInc.:rnMac-27ADBB7B4CEE8E61:rvriMac14,2:cvnAppleInc.:ct13:cvrMac-27ADBB7B4CEE8E61:
  dmi.product.name: iMac14,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Re: Built in speakers do not work on iMac 14, 2

[Paul]

I changed the status to Fix Commited.  That seems like a good
description of the current state of this.

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

Title:
  Built in speakers do not work on iMac 14,2

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Fix Committed

Bug description:
  Xubuntu 14.04 on iMac 14,2 no sound from internal speakers. Loud and clear 
using OSX 10.9.4. Also tried installing Lubuntu (no sound at all) Linux Mint 16 
& 17 and Ubuntu 13.04, 13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.

  To get the headphones to work I upgraded to the daily ALSA snapshot
  found here: https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages

  The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:
  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
    Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
    Amp-In vals: [0x00 0x00]
    Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
    Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
    Unsolicited: tag=0x00, enabled=0
    Power: setting=D0, actual=D0
    Delay: 1 samples

  WORKAROUND for the headphones only: # echo "options snd-hda-intel
  model=imac27_122" >> /etc/modprobe.d/imac_local.conf followed by a
  reboot.

  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ladmin 1910 F pulseaudio
   /dev/snd/controlC0:  ladmin 1910 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-08-11 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Apple Inc. iMac14,2
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic.efi.signed 
root=UUID=2f77d057-5c9c-42d8-b2c0-18507f43420e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-33-generic N/A
   linux-backports-modules-3.13.0-33-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty trusty
  Uname: Linux 3.13.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM142.88Z.0118.B02.1403141302
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-27ADBB7B4CEE8E61
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-27ADBB7B4CEE8E61
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM142.88Z.0118.B02.1403141302:bd03/14/2014:svnAppleInc.:pniMac14,2:pvr1.0:rvnAppleInc.:rnMac-27ADBB7B4CEE8E61:rvriMac14,2:cvnAppleInc.:ct13:cvrMac-27ADBB7B4CEE8E61:
  dmi.product.name: iMac14,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Re: Built in speakers do not work on iMac 14, 2

[Paul]

Wait, internal speakers appear to be working as well.  Not sure why I
wasn't getting anything before but the last reboot with kernel
v3.17-rc4-utopic appears to have fixed it.

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

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

Title:
  Built in speakers do not work on iMac 14,2

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Fix Committed

Bug description:
  Xubuntu 14.04 on iMac 14,2 no sound from internal speakers. Loud and clear 
using OSX 10.9.4. Also tried installing Lubuntu (no sound at all) Linux Mint 16 
& 17 and Ubuntu 13.04, 13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.

  To get the headphones to work I upgraded to the daily ALSA snapshot
  found here: https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages

  The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:
  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
    Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
    Amp-In vals: [0x00 0x00]
    Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
    Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
    Unsolicited: tag=0x00, enabled=0
    Power: setting=D0, actual=D0
    Delay: 1 samples

  WORKAROUND for the headphones only: # echo "options snd-hda-intel
  model=imac27_122" >> /etc/modprobe.d/imac_local.conf followed by a
  reboot.

  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ladmin 1910 F pulseaudio
   /dev/snd/controlC0:  ladmin 1910 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-08-11 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Apple Inc. iMac14,2
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic.efi.signed 
root=UUID=2f77d057-5c9c-42d8-b2c0-18507f43420e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-33-generic N/A
   linux-backports-modules-3.13.0-33-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty trusty
  Uname: Linux 3.13.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM142.88Z.0118.B02.1403141302
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-27ADBB7B4CEE8E61
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-27ADBB7B4CEE8E61
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM142.88Z.0118.B02.1403141302:bd03/14/2014:svnAppleInc.:pniMac14,2:pvr1.0:rvnAppleInc.:rnMac-27ADBB7B4CEE8E61:rvriMac14,2:cvnAppleInc.:ct13:cvrMac-27ADBB7B4CEE8E61:
  dmi.product.name: iMac14,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Re: Built in speakers do not work on iMac 14, 2

[Paul]

Just rebooted again with kernel  v3.17-rc4-utopic.  Now headphones are
working but internal speakers do not work when they are unplugged.  My
results are so inconsistent, changed status back to confirmed.

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

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

Title:
  Built in speakers do not work on iMac 14,2

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 14.04 on iMac 14,2 no sound from internal speakers. Loud and clear 
using OSX 10.9.4. Also tried installing Lubuntu (no sound at all) Linux Mint 16 
& 17 and Ubuntu 13.04, 13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.

  To get the headphones to work I upgraded to the daily ALSA snapshot
  found here: https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages

  The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:
  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
    Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
    Amp-In vals: [0x00 0x00]
    Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
    Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
    Unsolicited: tag=0x00, enabled=0
    Power: setting=D0, actual=D0
    Delay: 1 samples

  WORKAROUND for the headphones only: # echo "options snd-hda-intel
  model=imac27_122" >> /etc/modprobe.d/imac_local.conf followed by a
  reboot.

  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ladmin 1910 F pulseaudio
   /dev/snd/controlC0:  ladmin 1910 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-08-11 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Apple Inc. iMac14,2
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic.efi.signed 
root=UUID=2f77d057-5c9c-42d8-b2c0-18507f43420e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-33-generic N/A
   linux-backports-modules-3.13.0-33-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty trusty
  Uname: Linux 3.13.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM142.88Z.0118.B02.1403141302
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-27ADBB7B4CEE8E61
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac14,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-27ADBB7B4CEE8E61
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM142.88Z.0118.B02.1403141302:bd03/14/2014:svnAppleInc.:pniMac14,2:pvr1.0:rvnAppleInc.:rnMac-27ADBB7B4CEE8E61:rvriMac14,2:cvnAppleInc.:ct13:cvrMac-27ADBB7B4CEE8E61:
  dmi.product.name: iMac14,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1355984] Re: Built in speakers do not work on iMac 14, 2 and iMac 14, 4

[Paul]

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

** Tags added: kernel-sound

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

Title:
  Built in speakers do not work on iMac 14,2 and iMac 14,4

Status in “alsa-driver” package in Ubuntu:
  New
Status in “linux-meta” package in Ubuntu:
  New

Bug description:
  No sound from internal speakers but OK from plugged in headphones. Running 
Xubuntu 14.04 on partitioned  iMac 14,4 which has Intel HD Audio (S/PDIF 
DigitalAudio output). Headphones appear to be using analogue output. Both loud 
and clear using OSX 10.9.4.
  Have tried all fixes found on many Linux distro websites but no success. Also 
tried installing Lubuntu (no sound at all) Linux Mint 16 & 17 and Ubuntu 13.04, 
13.10 (same problem as Xubuntu).
  Have all PulseAudio utils installed, all devices are listed but only analogue 
volume meter shows outputs when playing but as above nothing from speakers.
  AlsaMixer shows S/PDIF (highlighted), SPDIF 1 & S/PDIF 2 not MM, set at 00 
but cannot be adjusted.
  What is the problem? I sense there is a simple solution here, if only to ger 
the analogue output via the internal speakers. 
  This is reminiscent of problemsI I had with Unbuntu 12.04 on an earlier iMac 
which were solved simply using AlsaMixer.
  That I have installed Ubuntu on my new iMac shows how much I prefer Linux to 
OSX, this small problem is spoiling my enjoyment of your great OS.
  Thank you in anticipation.
  Ed Hughes


  I have the same issue on an iMac 14,2. I think the audio hardware in the iMac 
14,2 and 14,4 is probably the same. To get the headphones to work I upgraded to 
the daily ALSA snapshot found here: 
https://code.launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages
  Neither the headphones or the internal speakers work with the default 
configuration so I did this: # echo "options snd-hda-intel model=imac27_122" >> 
/etc/modprobe.d/imac_local.conf followed by a reboot. This fix works on every 
other Mac I have tested so far, but for this machine it only fixes the 
headphone audio. The output of alsa-info.sh is here: 
http://www.alsa-project.org/db/?f=08cf13552b70232c96fea9293fdd54066243d79a I 
have downloaded the HDA Analyzer tool but I can't seem to get the internal 
speakers to work correctly in any consistent way, although they do occasionally 
work correctly for a few seconds. I can consistently make sound come from the 
speakers if I chose VREF = 50 or 80 in Node[0x0d]pin but it sounds like I am 
using a much smaller lower quality speaker when I do that. Here is the text 
dump for that node configuration:

  Node 0x0d [Pin Complex] wcaps 0x41048b: Stereo Amp-In
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals: [0x00 0x00]
Pincap 0x1764: IN Detect Balance
  Vref caps: HIZ 50 GRD 80
Pin Default 0x40f0: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0xf, Sequence = 0x0
Unsolicited: tag=0x00, enabled=0
Power: setting=D0, actual=D0
Delay: 1 samples

  The audio related parts of the output of # sudo lspci -vvnn is:

  00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
   Subsystem: Intel Corporation Device [8086:7270]
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1355984/+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 1320070] Re: Realtek Wifi card RTL8723BE drops connection with MSI enabled

[Paul]

Thanks https://launchpad.net/~pqwoerituytrueiwoq, this worked for me ...

Cheers,

Paul

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

Title:
  Realtek Wifi card RTL8723BE drops connection with MSI enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released

Bug description:
  As my testing result with ThinkPad E540 and other users' report[1],
  RTL8723BE drops connection with MSI enabled, need to backport
  329d6e299f92a591acb3a80f6d597a5f9dce7e6d "rtlwifi: rtl8723be: disable
  MSI interrupts mode"

  [1] https://bugs.launchpad.net/bugs/1240940

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320070/+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 1574382] Re: Default sound device changes after resuming system

[paul]

This may be a bug in Pulseaudio introduced in version 8 - at least it
was in my case. The issue is fixed in the newest release of Pulseaudio
(Automatic routing improvements) -
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/9.0/.

*It did not appear in Ubuntu 14.04 (which uses version 4) and does appear in 
16.10 (which uses version 8).
*I could fix it through brute force be making the *-default-sink file in 
~/.config/pulse ro.
*I fixed it through the temporary fix as outlined in this post - 
https://lists.freedesktop.org/archives/pulseaudio-bugs/2016-February/010460.html.
 Please note that this may introduce other regressions. Read the entire post to 
find out what. The regressions should not affect the vast majority of users.

Hope this helps.

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

Title:
  Default sound device changes after resuming system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 and 15.10, too
  After resuming from sleep, the default sound device is set to another one, I 
have to go in the sound settings and click on the primary one to get back. Did 
not see this bug after rebooting or power on.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vanyo  2021 F pulseaudio
   /dev/snd/controlC0:  vanyo  2021 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=09b833a2-0d71-4754-acb3-f94c71921de4
  InstallationDate: Installed on 2016-02-26 (59 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=155d6a5c-c997-4711-a3d2-bd61d31d2cff ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722
  dmi.board.name: NUC5i7RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H73774-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i7RYB:rvrH73774-102:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574382/+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 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"

[Paul]

Had it happen today for the first time.  Other than Ubuntu updates no
changes to the configuration in months so it seems to be a very recent
change.  The last time I used the dual monitor config was 5 days ago,
with no troubles at all.  Now the 2nd monitor (4k) goes blank and comes
back about every 5 seconds.  Tried resetting display resolution (and
then back again) and may have helped for now.

Latest Dell XPS13 dev edition running Ubuntu 15.04.

uname
Linux crom 3.19.0-33-generic #38-Ubuntu SMP Fri Nov 6 18:18:12 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

dmesg
[27734.104083] [drm:gen8_irq_handler [i915_bpo]] *ERROR* The master control 
interrupt lied (SDE)!
(many times)

lspci
00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated 
Graphics (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation Broadwell-U Camarillo 
Device (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller 
(rev 03)
00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio 
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 
(rev e3)
00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 
(rev e3)
00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller 
(rev 03)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller 
[AHCI Mode] (rev 03)
00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP 
Thermal Management Controller (rev 03)
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5249 PCI 
Express Card Reader (rev 01)
02:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless 
Network Adapter (rev 03)

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

Title:
  dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control
  interrupt lied (SDE)!"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a recent intel NUC using i915 graphics, I get the following errors
  in dmesg:

  [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt
  lied (SDE)!

  There are two monitors connected to this box, one with mini-
  HDMI->HDMI, one with mini-DP->HDMI cable.

  Maybe related:

  https://bugs.freedesktop.org/show_bug.cgi?id=80896

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic 3.19.0.26.25
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Wed Aug 26 10:07:31 2015
  InstallationDate: Installed on 2015-08-01 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1488719/+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 1814481] Re: Keychron K1 keyboard not working

[Paul]

I was having the same issue on the Vissles 84 mech keyboard, but

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/comments/19

mostly fixed it. F11 & F12 don't seem to be affected by the fix, they
still act as multimedia volume keys regardless of whether I hold the fn
key or not.

To clarify, my keyboard is also bluetooth but I use it wired due to
hardware issues on the linux PC. I am a VERY recent Linux user. My
problem was pretty much the same as OP: no fn keys, they only registered
as multimedia even with the fn key held. No fix in BIOS. I used the same
keyboard on a windows computer and it worked fine.

Anyway, thanks!  Was nervous since I don't know too much about the
command line yet, but it seems mostly fixed now.

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

Title:
  Keychron K1 keyboard not working

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
 

[Kernel-packages] [Bug 2031492] Re: zfs-dkms: support Linux 6.5

[Paul]

This doesn't affect me on mantic with the latest packages/kernel from
mantic updates ppa.

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

Title:
  zfs-dkms: support Linux 6.5

Status in zfs-linux package in Ubuntu:
  New
Status in zfs-linux source package in Mantic:
  New

Bug description:
  [Impact]

  zfs-dkms fails to build with the latest 6.5 kernel in Mantic:

  
  configure: error: 
*** None of the expected "bops->release()" interfaces were detected.
*** This may be because your kernel version is newer than what is
*** supported, or you are using a patched custom kernel with
*** incompatible modifications.
***
*** ZFS Version: zfs-2.2.0~rc1-0ubuntu2
*** Compatible Kernels: 3.10 - 6.3

  [Test case]

   $ sudo apt install zfs-dkms

  [Fix]

  Upstream zfs can now be compiled with kernel 6.5, cherry pick the
  minimum subset of patches to support the new kernel ABI.

  [Regression potential]

  We may experience filesystem regressions or potentially kernel crashes
  with kernels >= 6.5.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: zfs-dkms 2.2.0~rc1-0ubuntu2
  ProcVersionSignature: User Name 6.5.0-4.4-generic 6.5.0-rc6
  Uname: Linux 6.5.0-4-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230801
  CloudSubPlatform: config-disk (/dev/vdb)
  Date: Wed Aug 16 07:45:37 2023
  PackageArchitecture: all
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2031492/+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 2044657] Re: Multiple data corruption issues in zfs

[Paul]

Sorry I can't tell, is the data corruption bug backported into mantic
2.2.0?  Or is mantic still not protected?

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

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Lunar:
  Confirmed
Status in zfs-linux source package in Mantic:
  Incomplete
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  
  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will 
introduce slight slow down on amd64 (for hw accelerated assembly code-paths 
only in the encryption primitives)
   
   * Uncertain of the perfomance impact of the extra checks in dnat patch fix 
itself. Possibly affecting speed of operation, at the benefit of correctness.

  [ Other Info ]
   
   * https://github.com/openzfs/zfs/pull/15571 is most current consideration of 
affairs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+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 1866879] [NEW] Failure to boot on linux-image-5.3.0-40-generic

[Paul]

Public bug reported:

I installed Ubuntu on the laptop, rebooted and everything was fine. I
did an upgrade to all packages and found that when I rebooted, it fails
to load.

I found out that a workaround is to select linux-image-5.3.0-18-generic
in grub which leads me to think that the issue is related to the upgrade
of the linux-image 5.3.0 package.

To be clear, linux-image-5.3.0-18-generic works but linux-
image-5.3.0-40-generic does not.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-40-generic 5.3.0-40.32
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  paul   2027 F pulseaudio
 /dev/snd/controlC0:  paul   2027 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 10 18:25:57 2020
InstallationDate: Installed on 2020-03-09 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-18-generic N/A
 linux-backports-modules-5.3.0-18-generic  N/A
 linux-firmware1.183.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X512DA.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X512DA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: linux (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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1866879

Title:
  Failure to boot on linux-image-5.3.0-40-generic

Status in linux package in Ubuntu:
  New

Bug description:
  I installed Ubuntu on the laptop, rebooted and everything was fine. I
  did an upgrade to all packages and found that when I rebooted, it
  fails to load.

  I found out that a workaround is to select linux-
  image-5.3.0-18-generic in grub which leads me to think that the issue
  is related to the upgrade of the linux-image 5.3.0 package.

  To be clear, linux-image-5.3.0-18-generic works but linux-
  image-5.3.0-40-generic does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paul   2027 F pulseaudio
   /dev/snd/controlC0:  paul   2027 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 18:25:57 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 

[Kernel-packages] [Bug 1866879] Re: Failure to boot on linux-image-5.3.0-40-generic

[Paul]

The link in my previous comment is the second half, the first half is
here youtu.be/zuj4Sb9sxlI

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

Title:
  Failure to boot on linux-image-5.3.0-40-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu on the laptop, rebooted and everything was fine. I
  did an upgrade to all packages and found that when I rebooted, it
  fails to load.

  I found out that a workaround is to select linux-
  image-5.3.0-18-generic in grub which leads me to think that the issue
  is related to the upgrade of the linux-image 5.3.0 package.

  To be clear, linux-image-5.3.0-18-generic works but linux-
  image-5.3.0-40-generic does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paul   2027 F pulseaudio
   /dev/snd/controlC0:  paul   2027 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 18:25:57 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+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 1866879] Re: Failure to boot on linux-image-5.3.0-40-generic

[Paul]

Hi, I've uploaded a video to Youtube, see youtu.be/3jdXe3i3Ox0 , of what
it does and also what I do to make it work. I hope this is what you're
after. I've attached dmesg but I had to restart as you saw in the video
so not sure if it's as useful. Happy to run any other tests or what.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+attachment/5336296/+files/dmesg

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

Title:
  Failure to boot on linux-image-5.3.0-40-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu on the laptop, rebooted and everything was fine. I
  did an upgrade to all packages and found that when I rebooted, it
  fails to load.

  I found out that a workaround is to select linux-
  image-5.3.0-18-generic in grub which leads me to think that the issue
  is related to the upgrade of the linux-image 5.3.0 package.

  To be clear, linux-image-5.3.0-18-generic works but linux-
  image-5.3.0-40-generic does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paul   2027 F pulseaudio
   /dev/snd/controlC0:  paul   2027 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 18:25:57 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+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 1866879] Re: Failure to boot on linux-image-5.3.0-40-generic

[Paul]

Another log file

** Attachment added: "for i in {1..15}; do journalctl -k -b $i | grep 'Linux 
version'; done"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+attachment/5336433/+files/boots

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

Title:
  Failure to boot on linux-image-5.3.0-40-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu on the laptop, rebooted and everything was fine. I
  did an upgrade to all packages and found that when I rebooted, it
  fails to load.

  I found out that a workaround is to select linux-
  image-5.3.0-18-generic in grub which leads me to think that the issue
  is related to the upgrade of the linux-image 5.3.0 package.

  To be clear, linux-image-5.3.0-18-generic works but linux-
  image-5.3.0-40-generic does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paul   2027 F pulseaudio
   /dev/snd/controlC0:  paul   2027 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 18:25:57 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+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 1866879] Re: Failure to boot on linux-image-5.3.0-40-generic

[Paul]

Hi, I ran the steps as requested. After a few minutes of the blank
screen I noticed the fan turns on so I guess something is happening. I
don't see anything on the screen after it goes blank. I've attached the
logs as requested

** Attachment added: "journalctl -b -1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+attachment/5336432/+files/all

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

Title:
  Failure to boot on linux-image-5.3.0-40-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu on the laptop, rebooted and everything was fine. I
  did an upgrade to all packages and found that when I rebooted, it
  fails to load.

  I found out that a workaround is to select linux-
  image-5.3.0-18-generic in grub which leads me to think that the issue
  is related to the upgrade of the linux-image 5.3.0 package.

  To be clear, linux-image-5.3.0-18-generic works but linux-
  image-5.3.0-40-generic does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paul   2027 F pulseaudio
   /dev/snd/controlC0:  paul   2027 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 18:25:57 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+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 1866879] Re: Failure to boot on linux-image-5.3.0-40-generic

[Paul]

Add a photo of what the screen shows, not much help but I want to be as
complete as possible

** Attachment added: "Photo of blank screen"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+attachment/5336434/+files/IMG_20200313_112718.jpg

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

Title:
  Failure to boot on linux-image-5.3.0-40-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu on the laptop, rebooted and everything was fine. I
  did an upgrade to all packages and found that when I rebooted, it
  fails to load.

  I found out that a workaround is to select linux-
  image-5.3.0-18-generic in grub which leads me to think that the issue
  is related to the upgrade of the linux-image 5.3.0 package.

  To be clear, linux-image-5.3.0-18-generic works but linux-
  image-5.3.0-40-generic does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-40-generic 5.3.0-40.32
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paul   2027 F pulseaudio
   /dev/snd/controlC0:  paul   2027 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 18:25:57 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X512DA.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X512DA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX512DA.308:bd11/05/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866879/+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 2025538] Re: Unrequested kernel update

[Paul]

It seems like NVIDIA Driver metapackage 535 leads to kernel panics in my
case while NVIDIA Driver metapackage 525 works fine.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2025538

Title:
  Unrequested kernel update

Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in linux-signed-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  In Progress
Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was
  informed that new packages are available and I just hit update. This
  caused my system running 5.15.0-76-generic to be switched to
  5.19.0-1010-nvidia-lowlatency.

  I noted this as I was now running into bugs like
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/2017980

  The update was, as stated in history.log:

  Start-Date: 2023-07-01  00:25:40
  Commandline: packagekit role='update-packages'
  Requested-By: cm (1000)
  Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, 
automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 
(5.19.0-1010.10, automatic), 
linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, 
automatic)
  Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), 
modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2)

  => This simple update was changing my kernel from 5.15 to 5.19 without
  a request from my side

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10
  ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17
  Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul  1 21:16:09 2023
  InstallationDate: Installed on 2018-10-10 (1724 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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 2080635] Re: Wrong Battery Reading after Wake from S3 Sleep

[Paul]

Hi Matthew,

Awesome news,
Thanks a lot for the fast fix!

I've upgraded to 24.04 already, so, hopefully, would be able to check it
quite soon.

Cheers!

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

Title:
  Wrong Battery Reading after Wake from S3 Sleep

Status in linux-hwe-6.8 package in Ubuntu:
  Fix Released

Bug description:
  The bug was reported in
  https://bugzilla.kernel.org/show_bug.cgi?id=218881 and fixed from
  6.9.7 stable

  Ubuntu 22.04.4 LTS is on kernel 6.8.0

  Can the fix be ported to 6.8.x ?

  My system:
  Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.8/+bug/2080635/+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 1831974] Re: turbo boost doesnt work on battery in ubuntu for 8th gen intel core processors , Turbo boost works only when charger is plugged in . This reduces clock speed and ca

[Paul White]

** Changed in: debian
   Status: New => Incomplete

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

Title:
  turbo boost doesnt work on battery in ubuntu for 8th gen intel core
  processors , Turbo boost works only when charger is plugged in . This
  reduces clock speed and causes single core performance to throttle

Status in linux package in Ubuntu:
  Incomplete
Status in Debian:
  Incomplete

Bug description:
  Tried reinstalling and other versions of debian distro like PopOs , on every 
install turbo boost doesnt seem to work even when power plan is changed to high 
performance for 8th gen intel laptop cpu. 
  /sys/devices/system/cpu/intel_pstate/no_turbo is set to 1 , and the value 
cannot be changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831974/+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 1840796] Re: sound not working in 4.15.0-58, but does in 4.15.0-55

[Paul White]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1840796

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  sound not working in 4.15.0-58, but does in 4.15.0-55

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  First excuse me, this is my very first bug report, if anything is
  missing, notify me on email.

  --

  I find it rather hard to believe, but since I installed kernel:

  > 4.15.0-**58**

  several days ago, my sound on Linux Mint 19.2 Cinnamon stopped
  working, and no matter what I tried like:

  sudo apt reinstall alsa-base pulseaudio
  sudo alsa force-reload

  +

  reboot(-s)

  +

  alsamixer

  nothing brought me sound back, so I just installed an older kernel,
  namely the littlest bit older one:

  > 4.15.0-**55**

  now everything works like a charm.

  ---

  How can I debug this and figure out if the problem is a bug in the
  kernel itself or in some other audio-related package? I don't know
  what exact information you could require for this.

  ---

  I have just reproduced the problem by upgrading back to 4.15.0-**58**
  from 4.15.0-**55**. Sound not working again. Plus, by switching to an
  older kernel proves sound is functional.

  ---

  Hardware:

  laptop Dell HG6D142: [direct link to product page][1]

  --

  $ lsb_release -rd
  Description:  Linux Mint 19.2 Tina
  Release:  19.2

  
  ---

  expectation: sound working

  ---

  happened: sound does not work at all, neither with Intel GPU, nor
  Nvidia GPU online, tried all I could mentioned above

  
  

  I attach a simple diff between 55 and 58 loaded.

  ---

  Thank you!

[1]: https://www.dell.com/support/home/us/en/04/product-
  support/servicetag/0-dVRqMHhSVXVMa3ZPOVFNUUEzSk1mQT090/overview

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+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 1840796] Re: sound not working in 4.15.0-58, but does in 4.15.0-55

[Paul White]

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

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

Title:
  sound not working in 4.15.0-58, but does in 4.15.0-55

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  First excuse me, this is my very first bug report, if anything is
  missing, notify me on email.

  --

  I find it rather hard to believe, but since I installed kernel:

  > 4.15.0-**58**

  several days ago, my sound on Linux Mint 19.2 Cinnamon stopped
  working, and no matter what I tried like:

  sudo apt reinstall alsa-base pulseaudio
  sudo alsa force-reload

  +

  reboot(-s)

  +

  alsamixer

  nothing brought me sound back, so I just installed an older kernel,
  namely the littlest bit older one:

  > 4.15.0-**55**

  now everything works like a charm.

  ---

  How can I debug this and figure out if the problem is a bug in the
  kernel itself or in some other audio-related package? I don't know
  what exact information you could require for this.

  ---

  I have just reproduced the problem by upgrading back to 4.15.0-**58**
  from 4.15.0-**55**. Sound not working again. Plus, by switching to an
  older kernel proves sound is functional.

  ---

  Hardware:

  laptop Dell HG6D142: [direct link to product page][1]

  --

  $ lsb_release -rd
  Description:  Linux Mint 19.2 Tina
  Release:  19.2

  
  ---

  expectation: sound working

  ---

  happened: sound does not work at all, neither with Intel GPU, nor
  Nvidia GPU online, tried all I could mentioned above

  
  

  I attach a simple diff between 55 and 58 loaded.

  ---

  Thank you!

[1]: 
https://www.dell.com/support/home/us/en/04/product-support/servicetag/0-dVRqMHhSVXVMa3ZPOVFNUUEzSk1mQT090/overview
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vlastimil   2458 F pulseaudio
   /dev/snd/controlC1:  vlastimil   2458 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.2
  InstallationDate: Installed on 2018-06-16 (430 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180531
  MachineType: Dell Inc. Inspiron 7577
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro ipv6.disable=1 quiet splash 
fsck.mode=force fsck.repair=yes vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-58-generic N/A
   linux-backports-modules-4.15.0-58-generic  N/A
   linux-firmware 1.173.9
  Tags:  tina
  Uname: Linux 4.15.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0J8HMF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd04/19/2019:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0J8HMF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7577
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+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 1840906] Re: Firefox could not hear streaming Radiko

[Paul White]

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

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

Title:
  Firefox could not hear streaming Radiko

Status in firefox package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  dear everyone.

  this is not a bug, but may bug.

  I use ubuntu-18.04.3, and Firefox 68.0.2.
  In Japan radio streaming site named Radiko (http://radiko.jp),
  Firefox could not hear this.

  1 or 2 years old, Firefox + Adobe Flash use could hear Radiko.
  But now Firefox do not support adobe Flash.

  Radiko site change to use adobe flash to HTML5,
  I expected to hear Radiko to use Firefox.
  but could not.

  few days ago, I install chrome(proprietory version),
  chrome could hear radiko streaming.

  what change to need my firefox to hear radkio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840906/+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 1782716] Re: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

[Paul Graydon]

Seeing the same on Ubuntu 18.04.3 with the HWE kernel, 5.0.0-25-generic

AMD A6-9225 RADEON R4

This appears to be tied in to the problems resuming the laptop from
suspended (black screen, flashing cursor)

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

Title:
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running the 4.17.0-5-generic kernel on a ppc64le machine with a Radeon
  R9 Fury GPU

  
  0033:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] (rev ff)

  [ 2361.958847] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, 
last signaled seq=8777, last emitted seq=8778
  [ 2362.080397] EEH: Frozen PHB#33-PE#0 detected
  [ 2362.080470] EEH: PE location: CPU2 Slot1 (16x), PHB location: N/A
  [ 2362.080568] CPU: 53 PID: 874 Comm: kworker/53:1 Not tainted 
4.17.0-5-generic #6-Ubuntu
  [ 2362.080575] Workqueue: events drm_sched_job_timedout [gpu_sched]
  [ 2362.080577] Call Trace:
  [ 2362.080584] [c000fb7078f0] [c0d275ac] dump_stack+0xb0/0xf4 
(unreliable)
  [ 2362.080590] [c000fb707930] [c003ba0c] 
eeh_dev_check_failure+0x5bc/0x5e0
  [ 2362.080593] [c000fb7079e0] [c003babc] 
eeh_check_failure+0x8c/0xd0
  [ 2362.080628] [c000fb707a20] [c0080cfa1b88] 
amdgpu_mm_rreg+0x280/0x2a0 [amdgpu]
  [ 2362.080676] [c000fb707a70] [c0080d04cf68] 
gmc_v8_0_check_soft_reset+0x30/0xe0 [amdgpu]
  [ 2362.080711] [c000fb707aa0] [c0080cfa1194] 
amdgpu_device_ip_check_soft_reset.part.1+0x8c/0x140 [amdgpu]
  [ 2362.080745] [c000fb707b30] [c0080cfa649c] 
amdgpu_device_gpu_recover+0x854/0xa40 [amdgpu]
  [ 2362.080799] [c000fb707c00] [c0080d0b97a4] 
amdgpu_job_timedout+0x5c/0x80 [amdgpu]
  [ 2362.080805] [c000fb707c70] [c0080c8f0040] 
drm_sched_job_timedout+0x38/0x60 [gpu_sched]
  [ 2362.080810] [c000fb707c90] [c0137928] 
process_one_work+0x298/0x580
  [ 2362.080813] [c000fb707d20] [c0137c98] worker_thread+0x88/0x610
  [ 2362.080817] [c000fb707dc0] [c0140958] kthread+0x1a8/0x1b0
  [ 2362.080822] [c000fb707e30] [c000b658] 
ret_from_kernel_thread+0x5c/0x84
  [ 2362.080827] [drm] IP block:gmc_v8_0 is hung!
  [ 2362.080832] [drm] IP block:tonga_ih is hung!
  [ 2362.080843] [drm] IP block:gfx_v8_0 is hung!
  [ 2362.080845] EEH: Detected PCI bus error on PHB#33-PE#0
  [ 2362.080847] EEH: This PCI device has failed 1 times in the last hour
  [ 2362.080849] EEH: Notify device drivers to shutdown
  [ 2362.080850] [drm] IP block:sdma_v3_0 is hung!
  [ 2362.080856] [drm] IP block:uvd_v6_0 is hung!
  [ 2362.080858] EEH: Collect temporary log
  [ 2362.080866] [drm] IP block:vce_v3_0 is hung!
  [ 2362.080867] [drm] GPU recovery disabled.
  [ 2362.080903] EEH: of node=0033:01:00.1
  [ 2362.080905] EEH: PCI device/vendor: 
  [ 2362.080907] EEH: PCI cmd/status register: 
  [ 2362.080908] EEH: PCI-E capabilities and status follow:
  [ 2362.080915] EEH: PCI-E 00:     
  [ 2362.080920] EEH: PCI-E 10:     
  [ 2362.080921] EEH: PCI-E 20:  
  [ 2362.080922] EEH: PCI-E AER capability register set follows:
  [ 2362.080928] EEH: PCI-E AER 00:     
  [ 2362.080933] EEH: PCI-E AER 10:     
  [ 2362.080938] EEH: PCI-E AER 20:     
  [ 2362.080940] EEH: PCI-E AER 30:   
  [ 2362.080941] EEH: of node=0033:01:00.0
  [ 2362.080943] EEH: PCI device/vendor: 
  [ 2362.080945] EEH: PCI cmd/status register: 
  [ 2362.080945] EEH: PCI-E capabilities and status follow:
  [ 2362.080951] EEH: PCI-E 00:     
  [ 2362.080956] EEH: PCI-E 10:     
  [ 2362.080957] EEH: PCI-E 20:  
  [ 2362.080958] EEH: PCI-E AER capability register set follows:
  [ 2362.080964] EEH: PCI-E AER 00:     
  [ 2362.080969] EEH: PCI-E AER 10:     
  [ 2362.080974] EEH: PCI-E AER 20:     
  [ 2362.080975] EEH: PCI-E AER 30:   
  [ 2362.080977] PHB4 PHB#51 Diag-data (Version: 1)
  [ 2362.080978] brdgCtl:0002
  [ 2362.080979] RootSts:00060020 00402000 c1010008 00100107 
  [ 2362.080980] RootErrSts:  0020 
  [ 2362.080981] PhbSts: 001c 001c
  [ 2362.080982] Lem:0001  0001
  [ 2362.080983] PhbErr: 00c0 0080 214898000240 
a0084000
  [ 2362.080984] RegbErr:0090 0010 483c 
0200
  [ 2362.080985] PE[000] A/B: 800

[Kernel-packages] [Bug 1840906] Re: Firefox could not hear streaming Radiko

[Paul White]

Are you saying that you need to install ubuntu-restricted-extras in
order to hear audio from Radiko or that additional codecs needs to be
added to ubuntu-restricted-extras?

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

Title:
  Firefox could not hear streaming Radiko

Status in firefox package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dear everyone.

  this is not a bug, but may bug.

  I use ubuntu-18.04.3, and Firefox 68.0.2.
  In Japan radio streaming site named Radiko (http://radiko.jp),
  Firefox could not hear this.

  1 or 2 years old, Firefox + Adobe Flash use could hear Radiko.
  But now Firefox do not support adobe Flash.

  Radiko site change to use adobe flash to HTML5,
  I expected to hear Radiko to use Firefox.
  but could not.

  few days ago, I install chrome(proprietory version),
  chrome could hear radiko streaming.

  what change to need my firefox to hear radkio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840906/+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 1840906] Re: Firefox could not hear streaming Radiko

[Paul White]

Seiichi,

I'm marking the "linux" component of this bug report as "Invalid" as you
are not reporting a bug with the Linux kernel.

Not all codecs are included in a default installation of Ubuntu due to
copyright or legal issues in some countries. Other Linux distributions
are affected in the same way. If after installing ubuntu-restricted-
extras you can hear Radiko then this is not a bug in Firefox as far as
Ubuntu is concerned. You will find the same issues when using Chromium,
Epiphany or any other web browser included in the Ubuntu repositories.

I'm closing the Firefox bug too as you have confirmed that you can hear
Rdaiko by installing "ubuntu-restricted-extras".


 

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

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

Title:
  Firefox could not hear streaming Radiko

Status in firefox package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  dear everyone.

  this is not a bug, but may bug.

  I use ubuntu-18.04.3, and Firefox 68.0.2.
  In Japan radio streaming site named Radiko (http://radiko.jp),
  Firefox could not hear this.

  1 or 2 years old, Firefox + Adobe Flash use could hear Radiko.
  But now Firefox do not support adobe Flash.

  Radiko site change to use adobe flash to HTML5,
  I expected to hear Radiko to use Firefox.
  but could not.

  few days ago, I install chrome(proprietory version),
  chrome could hear radiko streaming.

  what change to need my firefox to hear radkio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840906/+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 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

[Paul Menzel]

@andre-miras, we do not experience the problem with Ubuntu 18.10(?) and
19.04 anymore. Please try to update, or test these releases. No idea,
what the cause and solution was in the end.

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

Title:
  XPS 13 9360 trackpad locks into scroll mode

Status in Dell Sputnik:
  Invalid
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I'm running Linux on a Dell XPS 13 (9360) laptop.

  I find that upwards of 10 times per day, my trackpad gets stuck in
  "scrolling" mode. Moving the trackpad won't move the X windows
  pointer, but will send scrolling events to the foreground window.

  When the trackpad is locked in this mode, the touchscreen will still
  let me move the mouse cursor, as will an external mouse.

  On Ubuntu 16.04 freshly restored from the Dell recovery image, I find
  that it's often difficult to get the trackpad to recover.

  I do find that the issue happens less frequently on Dell's build of
  Ubuntu 16.04 than on other linux distributions and versions, but it
  still happens enough to significantly impact my ability to do
  productive work.

  The issue does not occur when running Windows 10 on the same device.

  I suspect that the issue may be related to palm detection or
  misdetecting the user's palm as a gesture to enable scrolling mode,
  but have no proof for this.

  It seems that I'm often able to reproduce the issue by brushing the
  trackpad with my right palm.

  On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx
  4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I
  am able to get the trackpad to recover, simply by clicking the
  trackpad:

  /usr/share/X11/xorg.conf.d/99-libinput.conf:

  Section "InputClass"
  Identifier "libinput touchpad catchall"
  Driver "libinput"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "Tapping" "True"
  Option "DisableWhileTyping" "True"
  Option "NaturalScrolling" "False"
  Option "AccelProfile" "adaptive"
  Option "AccelSpeed" "0.05"
  Option "MiddleEmulation" "True"
  Option "ScrollMethod" "twofinger"
  # Option "ClickMethod" "clickfinger"
  Option "ClickMethod" "buttonareas"
  EndSection

  
  In my experience, the problem manifests using both the Xorg synaptics driver 
and the Xorg libinput driver.

  root@szx:/etc/modprobe.d# xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech M570   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL075B:01 06CB:76AF Touchpad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=14   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]
  root@szx:/etc/modprobe.d#

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+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 1841841] [NEW] disk stress test extremely slow progress after cpu offline/online

[Paul Larson]

Public bug reported:

One of the test systems we use for testing snap updates is:
Dell Inspiron 5759
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
Advanced Micro Devices, Inc. [AMD/ATI] - 1002:6660, Intel - 8086:1916

We picked this one, some time ago from a pool of hardware to use for one
of the test systems to test amd64/i386 snaps in beta.  One of the tests
in the test suite does some disk stress testing using:

   bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000

Looking back through our results, I see that it has often taken from
20-40 min. to complete the test, and sometimes hit our timeout
threshold. More recently, it seems to always just timeout, but as far
back as our history goes with testing on this platform, it's always
seemed bad to some extent.  I tried the exact same test on another
similar system, and it completed in only 11min. so we suspected a bad
disk.  After replacing the disk with a new one, it still has the same
problem.

We only see this problem on the core18 i386 images though, not on
core16, and not on core18-amd64.

Looking into it some more, I discovered that it was easily reproducible outside 
the test suite, but *only* if I tried running it after the full test suite 
without rebooting.  If I reboot the system, and run the bonnie++ command above 
without the rest of the tests, it completes in about 13 min.
I divided up the other tests and narrowed it down to a cpu offlining test - 
when that test runs, followed by this disk stress test, that's when it gets so 
horribly slow.

This was all done using checkbox-snappy as the test suite, but if you
have another way to get bonnie++ on here, it can be reproduced without
it (or you can use bonnie++ from checkbox-snappy easily by doing 'sudo
/snap/bin/checkbox-snappy.shell')

Here's the basic instructions to reproduce (on core18-i386):
$ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu1/online"
$ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu2/online"
$ sudo bash -c "echo 0 > /sys/devices/system/cpu/cpu3/online"
$ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu1/online"
$ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu2/online"
$ sudo bash -c "echo 1 > /sys/devices/system/cpu/cpu3/online"
$ sudo /snap/bin/checkbox-snappy.shell
# bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000

Nothing particularly interesting in dmesg during all of this other than the 
NOHZ messages during cpu offline:
[  189.085026] smpboot: CPU 1 is now offline
[  199.371529] smpboot: CPU 2 is now offline
[  203.291835] NOHZ: local_softirq_pending 282
[  203.293167] NOHZ: local_softirq_pending 282
[  203.294581] smpboot: CPU 3 is now offline
[  247.521569] x86: Booting SMP configuration:
[  247.521576] smpboot: Booting Node 0 Processor 1 APIC 0x2
[  247.522892] Initializing CPU#1
[  252.127965] smpboot: Booting Node 0 Processor 2 APIC 0x1
[  252.129533] Initializing CPU#2
[  255.632004] smpboot: Booting Node 0 Processor 3 APIC 0x3
[  255.633565] Initializing CPU#3


History I have for the past few kernels:
4.15.0-52.56-226 - passed - 41m
4.15.0-54.58-241 - passed - 36m
4.15.0-55.60-246 - passed after some timeouts/retries, took 41m though
4.15.0-55.60-253 - passed in 20min
4.15.0-56.62-263 - fails - seems to take much much longer from this point on

*These results were from that test as part of the full test run,
including the cpu offlining test. When the test is run by itself on the
same system, it takes only around 13min

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

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

Title:
  disk stress test extremely slow progress after cpu offline/online

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  One of the test systems we use for testing snap updates is:
  Dell Inspiron 5759
  Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  Advanced Micro Devices, Inc. [AMD/ATI] - 1002:6660, Intel - 8086:1916

  We picked this one, some time ago from a pool of hardware to use for
  one of the test systems to test amd64/i386 snaps in beta.  One of the
  tests in the test suite does some disk stress testing using:

 bonnie++ -d /var/lib/snapd/hostfs/writable -u root -r 8000

  Looking back through our results, I see that it has often taken from
  20-40 min. to complete the test, and sometimes hit our timeout
  threshold. More recently, it seems to always just timeout, but as far
  back as our history goes with testing on this platform, it's always
  seemed bad to some extent.  I tried the exact same test on another
  similar system, and it completed in only 11min. so we suspected a bad
  disk.  After replacing the disk with a new one, it still has the same
  problem.

  We only see this problem on the core18 i386 images though, not on
  core16, and not on core18-amd64.

  Looking into it some more, I discovered that it was easily reproducible 
ou

[Kernel-packages] [Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel

[Paul White]

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

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

Title:
  Out of Memory on boot with 5.2.0 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Upgraded from 19.04 to current 19.10 using "do-release-upgrade -d".
  Can still boot using the previous 5.0.0-25-generic kernel, but the
  5.2.0-15-generic fails to start.

  On selecting Ubuntu from Grub, the message "error: out of memory." is
  immediately shown. Pressing a key attempts to start boot-up but fails
  to mount root fs.

  Machine is HP Spectre X360 with 8GB RAM. Under kernel 5.0.0, free
  shows the following (run from Gnome terminal):

    totalusedfree  shared  buff/cache   
available
  Mem:7906564 1761196 3833240 1020216 2312128 
4849224
  Swap:   1003516   0 1003516

  Kernel packages installed:

  linux-generic  5.2.0.15.16 amd64
  linux-headers-5.2.0-15 5.2.0-15.16 all
  linux-headers-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-headers-generic  5.2.0.15.16 amd64
  linux-image-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-image-5.2.0-15-generic   5.2.0-15.16+signed1 amd64
  linux-image-generic5.2.0.15.16 amd64
  linux-modules-5.0.0-25-generic 5.0.0-25.26 amd64
  linux-modules-5.2.0-15-generic 5.2.0-15.16 amd64
  linux-modules-extra-5.0.0-25-generic   5.0.0-25.26 amd64
  linux-modules-extra-5.2.0-15-generic   5.2.0-15.16 amd64

  Photo of kernel panic attached.

  NVMe drive partition layout (GPT):

  Device   StartEnd   Sectors   Size Type
  /dev/nvme0n1p120481050623   1048576   512M EFI System
  /dev/nvme0n1p2 10506242549759   1499136   732M Linux filesystem
  /dev/nvme0n1p3 2549760 1000214527 997664768 475.7G Linux filesystem

  $ sudo pvs
    PV  VGFmt  Attr PSizePFree
    /dev/mapper/nvme0n1p3_crypt ubuntu-vg lvm2 a--  <475.71g0

  $ sudo lvs
    LV VGAttr   LSize   Pool Origin Data%  Meta%  Move Log 
Cpy%Sync Convert
    root   ubuntu-vg -wi-ao 474.75g
    swap_1 ubuntu-vg -wi-ao 980.00m

  Partition 3 is LUKS encrypted. Root LV is ext4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+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 1820583] Re: CAPS LOCK key not released

[Paul White]

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

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

Title:
  CAPS LOCK key not released

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometimes the caps lock key is not released and EVERYTHING IS IN CAPS 
AFTERWARDS. 
  It is only working properly after a restart.
  My Ubuntu version is 
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  It is not a hardware issue because it persists even if i change from the usb 
keyboard to the laptop keyboard.
  My kernel version is 
  4.15.0-43-generic
  but updating to 4.15.0-45 didn't help.
  Is there anything else i can report to help you find the source of this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820583/+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 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

[Paul Lai]

33823f4d6 x86/cpufeatures: Enumerate MOVDIRI instruction
ace6485a0 x86/cpufeatures: Enumerate MOVDIR64B instruction
65e259d5c tools arch x86: Update tools's copy of cpufeatures.h

(linux 5.1-rc1)
74f2370bb KVM: x86: expose MOVDIRI CPU feature into VM.
c029b5deb KVM: x86: expose MOVDIR64B CPU feature into VM.

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

Title:
  KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Triaged
Status in xen package in Ubuntu:
  Incomplete

Bug description:
  CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) 
features including:
  - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch 
with accelerators
  - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or 
wait-for-interrupt usages
  - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator 
usages.
  - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For 
latency critical accelerator usages

  Upstream target linux 5.1/Qemu-3.10

  Target Release: 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+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 1822239] Re: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta

[Paul White]

** Package changed: ubuntu => nvidia-graphics-drivers-390 (Ubuntu)

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

Title:
  NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't
  support 3D capabilities on Disco 19.04 beta

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Summary: I use a Dell Precision 5530 (I+N) machine and switch to Nivida card. 
(The Nvidia driver installed via Additional driver of Software & Update - 
nvida-driver-390)
  Try to run glxgears and got the error - Error: couldn't get an RGB, 
Double-buffered visual

  Steps to reproduce:
  1. Install the tool:
  $ sudo apt install mesa-utils
  2. Run glxgears
  $ glxgears

  Expected result:
  Open up a window with an OpenGL rendering of a simple arrangement of three 
rotating gears.

  Actual result:
  An error returns: Error: couldn't get an RGB, Double-buffered visual

  Failure rate: 100%

  -

  CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x)
  GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
  system-product-name: Precision 5530
  bios-version: 1.6.0
  system-manufacturer: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1822239/+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 1831075] Re: RT3290 has stopped working permanently on Ubuntu 18.04

[Paul White]

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

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

Title:
  RT3290 has stopped working permanently on Ubuntu 18.04

Status in Linux:
  New
Status in Ubuntu Server:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Kernel Version: 4.18.0-20-generic
  Arch: x86_64
  Ubuntu Version: 18.04.2

  Issue description:
  The Ralink RT3290 Card worked perfectly on 4.13.0-36-generic, however, after 
upgrading to 4.18.0-20-generic as a result of upgrading to 18.04.2. The newer 
kernel no longer allows the RT3290 Wi-Fi card to be used.
  When checked using rfkill, rfkill provides output that phy0 (inteface) is 
hard blocked

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1831075/+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 1831128] Re: ACPI error on boot

[Paul White]

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

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

Title:
  ACPI error on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i have a laptop with ryzen 5 2500u processor.and i got this error when boot,
  i tried ubuntu 16.04,18.04,19.04 and the result is same.
  system stuck on acpi error.i tried to disable it then the system is shut down.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831128/+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 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

[Paul Lai]

This patch is also needed for kernels before 4.18

  cd28325249 KVM: VMX: support MSR_IA32_ARCH_CAPABILITIES as a feature
MSR ( 25-6-18)

This patchset populates the structure in arch/x86/kvm/x86.c:
   msr_based_features{}

With out this patch, qemu asserts at

  kvm_get_supported_feature_msrs(KVMState *s):
 assert(msr_list.nmsrs > 0);

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

Status in intel:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Triaged

Bug description:
  This is a bug.

  Test Environment:

  Repro Steps:

  1. Boot up guest using: -cpu Cascadelake-Server

  [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
  if=virtio,id=hd,file=/home/x/x,format=qcow2  -m 4096 -smp 4 -cpu
  Cascadelake-Server -serial stdio

  char device redirected to /dev/pts/3 (label serial0)

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  qemu-system-x86_64: warning: host doesn't support requested feature:
  CPUID.07H:ECX [bit 4]

  2. To check CPU ID related to features[FEAT_7_0_EDX]
  ：CPUID_7_0_EDX_ARCH_CAPABILITIES

  Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
  1.

  Actual Result:

  Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
  ecx=0x0818 edx=0xbc00  (EDX bit 29=1)

  Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
  ecx=0x0818 edx=0x8400 (EDX bit 29=0)

  Commit:2bdb76c015df7125783d8394d6339d181cb5bc30

  Target Kerned: 5.1
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1828495/+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 1832472] Re: cdc_ncm floods syslog unneccessarily

[Paul White]

** Tags added: disco

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

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

Title:
  cdc_ncm floods syslog unneccessarily

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Upon plugging in a USB adapter for NBase-T ethernet with an Realtek
  chip RTL8156 the kernel module cdc_ncm starts flooding /var/log/syslog
  with unneccessary status info.

  The status lines either say that there's no ethernet link or show the
  interface as connected and state the link speed.

  The relevant parts from /var/log/syslog after attaching the adapter
  without ethernet link read like this:

  [...]
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.398485] usb 2-3: new SuperSpeed Gen 
1 USB device number 5 using xhci_hcd
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419463] usb 2-3: New USB device 
found, idVendor=0bda, idProduct=8156, bcdDevice=30.00
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419469] usb 2-3: New USB device 
strings: Mfr=1, Product=2, SerialNumber=6
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419472] usb 2-3: Product: USB 
10/100/1G/2.5G LAN
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419475] usb 2-3: Manufacturer: 
Realtek
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419477] usb 2-3: SerialNumber: 
1
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447769] cdc_ncm 2-3:2.0: 
MAC-Address: 00:13:3b:68:00:e9
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447775] cdc_ncm 2-3:2.0: setting 
rx_max = 16384
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447929] cdc_ncm 2-3:2.0: setting 
tx_max = 16384
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.448901] cdc_ncm 2-3:2.0 usb0: 
register 'cdc_ncm' at usb-:00:14.0-3, CDC NCM, 00:13:3b:68:00:e9
  Jun 12 10:48:58 resdz-v13 NetworkManager[916]:   [1560329338.1872] 
manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/8)
  Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: 
"/sys/devices/pci:00/:00:14.0/usb2/2-3"
  Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device
  Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Using default interface naming 
scheme 'v240'.
  Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: link_config: autonegotiation 
is unset or enabled, the speed and duplex are not writable.
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.466476] cdc_ncm 2-3:2.0 
enx00133b6800e9: renamed from usb0
  Jun 12 10:48:58 resdz-v13 NetworkManager[916]:   [1560329338.2315] 
device (usb0): interface index 7 renamed iface from 'usb0' to 'enx00133b6800e9'
  Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Process 
'vlan-network-interface UDEV' failed with exit code 1.
  Jun 12 10:48:58 resdz-v13 NetworkManager[916]:   [1560329338.2431] 
device (enx00133b6800e9): state change: unmanaged -> unavailable (reason 
'managed', sys-iface-state: 'external')
  Jun 12 10:48:58 resdz-v13 charon: 12[KNL] interface enx00133b6800e9 activated
  Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: 
"/sys/devices/pci:00/:00:14.0/usb2/2-3"
  Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.524052] cdc_ncm 2-3:2.0 
enx00133b6800e9: network connection: disconnected
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.556109] cdc_ncm 2-3:2.0 
enx00133b6800e9: network connection: disconnected
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.588054] cdc_ncm 2-3:2.0 
enx00133b6800e9: network connection: disconnected
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.620383] cdc_ncm 2-3:2.0 
enx00133b6800e9: network connection: disconnected
  Jun 12 10:48:58 resdz-v13 kernel: [ 4240.652415] cdc_ncm 2-3:2.0 
enx00133b6800e9: network connection: disconnected
  [...]

  Upon plugging in the ethernet cable I see
  [...]
  Jun 12 10:49:01 resdz-v13 kernel: [ 4243.372273] cdc_ncm 2-3:2.0 
enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
  Jun 12 10:49:01 resdz-v13 kernel: [ 4243.404278] cdc_ncm 2-3:2.0 
enx00133b6800e9: network connection: connected
  [...]
  and Network Manager starts its work. 

  After the interface is up the flooding continues:
  [...]
  Jun 12 10:49:01 resdz-v13 kernel: [ 4243.564056] cdc_ncm 2-3:2.0 
enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink
  Jun 12 10:49:01 resdz-v13 kernel: [ 4243.596051] cdc_ncm 2-3:2.0 
enx00133b6800e9: network connection: connected
  Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] The default IPv4 route 
is: /org/freedesktop/NetworkManager/ActiveConnection/4
  Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] Not a paid data plan: 
/org/freedesktop/NetworkManager/ActiveConnection/4
  Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] Found usable connection: 
/org/freedesktop/NetworkManager/ActiveConnection/4
  Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] online
  Jun 12 10:49:01 resdz-v13 kernel: [ 4243.628055] cdc_ncm 2-3:2.0 
enx00133b6800

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

[Paul Dufresne]

The patch is included in:
Linux 4.14.125
Linux 4.19.50
Linux 5.1.9
I don't have access to the laptop on which I investigated this problem anymore.

But it could be tested from the built kernel packages at:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.125/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.50/
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1.9/
Install linux-headers then linux-modules then linux-image (I think)

In fact, testing on other ATI hardware too see not bad results happen
would be... reassuring.

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1791312/+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 1791312]

[Paul Dufresne]

The patch is included in:
Linux 4.14.125
Linux 4.19.50
Linux 5.1.9

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1791312/+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 1832863] Re: Kernel 4.4.0.145 (& subsequent) boots to black screen.

[Paul White]

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

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

Title:
  Kernel 4.4.0.145 (& subsequent) boots to black screen.

Status in linux package in Ubuntu:
  New

Bug description:
  On my Asus EeePC 1015PED netbook, running Ubuntu 16.04LTS, I updated to 
kernel 4.4.0.145 on 3 April 2019.
  On the first boot after the update, I got the usual grub screen, then 
"Loading Linux 4.4.0.145 ... Loading initial ramdisk ..." then the screen went 
black with no mouse pointer or invite.
  I could hear disk activity ( & see the disk-activity light) then the usual 
drumroll for login, but the screen stayed black.
  I escaped using REISUO & retried several times with the same result.
  If I wait for the login drumroll then input my login, there is more disk 
activity (setting up the desktop) but the screen stays black.
  So the PC is not freezing, just no screen.
  Trying Ctrl+Alt+F1 (or other F keys) produces nothing.

  I can continue to use the PC normally if I select the previous kernel
  4.4.0.142 at the grub screen.

  On 10 June 2019, I updated to kernel 4.4.0.150 & have the same black
  screen as with .145.

  So I am unable to use this PC AT ALL with current kernels.

  I asked about this problem on Ubuntu Forum
  https://ubuntuforums.org/showthread.php?t=2415972
  with no success & the suggestion was to raise this bug...
  There may be useful information in that thread, including this output from 
"inxi -Fzr" (run in good kernel .142).

  chris@Netbk:~$ inxi -Fzr
  System:Host: Netbk Kernel: 4.4.0-142-generic x86_64 (64 bit)
 Desktop: Unity 7.4.5  Distro: Ubuntu 16.04 xenial
  Machine:   System: ASUSTeK (portable) product: 1015PE v: x.x
 Mobo: ASUSTeK model: 1015PE v: x.xx
 Bios: American Megatrends v: 0801 date: 10/06/2010
  CPU:   Single core Intel Atom N455 (-HT-) cache: 512 KB 
 clock speeds: max: 1667 MHz 1: 1667 MHz 2: 1667 MHz
  Graphics:  Card: Intel Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller
 Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
 Resolution: 1024x600@60.00hz
 GLX Renderer: Mesa DRI Intel Pineview M
 GLX Version: 1.4 Mesa 18.0.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832863/+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 1825235] [NEW] Load average inexplicably high with 5.0 kernel on rpi

[Paul Larson]

Public bug reported:

Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC
2019 aarch64 aarch64 aarch64 GNU/Linux

I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the 
disco release candidate.
After booting, the load average stays quite high, typically over 4.0. This 
persists, even if I leave it idle for several hours:
ubuntu@ubuntu:~$ w
 19:44:05 up  2:22,  1 user,  load average: 4.16, 4.03, 4.01

/proc/loadavg is consistent with these numbers. But when I check top,
there are no obvious culprits hogging the cpu or anything. Typically
everything looks to be <1% cpu usage, with top being the biggest cpu hog
at about 2%. The system doesn't seem too slow (for a pi), but it's
unusual to see such high numbers.

Nothing seems to be swapping:

ubuntu@ubuntu:~$ free -m
  totalusedfree  shared  buff/cache   available
Mem:908 173 422   6 312 707
Swap: 0   0   0


ubuntu@ubuntu:~$ iostat
Linux 5.0.0-1006-raspi2 (ubuntu)04/17/19_aarch64_   (4 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
   1.640.151.572.060.00   94.57

Device tpskB_read/skB_wrtn/skB_readkB_wrtn
loop0 0.08 0.50 0.00354  0
loop1 2.56 3.98 0.00   2805  0
loop2 0.01 0.01 0.00  4  0
mmcblk0  12.70   367.40   705.16 258830 496785

ubuntu@ubuntu:~$ vmstat 1
procs ---memory-- ---swap-- -io -system-- --cpu-
 r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa st
 0  0  0 514540  18004 2240720097   182 2564   76  2  2 94  2  0
 0  0  0 514512  18004 22413600 0  2012 10136  142  0  0 94  5  0
 0  0  0 514512  18004 22413600 0 0 10117  106  0  0 100  0 
 0
 0  0  0 514512  18004 22413600 0 0 10121   98  0  0 100  0 
 0
 0  0  0 514512  18012 22412800 0  2028 10129  141  0  0 93  7  0
 0  0  0 514512  18012 22413600 0 0 10149  135  0  0 100  0 
 0
 0  0  0 514512  18012 22413600 0 0 10108   97  0  0 100  0 
 0
 0  0  0 514512  18012 22413600 0  2012 10125  126  0  0 95  5  0
 0  0  0 514512  18012 22413600 0 0 10117  101  0  0 100  0 
 0
 0  1  0 514512  18012 22413600 0  2012 10109  104  0  0 98  2  0
 0  0  0 514512  18020 22412800 012 10139  150  0  0 96  4  0
 0  0  0 514512  18020 22412800 0 0 10108   90  0  0 100  0 
 0

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

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

Title:
  Load average inexplicably high with 5.0 kernel on rpi

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC
  2019 aarch64 aarch64 aarch64 GNU/Linux

  I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the 
disco release candidate.
  After booting, the load average stays quite high, typically over 4.0. This 
persists, even if I leave it idle for several hours:
  ubuntu@ubuntu:~$ w
   19:44:05 up  2:22,  1 user,  load average: 4.16, 4.03, 4.01

  /proc/loadavg is consistent with these numbers. But when I check top,
  there are no obvious culprits hogging the cpu or anything. Typically
  everything looks to be <1% cpu usage, with top being the biggest cpu
  hog at about 2%. The system doesn't seem too slow (for a pi), but it's
  unusual to see such high numbers.

  Nothing seems to be swapping:

  ubuntu@ubuntu:~$ free -m
totalusedfree  shared  buff/cache   
available
  Mem:908 173 422   6 312 
707
  Swap: 0   0   0

  
  ubuntu@ubuntu:~$ iostat
  Linux 5.0.0-1006-raspi2 (ubuntu)  04/17/19_aarch64_   (4 CPU)

  avg-cpu:  %user   %nice %system %iowait  %steal   %idle
 1.640.151.572.060.00   94.57

  Device tpskB_read/skB_wrtn/skB_readkB_wrtn
  loop0 0.08 0.50 0.00354  0
  loop1 2.56 3.98 0.00   2805  0
  loop2 0.01 0.01 0.00  4  0
  mmcblk0  12.70   367.40   705.16 258830 496785

  ubuntu@ubuntu:~$ vmstat 1
  procs ---memory-- ---swap-- -io -system-- 
--cpu-
   r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa 
st
   0  0  0 514

[Kernel-packages] [Bug 1825736] [NEW] Mouse scroll wheel barely works after suspend

[Paul Tansom]

Public bug reported:

After a resuming from a suspend the mouse scroll wheel is almost, but
not quite, non functional. If you scroll quickly for a while you do get
a slight movement of the scroll bar to show that there is some level of
communication, but nothing remotely usable.

The fix is to use the following commands to remove the hid_generic
module and reinstate it:

sudo rmmod hid_generic
sudo modprobe hid_generic

Following this all works as expected until the next suspend.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-modules-5.0.0-13-generic 5.0.0-13.14
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  paul   1905 F pulseaudio
 /dev/snd/controlC1:  paul   1905 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 21 19:02:00 2019
Dependencies:
 
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=8032c5f7-74fd-4a23-92cb-5ad7d0642a9f
InstallationDate: Installed on 2017-12-15 (491 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20238
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=63abd1a6-61ac-485b-9448-47d635ee8808 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-13-generic N/A
 linux-backports-modules-5.0.0-13-generic  N/A
 linux-firmware1.178
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-04-20 (1 days ago)
dmi.bios.date: 10/20/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 79CN50WW(V3.09)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 31900058Std
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G510
dmi.modalias: 
dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG510:
dmi.product.family: IDEAPAD
dmi.product.name: 20238
dmi.product.sku: LENOVO_MT_20238
dmi.product.version: Lenovo G510
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco

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

Title:
  Mouse scroll wheel barely works after suspend

Status in linux package in Ubuntu:
  New

Bug description:
  After a resuming from a suspend the mouse scroll wheel is almost, but
  not quite, non functional. If you scroll quickly for a while you do
  get a slight movement of the scroll bar to show that there is some
  level of communication, but nothing remotely usable.

  The fix is to use the following commands to remove the hid_generic
  module and reinstate it:

  sudo rmmod hid_generic
  sudo modprobe hid_generic

  Following this all works as expected until the next suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-modules-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1905 F pulseaudio
   /dev/snd/controlC1:  paul   1905 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 19:02:00 2019
  Dependencies:
   
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8032c5f7-74fd-4a23-92cb-5ad7d0642a9f
  InstallationDate: Installed on 2017-12-15 (491 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20238
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=63abd1a6-61ac-485b-9448-47d635ee8808 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-20 (1 days ago)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79CN50WW(V3.09)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G510
  dmi.modalias: 
dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG510:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20238
  dmi.product.sku: LENOVO_MT_20238
  dmi.product.version: Lenovo G510
  dmi.sys.vendor: LENOVO

To manage notifications about t

[Kernel-packages] [Bug 1825736] Re: Mouse scroll wheel barely works after suspend

[Paul Tansom]

I did not have this problem prior to upgrading to 19.04. The upgrade
process was an upgrade from 18.04 to 18.10 with an immediate upgrade to
19.04 (after a clean reboot), so there was no usage of 18.10 as a
desktop environment to compare with. The 18.04 install was kept up to
date.

I have tested using the installed linux-image-4.18.0-17-generic kernel
and found that there are no problems. During the test process I have
noted that there are no problems if the suspend is initiated manually
using the top right 'menu' to suspend instead of shutdown or reboot.
There is a problem, however, if the suspend is initiated by simply
closing the laptop.

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

Title:
  Mouse scroll wheel barely works after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After a resuming from a suspend the mouse scroll wheel is almost, but
  not quite, non functional. If you scroll quickly for a while you do
  get a slight movement of the scroll bar to show that there is some
  level of communication, but nothing remotely usable.

  The fix is to use the following commands to remove the hid_generic
  module and reinstate it:

  sudo rmmod hid_generic
  sudo modprobe hid_generic

  Following this all works as expected until the next suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-modules-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paul   1905 F pulseaudio
   /dev/snd/controlC1:  paul   1905 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 19:02:00 2019
  Dependencies:
   
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8032c5f7-74fd-4a23-92cb-5ad7d0642a9f
  InstallationDate: Installed on 2017-12-15 (491 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20238
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=63abd1a6-61ac-485b-9448-47d635ee8808 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-20 (1 days ago)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79CN50WW(V3.09)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G510
  dmi.modalias: 
dmi:bvnLENOVO:bvr79CN50WW(V3.09):bd10/20/2014:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG510:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20238
  dmi.product.sku: LENOVO_MT_20238
  dmi.product.version: Lenovo G510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825736/+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 1826228] [NEW] api3a+ hang when reading /sys/devices/platform/soc/driver_override

[Paul Larson]

Public bug reported:

I discovered this when running some tests on a core16 image with various rpi3 
devices. Rpi3b, b+, cm3, rpi2, etc... don't have this problem, only rpi3a+.
Kernel version: 
Linux localhost 4.4.0-1107-raspi2 #115-Ubuntu SMP Wed Apr 10 18:06:42 UTC 2019 
armv7l armv7l armv7l GNU/Linux


To reproduce, simply 'cat /sys/devices/platform/soc/driver_override'
The process just hangs and cannot be killed. On other rpi devices, I just get 
this output immediately:
(null)

There was nothing in dmesg or syslog when it happened, no kernel crash,
and I can still ssh into the system. The process that ran that command
just silently hangs and can't be killed even with sudo kill -9.

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

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

Title:
  api3a+ hang when reading /sys/devices/platform/soc/driver_override

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  I discovered this when running some tests on a core16 image with various rpi3 
devices. Rpi3b, b+, cm3, rpi2, etc... don't have this problem, only rpi3a+.
  Kernel version: 
  Linux localhost 4.4.0-1107-raspi2 #115-Ubuntu SMP Wed Apr 10 18:06:42 UTC 
2019 armv7l armv7l armv7l GNU/Linux

  
  To reproduce, simply 'cat /sys/devices/platform/soc/driver_override'
  The process just hangs and cannot be killed. On other rpi devices, I just get 
this output immediately:
  (null)

  There was nothing in dmesg or syslog when it happened, no kernel
  crash, and I can still ssh into the system. The process that ran that
  command just silently hangs and can't be killed even with sudo kill
  -9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1826228/+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 1826645] Re: no sound in laptop ASUS UX362FA - sending repair

[Paul White]

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

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=203443
   Importance: Unknown
   Status: Unknown

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

Title:
  no sound in laptop ASUS UX362FA - sending repair

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

Bug description:
  Hi,

I bought laptop ASUS UX362FA: https://www.asus.com/2-in-1-PCs/ASUS-
  ZenBook-Flip-13-UX362FA/

The sound didn't work. I was looking for solution and I found this
  article: https://forum.manjaro.org/t/alc294-analog-audio-card-
  detected-but-no-sound-internaly-or-headphones/54089/29


So I added this line into 
(https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_realtek.c):

SND_PCI_QUIRK(0x1043, 0x13e1, "ASUS UX362FA",
  ALC294_FIXUP_ASUS_SPK),

behind this line: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA",
  ALC294_FIXUP_ASUS_SPK)

  
 And recompile kernel and it works. I'm sending this report for others, who 
have the same problem with this laptop version. Please add this repair to 
kernel for the others. 

Thank you.

  
 

 my hwinfo:

  root@zenbook:~$ hwinfo --sound
  15: PCI 1f.3: 0403 Audio device 
[Created at pci.378]
Unique ID: nS1_.jsQALdVXpeB
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x9dc8 
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x13e1 
Revision: 0x30
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xb1218000-0xb121bfff (rw,non-prefetchable)
Memory Range: 0xb100-0xb10f (rw,non-prefetchable)
IRQ: 127 (100 events)
Module Alias: "pci:v8086d9DC8sv1043sd13E1bc04sc03i80"
Driver Info #0:
  Driver Status: snd_hda_intel is active
  Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
  Driver Status: snd_soc_skl is active
  Driver Activation Cmd: "modprobe snd_soc_skl"
Config Status: cfg=new, avail=yes, need=no, active=unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1826645/+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 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

[Paul Lai]

Chris: a little of both.  The UMONITOR/UMWAIT/TPAUSE is delay, but the
rest has been upstreamed (as you already noted.)

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

Title:
  KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Triaged
Status in xen package in Ubuntu:
  Incomplete

Bug description:
  CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) 
features including:
  - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch 
with accelerators
  - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or 
wait-for-interrupt usages
  - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator 
usages.
  - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For 
latency critical accelerator usages

  Upstream target linux 5.3/Qemu-3.10

  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+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 1782209] Re: KVM SnowRidge Split-lock disable

[Paul Lai]

Related QEMU patch can be found at:

https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg00507.html

and related kvm-unit-test can be found at:

https://patchwork.kernel.org/patch/10837677/

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

Title:
  KVM SnowRidge Split-lock disable

Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  New

Bug description:
  When bit 29 is set in Test Control MSR register 0x33, a #AC execption
   is generated for split locked accesses at all CPL irrespective of
   CR0.AM or EFLAGS.AC.

  This feature can help developers to capture memory accesses that
  across cachelines with #LOCK assertion. Then developers can
  reconstruct their program accordingly

  Upstream target linux 5.2
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782209/+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