[Kernel-packages] [Bug 1894793] Re: High load freezes ubuntu completely everytime (have to reboot)

2020-09-09 Thread Christopher M. Penalver
Alois Dirnaichner, thank you for reporting this and making Ubuntu
better.

Iin order to allow additional upstream mainline kernel developers to examine 
the issue, at your earliest convenience, could you please test the latest 
mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

** This bug is no longer a duplicate of bug 1555351
   High load freezes ubuntu completely everytime (have to reboot)

** Tags added: latest-bios-1.18.0

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

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

Title:
  High load freezes ubuntu completely everytime (have to reboot)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Followed the suggestion to report the Bug in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555351 by
  Christopher Penalver.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-115-generic 4.15.0-115.116
  ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18
  Uname: Linux 4.15.0-115-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alois  3256 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  8 09:07:16 2020
  InstallationDate: Installed on 2018-05-15 (846 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Latitude 7480
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-115-generic 
root=UUID=32418d9d-1b21-4d1f-91ed-be3fd7ad01cb ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-115-generic N/A
   linux-backports-modules-4.15.0-115-generic  N/A
   linux-firmware  1.173.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd06/05/2020:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1612916] Re: [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

2019-11-24 Thread Christopher M. Penalver
apsaras, it's helpful for developers if folks report their own bug so logs may 
be obtained from the hardware, regardless of similarities, via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

To do otherwise risks issues being ignored as unconfirmable noise.

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1848445] Re: [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot

2019-11-03 Thread Christopher M. Penalver
Ilgaz, could you please report this problem following the instructions
at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate
mailing list (TO: Rafael J. Wysocki and Len Brown CC: linux-acpi)?

Please provide a direct URL to your post to the mailing list (not
Bugzilla) when it becomes available so that it may be tracked.

Thank you for your help.

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

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

Title:
  [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi=
  required to boot

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1848445] Re: [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot

2019-11-03 Thread Christopher M. Penalver
Ilgaz, to help developers debug a potential ACPI/BIOS bug, could you please 
install the package acpidump and attach to this report uncompressed and 
untarred the following via a terminal:
sudo acpidump -o acpidump.txt

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

Title:
  [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi=
  required to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1848445] Re: [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= required to boot

2019-11-03 Thread Christopher M. Penalver
** Summary changed:

- Kernel needs a special workaround argument to boot 
+ [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi= 
required to boot

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

Title:
  [HP Pavilion 360 - 13-a200nt (ENERGY STAR)] Kernel parameter acpi_osi=
  required to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2019-11-03 Thread Christopher M. Penalver
whl2:

1) As noted in #32, one will want to keep testing the latest upstream
kernel (now 5.4-rc5) as it is released, or one risks developers not
paying attention to your problem.

2) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+subscriptions

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


[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2019-11-03 Thread Christopher M. Penalver
** Tags added: eoan needs-upstream-testing

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+subscriptions

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


[Kernel-packages] [Bug 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-03 Thread Christopher M. Penalver
Ilgaz, to clarify, did you actually try to gather logs as per all
techniques noted in
https://help.ubuntu.com/community/DebuggingSystemCrash or are you making
assumptions of your not being able to?

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-02 Thread Christopher M. Penalver
Ilgaz:

To advise, you have missed steps in two different comments, which are
vital to proceed. Please ensure you are responding to all items
requested.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/comments/10:
C) To further clarify, does removing the external HDD device (USB?) impact your 
ability to boot?

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/comments/13:
2) Please review https://help.ubuntu.com/community/DebuggingSystemCrash and 
attempt all suggestions to see if something useful may be obtained.

** Tags removed: kernel-bug-exists-upstream-5.4-rc3 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-5.4-rc5

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-02 Thread Christopher M. Penalver
Ilgaz:

1) To keep this relevant to upstream, you will want to continue to test
the latest mainline kernel as it is released (now 5.4-rc5). Instructions
are available via https://wiki.ubuntu.com/Kernel/MainlineBuilds .

2) Please review https://help.ubuntu.com/community/DebuggingSystemCrash
and attempt all suggestions to see if something useful may be obtained.

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-02 Thread Christopher M. Penalver
Ilgaz:

A) I'm afraid providing logs from a working boot does nothing to help.

B) To clarify, you removed all of the following kernel parameters:
quiet
splash
vt.handoff=7
acpi_osi=
pci=biosirq

then changed:
gfxmode $linux_gfx_mode

to:

gfxmode text

and then got the bad boot? If so, please provide video evidence starting
from the computer being off all the way to it stopped booting (e.g. take
a video of the computer screen via phone, get logs, etc.). Please note,
stating it was a bad boot isn't helpful given this was already known.

C) To further clarify, does removing the external HDD device (USB?)
impact your ability to boot?

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-02 Thread Christopher M. Penalver
** Description changed:

- When booting my computer, it stops with just a non-blinking white cursor
- on screen in the top left, and the Caps Lock doesn't respond when
- pressed.
+ When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops with
+ just a non-blinking white cursor on screen in the top left, and the Caps
+ Lock doesn't respond when pressed.
  
  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.
  
  WORKAROUND: Boot with kernel parameter:
  acpi_osi=
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

** Tags added: latest-bios-f.41

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my HP Pavilion 360 - 13-a200nt (ENERGY STAR), it stops
  with just a non-blinking white cursor on screen in the top left, and
  the Caps Lock doesn't respond when pressed.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems.

  WORKAROUND: Boot with kernel parameter:
  acpi_osi=

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  

[Kernel-packages] [Bug 1847151] Re: Touchpad not detected

2019-11-01 Thread Christopher M. Penalver
As per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847151/comments/4
.

** Changed in: linux (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/1847151

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrading to Ubuntu 5.0.0-31.33-generic 5.0.21 (from 5.0.0-29),
  my laptop's touchpad is no longer detected as a device. This is a new
  problem.

  Contents of /proc/bus/input/devices attached.

  Following directions from
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pss3353 F pulseaudio
   /dev/snd/controlC0:  pss3353 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Mon Oct  7 14:14:13 2019
  InstallationDate: Installed on 2019-04-24 (166 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS73 Stealth 8RF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=76a404c8-db6d-4ab3-8614-86dbef6fdda8 ro "acpi_osi=!acpi_osi=Windows 
2009" quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-29 (161 days ago)
  dmi.bios.date: 10/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17B7IMS.10F
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17B7
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17B7IMS.10F:bd10/03/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS73Stealth8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17B7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GS
  dmi.product.name: GS73 Stealth 8RF
  dmi.product.sku: 17B7.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-04-25T10:50:34.601584

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

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


[Kernel-packages] [Bug 1848017] Re: Kernel needs a special workaround argument to boot

2019-11-01 Thread Christopher M. Penalver
*** This bug is a duplicate of bug 1848445 ***
https://bugs.launchpad.net/bugs/1848445

** This bug has been marked a duplicate of bug 1848445
   Kernel needs a special workaround argument to boot

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

Title:
  Kernel needs a special workaround argument to boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 19.04
  Release:  19.04

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center

  3) What you expected to happen

  Boot

  4) What happened instead

  Freezes (see below for workaround), no visible sign of interaction
  possible. Caps lock "led" doesn't work indicating keyboard isn't
  working. Just a white cursor (non blinking) on screen, CPU doesn't
  seem to do anything since fan stops after a while.

  This is more likely a Linux "bug". Unless you pass acpi_osi= argument
  to Linux kernel, it won't boot, appear and behave frozen with a (non
  blinking) cursor on top left. There is no further information given to
  user further complicating things.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems on this particular laptop model (HP Pavilion
  X360 13 inch).

  As they are for proprietary broadcom bcm43142 chip, I am not adding
  further arguments in this bug report. Can tell on request if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-31-generic 5.0.0-31.33
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz  1897 F pulseaudio
   /dev/snd/controlC1:  ilgaz  1897 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz  1897 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 14 15:33:41 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (1 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-10-13 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1848445] Re: Kernel needs a special workaround argument to boot

2019-11-01 Thread Christopher M. Penalver
Ilgaz:

1) Could you please provide from the the sticker of the computer itself
(not from the Bug Description, or the result of a terminal command) the
full computer model? For example, HP Pavilion 13-u100 x360 Convertible
PC.

2) Could you please undo all WORKAROUNDs and non-default kernel
parameters and provide logs of a bad boot following
https://wiki.ubuntu.com/DebuggingKernelBoot ?

3) Could you please advise to the purpose of the non-default kernel
parameter pci=biosirq (i.e. is it required along with acpi_osi=, does it
improve functionality with or without other parameters, etc.)?

** Description changed:

- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
- Description: Ubuntu 19.10
- Release: 19.10
- 
- 2) The version of the package you are using, via 'apt-cache policy
- pkgname' or by checking in Software Center
- 
- 3) What you expected to happen
- 
- Boot
- 
- 4) What happened instead
- 
- Freezes (see below for workaround), no visible sign of interaction
- possible. Caps lock "led" doesn't work indicating keyboard isn't
- working. Just a white cursor (non blinking) on screen, CPU doesn't seem
- to do anything since fan stops after a while.
- 
- This is more likely a Linux "bug". Unless you pass acpi_osi= argument to
- Linux kernel, it won't boot, appear and behave frozen with a (non
- blinking) cursor on top left. There is no further information given to
- user further complicating things.
+ When booting my computer, it stops with just a non-blinking white cursor
+ on screen in the top left, and the Caps Lock doesn't respond when
+ pressed.
  
  Previously on 4.x kernels, system would boot using acpi=off argument
- creating more problems on this particular laptop model (HP Pavilion X360
- 13 inch).
+ creating more problems.
+ 
+ WORKAROUND: Boot with kernel parameter:
+ acpi_osi=
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
-  /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
-  /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
+  /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
+  /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
-  linux-restricted-modules-5.3.0-18-generic N/A
-  linux-backports-modules-5.3.0-18-generic  N/A
-  linux-firmware1.183
+  linux-restricted-modules-5.3.0-18-generic N/A
+  linux-backports-modules-5.3.0-18-generic  N/A
+  linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

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

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

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

** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing

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

Title:
  Kernel needs a special workaround argument to boot

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

Bug description:
  When booting my computer, it stops with just a non-blinking white
  cursor on screen in the top left, and the Caps Lock doesn't respond
  when pressed.

  Previously 

[Kernel-packages] [Bug 1849276] Re: alfa-AWUS036ACH wifi usb adapter not working

2019-11-01 Thread Christopher M. Penalver
azamet, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream mainline kernel developers to examine the 
issue, at your earliest convenience, could you please test the latest mainline 
kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

** Description changed:

- i did tryed the driver from ubuntu repo but even the light was not opening my 
wifi adaptor so i did tryed to install the driver from github source with this 
method down:
+ My ALfa AWUS036ACH WiFi USB adapter (
+ https://www.alfa.com.tw/products_detail/1.htm ) doesn't work with the
+ default drivers.
+ 
+ WORKAROUND: Install the driver via:
  https://drive.google.com/file/d/1Vn4KzClyCQ0XeMrAGjE7OvEMeBZgg6Xb/view
- 
- now it is working for connecting to networks but i cannot use any wifi tools 
cannot create ap airmon-ng wlanname monitor mode gives me:
- sudo airmon-ng start wlx00c0caa51d03
- 
- Found 4 processes that could cause trouble.
- Kill them using 'airmon-ng check kill' before putting
- the card in monitor mode, they will interfere by changing channels
- and sometimes putting the interface back in managed mode
- 
-   PID Name
-  1065 wpa_supplicant
-  1088 NetworkManager
-  1094 avahi-daemon
-  1109 avahi-daemon
- 
- PHY Interface   Driver  Chipset
- 
- phy0  wlo1iwlwifi Intel Corporation Wireless-AC 9560 
[Jefferson Peak] (rev 10)
- phy1  wlx00c0caa51d03 88XXau  Realtek Semiconductor Corp. RTL8812AU 
802.11a/b/g/n/ac 2T2R DB WLAN Adapter
- 
- Error setting channel: command failed: Device or resource busy (-16)
- Error -16 likely means your card was set back to station mode by something.
- Removing non-monitor wlx00c0caa51d03 interface...
- 
- if i try with check kill before the result of monitor mode is same only this 
no have:
- "  PID Name
-  1065 wpa_supplicant
-  1088 NetworkManager
-  1094 avahi-daemon
-  1109 avahi-daemon
- 
- "
- like that tool any tool i try giving me some errors how to fix those?
- 
- 
- w phy
-  16:57:53 up  2:15,  1 user,  load average: 0,78, 0,47, 0,44
- USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
- 
- 
- iw dev
- phy#1
-   Interface wlx00c0caa51d03
-   ifindex 4
-   wdev 0x10001
-   addr 00:c0:ca:a5:1d:03
-   type managed
-   txpower 0.00 dBm
- phy#0
-   Unnamed/non-netdev interface
-   wdev 0x2
-   addr 0c:dd:24:2a:ff:77
-   type P2P-device
-   txpower 0.00 dBm
-   Interface wlo1
-   ifindex 3
-   wdev 0x1
-   addr 0c:dd:24:2a:ff:76
-   ssid Azamet
-   type managed
-   channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
-   txpower 20.00 dBm
-   multicast TXQ:
-   qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol 
tx-bytestx-packets
-   0   0   0   0   0   0   0   
0   0
- 
- 
- systemctl status NetworkManager
- ● NetworkManager.service - Network Manager
-Loaded: loaded 

[Kernel-packages] [Bug 1612916] Re: Internal speakers don't work after standby

2019-10-28 Thread Christopher M. Penalver
Michael, it wouldn't hurt to update your BIOS to the latest (now. 6.30),
given it includes multiple, high severity security vulnerability fixes.

Once done, could you please advise if this changes anything, and post the 
results of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

If still reproducible, to keep this relevant, please attempt a suspend
via live environment of http://cdimage.ubuntu.com/daily-live/current/
and advise on the outcome.

** Changed in: linux (Ubuntu)
   Importance: Medium => Low

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

** Summary changed:

- Internal speakers don't work after standby
+ [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

** Description changed:

- I've a Toshiba x20t-C-121 (Skylake m7-6Y75 based). On initial boot,
- sound on internal speakers is working. After standby it doesn work
- anymore, but a analog headset does. Switching around in pavucontrol
- doesn't work... Internal microphone works.
+ On initial boot, sound on internal speakers is working. After standby it
+ doesn work anymore, but a analog headset does. Switching around in
+ pavucontrol doesn't work... Internal microphone works.
  
  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.
+ 
+ Toshiba/Dynabook Portege Z20T-C:
+ 
https://support.dynabook.com/support/modelHome?freeText=1200015981=785
+ 
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  On initial boot, sound on internal speakers is working. After standby
  it doesn work anymore, but a analog headset does. Switching around in
  pavucontrol doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.

  Toshiba/Dynabook Portege Z20T-C:
  
https://support.dynabook.com/support/modelHome?freeText=1200015981=785

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  

[Kernel-packages] [Bug 1612916] Re: Internal speakers don't work after standby

2019-10-28 Thread Christopher M. Penalver
** Tags removed: kernel-bug-exists-upstream latest-bios-5.60
** Tags added: bios-outdated-6.30 needs-upstream-testing

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

Title:
  [Tohsiba Portege Z20T-C] Internal speakers don't work after standby

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

Bug description:
  I've a Toshiba x20t-C-121 (Skylake m7-6Y75 based). On initial boot,
  sound on internal speakers is working. After standby it doesn work
  anymore, but a analog headset does. Switching around in pavucontrol
  doesn't work... Internal microphone works.

  I'm using Ubuntu 16.04 64 bit on a 4.4.0-34-generic kernel.
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michi  6510 F pulseaudio
  CurrentDesktop: GNOME-Flashback:Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/1tb-swap
  MachineType: TOSHIBA PORTEGE Z20t-C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-34-generic.efi.signed 
root=/dev/mapper/1tb-miniubuntu ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/27/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.60
  dmi.board.asset.tag: 00
  dmi.board.name: PORTEGE Z20t-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.60:bd06/27/2016:svnTOSHIBA:pnPORTEGEZ20t-C:pvrPT16BE-00W006GR:rvnTOSHIBA:rnPORTEGEZ20t-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z20t-C
  dmi.product.version: PT16BE-00W006GR
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 992778] Re: Dual Monitor Freeze after changing Display Settings in ubuntu 12.04

2019-10-28 Thread Christopher M. Penalver
Medya, this report is being closed as no debugging logs regarding your
problem have been provided by you, as requested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/992778/comments/43
.

However, if this is still reproducible in a supported release, please
follow the previous instructions, and mark this report as Status New.

** Description changed:

  I had 11.10 64bit, I upgraded to 12.04
  
  if I change the settings in the Display it will freeze .
  -  if I move the external monitor  to the left of laptop monitor , (or above 
it) it will freeze
-  - if I try to turn of the laptop monitor ,so I only have my external monitor 
it will freeze again.
+  - if I try to turn of the laptop monitor ,so I only have my external monitor 
it will freeze again.
  
  the mouse wont move and I have to reset the computer by ALT PRINT K to
  come back to ubuntu
  
- dual monitor used to work fine in ubuntu 11.10 , is there any way to 
downgrade the Display program to the one in 11.10 ?
- --- 
+ dual monitor used to work fine in ubuntu 11.10 , is there any way to
+ downgrade the Display program to the one in 11.10 ?
+ 
+ WORKAROUND: Install packages from
+ https://launchpad.net/~sarvatt/+archive/sru1/+build/3118994
+ 
+ ---
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  Package: linux (not installed)
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-meta
  Tags:  precise precise
  Uname: Linux 3.3.0-030300rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to precise on 2012-05-01 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

** Changed in: linux (Ubuntu)
   Status: Fix Released => 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/992778

Title:
  Dual Monitor Freeze after changing Display Settings in ubuntu 12.04

Status in X.Org X server:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I had 11.10 64bit, I upgraded to 12.04

  if I change the settings in the Display it will freeze .
  -  if I move the external monitor  to the left of laptop monitor , (or above 
it) it will freeze
   - if I try to turn of the laptop monitor ,so I only have my external monitor 
it will freeze again.

  the mouse wont move and I have to reset the computer by ALT PRINT K to
  come back to ubuntu

  dual monitor used to work fine in ubuntu 11.10 , is there any way to
  downgrade the Display program to the one in 11.10 ?

  WORKAROUND: Install packages from
  https://launchpad.net/~sarvatt/+archive/sru1/+build/3118994

  ---
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta
  Tags:  precise precise
  Uname: Linux 3.3.0-030300rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to precise on 2012-05-01 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/992778/+subscriptions

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


[Kernel-packages] [Bug 1727662] Re: [Lenovo ThinkPad T450s] Issues after docking and locking: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2019-10-17 Thread Christopher M. Penalver
Alexander Kops, to keep this relevant to upstream, one would want to
periodically check for, and test the latest mainline kernel (now
5.4-rc3) as it is released, to confirm if the drm-tip improvements have
been made available for inclusion into Ubuntu.

Could you please advise?

** This bug is no longer a duplicate of bug 1550779
   [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO 
underrun

** Summary changed:

- [Lenovo ThinkPad T450s] Issues after docking and locking: 
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO 
underrun
+ [Lenovo ThinkPad T450s] Issues after docking and locking

** Tags removed: bios-outdated-1.35 kernel-bug-exists-upstream
** Tags added: bios-outdated-1.37 needs-upstream-testing

** Attachment removed: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5218810/+files/dmesg

** Attachment removed: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+attachment/5205731/+files/kern.log

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

Title:
  [Lenovo ThinkPad T450s] Issues after docking and locking

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

Bug description:
  What happens is after I dock my laptop into a Lenovo ThinkPad Ultra Dock Type 
40A2 20V, lock it via clicking the lock icon, and wait ~30 minutes, one of the 
following three things happen ~50% of the time when I come back to unlock it:
  * Most of the time the computer is found shut down.
  * Sometimes the notebook screen flickers weirdly and one of the two external 
monitors show pixelation.
  * The notebook screen shows the lock screen but is completely frozen. 
Occasionally unlocking works.

  I have two external monitors attached to the docking station.

  When I dock my laptop, the battery indicator does recognize its
  charging.

  I've not seen this issue when:
  1) With the laptop in the dock, while actively using the laptop.
  2) With the laptop out of the dock and no external monitors present.

  This bug started after upgrading from Ubtuntu 17.04 to Ubuntu 17.10.

  Using or not using the following kernel parameter didn't change anything:
  i915.enable_rc6=0

  Updated docking station firmware to latest 2.33.00.

  PC temperatures are normal as per lm-sensors.

  20171109 - Not reproducible testing drm-tip for 1.5 days.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  akops  3337 F pulseaudio
   /dev/snd/controlC0:  akops  3337 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:44:11 2017
  HibernationDevice: RESUME=/dev/mapper/system-swap_1
  MachineType: LENOVO 20BWS2YL00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency 
root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 
crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-lowlatency N/A
   linux-backports-modules-4.13.0-16-lowlatency  N/A
   linux-firmware1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago)
  dmi.bios.date: 07/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET51WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS2YL00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS2YL00
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1589418] Re: udisksd high CPU usage

2019-09-27 Thread Christopher M. Penalver
eris23 (jdkatz23), it will help immensely if you use Ubuntu with the computer 
the problem is reproducible with and file a new report via a terminal to 
provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Tags removed: bios-outdated-1.22
** Tags added: bios-outdated-1.37

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

Title:
  udisksd high CPU usage

Status in linux package in Ubuntu:
  Expired

Bug description:
  Using:  libudisks2-0:amd64 2.1.6-2ubuntu1

  Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Description:  Ubuntu 15.10
  Release:  15.10

  When I add USB drives to my system I end-up with udisksd using 100% of
  a core shortly after. After some time this goes up to 200% (in one
  step), so using 2 cores. Thread view shows CPU time of CMD 'pool':

  # ps -T -p  
PID  SPID TTY  TIME CMD
  26229 26229 ?00:00:00 udisksd
  26229 26230 ?00:00:00 gmain
  26229 26232 ?00:00:00 gdbus
  26229 26233 ?00:00:00 probing-thread
  26229 26234 ?00:00:00 cleanup
  26229  3325 ?00:33:16 pool
  26229  5027 ?00:03:00 pool

  
  My solution is to kill it and let it restart.

  Strace needs to follow threads to show activity, it's then flooding
  with:

  # strace -p  -f
  [pid  3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, 
events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2 ([{fd=12, revents=POLLIN}, 
{fd=17, revents=POLLOUT}])
  [pid  3325] read(12, "\2\0\0\0\0\0\0\0", 16) = 8
  [pid  3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8
  [pid  3325] write(2, "\n(udisksd:26229): GLib-WARNING *"..., 87) = 87
  [pid  3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8
  [pid  3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, 
events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2 ([{fd=12, revents=POLLIN}, 
{fd=17, revents=POLLOUT}])
  [pid  3325] read(12, "\2\0\0\0\0\0\0\0", 16) = 8
  [pid  3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8
  [pid  3325] write(2, "\n(udisksd:26229): GLib-WARNING *"..., 87) = 87
  [pid  3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8
  [pid  3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, 
events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2 ([{fd=12, revents=POLLIN}, 
{fd=17, revents=POLLOUT}])
  [pid  3325] read(12, "\2\0\0\0\0\0\0\0", 16) = 8
  [pid  3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8
  [pid  3325] write(2, "\n(udisksd:26229): GLib-WARNING *"..., 87) = 87
  [pid  3325] write(12, "\1\0\0\0\0\0\0\0", 8) = 8
  [pid  3325] poll([{fd=12, events=POLLIN}, {fd=17, events=POLLOUT}, {fd=18, 
events=POLLIN}, {fd=20, events=POLLIN}], 4, 0) = 2^CProcess 26229 detached

  
  THANKS!
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bones  1880 F panel-8-mixer
bones  1944 F pulseaudio
   /dev/snd/controlC1:  bones  1880 F panel-8-mixer
bones  1944 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=34ae084e-472d-4798-bacb-fd0f010fe477
  InstallationDate: Installed on 2016-01-06 (154 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-36-generic N/A
   linux-backports-modules-4.2.0-36-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications 

[Kernel-packages] [Bug 1332764] Re: [Dell Studio 1458] Black (off) screen after waking from suspend

2019-09-18 Thread Christopher M. Penalver
André Barboza Rocha, it will help immensely if you use Ubuntu and provide 
required debugging information by running the following command in a terminal:
ubuntu-bug linux

Please feel free to subscribe me to 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/1332764

Title:
  [Dell Studio 1458] Black (off) screen after waking from suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  The laptop wakes up from suspend with a black screen i.e. screen not
  turned ON. The keyboard and mouse seems to be responsive as backlit
  turns ON if I click any key or touch track pad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  atul   2085 F pulseaudio
   /dev/snd/controlC0:  atul   2085 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jun 20 22:55:37 2014
  HibernationDevice: RESUME=UUID=15f965f3-ae06-4b09-a249-61c32e50481e
  InstallationDate: Installed on 2014-04-19 (62 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Studio 1458
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=12be9505-0800-40e5-8928-e60118a8f0c2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0VF0FR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/27/2010:svnDellInc.:pnStudio1458:pvrA06:rvnDellInc.:rn0VF0FR:rvrA06:cvnDellInc.:ct8:cvrA06:
  dmi.product.name: Studio 1458
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1584479] Re: [MSI GP72 6QE Leopard Pro] acpi=off required to boot

2019-09-18 Thread Christopher M. Penalver
Sam, to keep this relevant to upstream, could you please test the latest
mainline kernel (now 5.3)?

As new kernels are released upstream, please continue to test them.
Otherwise, you risk developers not remaining focused on your problem.

If reproducible, with the latest mainline kernel, please provide an
uncut, untarred, and uncompressed log of the failed boot (no
WORKAROUNDs).

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

Title:
  [MSI GP72 6QE Leopard Pro] acpi=off required to boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just install Ubuntu 16.04 on my new MSI laptop G72 6QE.
  My touchpad doesn't work and recognize at all.

  I try :
  - Fn+F3 to activate my touchpad
  - xinput list and is not listed
  - xev and nothing append (no signal)
  - cat /proc/bus/input/devices ddoesn't display touchpad (only HDMI, mic, 
headphone, external mouse and keyboard)
  - I don't know if there is a link, but some buttons of my keyboard don't work 
(like Fn+arrows to manage sound and luminosity) :
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  
  Thanks
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1305 F pulseaudio
moi1668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9649bbed-2d32-42cd-a446-43abaa9ab1f3
  InstallationDate: Installed on 2016-05-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Micro-Star International Co., Ltd. GP72 6QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=80432220-0bdf-49f0-a145-0c015ad36c2a ro rootflags=subvol=@ acpi=off 
acpi_osi=! acpi_backlight=native i8042.nopnp quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1795IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1795
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1795IMS.10C:bd12/10/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP726QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1795:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP72 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Kernel-packages] [Bug 1584479] Re: [MSI GP72 6QE Leopard Pro] acpi=off required to boot

2019-09-18 Thread Christopher M. Penalver
oscar (chillvamp), it will help immensely if you filed a new report to provide 
required debugging information via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Tags removed: kernel-bug-exists-upstream latest-bios-114
** Tags added: bios-outdated-e1795ims.11d needs-upstream-testing

** Changed in: linux (Ubuntu)
   Importance: Medium => Low

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

Title:
  [MSI GP72 6QE Leopard Pro] acpi=off required to boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just install Ubuntu 16.04 on my new MSI laptop G72 6QE.
  My touchpad doesn't work and recognize at all.

  I try :
  - Fn+F3 to activate my touchpad
  - xinput list and is not listed
  - xev and nothing append (no signal)
  - cat /proc/bus/input/devices ddoesn't display touchpad (only HDMI, mic, 
headphone, external mouse and keyboard)
  - I don't know if there is a link, but some buttons of my keyboard don't work 
(like Fn+arrows to manage sound and luminosity) :
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  
  Thanks
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1305 F pulseaudio
moi1668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9649bbed-2d32-42cd-a446-43abaa9ab1f3
  InstallationDate: Installed on 2016-05-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Micro-Star International Co., Ltd. GP72 6QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=80432220-0bdf-49f0-a145-0c015ad36c2a ro rootflags=subvol=@ acpi=off 
acpi_osi=! acpi_backlight=native i8042.nopnp quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1795IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1795
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1795IMS.10C:bd12/10/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP726QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1795:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP72 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Kernel-packages] [Bug 1792672] Re: Regression: acpi reports battery state incorrectly after sleep

2019-09-18 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1792672

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2019-09-01 Thread Christopher M. Penalver
** Tags removed: latest-bios-304
** Tags added: latest-bios-307

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+subscriptions

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


[Kernel-packages] [Bug 1833169] Re: intel_max_cstate is needed with baytrail to aviod hangups

2019-08-18 Thread Christopher M. Penalver
** Tags added: cherry-pick kernel-fixed-upstream

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

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

Title:
  intel_max_cstate is needed with baytrail to aviod hangups

Status in linux package in Ubuntu:
  Triaged

Bug description:
  https://bugzilla.kernel.org/show_bug.cgi?id=109051

  fix (will be merged on 5.2 merge window, so I will need backport):
  
https://cgit.freedesktop.org/drm-intel/commit/?id=a75d035fedbdecf83f86767aa2e4d05c8c4ffd95

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic-hwe-18.04 4.18.0.21.71
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 18 08:14:08 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-meta-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jaime  1741 F pulseaudio
   /dev/snd/controlC0:  jaime  1741 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-17 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 04f2:b490 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=b12b3d55-99d9-45f0-87f5-46cedaeb5806 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-22-generic N/A
   linux-backports-modules-4.18.0-22-generic  N/A
   linux-firmware 1.173.6
  Tags:  wayland-session bionic
  Uname: Linux 4.18.0-22-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/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

2019-08-12 Thread Christopher M. Penalver
Chi-Thanh Christopher Nguyen, please note:

1) The kernel 5.2.7 is not supported here on Launchapd. Hence, please
re-direct your inquiry to the relevant maintainer(s) upstream.

2) If you can reproduce the issue with a supported kernel then please file a 
new report to provide debugging logs via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

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

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

Title:
  14e4:1687 broadcom tg3 network driver disconnects under high load

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The tg3 broadcom network driver that binds with chipset 5762 goes offline and 
unable to recover (even with tg3 watchdog timeout) when network transmit is 
under high load.  Call trace:
  https://launchpadlibrarian.net/204185480/dmesg

  When this happens, only a reboot would be able to fix it.  Sometimes,
  however, bringing the interface offline and online (via ifconfig)
  would recover networking.  I've also tested with the latest tg3 driver
  (dec 2014 version) and networking is still problematic.  I have also
  disabled TSO, GSO etc... with ethtool and the bug still surfaces.
  This bug may be related to the integrated Firmware.

  Here is the procedure to replicate the issue because it is hard to
  replicate it under moderate network load.

  1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a 
Ubuntu/Kubunu Live CD 14.04-15.04.
  2. from another machine: start 5 sessions, repetitively copy (scp with public 
key authentication) a 70 meg file back and forth to the tg3 machine in each 
session. (not sure if this is necessary)
  3. create a 1GB file on the tg3 machine, with something like dd 
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
  4. from another machine: repetitively scp copy that 1GB file from the tg3 
machine. This can be done with something like:

  while [ 0 ]; do
     scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
  done;

  Networking will mostly goes offline in about 10-30 minutes.

  WORKAROUND: Add udev rule to make the changes permanent in 
/etc/udev/rules.d/80-tg3-fix.rules :
  ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", 
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3748 F pulseaudio
   /dev/snd/controlC0:  kubuntu3748 F pulseaudio
  CasperVersion: 1.360
  Date: Thu Apr 23 11:16:24 2015
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:

  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.15
  dmi.board.asset.tag: 2UA5041TG4
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5041TG4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

2019-08-12 Thread Christopher M. Penalver
** No longer affects: 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/1447664

Title:
  14e4:1687 broadcom tg3 network driver disconnects under high load

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The tg3 broadcom network driver that binds with chipset 5762 goes offline and 
unable to recover (even with tg3 watchdog timeout) when network transmit is 
under high load.  Call trace:
  https://launchpadlibrarian.net/204185480/dmesg

  When this happens, only a reboot would be able to fix it.  Sometimes,
  however, bringing the interface offline and online (via ifconfig)
  would recover networking.  I've also tested with the latest tg3 driver
  (dec 2014 version) and networking is still problematic.  I have also
  disabled TSO, GSO etc... with ethtool and the bug still surfaces.
  This bug may be related to the integrated Firmware.

  Here is the procedure to replicate the issue because it is hard to
  replicate it under moderate network load.

  1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a 
Ubuntu/Kubunu Live CD 14.04-15.04.
  2. from another machine: start 5 sessions, repetitively copy (scp with public 
key authentication) a 70 meg file back and forth to the tg3 machine in each 
session. (not sure if this is necessary)
  3. create a 1GB file on the tg3 machine, with something like dd 
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
  4. from another machine: repetitively scp copy that 1GB file from the tg3 
machine. This can be done with something like:

  while [ 0 ]; do
     scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
  done;

  Networking will mostly goes offline in about 10-30 minutes.

  WORKAROUND: Add udev rule to make the changes permanent in 
/etc/udev/rules.d/80-tg3-fix.rules :
  ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", 
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3748 F pulseaudio
   /dev/snd/controlC0:  kubuntu3748 F pulseaudio
  CasperVersion: 1.360
  Date: Thu Apr 23 11:16:24 2015
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:

  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.15
  dmi.board.asset.tag: 2UA5041TG4
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5041TG4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1455940] Re: 1969:1091 Ethernet connection lost after a while

2019-08-04 Thread Christopher M. Penalver
infopox:

1) Could you please advise to the upstream URL requested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455940/comments/33
?

2) Is this reproducible in a supported release?

** Changed in: linux (Ubuntu)
   Importance: Medium => Low

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

Title:
  1969:1091 Ethernet connection lost after a while

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ethernet network connection lost after a while.

  WORKAROUND: Temporarily via:
  ifconfig eth0 mtu 9000

  or permanently in network manager.

  ---
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eric   2349 F pulseaudio
   /dev/snd/controlC0:  eric   2349 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=8b4bc51b-4c9c-4e1e-823d-7daca442aab6
  InstallationDate: Installed on 2014-06-08 (344 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard h8-1340ef
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed 
root=UUID=3a75e1e0-7666-4142-a826-9eedc88f7f5d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.19.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.15
  dmi.board.name: 2AD5
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: CZC2316CR9
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.15:bd07/02/2012:svnHewlett-Packard:pnh8-1340ef:pvr1.00:rvnPEGATRONCORPORATION:rn2AD5:rvr1.03:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: h8-1340ef
  dmi.product.version: 1.00
  dmi.sys.vendor: Hewlett-Packard
  ---
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eric   2617 F pulseaudio
   /dev/snd/controlC0:  eric   2617 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=8b4bc51b-4c9c-4e1e-823d-7daca442aab6
  InstallationDate: Installed on 2014-06-08 (348 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed 
root=UUID=3a75e1e0-7666-4142-a826-9eedc88f7f5d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.19.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.21
  dmi.board.name: 2AD5
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.21:bd10/20/2014:svnHewlett-Packard:pn:pvr1.00:rvnPEGATRONCORPORATION:rn2AD5:rvr1.03:cvnHewlett-Packard:ct3:cvr:
  dmi.product.version: 1.00
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1555351] Re: High load freezes ubuntu completely everytime (have to reboot)

2019-07-24 Thread Christopher M. Penalver
Igor Buess, unfortunately, your comment is too vague, and lacking
details to be actionable in any way.

However, if you would like your issue addressed, it will help immensely if you 
use Ubuntu with the computer the problem is reproducible with and file a new 
report via a terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to 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/1555351

Title:
  High load freezes ubuntu completely everytime (have to reboot)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Whenever an intensive application runs which consumes lots of memory
  or hard drive i/o, Ubuntu freezes completely. It is even impossible to
  kill the offending task. Only "solution" is then to wait for the
  application to finish, or restart PC.

  Windows doesn't have this issue as bad as Ubuntu, in that Windows is
  always somewhat responsive, and you can attempt to kill the intensive
  application to recover the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-32-generic 4.2.0-32.37
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-32-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   Cannot stat file /proc/18210/fd/20: Input/output error
    USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cossio 2082 F pulseaudio
   /dev/snd/controlC1:  cossio 2082 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Mar  9 22:28:53 2016
  HibernationDevice: RESUME=UUID=37d586ee-f517-4977-b9cd-189c200b0bac
  InstallationDate: Installed on 2015-08-03 (219 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  MachineType: ASUSTeK COMPUTER INC. X550LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed 
root=UUID=52be177f-a0ea-4053-be39-bbeaff1a22df ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-32-generic N/A
   linux-backports-modules-4.2.0-32-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2016-01-31 (38 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.505
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LA.505:bd04/01/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LA
  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/1555351/+subscriptions

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


[Kernel-packages] [Bug 1837682] Re: [Dell XPS 13 9350] Mouse cursor flickers when connecting to 2nd monitor using Displaylink Dell 4-in-1 adapter

2019-07-24 Thread Christopher M. Penalver
Quoc Khanh Le, thank you for reporting this and helping make Ubuntu
better. Please answer all of the following:

1) To advise, you are using an unsupported version of Ubuntu (18.10, EOL July 
18, 2019). For more on this, please see https://wiki.ubuntu.com/Releases . 
Please upgrade to a supported version. Once done, please then run the following 
commmand once in a terminal to attach debugging information:
apport-collect 1837682

2)  To confirm, the 'Displaylink Dell 4-in-1 adapter' you have is the
'Dell Adapter - USB 3.0 to HDMI/VGA/Ethernet/USB 2.0 Model: DA100' noted
in https://www.dell.com/support/home/us/en/04/product-support/product
/dell-universal-dongle-da100/docs ?

3) To clarify what is the earliest version of all the following you tested that 
reproduced this problem:
3a. the DisplayLink driver
3b. Ubuntu (e.g. tried 14.04 x64 same hardware, same problem)

4) To confirm, the problem is reproducible via either USB port on your
laptop?

5) What is the full manufacturer and model of the second monitor?

6) Does this also happen if you use the HDMI port on the Dell 4-in-1
adapter instead of VGA?

7) Does the issue happen if you bypass the Dell 4-in-1 adapter and
connect the laptop directly to the second monitor?

8) To confirm a WORKAROUND if you use GNOME Flashback (Metacity) session
instead of KDE is the problem reproducible?

9) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

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

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

Title:
  [Dell XPS 13 9350] Mouse cursor flickers when connecting to 2nd
  monitor using Displaylink Dell 4-in-1 adapter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When my laptop is connected to a second monitor via the VGA port on
  the Dell 4-in-1 adapter, the mouse cursor flickers. DisplayLink driver
  5.2.14 is used.

  WORKAROUND: As per 
https://github.com/DisplayLink/evdi/issues/29#issuecomment-479529359 add to 
file:
  /usr/share/X11/xorg.conf.d/21-displaylink.conf

  the following and reboot:
  Section "Device"
    Identifier "DisplayLink"
    Driver "modesetting"
    Option "PageFlip" "false"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  qkle   1758 F pulseaudio
   /dev/snd/controlC0:  qkle   1758 F pulseaudio
   /dev/snd/pcmC0D0c:   qkle   1758 F...m pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jul 24 11:54:16 2019
  InstallationDate: Installed on 2018-11-22 (243 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=c68d8a53-b2fe-4f1b-8cd3-b52cc8908400 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2019-03-19 (126 days ago)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd08/31/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.product.sku: 0704
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1837682] Re: [Dell XPS 13 9350] Mouse cursor flickers when connecting to 2nd monitor using Displaylink Dell 4-in-1 adapter

2019-07-24 Thread Christopher M. Penalver
** Tags added: bios-outdated-1.10.1

** Description changed:

- I experienced the same issue reported in
- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1724307 on my
- Dell XPS 13 (9350) running Kubuntu 18.10 (4.18.0-25-generic) with KDE
- Plasma 5.13.5. My laptop was connected to the 2nd monitor using the VGA
- port on the Dell 4-in-1 adapter with the DisplayLink driver 5.2.14
+ When my laptop is connected to a second monitor via the VGA port on the
+ Dell 4-in-1 adapter, the mouse cursor flickers. DisplayLink driver
+ 5.2.14 is used.
  
- I followed the comment in this link
- (https://github.com/DisplayLink/evdi/issues/29#issuecomment-479529359)
- and mannually added /usr/share/X11/xorg.conf.d/21-displaylink.conf file
- with the content below:
+ WORKAROUND: As per 
https://github.com/DisplayLink/evdi/issues/29#issuecomment-479529359 add to 
file:
+ /usr/share/X11/xorg.conf.d/21-displaylink.conf
  
+ the following and reboot:
  Section "Device"
-   Identifier "DisplayLink"
-   Driver "modesetting"
-   Option "PageFlip" "false"
+   Identifier "DisplayLink"
+   Driver "modesetting"
+   Option "PageFlip" "false"
  EndSection
- 
- After rebooting, the mouse no longer flickers when connecting to the 2nd
- monitor using the DisplayLink adapater so I think it could be a solution
- for this problem.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  qkle   1758 F pulseaudio
-  /dev/snd/controlC0:  qkle   1758 F pulseaudio
-  /dev/snd/pcmC0D0c:   qkle   1758 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  qkle   1758 F pulseaudio
+  /dev/snd/controlC0:  qkle   1758 F pulseaudio
+  /dev/snd/pcmC0D0c:   qkle   1758 F...m pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jul 24 11:54:16 2019
  InstallationDate: Installed on 2018-11-22 (243 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=c68d8a53-b2fe-4f1b-8cd3-b52cc8908400 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-4.18.0-25-generic N/A
-  linux-backports-modules-4.18.0-25-generic  N/A
-  linux-firmware 1.175.6
+  linux-restricted-modules-4.18.0-25-generic N/A
+  linux-backports-modules-4.18.0-25-generic  N/A
+  linux-firmware 1.175.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2019-03-19 (126 days ago)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd08/31/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.product.sku: 0704
  dmi.sys.vendor: Dell Inc.

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

Title:
  [Dell XPS 13 9350] Mouse cursor flickers when connecting to 2nd
  monitor using Displaylink Dell 4-in-1 adapter

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When my laptop is connected to a second monitor via the VGA port on
  the Dell 4-in-1 adapter, the mouse cursor flickers. DisplayLink driver
  5.2.14 is used.

  WORKAROUND: As per 
https://github.com/DisplayLink/evdi/issues/29#issuecomment-479529359 add to 
file:
  /usr/share/X11/xorg.conf.d/21-displaylink.conf

  the following and reboot:
  Section "Device"
    Identifier "DisplayLink"
    Driver "modesetting"
    Option "PageFlip" "false"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  qkle   1758 F pulseaudio
   /dev/snd/controlC0:  qkle   1758 F pulseaudio
   /dev/snd/pcmC0D0c:   qkle   1758 F...m pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jul 24 11:54:16 2019
  InstallationDate: Installed on 2018-11-22 (243 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=c68d8a53-b2fe-4f1b-8cd3-b52cc8908400 ro quiet splash 

[Kernel-packages] [Bug 1836483] Re: ipw2100: wlp1s4: Failed to start the firmware

2019-07-14 Thread Christopher M. Penalver
axet, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your 
earliest convenience, could you please test the latest mainline kernel? Please 
keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

** Tags added: latest-bios-0207

** Description changed:

- Hello! I have connection issues with my old notebook running ubuntu
- 18.04 LTS. This is long story and I add referencies below. In short. I
- got a lot of "ipw2100: Fatal interrupt. Scheduling firmware restart"
- following by "ipw2100: wlp1s4: Failed to start the firmware" which force
- me to reboot the machine.
+ I have connection issues with my ASUS M3N Notebook ( 
https://www.asus.com/supportonly/M3N/HelpDesk_BIOS/ ) running ubuntu 18.04 LTS. 
As per dmesg:
+ ipw2100: Fatal interrupt. Scheduling firmware restart
+ 
+ following by:
+ ipw2100: wlp1s4: Failed to start the firmware
+ 
+ Reported upstream at:
+ https://bugzilla.kernel.org/show_bug.cgi?id=203915
+ 
+ WORKAROUND: Reboot the machine.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic i686
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  axet   1613 F pulseaudio
-  /dev/snd/pcmC1D0p:   axet   1613 F...m pulseaudio
-  /dev/snd/controlC1:  axet   1613 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  axet   1613 F pulseaudio
+  /dev/snd/pcmC1D0p:   axet   1613 F...m pulseaudio
+  /dev/snd/controlC1:  axet   1613 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sun Jul 14 16:46:10 2019
  HibernationDevice: RESUME=UUID=5431e7a1-fb6f-4411-ac30-21f6ecd48ac4
  InstallationDate: Installed on 2017-02-06 (888 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  MachineType: ASUSTeK Computer Inc. M3N
  PccardctlStatus:
-  Socket 0:
-5.0V
-   16-bit
-   PC Card
-Subdevice 0 (function 0) bound to driver "serial_cs"
+  Socket 0:
+    5.0V
+   16-bit
+   PC Card
+    Subdevice 0 (function 0) bound to driver "serial_cs"
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic 
root=UUID=8a9a2822-70c7-45c0-a01b-379c952d190d ro forcepae mem=2000M 
priority=low log_buf_len=1M
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-54-generic N/A
-  linux-backports-modules-4.15.0-54-generic  N/A
-  linux-firmware 1.173.8
+  linux-restricted-modules-4.15.0-54-generic N/A
+  linux-backports-modules-4.15.0-54-generic  N/A
+  linux-firmware 1.173.8
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  StagingDrivers: nsc_ircc irda
  UpgradeStatus: Upgraded to bionic on 2019-04-19 (86 days ago)
  dmi.bios.date: 03/16/2004
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0207
  

[Kernel-packages] [Bug 24776] Re: ipw2100 - "Fatal interrupt. Scheduling firmware restart."

2019-07-14 Thread Christopher M. Penalver
axet (axet-l), this report has been closed since 2017. Hence, it is not
scoped to you, or your problem.

If you would like your problem addressed, it will help immensely if you use 
Ubuntu with the computer the problem is reproducible with and file a new report 
via a terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Attachment removed: "dmesg.log"
   
https://bugs.launchpad.net/baltix/+source/linux-source-2.6.22/+bug/24776/+attachment/5271053/+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/24776

Title:
  ipw2100 - "Fatal interrupt. Scheduling firmware restart."

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.22 package in Baltix:
  Invalid

Bug description:
  / ATTENTION 
  I believe this issue is specific to the error that a chipset that is not 
802.11G capable will return when it picks up an a beacon from a router that is 
not mixed-mode, but 802.11G specific. Please verify. Remove mixed-mode from 
your G routers, and see if you can get this repeated. Then add back mix mode 
and see if it goes away and if you're connected with 802.11B.
  /

  [ Current Status ]

  The ipw2100 driver was last updated on 2007-01-31.  That tarball
  release contained an issues file that described this particular bug:

  Firmware restart is detected randomly
  --

  After running one or two days, Intel PRO/Wireless 2100 Network Connection
  driver will only occasionally restart the firmware.
  "ipw2100: Fatal interrupt. Scheduling firmware restart"

  To resolve this problem, the system must be rebooted.

  Defect #329

  [ Original Description ]
  Since I've upgrade to Breezy, ipw2100 driver no longer works and in dmesg I've
  got plenty 
  "Fatal interrupt. Scheduling firmware restart."

  I'm always able to do an iwlist :

  % sudo iwlist eth1 scanning
  eth1  Scan completed :
  ...
Cell 02 - Address: 00:07:CB:51:65:E0
  ESSID:"gaspard"
  Protocol:IEEE 802.11b
  Mode:Master
  Channel:11
  Encryption key:on
  Bit Rate:11 Mb/s
  Extra: Rates (Mb/s): 1 2 5.5 11
  Quality=92/100  Signal level=-36 dBm
  Extra: Last beacon: 31ms ago

  But the card no longer register. It stays "unassociated" whatever I've
  tried :

  % sudo iwconfig eth1 essid gaspard key open XX mode auto
  % sudo iwconfig eth1
  eth1  unassociated  ESSID:"gaspard"  Nickname:"ipw2100"
Mode:Managed  Channel=0  Access Point: 00:00:00:00:00:00
Bit Rate=0 kb/s   Tx-Power:off
Retry min limit:7   RTS thr:off   Fragment thr:off
Encryption key:4D7E-7ED3-1D   Security mode:open
Power Management:off
Link Quality:0  Signal level:0  Noise level:0
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:0   Missed beacon:0

  Sometimes, it works for a short time and after half an hour or an hour, it 
crash
  again.

  I've tried to upgrade ipw2100 and the firmware. No way.

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

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


[Kernel-packages] [Bug 1510789] Re: [HP Spectre x360 - 13-4002dx] No sound card detected

2019-07-09 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Importance: Medium => Low

** Tags removed: latest-bios-f.2c
** Tags added: bios-outdated-f.51

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

Title:
  [HP Spectre x360 - 13-4002dx] No sound card detected

Status in linux package in Ubuntu:
  Expired

Bug description:
  lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  apt-cache policy linux-image-generic
  linux-image-generic:
    Installed: 4.2.0.17.19
    Candidate: 4.2.0.17.19
    Version table:
   *** 4.2.0.17.19 0
  500 http://mirror.as43289.net/ubuntu/ wily-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.2.0.16.18 0
  500 http://mirror.as43289.net/ubuntu/ wily/main amd64 Packages

  I expect the sound card to be detected without additional modification of 
boot options.
  The sound card is not detected unless the following line in /etc/default/grub 
is adjusted to look so
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi='!Windows 2013' 
acpi_osi='!Windows 2012'"
  and the system is rebooted twice after booting to windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-17-generic 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username  2422 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct 28 07:05:49 2015
  HibernationDevice: RESUME=UUID=4b24424f-03e9-4f7f-8670-e714d50eae33
  InstallationDate: Installed on 2015-06-20 (129 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: Hewlett-Packard HP Spectre x360 Convertible 13
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic.efi.signed 
root=UUID=5e212365-e902-4afa-bf5f-b0adb8e59763 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-17-generic N/A
   linux-backports-modules-4.2.0-17-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 802D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 58.39
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.25:bd08/19/2015:svnHewlett-Packard:pnHPSpectrex360Convertible13:pvr:rvnHewlett-Packard:rn802D:rvr58.39:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Spectre x360 Convertible 13
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 336652] Re: Poor system performance under I/O load

2019-07-09 Thread Christopher M. Penalver
Last response from OR 2009. Upstream code fix 2012. -> Invalid

** No longer affects: linux (Ubuntu)

** Project changed: linux => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Remote watch: Linux Kernel Bug Tracker #12309 => None

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

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

Title:
  Poor system performance under I/O load

Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug seems to particularly affect the Dell Latitude D420, D430 and
  (from the kernel.org bug) at least the D830 laptop models; but others
  have been reported.

  Under I/O load, which need not be excessive - running usb-creator or
  even just checking one's email - the system performs remarkably
  poorly, far less than other laptop users see.  It can often take
  minutes to open a window, and sometimes the screen isn't repainted.
  Certainly most applications are "dimmed" by Compiz under I/O.

  It also appears to massively negatively affect boot performance, with
  one core spending its entire time in I/O wait - something we don't see
  elsewhere.

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

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


[Kernel-packages] [Bug 595047] Re: Frequent swapping causes system to hang

2019-07-09 Thread Christopher M. Penalver
Last response from OR 2010, upstream commit fixed since 2012. -> Invalid

** No longer affects: linux (Ubuntu)

** Project changed: linux => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Remote watch: Linux Kernel Bug Tracker #12309 => None

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

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

Title:
  Frequent swapping causes system to hang

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Periodically I notice my system slows to a near stand still, and the
  hard drive light is constantly going.  This seems to be a massive
  amount of disk i/o and it lasts for a long time (lets say 30 mins to
  put a number on it).  I installed and ran iotop (`iotop -a`) and it
  seems to point to jbd2.  From what I can see jbd2 is related to ext4
  journaling, but I cannot figure out how to kill this operation.  It
  might even be a red herring because I have also stopped the disk
  activity by kill either chromium or firefox.  I need to understand
  what else I can do to troubleshoot this.

  $ lsb_release -rd
  Description:  Ubuntu maverick (development branch)
  Release:  10.10

  Up-to-date as of 16th June 2010.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pgoodall   1372 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x5644 irq 44'
 Mixer name : 'Realtek ALC272X'
 Components : 'HDA:10ec0272,1025022c,0011'
 Controls  : 14
 Simple ctrls  : 8
  DistroRelease: Ubuntu 10.10
  Frequency: Once a day.
  HibernationDevice: RESUME=UUID=145f27a9-859a-4987-8132-ac878c832747
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
  MachineType: Acer AO531h
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic 
root=UUID=11f96f8b-5e04-4e20-a201-0fa5d0fc07fa ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
  Regression: Yes
  RelatedPackageVersions: linux-firmware 1.37
  Reproducible: No
  Tags: maverick ubuntu-une kconfig regression-potential needs-upstream-testing
  Uname: Linux 2.6.35-6-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 12/22/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3304
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3304:bd12/22/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: AO531h
  dmi.product.version: 1
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1792672] Re: Regression: acpi reports battery state incorrectly after sleep

2019-07-09 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1792672

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1523178] Re: 1217:8520 [Dell Latitude E7450] O2 Micro, SD/MMC Card Reader doesn't work

2019-07-09 Thread Christopher M. Penalver
happydemic, to advise, making comments about the Ubuntu kernel upstream
is promptly ignored. They don't use Ubuntu kernels.

Despite this, if you would like your issue addressed, it will help immensely if 
you use Ubuntu with the computer the problem is reproducible with and file a 
new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to 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/1523178

Title:
  1217:8520 [Dell Latitude E7450] O2 Micro, SD/MMC Card Reader doesn't
  work

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Under ubuntu 15.10 I can't use my Sandisk ultra 64GB microSD (with a
  SD card adapter) with the built in SD card reader. I seem to be
  getting the following errors.

  [ 1268.126602] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1268.128381] mmc0: tuning execution failed
  [ 1268.128386] mmc0: error -5 whilst initialising SD card
  [ 1268.554319] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1268.556098] mmc0: tuning execution failed
  [ 1268.556103] mmc0: error -5 whilst initialising SD card
  [ 1268.993995] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1268.995778] mmc0: tuning execution failed
  [ 1268.995786] mmc0: error -5 whilst initialising SD card
  [ 1269.453666] sdhci: Timeout waiting for Buffer Read Ready interrupt during 
tuning procedure, falling back to fixed sampling clock
  [ 1269.455449] mmc0: tuning execution failed
  [ 1269.455458] mmc0: error -5 whilst initialising SD card

  It was working fine under vivid with kernel 3.19.

  Went through all the kernels from 3.19 to 4.2
  (http://kernel.ubuntu.com/~kernel-ppa/) and found out that until
  4.1.8-040108-generic the SD card reader would play fine and only after
  I put 4.1.9 and on I started getting the errors.

  WORKAROUND: rmmod sdhci sdhci_pci sdhci_acpi
  modprobe sdhci debug_quirks2="0x1"
  modprobe sdhci_pci

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  alex   1606 F pulseaudio
   /dev/snd/controlC0:  alex   1606 F pulseaudio
   /dev/snd/controlC1:  alex   1606 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Dec  6 01:40:18 2015
  HibernationDevice: RESUME=UUID=acf75838-59f9-4461-9fe4-e9bdf33b28be
  InstallationDate: Installed on 2015-10-27 (38 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Latitude E7450
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=c654e4bc-b0e1-4a85-844f-99f068b2efff ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-11-04 (31 days ago)
  dmi.bios.date: 10/28/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0R1VJD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/28/2015:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0R1VJD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1833169] Re: intel_max_cstate is needed with baytrail to aviod hangups

2019-07-09 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1833169

Title:
  intel_max_cstate is needed with baytrail to aviod hangups

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  https://bugzilla.kernel.org/show_bug.cgi?id=109051

  fix (will be merged on 5.2 merge window, so I will need backport):
  
https://cgit.freedesktop.org/drm-intel/commit/?id=a75d035fedbdecf83f86767aa2e4d05c8c4ffd95

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic-hwe-18.04 4.18.0.21.71
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 18 08:14:08 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-meta-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jaime  1741 F pulseaudio
   /dev/snd/controlC0:  jaime  1741 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-17 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 04f2:b490 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=b12b3d55-99d9-45f0-87f5-46cedaeb5806 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-22-generic N/A
   linux-backports-modules-4.18.0-22-generic  N/A
   linux-firmware 1.173.6
  Tags:  wayland-session bionic
  Uname: Linux 4.18.0-22-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/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Kernel-packages] [Bug 1487524] Re: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range

2019-06-26 Thread Christopher M. Penalver
vasillalov, this report has been closed Fix Released since 2015:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1487524/comments/11

Hence, if you would like your problem addressed, it will help immensely if you 
use Ubuntu with the computer the problem is reproducible with and file a new 
report via a terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  14e4:43ba Broadcom BCM43602 not seeing 5Ghz range

Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  On a MacbookPro12,1 (2015 model), the wireless works with the brcmfmac
  on a wily install out of the box, but can't see any APs on the 5GHz
  range even though there are APs broadcasting on 5Ghz.

  03:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac Wireless 
LAN SoC (rev 01)
Subsystem: Apple Inc. Device 0152
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: brcmfmac

  $ sudo iwlist wlp3s0 scan|grep Freq
  Frequency:2.412 GHz (Channel 1)
  Frequency:2.422 GHz (Channel 3)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-3-generic 4.1.0-3.3 [modified: 
boot/vmlinuz-4.1.0-3-generic]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC2:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC1:  jbarnett   1545 F pulseaudio
   /dev/snd/controlC0:  jbarnett   1545 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Aug 21 08:46:15 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945
  InstallationDate: Installed on 2015-08-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.146
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1396291] Re: Maximum CPU frequency incorrect and there is no CPU scaling

2019-06-25 Thread Christopher M. Penalver
UbUK, best bet in maximizing traction with upstream is test latest
mainline kernel (now 5.2-rc6). If still reproducible with the latest
mainline kernel, advise of this on a follow up of https://marc.info/?l
=linux-pm=141741418405179=2 (TO Rafael J. Wysocki and Viresh Kumar
CC linux-pm).

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

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

Title:
  Maximum CPU frequency incorrect and there is no CPU scaling

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Acer Aspire 5720 and it is set up to dual boot Vista and
  ubuntu 14.04 LTS. From new the laptop came with an Intel T7300 2.00
  Ghz CPU and 1 GB DDR2 RAM. A few weeks ago I upgraded to 4 GB RAM,
  which works perfectly, and a few days ago I upgraded to an Intel T9300
  2.5 Ghz CPU.

  The BIOS (up to date), Vista and ubuntu all recognise the CPU
  correctly as:

  "Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50 GHz".

  Vista allows the CPU to run correctly at up to 2.5 Ghz and will step
  the CPU speed lower when not needed, depending on which power settings
  are chosen.

  The problem is that ubuntu will only allow the CPU to run at a fixed
  frequency of 2.4 Ghz, which is incorrect as it's a 2.5Ghz CPU, and
  there is no stepping to lower the CPU frequency when max frequency is
  not needed.

  "cpupower frequency-info" in a terminal returns:

  analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 2.40 GHz - 2.40 GHz
  available frequency steps: 2.40 GHz, 2.40 GHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, 
performance
  current policy: frequency should be within 2.40 GHz and 2.40 GHz.
  The governor "ondemand" may decide which speed to use
  within this range.
  current CPU frequency is 2.40 GHz.
  cpufreq stats: 2.40 GHz:10.47%, 2.40 GHz:89.53% (12799)
  boost state support:
  Supported: yes
  Active: yes 

  I have tried using ondemand, performance and powersave - nothing makes
  any difference. I have also installed CPU Frequency Scaling Indicator
  (which shows only 2.4 Ghz and 2.4 Ghz (turbo mode) as available
  frequencies) and I have also tried TLP but nothing makes any
  difference.

  According to this website:

  http://www.phoronix.com/scan.php?page=article=mobile_penryn=3

  the T9300 CPU should have the following frequency steps:

  2.50 GHz, 2.00 GHz, 1.60 GHz, 1.20 GHz and 800 MHz.

  I have spent days trawling the internet for a solution but to no avail.  
Hence filing this bug report in the hope a solution might be found.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0c4e3b98-0d40-4db3-9f4d-d1c53eb96355
  InstallationDate: Installed on 2014-04-23 (216 days ago)
  InstallationMedia: It
  MachineType: Acer Aspire 5720
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=9675b492-c55a-4c72-991b-263a27d74d5e ro quiet splash 
processor.ignore_ppc=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-40-generic N/A
   linux-backports-modules-3.13.0-40-generic  N/A
   linux-firmware 1.127.8
  Tags:  trusty
  Uname: Linux 3.13.0-40-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.45
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: eMachine
  dmi.board.vendor: Acer
  dmi.board.version: V1.45
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.45
  dmi.modalias: 
dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5720:pvrV1.45:rvnAcer:rneMachine:rvrV1.45:cvnAcer:ct1:cvrV1.45:
  dmi.product.name: Aspire 5720
  dmi.product.version: V1.45
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=0c4e3b98-0d40-4db3-9f4d-d1c53eb96355
  InstallationDate: Installed on 2014-04-23 (216 days ago)
  InstallationMedia: It
  MachineType: Acer Aspire 5720
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=9675b492-c55a-4c72-991b-263a27d74d5e ro 

[Kernel-packages] [Bug 1833169] Re: intel_max_cstate is needed with baytrail to aviod hangups

2019-06-21 Thread Christopher M. Penalver
Jaime Pérez, please answer all of the following:

1) Have you tested an upstream kernel containing the proposed commit, or tested 
the commit to confirm it resolves the issue for your hardware? If not, one may 
test the relevant usptream kernel via:
https://wiki.ubuntu.com/Kernel/MainlineBuilds

or testing only a patch via:
https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream

2) Does the following kernel parameter you are using provide a WORKAROUND for 
your hardware:
intel_idle.max_cstate=1

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

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

Title:
  intel_max_cstate is needed with baytrail to aviod hangups

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  https://bugzilla.kernel.org/show_bug.cgi?id=109051

  fix (will be merged on 5.2 merge window, so I will need backport):
  
https://cgit.freedesktop.org/drm-intel/commit/?id=a75d035fedbdecf83f86767aa2e4d05c8c4ffd95

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic-hwe-18.04 4.18.0.21.71
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 18 08:14:08 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: linux-meta-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jaime  1741 F pulseaudio
   /dev/snd/controlC0:  jaime  1741 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-17 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 04f2:b490 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=b12b3d55-99d9-45f0-87f5-46cedaeb5806 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-22-generic N/A
   linux-backports-modules-4.18.0-22-generic  N/A
   linux-firmware 1.173.6
  Tags:  wayland-session bionic
  Uname: Linux 4.18.0-22-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/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller

2019-06-11 Thread Christopher M. Penalver
Johannes, thank you for reporting this and helping make Ubuntu better.
Please answer all of the following:

1) Which firmware file did downloaded precisely? There are a lot of
2.3.X. files listed on the site.

2) When you boot into the BIOS does it state which version of the
Marvell BIOS and firmware is presently installed?

3) To confirm, does using the following kernel boot parameter provide a 
WORKAROUND:
amd_iommu=off

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

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

** Summary changed:

- failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller
+ failed command: WRITE FPDMA QUEUED on ata6 port of Marvell 88EE9230 controller

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

Title:
  failed command: WRITE FPDMA QUEUED on ata6 port of Marvell 88EE9230
  controller

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating the Marvell 88EE9230 SATA controller firmware to 2.3.xxx from:
  
https://www.station-drivers.com/index.php?option=com_remository=352=select=347=en

  approximately every 2-3 weeks the ata6 port populated with a SAMSUNG MZ7TN512 
throws errors:
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  The other ports don't throw errors.

  However, when the Marvell controller was initially using firmware 1.x.xxx, 
the siutation was even worse. Frequently, links were rested, raid corruption 
happened, and kernel panics occurred. Example from May/2018 (hostname changed, 
same machine):
  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):
  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 1 Jun 11 01:17 seq
   crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
  InstallationDate: Installed on 2018-03-29 (438 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp3s0 no wireless extensions.

   lo no 

[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller

2019-06-11 Thread Christopher M. Penalver
** Tags added: latest-bios-p1.50

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

Title:
  failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata
  controller

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating the Marvell 88EE9230 SATA controller firmware to 2.3.xxx from:
  
https://www.station-drivers.com/index.php?option=com_remository=352=select=347=en

  approximately every 2-3 weeks the ata6 port populated with a SAMSUNG MZ7TN512 
throws errors:
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out

  The other ports don't throw errors.

  However, when the Marvell controller was initially using firmware 1.x.xxx, 
the siutation was even worse. Frequently, links were rested, raid corruption 
happened, and kernel panics occurred. Example from May/2018 (hostname changed, 
same machine):
  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete

  Which also caused errors within the drives (smartctl -a /dev/sdd):
  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.

    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231

    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT

  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 1 Jun 11 01:17 seq
   crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
  InstallationDate: Installed on 2018-03-29 (438 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IwConfig:
   enp3s0 no wireless extensions.

   lo no wireless extensions.

   enp5s0 no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  PciMultimedia:

  ProcFB:
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=c77001fd-6968-4606-9baa-a60439b1e173 ro
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio 
daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-21-generic N/A
   linux-backports-modules-4.18.0-21-generic N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 

[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on port of marvell 88EE9230 sata controller

2019-06-11 Thread Christopher M. Penalver
** Description changed:

- This is connected to:
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/158
+ After updating the Marvell 88EE9230 SATA controller firmware to 2.3.xxx from:
+ 
https://www.station-drivers.com/index.php?option=com_remository=352=select=347=en
  
- CORRECTION: ata6 is populated! I made a mistake! Please see Post #14
- 
- My machines throws errors on ata6.00 like these:
- 
+ approximately every 2-3 weeks the ata6 port populated with a SAMSUNG MZ7TN512 
throws errors:
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA 
QUEUED
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
  Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd 
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
  
- ata6 is an unpopulated port of a Marvell 88EE9230 controller. The 3 populated 
ports don't trigger any failures after updating the firmware (2.3.xxx) of the 
Sata controller.
- The problem occurs every 2-3 weeks and I did not find a method to replicate 
the behaviour. Anyhow, the system is stable.
+ The other ports don't throw errors.
  
- ##
- 
- The Marvell controller itself initially was used with firmware  1.x.xxx
- which caused massive problems with all connected drives. It was common,
- that the kernel rested links, which caused raid corruption, kernel
- panics. Example from May/2018 (hostname changed, same machine)
- 
+ However, when the Marvell controller was initially using firmware 1.x.xxx, 
the siutation was even worse. Frequently, links were rested, raid corruption 
happened, and kernel panics occurred. Example from May/2018 (hostname changed, 
same machine):
  May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command: 
WRITE FPDMA QUEUED
  May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd 
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
  May 31 18:25:43 amd-server kernel: [ 3339.412748]  res 
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
  May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
  May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
  May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps 
(SStatus 133 SControl 300)
  May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for 
UDMA/133
  May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported 
invalid CHS sector 0
  May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
  
  Which also caused errors within the drives (smartctl -a /dev/sdd):
- 
  Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
    When the command that caused the error occurred, the device was active or 
idle.
  
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    -- -- -- -- -- -- --
    84 51 71 8f 66 c9 0f  Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f = 
264857231
  
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
    -- -- -- -- -- -- -- --    
    25 00 00 00 60 c9 e0 00  03:34:02.078  READ DMA EXT
    25 00 00 00 5c c9 e0 00  03:34:02.060  READ DMA EXT
    25 00 00 00 58 c9 e0 00  03:34:02.042  READ DMA EXT
    25 00 00 00 54 c9 e0 00  03:34:02.026  READ DMA EXT
    25 00 00 00 4c c9 e0 00  03:34:02.024  READ DMA EXT
+ 
+ ---
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116, 1 Jun 11 01:17 seq
+  crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 18.04
+ EcryptfsInUse: Yes
+ HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
+ InstallationDate: Installed on 2018-03-29 (438 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
+ IwConfig:
+  enp3s0 no wireless extensions.
+ 
+  lo no wireless extensions.
+ 
+  enp5s0 no wireless extensions.
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: linux (not installed)
+ PciMultimedia:
+ 
+ ProcFB:

[Kernel-packages] [Bug 1810239] Re: amd_iommu conflict with Marvell 88SE9230 SATA Controller

2019-06-09 Thread Christopher M. Penalver
Johannes (piktogrammdd+ubuntu), it will help immensely if you use Ubuntu with 
the computer the problem is reproducible with and file a new report via a 
terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Tags removed: latest-bios-f2
** Tags added: bios-outdated-f.40

** Tags added: needs-upstream-testing

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

Title:
  amd_iommu conflict with  Marvell 88SE9230 SATA Controller

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  Booting with kernel 4.18.0-13.14~18.04.1-generic shows errors:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810239/comments/153

  WORKAROUND: Use kernel boot parameter:
  amd_iommu=off

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 1170 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-07-02 (913 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.

   enp9s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-root ro verbose 
drm_kms_helper.edid_firmware=HDMI-A-3:edid/panasonic.edid
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:

  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-27 (158 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv nopasswdlogin plugdev sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

2019-05-26 Thread Christopher M. Penalver
James Ward, given this report is closed and resolved for the original
reporter, you have a different problem then what is scoped to here.

Hence, it will help immensely if you use Ubuntu with the computer the problem 
is reproducible with and file a new report via a terminal to provide necessary 
debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to 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/1694225

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The disabled touchpad of my Thinkpad T450s sometimes triggers a click
  lock when I touch it with my palm. This is typical when I'm reaching
  to click the trackpoint's (red pointing stick) left button.

  Reproduction steps:
  1. Disable the touchpad via Ubuntu's "Mouse & Touchpad" setting.

  2. Place and hold two fingers in contact with the touchpad.

  3. Click then release the trackpoint's left button once while the
  cursor is on the desktop area. Then immediately move the cursor with
  the pointing stick.

  4. If the click lock effect gets triggered, a selection would have
  been made and dragged on the desktop area. If the click lock doesn't
  happen, repeat step 3.

  The evtest log on the trackpoint:
  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  This issue doesn't happen with Windows. I can confirm it happens on
  Ubuntu v17/v16, Kubuntu, Ubuntu Mate, Xubuntu, Lubuntu, Linux Mint,
  Fedora, and Open Suse.

  Also, the issue doesn't occur on older thinkpad models which doesn't
  use the same clickpad, e.g. T430 or X230.

  WORKAROUND: Execute at a terminal:
  sudo rmmod psmouse && sudo modprobe psmouse proto=imps

  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-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/16/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET64WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX001LUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Kernel-packages] [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.

2019-05-22 Thread Christopher M. Penalver
As per upstream in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1063038/comments/27
the device is rate limited in firmware intentionally. Hence, while it is
technically possible to override this from a firmware perspective (i.e.
Acer+Broadcom would release a firmware update), from a linux project
perspective, investigating and, if viable, implementing an override of
said firmware rate limiting as it stands today would need to be done
upstream.

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

** Changed in: linux (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I've got a device with a Broadcom 57780 ethernet NIC. It uses the
  tg3.ko driver module. The problem is that this NIC cannot connect at
  gigabit (1000MBps) speed. In all cases connection works well at
  100MBps. Following are the tests I've completed:

  - Cables tested with cable tester
  - Cables tested to work at gigabit speed with Realtek and Intel gigabit NICs.
  - All unmanaged switch ports tested at ggigabit speed with other NICs.
  - Tried to connect with NetworkManager enabled and disabled.
  - Tried both dhcp and static connections.
  - Tried to renegotiate connection with `ethtool -r` both with TSO enabled and 
disabled.
  - Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic 3.6.0-999-generic 
kernels from main, xorg-edgers and mainline repos.
  - Used 'tg3_debug=1' kernel option in grub with the following output:

  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ 
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
  [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ 
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
  [5.963136] tg3.c:v3.123 (March 21, 2012)
  [5.995781] tg3 mdio bus: probed
  [6.005583] tg3 :01:00.0: >eth0: Tigon3 [partno(BCM57780) rev 
57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5
  [6.005687] tg3 :01:00.0: >eth0: attached PHY driver [Broadcom 
BCM57780] (mii_bus:phy_addr=100:01)
  [6.005790] tg3 :01:00.0: >eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] TSOcap[1]
  [6.005887] tg3 :01:00.0: >eth0: dma_rwctrl[7618] 
dma_mask[64-bit]
  [  294.987653] tg3 :01:00.0: >irq 44 for MSI/MSI-X
  [  295.893224] tg3 :01:00.0: >eth0: Link is down
  [  309.887879] tg3 :01:00.0: >eth0: Link is up at 100 Mbps, full 
duplex
  [  309.887886] tg3 :01:00.0: >eth0: Flow control is on for TX and on 
for RX

  Other distros' forums suggest loading broadcom.ko first; however, this
  module is no present.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lzane  2139 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43'
     Mixer name : 'Realtek ALC272X'
     Components : 'HDA:10ec0272,10250601,0011'
     Controls  : 22
     Simple ctrls  : 11
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=e3645816-84f7-43fe-91a8-28638a230826
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424)
  Lsusb:
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd
  MachineType: Acer Aspire 5733
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ 
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
  ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.

2019-05-22 Thread Christopher M. Penalver
** No longer affects: 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/1063038

Title:
  Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I've got a device with a Broadcom 57780 ethernet NIC. It uses the
  tg3.ko driver module. The problem is that this NIC cannot connect at
  gigabit (1000MBps) speed. In all cases connection works well at
  100MBps. Following are the tests I've completed:

  - Cables tested with cable tester
  - Cables tested to work at gigabit speed with Realtek and Intel gigabit NICs.
  - All unmanaged switch ports tested at ggigabit speed with other NICs.
  - Tried to connect with NetworkManager enabled and disabled.
  - Tried both dhcp and static connections.
  - Tried to renegotiate connection with `ethtool -r` both with TSO enabled and 
disabled.
  - Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic 3.6.0-999-generic 
kernels from main, xorg-edgers and mainline repos.
  - Used 'tg3_debug=1' kernel option in grub with the following output:

  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ 
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
  [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ 
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
  [5.963136] tg3.c:v3.123 (March 21, 2012)
  [5.995781] tg3 mdio bus: probed
  [6.005583] tg3 :01:00.0: >eth0: Tigon3 [partno(BCM57780) rev 
57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5
  [6.005687] tg3 :01:00.0: >eth0: attached PHY driver [Broadcom 
BCM57780] (mii_bus:phy_addr=100:01)
  [6.005790] tg3 :01:00.0: >eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] TSOcap[1]
  [6.005887] tg3 :01:00.0: >eth0: dma_rwctrl[7618] 
dma_mask[64-bit]
  [  294.987653] tg3 :01:00.0: >irq 44 for MSI/MSI-X
  [  295.893224] tg3 :01:00.0: >eth0: Link is down
  [  309.887879] tg3 :01:00.0: >eth0: Link is up at 100 Mbps, full 
duplex
  [  309.887886] tg3 :01:00.0: >eth0: Flow control is on for TX and on 
for RX

  Other distros' forums suggest loading broadcom.ko first; however, this
  module is no present.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lzane  2139 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43'
     Mixer name : 'Realtek ALC272X'
     Components : 'HDA:10ec0272,10250601,0011'
     Controls  : 22
     Simple ctrls  : 11
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=e3645816-84f7-43fe-91a8-28638a230826
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424)
  Lsusb:
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd
  MachineType: Acer Aspire 5733
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ 
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
  ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.94
  Tags:  precise
  Uname: Linux 3.5.0-17-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/07/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Base Board 

[Kernel-packages] [Bug 1063038] Re: Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.

2019-05-22 Thread Christopher M. Penalver
** Project changed: linux => linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Remote watch: Email to netdev@vger # => None

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

Title:
  Broadcom BCM57780 Cannot Connect at Gigabit Speed using tg3 module.

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I've got a device with a Broadcom 57780 ethernet NIC. It uses the
  tg3.ko driver module. The problem is that this NIC cannot connect at
  gigabit (1000MBps) speed. In all cases connection works well at
  100MBps. Following are the tests I've completed:

  - Cables tested with cable tester
  - Cables tested to work at gigabit speed with Realtek and Intel gigabit NICs.
  - All unmanaged switch ports tested at ggigabit speed with other NICs.
  - Tried to connect with NetworkManager enabled and disabled.
  - Tried both dhcp and static connections.
  - Tried to renegotiate connection with `ethtool -r` both with TSO enabled and 
disabled.
  - Tried 3.2.0-23-generic 3.5.0-15-generic3.5.0-17-generic 3.6.0-999-generic 
kernels from main, xorg-edgers and mainline repos.
  - Used 'tg3_debug=1' kernel option in grub with the following output:

  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ 
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
  [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ 
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
  [5.963136] tg3.c:v3.123 (March 21, 2012)
  [5.995781] tg3 mdio bus: probed
  [6.005583] tg3 :01:00.0: >eth0: Tigon3 [partno(BCM57780) rev 
57780001] (PCI Express) MAC address dc:0e:a1:ac:38:d5
  [6.005687] tg3 :01:00.0: >eth0: attached PHY driver [Broadcom 
BCM57780] (mii_bus:phy_addr=100:01)
  [6.005790] tg3 :01:00.0: >eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[0] TSOcap[1]
  [6.005887] tg3 :01:00.0: >eth0: dma_rwctrl[7618] 
dma_mask[64-bit]
  [  294.987653] tg3 :01:00.0: >irq 44 for MSI/MSI-X
  [  295.893224] tg3 :01:00.0: >eth0: Link is down
  [  309.887879] tg3 :01:00.0: >eth0: Link is up at 100 Mbps, full 
duplex
  [  309.887886] tg3 :01:00.0: >eth0: Flow control is on for TX and on 
for RX

  Other distros' forums suggest loading broadcom.ko first; however, this
  module is no present.

  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lzane  2139 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd440 irq 43'
     Mixer name : 'Realtek ALC272X'
     Components : 'HDA:10ec0272,10250601,0011'
     Controls  : 22
     Simple ctrls  : 11
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=e3645816-84f7-43fe-91a8-28638a230826
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424)
  Lsusb:
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd
  MachineType: Acer Aspire 5733
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic 
root=UUID=eccabacd-efb2-45b4-b7a6-2f530d50afd3 ro rootflags=subvol=@ 
tg3_debug=1 i915_enable_rc6=7 i915_enable_fbc=1 lvds_downclock=1
  ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.94
  Tags:  precise
  Uname: Linux 3.5.0-17-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/07/2011
  

[Kernel-packages] [Bug 1828168] Re: [Surface Pro 3] Marvell 88W8897 wifi (module mwifiex) does not work

2019-05-20 Thread Christopher M. Penalver
PaulSchulz,  the issue you are reporting is an upstream one. Could you
please report this problem following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Amitkumar Karwar, Nishant Sarmukadam, Ganapathi Bhat,  and
Xinming Hu CC linux-wireless)?

This article was written for folks who don't know anything about linux,
so it's easy to follow.

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your help.

** Tags removed: bios-outdated-38.16.85.0
** Tags added: latest-bios-3.11.2550

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

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

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

Title:
  [Surface Pro 3] Marvell 88W8897 wifi (module mwifiex) does not work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-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   2763 F pulseaudio
   /dev/snd/controlC1:  paul   2763 F pulseaudio
  Date: Wed May  8 16:35:11 2019
  InstallationDate: Installed on 2018-01-13 (480 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Microsoft Corporation Surface Pro 3
  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-5.0.0-13-generic 
root=UUID=2aaa6b5c-4cbb-4d78-92b5-b8f96f30eb4f ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-23 (14 days ago)
  dmi.bios.date: 06/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11.2550
  dmi.board.asset.tag: 0
  dmi.board.name: Surface Pro 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2550:bd06/12/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 3
  dmi.product.sku: Surface_Pro_3
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

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

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


[Kernel-packages] [Bug 1552693] Re: Radeon driver only provides 1024x768 resolution

2019-05-20 Thread Christopher M. Penalver
iceboy, to confirm this is resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

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

** Summary changed:

- Radeon driver only provides 1024x768 resolution
+ [Radeon HD 7950] Unable to set resolution higher than 1024x768

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

Title:
  [Radeon HD 7950] Unable to set resolution higher than 1024x768

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm using the latest development version of xenial. My graphics card
  is AMD HD7950 and I use an mini-DP to DP converter to connect it to an
  Acer XB240H monitor. The system works well in Windows 7.

  While using the open source radeon driver, the system was only able to
  detect resolution up to 1024x768:

  $ xrandr
  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1024x768+0+0 (normal left inverted right x 
axis y axis) 0mm x 0mm
     1024x768  60.00*
     800x600   60.3256.25
     848x480   60.00
     640x480   59.94
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  DVI-0 disconnected (normal left inverted right x axis y axis)

  $ dmesg | grep drm
  [0.615419] [drm] Initialized drm 1.1.0 20060810
  [0.630977] [drm] radeon kernel modesetting enabled.
  [0.633712] fb: switching to radeondrmfb from VESA VGA
  [0.633863] [drm] initializing kernel modesetting (TAHITI 0x1002:0x679A 
0x1682:0x3221).
  [0.633870] [drm] register mmio base: 0xF7E0
  [0.633870] [drm] register mmio size: 262144
  [0.633935] [drm] Changing default dispclk from 500Mhz to 600Mhz
  [0.633942] [drm] Detected VRAM RAM=3072M, BAR=256M
  [0.633943] [drm] RAM width 384bits DDR
  [0.633980] [drm] radeon: 3072M of VRAM memory ready
  [0.633980] [drm] radeon: 2048M of GTT memory ready.
  [0.633985] [drm] Loading tahiti Microcode
  [0.634037] [drm] Internal thermal controller with fan control
  [0.634064] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
  [0.638427] [drm] radeon: dpm initialized
  [0.639773] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
  [0.639776] [drm] GART: num cpu pages 524288, num gpu pages 524288
  [0.640486] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
  [0.640489] [drm] PCIE gen 3 link speeds already enabled
  [0.655393] [drm] PCIE GART of 2048M enabled (table at 0x002E8000).
  [0.675799] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [0.675800] [drm] Driver supports precise vblank timestamp query.
  [0.675874] [drm] radeon: irq initialized.
  [0.816685] [drm] ring test on 0 succeeded in 1 usecs
  [0.816689] [drm] ring test on 1 succeeded in 1 usecs
  [0.816692] [drm] ring test on 2 succeeded in 1 usecs
  [0.816697] [drm] ring test on 3 succeeded in 3 usecs
  [0.816701] [drm] ring test on 4 succeeded in 2 usecs
  [1.002289] [drm] ring test on 5 succeeded in 1 usecs
  [1.002294] [drm] UVD initialized successfully.
  [1.111494] [drm] ring test on 6 succeeded in 21 usecs
  [1.111505] [drm] ring test on 7 succeeded in 4 usecs
  [1.111505] [drm] VCE initialized successfully.
  [1.111627] [drm] ib test on ring 0 succeeded in 0 usecs
  [1.111648] [drm] ib test on ring 1 succeeded in 0 usecs
  [1.111673] [drm] ib test on ring 2 succeeded in 0 usecs
  [1.111688] [drm] ib test on ring 3 succeeded in 0 usecs
  [1.111702] [drm] ib test on ring 4 succeeded in 0 usecs
  [1.780603] [drm] ib test on ring 5 succeeded
  [2.280602] [drm] ib test on ring 6 succeeded
  [2.780592] [drm] ib test on ring 7 succeeded
  [2.781353] [drm] Radeon Display Connectors
  [2.781354] [drm] Connector 0:
  [2.781354] [drm]   DP-1
  [2.781355] [drm]   HPD5
  [2.781356] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 
0x653c
  [2.781357] [drm]   Encoders:
  [2.781357] [drm] DFP1: INTERNAL_UNIPHY2
  [2.781358] [drm] Connector 1:
  [2.781358] [drm]   DP-2
  [2.781359] [drm]   HPD4
  [2.781360] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 
0x654c
  [2.781360] [drm]   Encoders:
  [2.781361] [drm] DFP2: INTERNAL_UNIPHY2
  [2.781361] [drm] Connector 2:
  [2.781362] [drm]   HDMI-A-1
  [2.781362] [drm]   HPD1
  [2.781363] [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 
0x655c
  [2.781363] [drm]   Encoders:
  [2.781364] [drm] DFP3: INTERNAL_UNIPHY1
  [2.781364] [drm] Connector 3:
  [2.781365] [drm]   DVI-I-1
  [2.781365] [drm]   HPD3
  [2.781366] [drm]   DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 

[Kernel-packages] [Bug 1552693] Re: Radeon driver only provides 1024x768 resolution

2019-05-20 Thread Christopher M. Penalver
Marius Helmeseanu, it is most helpful if you use the computer the problem is 
reproducible with and file a new report with Ubuntu by first ensuring the 
package xdiagnose is installed, and click the Yes button for attaching 
additional debugging information after running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

** Tags removed: apport-collected disco

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264915/+files/AlsaInfo.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264916/+files/CRDA.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264917/+files/CurrentDmesg.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264918/+files/Lspci.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264919/+files/Lsusb.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264920/+files/ProcCpuinfo.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264921/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264922/+files/ProcEnviron.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264923/+files/ProcInterrupts.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264924/+files/ProcModules.txt

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264925/+files/PulseList.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264926/+files/UdevDb.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1552693/+attachment/5264927/+files/WifiSyslog.txt

** Tags removed: bios-outdated-3103
** Tags added: bios-outdated-3201

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

Title:
  [Radeon HD 7950] Unable to set resolution higher than 1024x768

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm using the latest development version of xenial. My graphics card
  is AMD HD7950 and I use an mini-DP to DP converter to connect it to an
  Acer XB240H monitor. The system works well in Windows 7.

  While using the open source radeon driver, the system was only able to
  detect resolution up to 1024x768:

  $ xrandr
  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1024x768+0+0 (normal left inverted right x 
axis y axis) 0mm x 0mm
     1024x768  60.00*
     800x600   60.3256.25
     848x480   60.00
     640x480   59.94
  HDMI-0 disconnected (normal left inverted right x axis y axis)
  DVI-0 disconnected (normal left inverted right x axis y axis)

  $ dmesg | grep drm
  [0.615419] [drm] Initialized drm 1.1.0 20060810
  [0.630977] [drm] radeon kernel modesetting enabled.
  [0.633712] fb: switching to radeondrmfb from VESA VGA
  [0.633863] [drm] initializing kernel modesetting (TAHITI 0x1002:0x679A 
0x1682:0x3221).
  [0.633870] [drm] register mmio base: 0xF7E0
  [0.633870] [drm] register mmio size: 262144
  [0.633935] [drm] Changing default dispclk from 500Mhz to 600Mhz
  [0.633942] [drm] Detected VRAM RAM=3072M, BAR=256M
  [0.633943] [drm] RAM width 384bits DDR
  [0.633980] [drm] radeon: 3072M of VRAM memory ready
  [0.633980] [drm] radeon: 2048M of GTT memory ready.
  [0.633985] [drm] Loading tahiti Microcode
  [0.634037] [drm] Internal thermal controller with fan control
  [0.634064] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
  [0.638427] [drm] radeon: dpm initialized
  [0.639773] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
  [0.639776] [drm] GART: num cpu pages 524288, num gpu pages 524288
  [0.640486] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
  [0.640489] [drm] PCIE gen 3 link speeds already enabled
  [0.655393] [drm] PCIE GART of 2048M enabled (table at 0x002E8000).
  [0.675799] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [0.675800] [drm] Driver supports precise vblank timestamp query.
  [0.675874] [drm] radeon: irq initialized.
  [0.816685] [drm] 

[Kernel-packages] [Bug 1829643] Re: 1 network printer + 3 configurations (copies) disappear

2019-05-19 Thread Christopher M. Penalver
FrankStefani, please note, you have filed two different reports about
the same thing (LP#1829643 and and LP#1829644), and LP#1829644 has been
marked a duplicate of this one.

Hence, all future comments, attachments, etc. should be done here on LP#1829643 
so folks don't get confused:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829643

** Tags added: latest-bios-p2.90

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

Title:
  1 network printer + 3 configurations (copies) disappear

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  ###-
  ### NOTE English is not my native language, I do my best ...
  ###-

  Distribution is Lubuntu (Ubuntu-19.04).

  ###-
  ### NOTE by request
  ###-
  # cat /proc/version_signature
  Ubuntu 5.0.0-15.16-generic 5.0.6

  # apt-cache policy cups
  cups:
Installed: 2.2.10-4ubuntu1
Candidate: 2.2.10-4ubuntu1
Version table:
   *** 2.2.10-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.2.10-4 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages

  # lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  ###-
  ### NOTE starting point
  ###-
  My printing system for the last 12-15 years based on cups had/has the 
following setup:

  * 1 network laser printer "Brother MFC 9142CDN"
  * 3 "symbolic" printers which are copies of the former, configured to set 
defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full 
color) and "labelprinter" (use of manual feed)

  The "Brother MFC 9142CDN" was instantly discovered and completely PPD
  configured and successfully tested with a fresh Lubuntu-19.04 install,
  last week.

  ###-
  ### NOTE by request: see attachment for "ubuntu-bug cups" output
  ###-

  ###-
  ### NOTE After first install and fresh configuration my printer setup looks 
as follows
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE Only the first of these (Brother_MFC_9142CDN) survives a reboot
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print

  ###-
  ### NOTE strangely, this one also disappears after some minutes
  ###-
  LANG=en lpstat -s
  no system default destination
  lpstat: No destinations added.
  lpstat: No destinations added.

  ###-
  ### NOTE printers.conf / printers.conf.O - mind the sizes
  ###
  ### printers.conf: no printer definition, just standard comment "DO NOT EDIT 
..."
  ### printers.conf.O: only the physical network printer "Brother_MFC_9142CDN" 
description
  ###   while the 3 other printers (monoprinter, colorprinter, labelprinter) 
are missing
  ###-
  # ls -l /etc/cups/printers.conf*
  -rw--- 1 root lp 111 Mai 19 08:00 printers.conf
  -rw--- 1 root lp 923 Mai 19 07:55 printers.conf.O

  ###-
  ### NOTE the PPDs are also lost at this time
  ###-
  # ls -l /etc/cups/ppd/
  total 0

  ###-
  ### NOTE after my fresh and working configuration, the PPDs looked like this
  ###
  ### Only the "Brother_MFC_9142CDN" survives a reboot though it also 
disappears later.
  ### Mind the permissions: 664 versus 640 ... don't know why
  ###-
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE
  ###
  ### Apart from the different settings in "/etc/cups/printers.conf" for my 3 
copies,
  ### the DeviceURI is the same for all four. Only the UUID differs
  ###-
  
  UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3
  DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print
  
  
  

[Kernel-packages] [Bug 1829643] Re: 1 network printer + 3 configurations (copies) disappear

2019-05-19 Thread Christopher M. Penalver
FrankStefani, could you please run an apport-collect only once more to gather 
debugging information against the package cups:
apport-collect 1829643

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

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

Title:
  1 network printer + 3 configurations (copies) disappear

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  ###-
  ### NOTE English is not my native language, I do my best ...
  ###-

  Distribution is Lubuntu (Ubuntu-19.04).

  ###-
  ### NOTE by request
  ###-
  # cat /proc/version_signature
  Ubuntu 5.0.0-15.16-generic 5.0.6

  # apt-cache policy cups
  cups:
Installed: 2.2.10-4ubuntu1
Candidate: 2.2.10-4ubuntu1
Version table:
   *** 2.2.10-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.2.10-4 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages

  # lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  ###-
  ### NOTE starting point
  ###-
  My printing system for the last 12-15 years based on cups had/has the 
following setup:

  * 1 network laser printer "Brother MFC 9142CDN"
  * 3 "symbolic" printers which are copies of the former, configured to set 
defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full 
color) and "labelprinter" (use of manual feed)

  The "Brother MFC 9142CDN" was instantly discovered and completely PPD
  configured and successfully tested with a fresh Lubuntu-19.04 install,
  last week.

  ###-
  ### NOTE by request: see attachment for "ubuntu-bug cups" output
  ###-

  ###-
  ### NOTE After first install and fresh configuration my printer setup looks 
as follows
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE Only the first of these (Brother_MFC_9142CDN) survives a reboot
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print

  ###-
  ### NOTE strangely, this one also disappears after some minutes
  ###-
  LANG=en lpstat -s
  no system default destination
  lpstat: No destinations added.
  lpstat: No destinations added.

  ###-
  ### NOTE printers.conf / printers.conf.O - mind the sizes
  ###
  ### printers.conf: no printer definition, just standard comment "DO NOT EDIT 
..."
  ### printers.conf.O: only the physical network printer "Brother_MFC_9142CDN" 
description
  ###   while the 3 other printers (monoprinter, colorprinter, labelprinter) 
are missing
  ###-
  # ls -l /etc/cups/printers.conf*
  -rw--- 1 root lp 111 Mai 19 08:00 printers.conf
  -rw--- 1 root lp 923 Mai 19 07:55 printers.conf.O

  ###-
  ### NOTE the PPDs are also lost at this time
  ###-
  # ls -l /etc/cups/ppd/
  total 0

  ###-
  ### NOTE after my fresh and working configuration, the PPDs looked like this
  ###
  ### Only the "Brother_MFC_9142CDN" survives a reboot though it also 
disappears later.
  ### Mind the permissions: 664 versus 640 ... don't know why
  ###-
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE
  ###
  ### Apart from the different settings in "/etc/cups/printers.conf" for my 3 
copies,
  ### the DeviceURI is the same for all four. Only the UUID differs
  ###-
  
  UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3
  DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print
  
  
  UUID urn:uuid:63efeecc-be6e-3065-6c0c-9a73bdd0dd62
  DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print
  
  

[Kernel-packages] [Bug 1829644] Re: 1 network printer + 3 configurations (copies) disappear

2019-05-19 Thread Christopher M. Penalver
*** This bug is a duplicate of bug 1829643 ***
https://bugs.launchpad.net/bugs/1829643

** Attachment removed: "20190519-0814-CEST-apport.cups.k1bxh64q.apport"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829644/+attachment/5264743/+files/20190519-0814-CEST-apport.cups.k1bxh64q.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/1829644

Title:
  1 network printer + 3 configurations (copies) disappear

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ###-
  ### NOTE English is not my native language, I do my best ...
  ###-

  Distribution is Lubuntu (Ubuntu-19.04).

  ###-
  ### NOTE by request
  ###-
  # cat /proc/version_signature
  Ubuntu 5.0.0-15.16-generic 5.0.6

  # apt-cache policy cups
  cups:
Installed: 2.2.10-4ubuntu1
Candidate: 2.2.10-4ubuntu1
Version table:
   *** 2.2.10-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.2.10-4 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages

  # lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  ###-
  ### NOTE starting point
  ###-
  My printing system for the last 12-15 years based on cups had/has the 
following setup:

  * 1 network laser printer "Brother MFC 9142CDN"
  * 3 "symbolic" printers which are copies of the former, configured to set 
defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full 
color) and "labelprinter" (use of manual feed)

  The "Brother MFC 9142CDN" was instantly discovered and completely PPD
  configured and successfully tested with a fresh Lubuntu-19.04 install,
  last week.

  ###-
  ### NOTE by request: see attachment for "ubuntu-bug cups" output
  ###-

  ###-
  ### NOTE After first install and fresh configuration my printer setup looks 
as follows
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE Only the first of these (Brother_MFC_9142CDN) survives a reboot
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print

  ###-
  ### NOTE strangely, this one also disappears after some minutes
  ###-
  LANG=en lpstat -s
  no system default destination
  lpstat: No destinations added.
  lpstat: No destinations added.

  ###-
  ### NOTE printers.conf / printers.conf.O - mind the sizes
  ###
  ### printers.conf: no printer definition, just standard comment "DO NOT EDIT 
..."
  ### printers.conf.O: only the physical network printer "Brother_MFC_9142CDN" 
description
  ###   while the 3 other printers (monoprinter, colorprinter, labelprinter) 
are missing
  ###-
  # ls -l /etc/cups/printers.conf*
  -rw--- 1 root lp 111 Mai 19 08:00 printers.conf
  -rw--- 1 root lp 923 Mai 19 07:55 printers.conf.O

  ###-
  ### NOTE the PPDs are also lost at this time
  ###-
  # ls -l /etc/cups/ppd/
  total 0

  ###-
  ### NOTE after my fresh and working configuration, the PPDs looked like this
  ###
  ### Only the "Brother_MFC_9142CDN" survives a reboot though it also 
disappears later.
  ### Mind the permissions: 664 versus 640 ... don't know why
  ###-
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE
  ###
  ### Apart from the different settings in "/etc/cups/printers.conf" for my 3 
copies,
  ### the DeviceURI is the same for all four. Only the UUID differs
  ###-
  
  UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3
  DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print
  
  
  UUID urn:uuid:63efeecc-be6e-3065-6c0c-9a73bdd0dd62
  DeviceURI 

[Kernel-packages] [Bug 1829643] Re: 1 network printer + 3 configurations (copies) disappear

2019-05-19 Thread Christopher M. Penalver
FrankStefani, please don't manually attach apport-collects to reports as
this cannot be processed automatically.

Instead, simply run the command noted in #2 so that debugging information may 
be obtained, processed, and reviewed:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829643/comments/2

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

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

Title:
  1 network printer + 3 configurations (copies) disappear

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ###-
  ### NOTE English is not my native language, I do my best ...
  ###-

  Distribution is Lubuntu (Ubuntu-19.04).

  ###-
  ### NOTE by request
  ###-
  # cat /proc/version_signature
  Ubuntu 5.0.0-15.16-generic 5.0.6

  # apt-cache policy cups
  cups:
Installed: 2.2.10-4ubuntu1
Candidate: 2.2.10-4ubuntu1
Version table:
   *** 2.2.10-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.2.10-4 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages

  # lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  ###-
  ### NOTE starting point
  ###-
  My printing system for the last 12-15 years based on cups had/has the 
following setup:

  * 1 network laser printer "Brother MFC 9142CDN"
  * 3 "symbolic" printers which are copies of the former, configured to set 
defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full 
color) and "labelprinter" (use of manual feed)

  The "Brother MFC 9142CDN" was instantly discovered and completely PPD
  configured and successfully tested with a fresh Lubuntu-19.04 install,
  last week.

  ###-
  ### NOTE by request: see attachment for "ubuntu-bug cups" output
  ###-

  ###-
  ### NOTE After first install and fresh configuration my printer setup looks 
as follows
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE Only the first of these (Brother_MFC_9142CDN) survives a reboot
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print

  ###-
  ### NOTE strangely, this one also disappears after some minutes
  ###-
  LANG=en lpstat -s
  no system default destination
  lpstat: No destinations added.
  lpstat: No destinations added.

  ###-
  ### NOTE printers.conf / printers.conf.O - mind the sizes
  ###
  ### printers.conf: no printer definition, just standard comment "DO NOT EDIT 
..."
  ### printers.conf.O: only the physical network printer "Brother_MFC_9142CDN" 
description
  ###   while the 3 other printers (monoprinter, colorprinter, labelprinter) 
are missing
  ###-
  # ls -l /etc/cups/printers.conf*
  -rw--- 1 root lp 111 Mai 19 08:00 printers.conf
  -rw--- 1 root lp 923 Mai 19 07:55 printers.conf.O

  ###-
  ### NOTE the PPDs are also lost at this time
  ###-
  # ls -l /etc/cups/ppd/
  total 0

  ###-
  ### NOTE after my fresh and working configuration, the PPDs looked like this
  ###
  ### Only the "Brother_MFC_9142CDN" survives a reboot though it also 
disappears later.
  ### Mind the permissions: 664 versus 640 ... don't know why
  ###-
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE
  ###
  ### Apart from the different settings in "/etc/cups/printers.conf" for my 3 
copies,
  ### the DeviceURI is the same for all four. Only the UUID differs
  ###-
  
  UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3
  

[Kernel-packages] [Bug 1829644] Re: 1 network printer + 3 configurations (copies) disappear

2019-05-19 Thread Christopher M. Penalver
*** This bug is a duplicate of bug 1829643 ***
https://bugs.launchpad.net/bugs/1829643

** This bug has been marked a duplicate of bug 1829643
   1 network printer + 3 configurations (copies) disappear

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

Title:
  1 network printer + 3 configurations (copies) disappear

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ###-
  ### NOTE English is not my native language, I do my best ...
  ###-

  Distribution is Lubuntu (Ubuntu-19.04).

  ###-
  ### NOTE by request
  ###-
  # cat /proc/version_signature
  Ubuntu 5.0.0-15.16-generic 5.0.6

  # apt-cache policy cups
  cups:
Installed: 2.2.10-4ubuntu1
Candidate: 2.2.10-4ubuntu1
Version table:
   *** 2.2.10-4ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   2.2.10-4 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages

  # lsb_release -rd
  Description:Ubuntu 19.04
  Release:19.04

  ###-
  ### NOTE starting point
  ###-
  My printing system for the last 12-15 years based on cups had/has the 
following setup:

  * 1 network laser printer "Brother MFC 9142CDN"
  * 3 "symbolic" printers which are copies of the former, configured to set 
defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full 
color) and "labelprinter" (use of manual feed)

  The "Brother MFC 9142CDN" was instantly discovered and completely PPD
  configured and successfully tested with a fresh Lubuntu-19.04 install,
  last week.

  ###-
  ### NOTE by request: see attachment for "ubuntu-bug cups" output
  ###-

  ###-
  ### NOTE After first install and fresh configuration my printer setup looks 
as follows
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE Only the first of these (Brother_MFC_9142CDN) survives a reboot
  ###-
  # lpstat -s
  device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print

  ###-
  ### NOTE strangely, this one also disappears after some minutes
  ###-
  LANG=en lpstat -s
  no system default destination
  lpstat: No destinations added.
  lpstat: No destinations added.

  ###-
  ### NOTE printers.conf / printers.conf.O - mind the sizes
  ###
  ### printers.conf: no printer definition, just standard comment "DO NOT EDIT 
..."
  ### printers.conf.O: only the physical network printer "Brother_MFC_9142CDN" 
description
  ###   while the 3 other printers (monoprinter, colorprinter, labelprinter) 
are missing
  ###-
  # ls -l /etc/cups/printers.conf*
  -rw--- 1 root lp 111 Mai 19 08:00 printers.conf
  -rw--- 1 root lp 923 Mai 19 07:55 printers.conf.O

  ###-
  ### NOTE the PPDs are also lost at this time
  ###-
  # ls -l /etc/cups/ppd/
  total 0

  ###-
  ### NOTE after my fresh and working configuration, the PPDs looked like this
  ###
  ### Only the "Brother_MFC_9142CDN" survives a reboot though it also 
disappears later.
  ### Mind the permissions: 664 versus 640 ... don't know why
  ###-
  # ls -l ppd/
  total 96
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
  -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
  -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
  -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
  -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
  -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
  -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

  ###-
  ### NOTE
  ###
  ### Apart from the different settings in "/etc/cups/printers.conf" for my 3 
copies,
  ### the DeviceURI is the same for all four. Only the UUID differs
  ###-
  
  UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3
  DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print
  
  
  UUID urn:uuid:63efeecc-be6e-3065-6c0c-9a73bdd0dd62
  DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print
  
  
  UUID urn:uuid:756313d5-4548-327f-666b-9f2edf2c8942
  

[Kernel-packages] [Bug 554172] Re: system services using "console output" not starting at boot

2019-05-18 Thread Christopher M. Penalver
FrankStefani, given the scope of this closed report was fixed in Ubuntu
10.10 (i.e. pre-dating your usage of 12.04), it had and has nothing to
do with your problem.

However, regarding the problem you are experiencing, it is most helpful if you 
use the computer the problem is reproducible with and file a new report by 
running the following from a terminal:
ubuntu-bug cups

Also, please feel free to subscribe me to 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/554172

Title:
  system services using "console output" not starting at boot

Status in linux package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Won't Fix
Status in upstart source package in Lucid:
  Fix Released
Status in linux source package in Maverick:
  Won't Fix
Status in upstart source package in Maverick:
  Fix Released

Bug description:
  Binary package hint: cups

  Cups is not loading on my machine at boot, must run sudo
  /etc/init.d/cups start to after booting to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: cups 1.4.2-10
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Apr  2 13:07:35 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  MachineType: Dell Inc. Studio XPS 1340
  Papersize: letter
  PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono 
(recommended)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0Y279R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: 1234567890
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Studio XPS 1340
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed

2019-05-09 Thread Christopher M. Penalver
** Tags added: needs-reverse-bisect

** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-5.1

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

Title:
  [MacBookPro11,5] wakes up and suspends in a loop while closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/

  The first time suspending works great but after that suspending causes
  the laptop to wake up regardless of the method used to suspend.

  Workaround: use kernel 4.19.4.

  Sidenote: thanks to penalvch for explaining how to report this!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siilwyn1852 F pulseaudio
   /dev/snd/controlC1:  siilwyn1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:40:14 2019
  InstallationDate: Installed on 2019-01-19 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B25.1706181512
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-05-09 Thread Christopher M. Penalver
** Tags added: needs-reverse-bisect

** Tags removed: kernel-bug-exists-upstream needs-bisect
** Tags added: kernel-fixed-upstream-5.1

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1579410] Re: Cannot suspend HP ProLiant SE316M1R2

2019-05-08 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Importance: Medium => Wishlist

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

Title:
  Cannot suspend HP ProLiant SE316M1R2

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  pm-suspend does not work on HP ProLiant SE316M1R2 system.

  I am not sure if hardware actually supports that though, but there is
  kernel crash (see syslog.txt attached with Call Trace) which maybe is
  the cause.

  Monitor goes off for few seconds but after that system resumes and
  works as before.

  Also, some interesting lines:

  May  7 20:58:23 tomashp-server kernel: [ 4374.025981] pci_legacy_suspend(): 
hpsa_suspend+0x0/0x10 [hpsa] returns -38
  May  7 20:58:23 tomashp-server kernel: [ 4374.025986] dpm_run_callback(): 
pci_pm_freeze+0x0/0xe0 returns -38
  May  7 20:58:23 tomashp-server kernel: [ 4374.025987] PM: Device :06:00.0 
failed to freeze async: error -38s2disks

  These lines also appears when using s2disk.

  s2ram gives:

  KMS graphics driver is in use, skipping quirks.
  s2ram_do: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.21.22
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sat May  7 20:55:52 2016
  HibernationDevice: RESUME=UUID=2f75ed7f-85b4-4d1f-abd5-04d88f7c8be3
  InstallationDate: Installed on 2015-10-12 (208 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: HP ProLiant SE316M1R2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=4d4fc552-1b5c-42b8-8829-9249646d798c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (15 days ago)
  dmi.bios.date: 07/02/2013
  dmi.bios.vendor: HP
  dmi.bios.version: R02
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1R2:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant SE316M1R2
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed

2019-05-08 Thread Christopher M. Penalver
Selwyn, to clarify, have you tested the commit noted in #31 with your
hardware and confirmed it fixes the issue?

** Tags added: 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/1812561

Title:
  [MacBookPro11,5] wakes up and suspends in a loop while closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/

  The first time suspending works great but after that suspending causes
  the laptop to wake up regardless of the method used to suspend.

  Workaround: use kernel 4.19.4.

  Sidenote: thanks to penalvch for explaining how to report this!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siilwyn1852 F pulseaudio
   /dev/snd/controlC1:  siilwyn1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:40:14 2019
  InstallationDate: Installed on 2019-01-19 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B25.1706181512
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1828168] Re: Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro

2019-05-08 Thread Christopher M. Penalver
PaulSchulz, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream mainline kernel developers to examine the 
issue, at your earliest convenience, could you please test the latest mainline 
kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

** Tags added: bios-outdated-38.16.85.0

** Summary changed:

-  Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro
+ [Surface Pro 3] Marvell 88W8897 wifi (module mwifiex) does not work

** Description changed:

- Original bug here: https://bugs.launchpad.net/bugs/1449438
- 
- This bug was created with - ubuntu-bug linux
- 
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-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   2763 F pulseaudio
-  /dev/snd/controlC1:  paul   2763 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  paul   2763 F pulseaudio
+  /dev/snd/controlC1:  paul   2763 F pulseaudio
  Date: Wed May  8 16:35:11 2019
  InstallationDate: Installed on 2018-01-13 (480 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Microsoft Corporation Surface Pro 3
  ProcEnviron:
-  LANGUAGE=en_AU:en
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_AU.UTF-8
-  SHELL=/bin/bash
+  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-5.0.0-13-generic 
root=UUID=2aaa6b5c-4cbb-4d78-92b5-b8f96f30eb4f ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.0.0-13-generic N/A
-  linux-backports-modules-5.0.0-13-generic  N/A
-  linux-firmware1.178
+  linux-restricted-modules-5.0.0-13-generic N/A
+  linux-backports-modules-5.0.0-13-generic  N/A
+  linux-firmware1.178
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-23 (14 days ago)
  dmi.bios.date: 06/12/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11.2550
  dmi.board.asset.tag: 0
  dmi.board.name: Surface Pro 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2550:bd06/12/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 3
  dmi.product.sku: Surface_Pro_3
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

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

** Changed in: linux 

[Kernel-packages] [Bug 1792672] Re: Regression: acpi reports battery state incorrectly after sleep

2019-05-08 Thread Christopher M. Penalver
Gioele Barabucci, instructions for testing the latest mainline kernel
are available via
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792672/comments/18
.

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

Title:
  Regression: acpi reports battery state incorrectly after sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Samsung Series 9 laptops the battery state and the charger status
  are incorrectly reported in kernel 4.15.

  This bug is a regression: it has been fixed in 2012 [1] it used to
  work fine until Linux 14.10 (included).

  Quoting Matthew McCallum from
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/161

  > If I disconnect power, remove the back cover, disconnect both the main 
battery and the backup battery, I am able to get power status updates (e.g. 
battery will show as charging/charged when plugged in, or just regular battery 
when not). Once I sleep, I have to repeat this process if I want the battery 
status to work again.
  >
  > `acpi -p` correctly shows the charging state, but `tlp-stat -b` does not.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/971061/comments/159
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gioele 1939 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7e63a512-9a2c-4503-9bd9-ec2f74a7f029
  InstallationDate: Installed on 2017-06-24 (447 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=696c5d50-d388-4d33-b14a-babf7a7359df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.157.20
  Tags:  xenial
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3D-A03IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP07ABK:bd04/09/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3D-A03IT:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1270676] Re: SD Card Reader broken on UX302LG

2019-05-07 Thread Christopher M. Penalver
** Tags added: cherry-pick

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

Title:
  SD Card Reader broken on UX302LG

Status in linux package in Ubuntu:
  Triaged

Bug description:
  SD card reader (controller Alcor Micro AU6601) is dysfunctional in UX302LG 
laptop. USB readers work without problem. Nothing happens when pluggin 
SD/mSD/SDHC/mSDHC cards in the reader (might as well use a piece of wood).
  Nothing is listed in lsusb -v that could be the reader.
  Nohting is listed in lspci -k -vv -nnn.
  Nothing in acpi_listen.
  Nothing in kern.log etc.

  According to (select "Windows 8" then "Card Reader") :
  
http://support.asus.com/download.aspx?SLanguage=en=3=597=UX302LG==GEZaY8oaj8oSlQ3U

  Reader vendor is :
  Alcor Multi-Card Reader Driver
  http://www.pcidatabase.com/vendor_details.php?id=1672

  There is only one device that is "Unassigned class" 1aea:6601 but
  searching this online only pops up my other bug reports (sigh) and
  vendor is unassigned on pcidatabase.com.

  But...Downloading the 14M Win driver for the reader, vendor id 1aea and 
device id 6601 is present at multiple instances :
  [DeviceList.NTamd64]
  ; For XP and later
  %AMPCIECR% = DriverInstall_6601, PCI\VEN_1aea_6601

  Also there is mention of _Gen instance in the .inf, might point to a 
"Generic" alternative ?
  [DeviceList_Gen.NTamd64]
  ; For XP and later
  %AMPCIECR_GEN% = DriverInstall_Gen, PCI\VEN_105b_0ef6

  This does point to something totally different online 105b:0ef6 points
  to some Realtek HD Audio device.

  A proposed patch was submitted upstream as per:
  http://www.spinics.net/lists/linux-mmc/msg29230.html

  ---
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=e6458b44-fdb9-4db5-8cac-40ee0bbf9cf6
  InstallationDate: Installed on 2013-12-31 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131231)
  MachineType: ASUSTeK COMPUTER INC. UX302LG
  Package: linux (not installed)
  ProcFB: 0 simple
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-4-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi= nomodeset 
plymouth:debug vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-4-generic N/A
   linux-backports-modules-3.13.0-4-generic  N/A
   linux-firmware1.121
  Tags:  trusty
  Uname: Linux 3.13.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 10/30/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX302LG.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX302LG
  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.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX302LG
  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/1270676/+subscriptions

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


[Kernel-packages] [Bug 1568211] Re: Unable to boot

2019-05-07 Thread Christopher M. Penalver
shadowvzs, it will help immensely if you use Ubuntu with the computer the 
problem is reproducible with and file a new report via a terminal to provide 
necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to 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/1568211

Title:
  Unable to boot

Status in linux package in Ubuntu:
  Expired

Bug description:
  I upgraded overnight from Wily to Xenial. The system will not boot.
  Only a blank screen after grub loads the kernel.

  The recovery kernel loads fine and I was able to find the following
  messages:

  [drm] VGACON disable radeon kernel modesetting
  [drm:radeon_init [radeon]] *ERROR* no UMS support in radeon module!

  The recovery kernel command line had a nomodeset parameter that was
  not in the main kernel command line.

  Note: For what it's worth I reported a similar issue against several
  Utopic kernels (bug #1407505). There was a back and forth with
  jsalisbury until a kernel finally worked. I have had no problems until
  today.

  WORKAROUND: Adding the nomodeset parameter the main kernel command
  line finally booted the system.

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

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


[Kernel-packages] [Bug 1812561] Re: [MacBookPro11, 5] wakes up and suspends in a loop while closed

2019-05-07 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1812561

Title:
  [MacBookPro11,5] wakes up and suspends in a loop while closed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Similar bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/

  The first time suspending works great but after that suspending causes
  the laptop to wake up regardless of the method used to suspend.

  Workaround: use kernel 4.19.4.

  Sidenote: thanks to penalvch for explaining how to report this!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-13-generic 4.18.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siilwyn1852 F pulseaudio
   /dev/snd/controlC1:  siilwyn1852 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:40:14 2019
  InstallationDate: Installed on 2019-01-19 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=57f2dc4c-30f7-40b6-a9db-9b6f93c214cb ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B25.1706181512
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 595047] Re: Frequent swapping causes system to hang

2019-05-07 Thread Christopher M. Penalver
** Tags added: latest-bios-3304

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

Title:
  Frequent swapping causes system to hang

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

Bug description:
  Periodically I notice my system slows to a near stand still, and the
  hard drive light is constantly going.  This seems to be a massive
  amount of disk i/o and it lasts for a long time (lets say 30 mins to
  put a number on it).  I installed and ran iotop (`iotop -a`) and it
  seems to point to jbd2.  From what I can see jbd2 is related to ext4
  journaling, but I cannot figure out how to kill this operation.  It
  might even be a red herring because I have also stopped the disk
  activity by kill either chromium or firefox.  I need to understand
  what else I can do to troubleshoot this.

  $ lsb_release -rd
  Description:  Ubuntu maverick (development branch)
  Release:  10.10

  Up-to-date as of 16th June 2010.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pgoodall   1372 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x5644 irq 44'
 Mixer name : 'Realtek ALC272X'
 Components : 'HDA:10ec0272,1025022c,0011'
 Controls  : 14
 Simple ctrls  : 8
  DistroRelease: Ubuntu 10.10
  Frequency: Once a day.
  HibernationDevice: RESUME=UUID=145f27a9-859a-4987-8132-ac878c832747
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
  MachineType: Acer AO531h
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-6-generic 
root=UUID=11f96f8b-5e04-4e20-a201-0fa5d0fc07fa ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
  Regression: Yes
  RelatedPackageVersions: linux-firmware 1.37
  Reproducible: No
  Tags: maverick ubuntu-une kconfig regression-potential needs-upstream-testing
  Uname: Linux 2.6.35-6-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 12/22/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3304
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3304:bd12/22/2009:svnAcer:pnAO531h:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: AO531h
  dmi.product.version: 1
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1449438] Re: Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro

2019-05-07 Thread Christopher M. Penalver
PaulSchulz, it will help immensely if you use Ubuntu with the computer the 
problem is reproducible with and file a new report via a terminal to provide 
necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to 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/1449438

Title:
  Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been running Ubuntu 14.10 on a Microsoft Surface Pro. After some
  initial problems (see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165938) (fixed
  by kernel updates I guess) the wifi was working fine. Since the
  upgrade to 15.04 the problems are back: I can connect to a wifi
  network, the connection is working for a few seconds but drops right
  after. I attached the relevant entries in dmes.log.

  I tried installing the marvell firmware from git://git.marvell.com
  /mwifiex-firmware.git, that didn't change anything. I also tried the
  mainline kernel from http://kernel.ubuntu.com/~kernel-
  ppa/mainline/v4.1-rc1-vivid/: the connection is again working for a
  few seconds but the whole system hangs afterwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wilk   1792 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 28 10:57:42 2015
  HibernationDevice: RESUME=UUID=adb12a68-9928-4181-b4e2-487010d3c501
  InstallationDate: Installed on 2014-02-19 (432 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Microsoft Corporation Surface with Windows 8 Pro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed 
root=UUID=919f00b8-5010-46e1-b2f9-c129e17d5312 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago)
  dmi.bios.date: 01/08/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.00.0250
  dmi.board.asset.tag: 0
  dmi.board.name: Surface with Windows 8 Pro
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 17
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00.0250:bd01/08/2013:svnMicrosoftCorporation:pnSurfacewithWindows8Pro:pvr1:rvnMicrosoftCorporation:rnSurfacewithWindows8Pro:rvr1:cvnMicrosoftCorporation:ct17:cvr1:
  dmi.product.name: Surface with Windows 8 Pro
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

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

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


[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2019-05-07 Thread Christopher M. Penalver
** Tags added: disco

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

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

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+subscriptions

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


[Kernel-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

2019-05-07 Thread Christopher M. Penalver
As per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694225/comments/31
.

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

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The disabled touchpad of my Thinkpad T450s sometimes triggers a click
  lock when I touch it with my palm. This is typical when I'm reaching
  to click the trackpoint's (red pointing stick) left button.

  Reproduction steps:
  1. Disable the touchpad via Ubuntu's "Mouse & Touchpad" setting.

  2. Place and hold two fingers in contact with the touchpad.

  3. Click then release the trackpoint's left button once while the
  cursor is on the desktop area. Then immediately move the cursor with
  the pointing stick.

  4. If the click lock effect gets triggered, a selection would have
  been made and dragged on the desktop area. If the click lock doesn't
  happen, repeat step 3.

  The evtest log on the trackpoint:
  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  This issue doesn't happen with Windows. I can confirm it happens on
  Ubuntu v17/v16, Kubuntu, Ubuntu Mate, Xubuntu, Lubuntu, Linux Mint,
  Fedora, and Open Suse.

  Also, the issue doesn't occur on older thinkpad models which doesn't
  use the same clickpad, e.g. T430 or X230.

  WORKAROUND: Execute at a terminal:
  sudo rmmod psmouse && sudo modprobe psmouse proto=imps

  --- 
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 3980 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3980 F pulseaudio
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20BX001LUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-16-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/16/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET64WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX001LUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET64WW(1.28):bd03/16/2017:svnLENOVO:pn20BX001LUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001LUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BX001LUS
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications 

[Kernel-packages] [Bug 1579410] Re: Cannot suspend HP ProLiant SE316M1R2

2019-05-07 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Status: Expired => 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/1579410

Title:
  Cannot suspend HP ProLiant SE316M1R2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  pm-suspend does not work on HP ProLiant SE316M1R2 system.

  I am not sure if hardware actually supports that though, but there is
  kernel crash (see syslog.txt attached with Call Trace) which maybe is
  the cause.

  Monitor goes off for few seconds but after that system resumes and
  works as before.

  Also, some interesting lines:

  May  7 20:58:23 tomashp-server kernel: [ 4374.025981] pci_legacy_suspend(): 
hpsa_suspend+0x0/0x10 [hpsa] returns -38
  May  7 20:58:23 tomashp-server kernel: [ 4374.025986] dpm_run_callback(): 
pci_pm_freeze+0x0/0xe0 returns -38
  May  7 20:58:23 tomashp-server kernel: [ 4374.025987] PM: Device :06:00.0 
failed to freeze async: error -38s2disks

  These lines also appears when using s2disk.

  s2ram gives:

  KMS graphics driver is in use, skipping quirks.
  s2ram_do: Invalid argument

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.21.22
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sat May  7 20:55:52 2016
  HibernationDevice: RESUME=UUID=2f75ed7f-85b4-4d1f-abd5-04d88f7c8be3
  InstallationDate: Installed on 2015-10-12 (208 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  MachineType: HP ProLiant SE316M1R2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=4d4fc552-1b5c-42b8-8829-9249646d798c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (15 days ago)
  dmi.bios.date: 07/02/2013
  dmi.bios.vendor: HP
  dmi.bios.version: R02
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR02:bd07/02/2013:svnHP:pnProLiantSE316M1R2:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant SE316M1R2
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

2019-04-21 Thread Christopher M. Penalver
Emrah ÖZCAN, please answer all of the following:

1) To clarify, is your computer set to suspend when you close the lid?

2) Did this issue start to happen with your Acer TravelMate 5335 after
an update? If so, which one precisely?

3) To see if this is already resolved in Ubuntu, could you please test
the latest x64 (not 32-bit) version of Ubuntu via
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Changed in: linux (Ubuntu)
   Importance: Low => Medium

** Tags added: latest-bios-1.14

** Description changed:

- ubuntu 16.04
- i386 32 bit processor
+ On ubuntu 16.04 settings "do anything when closing lid" is applied. Hard
+ reset needs.
  
- On settings "do anything when closing lid" is aplied.
- Hard reset needs .
- 
- Tried all other ways.
- --- 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0p:   neslihan   1863 F...m pulseaudio
-  /dev/snd/controlC0:  neslihan   1863 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0p:   neslihan   1863 F...m pulseaudio
+  /dev/snd/controlC0:  neslihan   1863 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8d46be5d-cb53-468c-8826-6480bbcff947
  InstallationDate: Installed on 2018-09-12 (220 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  MachineType: Acer TravelMate 5335
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=6596dc88-fde4-492e-b958-403339a8228f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-47-generic N/A
-  linux-backports-modules-4.15.0-47-generic  N/A
-  linux-firmware 1.157.21
+  linux-restricted-modules-4.15.0-47-generic N/A
+  linux-backports-modules-4.15.0-47-generic  N/A
+  linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-47-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: BA51_MV
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnAcer:bvrV1.14:bd07/26/2011:svnAcer:pnTravelMate5335:pvrV1.14:rvnAcer:rnBA51_MV:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Intel_Mobile
  dmi.product.name: TravelMate 5335
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

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

Title:
  Acer Aspire Travelmate 5335 after opening lid black screen and freeze
  occurs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On ubuntu 16.04 settings "do anything when closing lid" is applied.
  Hard reset needs.

  ---
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   neslihan   1863 F...m pulseaudio
   /dev/snd/controlC0:  neslihan   1863 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8d46be5d-cb53-468c-8826-6480bbcff947
  InstallationDate: Installed on 2018-09-12 (220 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  MachineType: Acer TravelMate 5335
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=6596dc88-fde4-492e-b958-403339a8228f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-47-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: BA51_MV
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnAcer:bvrV1.14:bd07/26/2011:svnAcer:pnTravelMate5335:pvrV1.14:rvnAcer:rnBA51_MV:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Intel_Mobile
  dmi.product.name: TravelMate 5335
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

To 

[Kernel-packages] [Bug 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

2019-04-21 Thread Christopher M. Penalver
** This bug is no longer a duplicate of bug 982299
   [Dell Inspiron 1520] Screen stays black after laptop lid is opened

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

Title:
  Acer Aspire Travelmate 5335 after opening lid black screen and freeze
  occurs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 16.04
  i386 32 bit processor

  On settings "do anything when closing lid" is aplied.
  Hard reset needs .

  Tried all other ways.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   neslihan   1863 F...m pulseaudio
   /dev/snd/controlC0:  neslihan   1863 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=8d46be5d-cb53-468c-8826-6480bbcff947
  InstallationDate: Installed on 2018-09-12 (220 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  MachineType: Acer TravelMate 5335
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=6596dc88-fde4-492e-b958-403339a8228f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-47-generic N/A
   linux-backports-modules-4.15.0-47-generic  N/A
   linux-firmware 1.157.21
  Tags:  xenial
  Uname: Linux 4.15.0-47-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: BA51_MV
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnAcer:bvrV1.14:bd07/26/2011:svnAcer:pnTravelMate5335:pvrV1.14:rvnAcer:rnBA51_MV:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Intel_Mobile
  dmi.product.name: TravelMate 5335
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1825219] Re: Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

2019-04-20 Thread Christopher M. Penalver
Emrah ÖZCAN, thank you for reporting this and helping make Ubuntu
better.

Please execute the following command only once, as it will automatically gather 
debugging information, in a terminal:
apport-collect 1825219

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)
   Importance: Undecided => Low

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

Title:
  Acer Aspire Travelmate 5335 after opening lid black screen and freeze
  occurs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 16.04
  i386 32 bit processor

  On settings "do anything when closing lid" is aplied.
  Hard reset needs .

  Tried all other ways.

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

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


[Kernel-packages] [Bug 982299] Re: [Dell Inspiron 1520] Screen stays black after laptop lid is opened

2019-04-20 Thread Christopher M. Penalver
** This bug is no longer a duplicate of bug 1825219
   Acer Aspire Travelmate 5335 after opening lid black screen and freeze occurs

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

Title:
  [Dell Inspiron 1520] Screen stays black after laptop lid is opened

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

Bug description:
  Every time I close my laptop's lid and wait for few minutes -- screen stays 
black.
  I can switch to text console (Alt-Ctrl-F1) and back to black X screen 
(Alt-Ctrl-F7). I can login in console.
  I don't see mouse cursor on X screen.
  I'm using free nouveau drivers.

  This issue appeared just after I've upgraded to 12.04 beta2.

  I'm running 'sudo restart lightdm' from console to bring X to life.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sun Apr 15 16:35:07 2012
  DistUpgraded: 2012-03-30 06:52:10,270 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/gnome/defaults.list'
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: Dell Inc. Inspiron 1520
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-22-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to precise on 2012-03-30 (16 days ago)
  dmi.bios.date: 07/11/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0UW306
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0UW306:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.4-0ubuntu3
  version.ia32-libs: ia32-libs 20090808ubuntu35
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Kernel-packages] [Bug 1168819] Re: 168c:0032 [Asus G75VX] Slow wireless with AR9485 ath9k

2019-03-19 Thread Christopher M. Penalver
** No longer affects: linux (Ubuntu)

** Project changed: linux => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Remote watch: Linux Kernel Bug Tracker #49201 => None

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

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

Title:
  168c:0032 [Asus G75VX] Slow wireless with AR9485 ath9k

Status in linux package in Ubuntu:
  Invalid

Bug description:
  With the latest raring kernel image (linux-signed-image-3.8.0-18-generic) my 
wireless connection becomes very slow after a few minutes (ping to my AP 
increases from < 1ms to ~ 900ms).
  Kernel 3.8.0.17.27 is still fine, other wireless devices continue to work 
fine if the problem occurs.
  HW is AR9485 (ath9k) 1x1 802.11n in Asus G75VX laptop, AP is Asus RT-AC66U.
  ~
  ---
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 13.04
  EcryptfsInUse: Yes
  HibernationDevice:
   #RESUME=UUID=8c98d3e1-50af-4c74-820b-e3f29cefc50c
   #RESUME=/dev/mapper/cryptswap1
  InstallationDate: Installed on 2013-03-27 (17 days ago)
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 
(20121017.2)
  MachineType: ASUSTeK COMPUTER INC. G75VX
  MarkForUpload: True
  NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic.efi.signed 
root=UUID=93525b3d-45ae-49d5-be79-e00da8ca123b ro bootchart=disable
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-17-generic N/A
   linux-backports-modules-3.8.0-17-generic  N/A
   linux-firmware1.105
  Tags:  raring
  Uname: Linux 3.8.0-17-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-04-06 (8 days ago)
  UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev sambashare scanner tape vboxusers video
  dmi.bios.date: 02/27/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G75VX.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G75VX
  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.:bvrG75VX.206:bd02/27/2013:svnASUSTeKCOMPUTERINC.:pnG75VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G75VX
  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/1168819/+subscriptions

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


[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2019-03-19 Thread Christopher M. Penalver
** Tags added: cosmic

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

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

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  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/1775717/+subscriptions

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


[Kernel-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"

2019-03-14 Thread Christopher M. Penalver
Peter Schüller, please advise to all of the following:

1) While attached logs when using an upstream kernel advised one to
contact "the Linux USB developers" (i.e. linux-usb and Maintainer Greg
Kroah-Hartman, as GKH ultimately reviews+approves/declines usb commits,
and this would give him a heads up on whats coming down the pike for
this issue), it is helpful to contact the recipients noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819362/comments/40
with help from https://wiki.ubuntu.com/Bugs/Upstream/kernel .

2) As per Kai-Heng Feng in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819362/comments/41
there might be a WORKAROUND available while waiting for a fix. Does this
allow the opportunity to use your device for 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/1819362

Title:
  HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux
  USB developers"

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have a HUAWEI E3531 HSPA+ USB Stick

  When I plug it in, journalctl shows me

  Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 
12d1:14dc on 1/9
  Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI   TF CARD 
Storage  2.31 PQ: 0 ANSI: 2
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
  Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind 
list file: No such file or directory
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 
12d1:14dc to driver option
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Mär 10 19:21:22 pshp ModemManager[860]:   Couldn't check support for 
device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any 
plugin

  And the modem does not work (no ttyUSBX appears)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 10 19:17:23 2019
  EcryptfsInUse: Yes
  SourcePackage: linux-signed-hwe
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P78 Ver. 01.08
  dmi.board.name: 8292
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 45.3C
  dmi.chassis.asset.tag: 5CG7453N9P
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 820 G4
  dmi.product.sku: X3T22AV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64

[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-13 Thread Christopher M. Penalver
elhoir:

>"i contacted with a guy with an AMD RX 470 GPU and he says irs working
fine on his system"

Besides mundane root causes (card hardware jacked and needs RMA), there
are other reason why your results differ from others (not all RX 470
cards are equivalent in every way due to OEM implementation differences,
firmware on the card itself differing, the root cause is due to both the
card and the hardware its plugged into, different operating system
environments, etc.).

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"

2019-03-13 Thread Christopher M. Penalver
Peter Schüller, if this is confirmed with the latest mainline kernel
(now 5.0.2), then the issue you are reporting is an upstream one. Could
you please report this problem following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO linux-usb CC Greg Kroah-Hartman)?

This article was written for folks who don't know anything about linux,
so it's easy to follow.

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your help.

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

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

Title:
  HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux
  USB developers"

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have a HUAWEI E3531 HSPA+ USB Stick

  When I plug it in, journalctl shows me

  Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 
12d1:14dc on 1/9
  Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI   TF CARD 
Storage  2.31 PQ: 0 ANSI: 2
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
  Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind 
list file: No such file or directory
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 
12d1:14dc to driver option
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Mär 10 19:21:22 pshp ModemManager[860]:   Couldn't check support for 
device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any 
plugin

  And the modem does not work (no ttyUSBX appears)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 10 19:17:23 2019
  EcryptfsInUse: Yes
  SourcePackage: linux-signed-hwe
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P78 Ver. 01.08
  dmi.board.name: 8292
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 45.3C
  dmi.chassis.asset.tag: 5CG7453N9P
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 820 G4
  dmi.product.sku: X3T22AV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner 

[Kernel-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"

2019-03-10 Thread Christopher M. Penalver
Peter Schüller, in order to allow additional upstream mainline kernel 
developers to examine the issue, at your earliest convenience, could you please 
test the latest mainline kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

** Tags added: bios-outdated-1.25

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

Title:
  HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux
  USB developers"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a HUAWEI E3531 HSPA+ USB Stick

  When I plug it in, journalctl shows me

  Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 
12d1:14dc on 1/9
  Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI   TF CARD 
Storage  2.31 PQ: 0 ANSI: 2
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
  Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind 
list file: No such file or directory
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 
12d1:14dc to driver option
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Mär 10 19:21:22 pshp ModemManager[860]:   Couldn't check support for 
device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any 
plugin

  And the modem does not work (no ttyUSBX appears)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 10 19:17:23 2019
  EcryptfsInUse: Yes
  SourcePackage: linux-signed-hwe
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ps 1825 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93
  MachineType: HP HP EliteBook 820 G4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic wayland-session
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)
  UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: 

[Kernel-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"

2019-03-10 Thread Christopher M. Penalver
Peter Schüller, thank you for reporting this and helping make Ubuntu better. 
Could you please execute the following command only once, as it will 
automatically gather debugging information, in a terminal: 
apport-collect 1819362

** Changed in: linux-signed-hwe (Ubuntu)
   Importance: Undecided => Low

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

** Package changed: linux-signed-hwe (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/1819362

Title:
  HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux
  USB developers"

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a HUAWEI E3531 HSPA+ USB Stick

  When I plug it in, journalctl shows me

  Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 
12d1:14dc on 1/9
  Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI   TF CARD 
Storage  2.31 PQ: 0 ANSI: 2
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0
  Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk
  Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind 
list file: No such file or directory
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 
12d1:14dc to driver option
  Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Mär 10 19:21:22 pshp ModemManager[860]:   Couldn't check support for 
device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any 
plugin

  And the modem does not work (no ttyUSBX appears)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 10 19:17:23 2019
  EcryptfsInUse: Yes
  SourcePackage: linux-signed-hwe
  UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago)

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

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-09 Thread Christopher M. Penalver
elhoir, if its actually true you personally were able to boot using the
RX470 without WORKAROUNDs, its possible that either when you are
installing older kernels you aren't installing the correct packages, or
you were mistaken and it only booted either with a WORKAROUND or when a
different graphics card was installed.

Unless the above may be confirmed, one is at the mercy of whomever has
your hardware to confirm a regression.

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

** Tags removed: regression-update
** Tags added: regression-potential

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-09 Thread Christopher M. Penalver
elhoir:

1)
>"but i cannot find a working scenario to start with"

To clarify, you stepped through all the Ubuntu kernel versions from
4.19.0-7.8 to 5.0.0-7.8 and the problem is still reproducible?

If so, stepping through versions older than 4.19.0-7.8 until a working
state is found would be next.

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1819242] Re: The touchpad doesn't work unless I move the mouse slowly.. Also I am unable to click and drag.

2019-03-09 Thread Christopher M. Penalver
yoshiki2:

In order to allow additional upstream mainline kernel developers to examine the 
issue, at your earliest convenience, could you please test the latest mainline 
kernel? Please keep in mind the following:
1) The one to test is in a folder at the very top of the page (not the daily 
folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the Bug 
Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

In addition, to keep this issue relevant to upstream, please continue to
test the latest mainline kernel as it becomes available.

Lastly, it is most helpful that after testing of the latest mainline
kernel is complete, you mark this report Status Confirmed.

Thank you for your help.

** Tags added: latest-bios-a08

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

Title:
  The touchpad doesn't work unless I move the mouse slowly..  Also I am
  unable to click and drag.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am unable to use the touchpad properly. I am also unable to click and drag. 
This worked alright on previous versions of ubuntu.. (16.04)
  I am using ubuntu 18.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-16-generic 4.18.0-16.17~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 20:44:08 2019
  InstallationDate: Installed on 2019-03-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alfredo1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=55101717-1323-4f12-8339-2784d2f33f81 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0Y4RM9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd01/22/2013:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn0Y4RM9:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  

[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-09 Thread Christopher M. Penalver
elhoir, while you are welcome to wait for whenever a maintainer may
respond, given this issue has been reported a regression, it is known
that it helps developers expedite a fix if the offending commit(s) are
identified via bisect.

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1819242] Re: The touchpad doesn't work unless I move the mouse slowly.. Also I am unable to click and drag.

2019-03-09 Thread Christopher M. Penalver
yoshiki2, thank you for reporting this and helping make Ubuntu better.

 Please execute the following command only once, as it will automatically 
gather debugging information, in a terminal:
apport-collect 1819242

** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu)

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

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

** Tags added: regression-release

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

Title:
  The touchpad doesn't work unless I move the mouse slowly..  Also I am
  unable to click and drag.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am unable to use the touchpad properly. I am also unable to click and drag. 
This worked alright on previous versions of ubuntu.. (16.04)
  I am using ubuntu 18.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-16-generic 4.18.0-16.17~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 20:44:08 2019
  InstallationDate: Installed on 2019-03-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1048258] Re: Cypress trackpad gets psmouse lost sync / driver resynced warnings

2019-03-07 Thread Christopher M. Penalver
yoshiki2, it will help immensely if you use Ubuntu with the computer the 
problem is reproducible with and file a new report via a terminal to provide 
necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to 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/1048258

Title:
  Cypress trackpad gets psmouse lost sync / driver resynced warnings

Status in Dell Sputnik:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Quantal:
  Fix Released

Bug description:
  I installed Kubuntu 12.04 with ppa suggested on this forum but I still
  have intermittent problem with touchpad.I also install kde-config-
  touchpad and have full control on touchpad(ex.: disable when mouse
  plugged).

  It work like I want but after come back from sleep mode, I got error message 
about synaptics and the syslog look like this:
  Sep  9 10:28:34 XPS-L321X kernel: [ 6839.441575] psmouse serio1: Trackpad at 
isa0060/serio1/input0 lost sync at byte 1
  Sep  9 10:28:34 XPS-L321X kernel: [ 6839.442852] psmouse serio1: Trackpad at 
isa0060/serio1/input0 - driver resynced.

  These lines are repeated in infinite loop.

  I tried these command:
  sudo modprobe -r psmouse
  sudo modprobe psmouse

  It reassign input:
  input: CyPS/2 Cypress as /devices/platform/i8042/serio1/input/input17
  It stop the loop for 2 minutes and start again

  Only way to fix is restart x session

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1048258/+subscriptions

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


[Kernel-packages] [Bug 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade

2019-03-07 Thread Christopher M. Penalver
yoshiki2, it will help immensely if you use Ubuntu with the computer the 
problem is reproducible with and file a new report via a terminal to provide 
necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to 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/1816947

Title:
  [Dell XPS L321X] Touchpad not working after last apt-get upgrade

Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touchpad doesn't work unless the cursor is moved slowly.

  WORKAROUND: Execute at a terminal:
  sudo modprobe -r psmouse
  sudo modprobe psmouse proto=imps

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.402
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 02:56:45 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  MachineType: Dell Inc. Dell System XPS L321X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.394
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:052e]
  LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: libinput (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Tags:  bionic ubuntu
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L321X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 

[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread Christopher M. Penalver
elhoir:

1)
Please ensure you are not using non-default kernel parameters. As per most 
recent dmesg remove:
acpi_osi=Linux modprobe.blacklist=amdgpu crashkernel=384M-:128M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M crashkernel=512M-:192M 
crashkernel=512M-:192M

2)
Keep testing successively newer kernels, until you either find one that does 
boot, or reach Ubuntu kernel 5.0.0-7.8.

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread Christopher M. Penalver
elhoir, the next step is to fully commit bisect from Ubuntu kernel
4.19.0-7.8 to Ubuntu kernel 5.0.0-7.8. This will allow for a direct
review of the offending commit(s) for either reverting, or further
improvements. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was
written for folks who don't know anything about linux, so it's easy to
follow.

Please note, finding adjacent kernel versions, or providing a commit
without testing it and reverting it is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the bad commit (not kernel version) has
been confirmed via testing, you then mark this report Status Confirmed.

Thank you for your help.

** Attachment removed: "amdgpu-at-dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+attachment/5244194/+files/amdgpu-at-dmesg

** Description changed:

  I cannot boot PC normally, i must use recovery mode.
+ 
+ Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
+ 
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt
  
  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:
  
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Tags removed: regression-potential
** Tags added: needs-bisect regression-update

** Tags removed: needs-debug-logs

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 

[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-06 Thread Christopher M. Penalver
elhoir:

1)
>"yes, its a copy paste of crash part of dmesg, not entire output."

Then attach a full dmesg as previously advised.

2)
>"GPU (RX 470) is quite new. I tested Ubuntu Cosmic and Ubuntu Dingo."

To confirm, using only the RX470, it worked fine in Cosmic and Dingo.
However, while using Dingo after a kernel update, Dingo stopped booting
without a WORKAROUND? If so, which kernel update specifically?

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-06 Thread Christopher M. Penalver
elhoir:

1)
Regarding the dmesg posted in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/20 did 
you cut/snip it? Please ensure all logs are attached in their entirety (no 
cuts, snips, etc.).

2)
To confirm a regression, regarding only the current AMD graphics card 
installed, what prior Ubuntu releases and prior kernel versions have you tested 
specifically, and did they require any WORKAROUNDs?

** Tags removed: regression
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-5.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/1818580

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-06 Thread Christopher M. Penalver
elhoir:

Without evidence (screenshots, recording, logs, etc.) developers cannot
root cause, and fix your issue. Hence, when will you be posting the
video you said will be captured as per your comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/13
?

** Tags added: needs-debug-logs regression-potential

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-05 Thread Christopher M. Penalver
elhoir:

1)
Regarding your comment 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/9 :
>" No, never, but i never used amdgpu driver before"

I'm afraid this didn't answer my question. Which release precisely did
you have to start using nomodeset to boot?

2)
Regarding your comment 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/9 :
>"...only radeonsi or nouveau."

To advise, nouveau is used for nvidia cards. Did you swap out/in a
nvidia card at some point?

3)
Regarding your comment 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/11 :
>"Boot gets frozen..."

To clarify, you followed verbatim
https://wiki.ubuntu.com/DebuggingKernelBoot#Capture_information_from_a_bad_boot_and_post_to_your_bug_report
and while recording video with a cell phone or video recorder there is
nothing on the screen from startup all the way to boot is frozen?

4)
Regarding your comment 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/11 :
>"...so i cant mount it to get logs from /var/log"

You may want to try using a live environment via
http://cdimage.ubuntu.com/daily-live/current/ as this will provide a
fresh boot versus one that may have upgrade cruft left over, and help
rule some things out.

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/1818580/+subscriptions

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


[Kernel-packages] [Bug 1818580] Re: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-05 Thread Christopher M. Penalver
elhoir:

1) It looks like you installed Ubuntu originally with 11.10, and then
upgraded all the way to 19.04. To clarify, have you always had to use
the kernel parameter nomodeset to boot since 11.10?

2) With all of the following kernel parameters removed (and any
WORKAROUND or other non-default also removed), could you please provide
the missing logs from a bad boot following
https://wiki.ubuntu.com/DebuggingKernelBoot ?

quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel
=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1

** Description changed:

- i cannot boot PC normally, i must use recovery mode.
+ I cannot boot PC normally, i must use recovery mode.
+ 
+ WORKAROUND: Use kernel parameter:
+ nomodeset
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:
-  
+ 
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
-Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
+  Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
+    Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

** Tags added: latest-bios-1.0f

** Summary changed:

- [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
+ [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu 
kernel modesetting.

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 

  1   2   3   4   5   6   7   8   9   10   >