[Kernel-packages] [Bug 2042851] Re: kernel crash after suspend: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

Thanks for the reply. I was not sure how to update to that specific
version, so I updated to the latest available (6.2.0-36). I will provide
an update in a week time.

Linux ASUS 6.2.0-36-generic #37~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon
Oct  9 15:34:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 2043125] [NEW] Updating to Linux 5.15.0-90-generic breaks r8152 ethernet on thunderbolt

[Pablo Oliveira]

Public bug reported:

Updating from Linux 5.15.0-88-generic to 5.15.0-90-generic breaks
ethernet support.

In my setup, the ethernet port is inside a Thunderbolt Dell WD19TB
docking station.

On 5.15.0-88 the ethernet device works and is shown with ip and on dmesg
logs :

$ sudo dmesg
...
 27 [2.260869] r8152 4-1.4:1.0 eth0: v1.12.13
 28 [2.268290] r8152 4-1.4:1.0 enxcc483ac3b5f5: renamed from eth0
 29 [2.268290] r8152 4-1.4:1.0 enxcc483ac3b5f5: renamed from eth0
 30 [7.308677] r8152 4-1.4:1.0 enxcc483ac3b5f5: carrier on
 31 [7.523473] IPv6: ADDRCONF(NETDEV_CHANGE): enxcc483ac3b5f5: link becomes 
ready
...

$ ip a
[...]
2: enxcc483ac3b5f5:  mtu 1500 qdisc fq_codel 
state UP group default qlen 1000
link/ether cc:48:3a:c3:b5:f5 brd ff:ff:ff:ff:ff:ff
inet 192.168.133.178/24 brd 192.168.133.255 scope global dynamic 
noprefixroute enxcc483ac3b5f5
   valid_lft 1760sec preferred_lft 1760sec
inet6 fe80::887f:293c:8126:cb43/64 scope link noprefixroute
   valid_lft forever preferred_lft forever

On 5.15.0-90 the device cannot be found.

Thanks for looking into this regression.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-90-generic 5.15.0-90.100
ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131
Uname: Linux 5.15.0-90-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  poliveira   1905 F pulseaudio
 /dev/snd/controlC0:  poliveira   1905 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 16:58:05 2023
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X79
InstallationDate: Installed on 2020-10-29 (1106 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
IwConfig:
 lono wireless extensions.
 
 wlp59s0   no wireless extensions.
MachineType: Dell Inc. Precision 5540
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic 
root=UUID=52eafe9e-33dc-415d-9dec-5c74761fa536 ro nvidia-drm.modeset=1 
mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-90-generic N/A
 linux-backports-modules-5.15.0-90-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.22
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/18/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 03G9D9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd07/18/2023:br1.23:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn03G9D9:rvrA00:cvnDellInc.:ct10:cvr:sku0906:
dmi.product.family: Precision
dmi.product.name: Precision 5540
dmi.product.sku: 0906
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug jammy package-from-proposed

** Summary changed:

- Updating to Dell WD19TB breaks r8152 ethernet on thunderbolt
+ Updating to Linux 5.15.0-90-generic breaks r8152 ethernet on thunderbolt

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

Title:
  Updating to Linux 5.15.0-90-generic breaks r8152 ethernet on
  thunderbolt

Status in linux package in Ubuntu:
  New

Bug description:
  Updating from Linux 5.15.0-88-generic to 5.15.0-90-generic breaks
  ethernet support.

  In my setup, the ethernet port is inside a Thunderbolt Dell WD19TB
  docking station.

  On 5.15.0-88 the ethernet device works and is shown with ip and on
  dmesg logs :

  $ sudo dmesg
  ...
   27 [2.260869] r8152 4-1.4:1.0 eth0: v1.12.13
   28 [2.268290] r8152 4-1.4:1.0 enxcc483ac3b5f5: renamed from eth0
   29 [2.268290] r8152 4-1.4:1.0 enxcc483ac3b5f5: renamed from eth0
   30 [7.308677] r8152 4-1.4:1.0 enxcc483ac3b5f5: carrier on
   31 [7.523473] IPv6: ADDRCONF(NETDEV_CHANGE): enxcc483ac3b5f5: link 
becomes ready
  ...

  $ ip a
  [...]
  2: enxcc483ac3b5f5:  mtu 1500 qdisc fq_codel 
state UP group default qlen 1000
  link/ether cc:48:3a:c3:b5:f5 brd ff:ff:ff:ff:ff:ff
  inet 192.168.133.178/24 brd 192.168.133.255 scope global dynamic 
noprefixroute enxcc483ac3b5f5
 valid_lft 1760sec preferred_lft 1760sec
  inet6 fe80::887f:293c:8126:cb43/64 scope link noprefixroute
 valid_lft forever preferred_lft forever

  On 5.15.0-90 the device cannot be found.

  Thanks for looking into this regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: 

[Kernel-packages] [Bug 2042851] Re: kernel crash after wakeup: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

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

** Summary changed:

- kernel crash after wakeup: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
+ kernel crash after suspend: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 2042851] Re: kernel crash after wakeup: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042851/+attachment/5716488/+files/lspci-vnvn.log

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 2042851] [NEW] kernel crash after suspend: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

Public bug reported:

Laptop may or may not wake up after resume. 2 out of 10 times it will
display an error message and become unresponsive:

nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

Attaching dmesg log file for analysis.


===

At a minimum every hibernate/resume report should contain responses to
each item in this section before being considered Triaged.

1. Is this really a failure?
Yes, as machine hangs and becomes unresponsive.

2. Is it reproducible? If not, how often would it be reproducible?
I'd say it happens 20% of the time.

3. Did it work before on a prior kernel in the same release, or prior release?
Not really sure. I started using the suspend functionality quite recently.

4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
It is the same symptoms each time.

5. Do you end up with a flashing Caps Lock light?
No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

6. Please advise on how the computer hibernated, and resumed specifically.
I suspended it by clicking on the word 'Suspend' in the Gui and then closed the 
lid.
When I opened the lid the computer showed the error.

 
7. Did the machine break while going into hibernation or waking up?
According to the log it broke when suspending.

8. Did you see any error messages leading up to the failure?
Nope.

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

** Attachment added: "output of `sudo journalctl  -k -b -1  --no-tail`"
   https://bugs.launchpad.net/bugs/2042851/+attachment/5716485/+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/2042851

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 2042851] Re: kernel crash after wakeup: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

** Attachment added: "cmdline"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042851/+attachment/5716487/+files/cmdline

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 2042851] Re: kernel crash after wakeup: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

[Pablo Rubinstein]

** Attachment added: "resume"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042851/+attachment/5716486/+files/resume

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

Title:
  kernel crash after suspend: UBSAN: invalid-load in
  /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46

Status in linux package in Ubuntu:
  New

Bug description:
  Laptop may or may not wake up after resume. 2 out of 10 times it will
  display an error message and become unresponsive:

  nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in 
/build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46
  nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type 
'_Bool

  Attaching dmesg log file for analysis.

  
  ===

  At a minimum every hibernate/resume report should contain responses to
  each item in this section before being considered Triaged.

  1. Is this really a failure?
  Yes, as machine hangs and becomes unresponsive.

  2. Is it reproducible? If not, how often would it be reproducible?
  I'd say it happens 20% of the time.

  3. Did it work before on a prior kernel in the same release, or prior release?
  Not really sure. I started using the suspend functionality quite recently.

  4. Do the symptoms vary at all between hibernation attempts? For example, one 
time WiFi didn't work, but another a kernel error shows on the screen.
  It is the same symptoms each time.

  5. Do you end up with a flashing Caps Lock light?
  No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn 
light on. Only solution is to press power off key.

  6. Please advise on how the computer hibernated, and resumed specifically.
  I suspended it by clicking on the word 'Suspend' in the Gui and then closed 
the lid.
  When I opened the lid the computer showed the error.

   
  7. Did the machine break while going into hibernation or waking up?
  According to the log it broke when suspending.

  8. Did you see any error messages leading up to the failure?
  Nope.

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


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

[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system

[Pablo]

I am facing this issue. Is there a workaround to avoid it. I have 4
computers crashing every day.

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

Title:
  amdgpu no-retry page fault resulting in black screen and unresponsive
  system

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.19 package in Ubuntu:
  Triaged
Status in linux-oem-6.1 package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Triaged

Bug description:
  When using Skype in snap, amdgpu crashed, resulting in black screen
  and unresponsive system.

  Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu 
firmware.
  Affected laptop is T14 with Ryzen 5850U.

  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142c000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00540051
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x5
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x1
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry 
page fault (src_id:0 ring:40 vmid:5 pasid:0, for process  pid 0 thread  pid 0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:   in page 
starting at address 0x80010142d000 from IH client 0x12 (VMC)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  Faulty UTCL2 
client ID: MP1 (0x0)
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 
0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
WALKER_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
PERMISSION_FAULTS: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  
MAPPING_ERROR: 0x0
  Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu:  RW: 0x0

  
  This happens in a loop and eventually leads to GPU reset, which fails.

  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
ring sdma0 timeout, signaled seq=211509, emitted seq=211512
  Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 
154558
  Nov 03 16:35:55 laptop kernel: amdgpu 

[Kernel-packages] [Bug 1970957] Re: suspend problem

[Pablo Angulo]

I also had the problem occasionally, I tried kernel 5.15.0-40 but the
problem still appeared from time to time. Disabling screen lock solved
the problem, but this is functionality I miss :-(

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970957] Re: suspend problem

[Pablo Nussembaum]

I switched back XOrg by disabling Wayland in file /etc/gdm3/custom.conf and 
using the standard kernel.
this is the section of the conf file to disable wayland:

[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970957] Re: suspend problem

[Pablo Nussembaum]

after upgrading to Linux 5.18 it seems that nvidia proprietary driver doesn't 
work
thread from archLinux: 
https://github.com/NVIDIA/open-gpu-kernel-modules/issues/256


** Bug watch added: github.com/NVIDIA/open-gpu-kernel-modules/issues #256
   https://github.com/NVIDIA/open-gpu-kernel-modules/issues/256

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970957] Re: suspend problem

[Pablo Nussembaum]

This is to confirm Linux 5.18.0-051800-generic x86_64 fixed my Lenovo Y50-70 
Touch. Thanks mo!
Will this be backported to Linux 5.15 kernel?

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

Title:
  suspend problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok
  intermittently. Some times it works fine, other times the computer
  does not enter the suspend mode (the screen gets blank, but the
  machine is still running and the ThinPad led is on, and there is no
  way out... no response from keyboard or mouse... the only solution is
  to switch off manually hitting and holding the power button), other
  times the machine does not wakes up from suspension mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 29 10:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leoca  1913 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-24 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 20KQ000EBR
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-27-generic N/A
   linux-backports-modules-5.15.0-27-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/14/2018
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0PET42W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KQ000EBR
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480:
  dmi.product.family: ThinkPad E480
  dmi.product.name: 20KQ000EBR
  dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480
  dmi.product.version: ThinkPad E480
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1970197] [NEW] package linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 failed to install/upgrade: installed linux-image-5.13.0-40-generic package post-installation script sub

[Pablo Matorras]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Apr 25 08:15:43 2022
DuplicateSignature:
 package:linux-image-5.13.0-40-generic:5.13.0-40.45~20.04.1
 Setting up linux-image-5.13.0-40-generic (5.13.0-40.45~20.04.1) ...
 Segmentation fault (core dumped)
 dpkg: error processing package linux-image-5.13.0-40-generic (--configure):
  installed linux-image-5.13.0-40-generic package post-installation script 
subprocess returned error exit status 139
ErrorMessage: installed linux-image-5.13.0-40-generic package post-installation 
script subprocess returned error exit status 139
InstallationDate: Installed on 2020-10-30 (542 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: linux-signed-hwe-5.13
Title: package linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 failed to 
install/upgrade: installed linux-image-5.13.0-40-generic package 
post-installation script subprocess returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 failed to
  install/upgrade: installed linux-image-5.13.0-40-generic package post-
  installation script subprocess returned error exit status 139

Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 25 08:15:43 2022
  DuplicateSignature:
   package:linux-image-5.13.0-40-generic:5.13.0-40.45~20.04.1
   Setting up linux-image-5.13.0-40-generic (5.13.0-40.45~20.04.1) ...
   Segmentation fault (core dumped)
   dpkg: error processing package linux-image-5.13.0-40-generic (--configure):
installed linux-image-5.13.0-40-generic package post-installation script 
subprocess returned error exit status 139
  ErrorMessage: installed linux-image-5.13.0-40-generic package 
post-installation script subprocess returned error exit status 139
  InstallationDate: Installed on 2020-10-30 (542 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: linux-signed-hwe-5.13
  Title: package linux-image-5.13.0-40-generic 5.13.0-40.45~20.04.1 failed to 
install/upgrade: installed linux-image-5.13.0-40-generic package 
post-installation script subprocess returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1970197/+subscriptions


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Pablo]

I confirm having the issue

Ubuntu 20.04
External soundcard Behringer UM2

Workaround fixed the issue with most app BUT Ardour (going through
ALSA).

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
  next packet size") landed in 5.13.0-35 introduced regression to USB
  audio device.

  It's because this patch introduced the available frame size check, but
  the conversion forgot to initialize the temporary variable properly.

  A workaround is to modify /etc/pulse/daemon.conf, set the
  default-sample-rate to 48000, uncomment it by removing the semicolon
  at the beginning of the line. And restart pulseaudio with: 
systemctl --user restart pulseaudio.service

  [Fix]
  * 23939115 ALSA: usb-audio: Fix packet size calculation regression
  This patch can be cherry-picked into Impish kernel, and it's already in
  the master-next branch of Jammy tree.

  [Test]
  Test kernels built with 5.13.0-37 + this patch, can be found in:
  * Focal-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
  * Impish-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/

  Both kernels were tested by affected users and they're working as
  expected.

  [Where problems could occur]
  If this patch is incorrect, it might affect USB audio devices.

  
  [Original Bug Report]
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1943539] [NEW] NVIDIA 470 kernel warning

[Pablo Catalina]

Public bug reported:

I got the following error several times each day:


81424.410080] [ cut here ]
[81424.410081] WARNING: CPU: 11 PID: 352896 at 
/var/lib/dkms/nvidia/470.63.01/build/nvidia-drm/nvidia-drm-drv.c:574 
nv_drm_master_set+0x27/0x30 [nvidia_drm]
[81424.410084] Modules linked in: snd_usb_audio snd_usbmidi_lib cdc_ether 
usbnet r8152 mii ses enclosure scsi_transport_sas uas usb_storage thunderbolt 
xt_state xt_conntrack ipt_REJECT nf_reject_ipv4 nf_nat_h323 nf_conntrack_h323 
nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip 
nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp 
8812au(OE) sctp ip6_udp_tunnel udp_tunnel ccm vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) rfcomm iptable_mangle xt_CHECKSUM iptable_nat xt_MASQUERADE nf_nat 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_tcpudp bridge stp llc 
iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep zram 
binfmt_misc nls_iso8859_1 btusb uvcvideo btrtl btbcm videobuf2_vmalloc 
videobuf2_memops btintel videobuf2_v4l2 videobuf2_common bluetooth videodev 
ecdh_generic mc ecc mei_hdcp joydev intel_rapl_msr snd_sof_pci 
snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc 
snd_sof snd_sof_xtensa_dsp
[81424.410115]  snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match 
snd_hda_codec_realtek snd_soc_acpi snd_hda_codec_generic x86_pkg_temp_thermal 
intel_powerclamp snd_hda_codec_hdmi kvm_intel snd_hda_intel kvm 
snd_intel_dspcfg soundwire_intel iwlmvm soundwire_generic_allocation 
soundwire_cadence rapl snd_hda_codec mac80211 intel_cstate snd_hda_core libarc4 
snd_hwdep soundwire_bus iwlwifi input_leds snd_soc_core thinkpad_acpi serio_raw 
processor_thermal_device processor_thermal_rfim ucsi_acpi nvram cfg80211 
snd_compress elan_i2c ledtrig_audio efi_pstore ac97_bus wmi_bmof 
snd_pcm_dmaengine intel_wmi_thunderbolt snd_seq_midi typec_ucsi 
snd_seq_midi_event ee1004 8250_dw processor_thermal_mbox snd_pcm mei_me typec 
snd_rawmidi mei processor_thermal_rapl intel_rapl_common intel_pch_thermal 
intel_soc_dts_iosf snd_seq snd_seq_device snd_timer snd int3403_thermal 
soundcore int340x_thermal_zone mac_hid int3400_thermal acpi_thermal_rel 
acpi_pad nvidia_uvm(POE) sch_fq_codel coretemp msr
[81424.410142]  parport_pc ppdev lp parport binder_linux ashmem_linux(CE) 
sunrpc ip_tables x_tables autofs4 dm_crypt hid_logitech_hidpp wacom 
hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) 
nvidia(POE) rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel i2c_algo_bit aesni_intel drm_kms_helper syscopyarea 
crypto_simd sysfillrect sysimgblt fb_sys_fops cec cryptd glue_helper rc_core 
psmouse e1000e drm nvme intel_lpss_pci i2c_i801 intel_lpss i2c_smbus nvme_core 
idma64 xhci_pci rtsx_pci virt_dma xhci_pci_renesas wmi video pinctrl_cannonlake
[81424.410163] CPU: 11 PID: 352896 Comm: gpu-manager Tainted: PWC OE
 5.11.0-34-lowlatency #36~20.04.1-Ubuntu
[81424.410164] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET59W (1.42 
) 04/27/2021
[81424.410165] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm]
[81424.410167] Code: 0f 1f 00 0f 1f 44 00 00 55 48 8b 47 48 48 8b 78 20 48 8b 
05 ab 6c 00 00 48 89 e5 48 8b 40 28 e8 9f 40 be d1 84 c0 74 02 5d c3 <0f> 0b 5d 
c3 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56
[81424.410168] RSP: 0018:9e5d84c63b20 EFLAGS: 00010246
[81424.410169] RAX:  RBX: 8a9486ce4400 RCX: 0008
[81424.410170] RDX: c2b8fe98 RSI: 0296 RDI: c2b8fe60
[81424.410171] RBP: 9e5d84c63b20 R08: 0008 R09: 9e5d84c63b08
[81424.410171] R10:  R11: c04151d8 R12: 8a925c9a9800
[81424.410172] R13: 8a933c608a80 R14: 0001 R15: 8a925c9a9800
[81424.410173] FS:  7f63e2203b80() GS:8a99bc4c() 
knlGS:
[81424.410174] CS:  0010 DS:  ES:  CR0: 80050033
[81424.410175] CR2: 7f63e25e1c40 CR3: 0001139cc006 CR4: 003726e0
[81424.410176] DR0:  DR1:  DR2: 
[81424.410177] DR3:  DR6: fffe0ff0 DR7: 0400
[81424.410178] Call Trace:
[81424.410179]  drm_set_master+0x55/0x80 [drm]
[81424.410192]  drm_new_set_master+0x4d/0xa0 [drm]
[81424.410205]  drm_master_open+0x6e/0xa0 [drm]
[81424.410217]  drm_open+0x18a/0x260 [drm]
[81424.410231]  drm_stub_open+0xae/0x110 [drm]
[81424.410245]  chrdev_open+0xa7/0x1c0
[81424.410247]  ? security_file_open+0xdd/0x150
[81424.410249]  ? cdev_put.part.0+0x20/0x20
[81424.410251]  do_dentry_open+0x156/0x370
[81424.410252]  vfs_open+0x2d/0x30
[81424.410254]  path_openat+0xb15/0x1110
[81424.410255]  ? xa_destroy+0x9b/0xe0
[81424.410257]  do_filp_open+0x91/0x100
[81424.410258]  ? __check_object_size+0x13f/0x150
[81424.410260]  do_sys_openat2+0x221/0x2e0
[81424.410262]  do_sys_open+0x46/0x80
[81424.410263]  

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[pablo]

Same thing with 5.8.0-63-generic, on 20.04.2.

Need a lot of rebooting to load the kernel.

Adding kernel options:

nolapic => loads the kernel, but disables multicore, making use
impracticable

intremap=off => loads the kernel, does not seem to have noticeable side
effects

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Pablo]

Hi, I booted by disabling secure boot as suggested and it seems to fix
the wifi issue.

After disabling secure boot, I had to reboot into Windows once to get
wifi working again, and then I tried rebooting into Linux a couple of
times.  So far wifi has worked everytime.

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

Title:
  RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal
  Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ 

[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Pablo]

Hi Feng, I was unable to try the suggested kernel as it is unsigned (and
I could not find instructions on how to get an unsigned kernel 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/1872984

Title:
  RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal
  Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  Device is unable to 

[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Pablo]

Update:

Based on comments here:
https://bugzilla.kernel.org/show_bug.cgi?id=206411#c12

I tried adding "options rtw88_pci disable_aspm=1" to
/etc/modprobe.d/rtw88_pci.conf , which appears to solve the issue in
Groovy Gorilla under 5.8.0-25-generic.

I will update if this workaround is not permanent.

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

Title:
  RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal
  Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 

[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Pablo]

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

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

Title:
  RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal
  Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 
563278766710
  [   10.714780] ---[ end trace f00c16109236af6f ]---
  [   10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5

  Device is unable to scan for networks and error occurs when attempting
  to turn on/off wifi in 

[Kernel-packages] [Bug 1872984] Re: RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

[Pablo]

I can confirm this problem exists on Lenovo Flex 6 14IKB, on both Ubuntu
20.04 (using 5.4.0-26-generic and above) and on 20.10 (using
5.8.0-25-generic).

Upgrading BIOS to latest did NOT solve this issue for me.

As others have reported, wifi appears to work normally for a while, but
in my case it stops working after I ask NetworkManager to connect to a
network.

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

Title:
  RTL8822BE [10ec:b822] network driver rtl_wifi crashes on boot in Focal
  Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  RTL8822BE crashes after rtw_pci starts on boot after kernel update to
  5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is
  still present on latest mainline kernel version
  5.7.0-050700rc1-generic .

  [   10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0
  [   10.714544] [ cut here ]
  [   10.714545] failed to read DBI register, addr=0x0719
  [   10.714577] WARNING: CPU: 0 PID: 939 at 
drivers/net/wireless/realtek/rtw88/pci.c:1156 
rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714577] Modules linked in: (see attached dmesg)
  [   10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 
5.7.0-050700rc1-generic #202004122032
  [   10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 
01/23/2018
  [   10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci]
  [   10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 
31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 
fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00
  [   10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282
  [   10.714618] RAX:  RBX:  RCX: 
0007
  [   10.714619] RDX: 0007 RSI: 0092 RDI: 
933cc9e19c80
  [   10.714619] RBP: b466007e7898 R08: 03d2 R09: 
0004
  [   10.714620] R10:  R11: 0001 R12: 
933cbdf31ea0
  [   10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: 

  [   10.714622] FS:  7fbcedc6efc0() GS:933cc9e0() 
knlGS:
  [   10.714622] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 
003606f0
  [   10.714623] Call Trace:
  [   10.714627]  rtw_pci_link_ps+0x4e/0x90 [rtwpci]
  [   10.714630]  ? _raw_spin_unlock_bh+0x1e/0x20
  [   10.714637]  rtw_leave_ips+0x1f/0x80 [rtw88]
  [   10.714640]  rtw_ops_config+0xa3/0xe0 [rtw88]
  [   10.714658]  ieee80211_hw_config+0x95/0x390 [mac80211]
  [   10.714669]  ieee80211_recalc_idle+0x27/0x30 [mac80211]
  [   10.714679]  __ieee80211_start_scan+0x334/0x750 [mac80211]
  [   10.714688]  ieee80211_request_scan+0x30/0x50 [mac80211]
  [   10.714699]  ieee80211_scan+0x5c/0xa0 [mac80211]
  [   10.714719]  nl80211_trigger_scan+0x59a/0x6c0 [cfg80211]
  [   10.714722]  genl_rcv_msg+0x1a8/0x470
  [   10.714724]  ? ep_poll_callback+0x2a0/0x2c0
  [   10.714725]  ? genl_family_rcv_msg_attrs_parse+0x100/0x100
  [   10.714726]  netlink_rcv_skb+0x50/0x120
  [   10.714728]  genl_rcv+0x29/0x40
  [   10.714729]  netlink_unicast+0x1a8/0x250
  [   10.714730]  netlink_sendmsg+0x233/0x460
  [   10.714739]  ? _copy_from_user+0x31/0x60
  [   10.714750]  sock_sendmsg+0x65/0x70
  [   10.714751]  sys_sendmsg+0x212/0x280
  [   10.714752]  ? copy_msghdr_from_user+0x5c/0x90
  [   10.714755]  ? __check_object_size+0x4d/0x150
  [   10.714756]  ___sys_sendmsg+0x81/0xc0
  [   10.714757]  ? __check_object_size+0x4d/0x150
  [   10.714759]  ? unix_ioctl+0x99/0x180
  [   10.714760]  ? sock_getsockopt+0x198/0xc04
  [   10.714761]  ? sock_do_ioctl+0x47/0x140
  [   10.714763]  ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0
  [   10.714765]  ? _cond_resched+0x19/0x30
  [   10.714767]  ? aa_sk_perm+0x43/0x1b0
  [   10.714768]  __sys_sendmsg+0x5c/0xa0
  [   10.714770]  __x64_sys_sendmsg+0x1f/0x30
  [   10.714772]  do_syscall_64+0x57/0x1b0
  [   10.714773]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   10.714774] RIP: 0033:0x7fbcedffb5b7
  [   10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10
  [   10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 
002e
  [   10.714777] RAX: ffda RBX: 5632787355d0 RCX: 
7fbcedffb5b7
  [   10.714777] RDX:  RSI: 7fff88e222c0 RDI: 
0006
  [   10.714778] RBP: 563278761380 R08: 0004 R09: 
563278761380
  [   10.714778] R10: 7fff88e22394 R11: 0246 R12: 
5632787354e0
  [   

[Kernel-packages] [Bug 1901890] [NEW] realtek r8822be kernel module fails after update to linux kernel-headers 5.0.4-28

[Pablo]

Public bug reported:

My recent upgrade to Focal (20.04) using 5.4.0-28 version of the kernel
kills wifi.  Wifi was working properly under 19.10 (using 5.3.0-68).
The issue persists using both rtw88 and rtwpci (which work under 19.10).
20.04 live CD has the same issue. I also tried installing 20.10 and
found the same issue. On startup wireless works for a little while,
allowing to see and connect to networks, but stops working shortly
thereafter (mere seconds).

Further, just trying the 20.04 live CD appears to mess the wireless card
when returning to 19.10 (which is installed on a proper drive in my
laptop). Needed to reinstall the kernel (same version: 5.3.0-51-generic)
in 19.10 to get it working again. I have no idea what this means.

I have followed several of the suggestions in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133 (which
seems to be the same bug for a previous kernel version, so may be this
is a reversion?), to no avail.

My wireless adapter is an RTL8822BE which shows up in lspci and lshw -C
network, although under 5.4.0-28 lshw shows it as disabled (as I said,
it appears to work for a few seconds after startup). dsmeg shows some
issues with changing the power mode of the device although I am too much
of a noob to understand it.

In order to post this I rolled back to 19.10, so I no longer have access
to a machine experiencing this issue (and cannot post the logs), but can
reboot on the live CD and obtain them if there is any useful debugging
to be done.

Thanks!

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

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

Title:
   realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.4-28

Status in linux package in Ubuntu:
  New

Bug description:
  My recent upgrade to Focal (20.04) using 5.4.0-28 version of the
  kernel kills wifi.  Wifi was working properly under 19.10 (using
  5.3.0-68).  The issue persists using both rtw88 and rtwpci (which work
  under 19.10).  20.04 live CD has the same issue. I also tried
  installing 20.10 and found the same issue. On startup wireless works
  for a little while, allowing to see and connect to networks, but stops
  working shortly thereafter (mere seconds).

  Further, just trying the 20.04 live CD appears to mess the wireless
  card when returning to 19.10 (which is installed on a proper drive in
  my laptop). Needed to reinstall the kernel (same version:
  5.3.0-51-generic) in 19.10 to get it working again. I have no idea
  what this means.

  I have followed several of the suggestions in:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133 (which
  seems to be the same bug for a previous kernel version, so may be this
  is a reversion?), to no avail.

  My wireless adapter is an RTL8822BE which shows up in lspci and lshw
  -C network, although under 5.4.0-28 lshw shows it as disabled (as I
  said, it appears to work for a few seconds after startup). dsmeg shows
  some issues with changing the power mode of the device although I am
  too much of a noob to understand it.

  In order to post this I rolled back to 19.10, so I no longer have
  access to a machine experiencing this issue (and cannot post the
  logs), but can reboot on the live CD and obtain them if there is any
  useful debugging to be done.

  Thanks!

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

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

[Kernel-packages] [Bug 1879287] Re: [nvidia+amdgpu] System sometimes starts with a black screen with Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works perfectly)

[Juan Pablo]

I have a very similar problem, today I asked a question on ask ubuntu


https://askubuntu.com/questions/1265779/video-issues-with-amd-igpu-and-nvidia-gpu-in-an-aspire-a715-41g-laptop

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

Title:
  [nvidia+amdgpu] System sometimes starts with a black screen with
  Nvidia PRIME setup on Ryzen+Nvidia system (but kernel 5.6.14 works
  perfectly)

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-prime package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  I've recently installed Ubuntu on a laptop that has a Ryzen APU (with
  Vega 8 integrated graphics) and a Nvidia dedicated GPU. The first
  issue that this kind of setup gives on a fresh install is that that
  PRIME render offloading doesn't work, I presume that Ubuntu currently
  sets up hybrid graphics for laptop with Intel+Nvidia, not AMD+Nvidia
  but that's another separate issue. As a workaround I created an Xorg
  configuration (attached in this report) that sets up both GPUs (with
  the appropiate BusIDs), after such configuration is applied the system
  boots fine with AMD integrated graphics being used and the ability to
  switch to Nvidia with PRIME render off-loading.

  The problem comes when I try to use the computer the next day, then it
  gives me a black screen without having the ability to switch to a tty,
  the boot log doesn't throw any errors I just see a black screen after
  Xorg tries to start. I can make it work again by entering in recovery
  mode, logging into a root console and switching between "nvidia" and
  "on-demand" modes using prime-select (I set it up to "on-demand"
  profile after installing Ubuntu).

  For the moment I cannot provide any relevant logs since it's now
  working fine (and I don't remember seeing any errors on Xorg logs),
  also I don't really know where to look for this kind of issues.

  My system information:
  -CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
  -GPU: Nvidia GTX 1650 Mobile (TU117M) (Using Nvidia binary driver version 
440.64 from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  -RAM: 8 GB
  -Kubuntu 20.04 LTS (Using KDE Plasma 5.18.4)
  -Xorg 1.20.8-2ubuntu2

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

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

[Kernel-packages] [Bug 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550

[Pablo Carballo]

nvidia-driver-440:
  Instalados: (ninguno)
  Candidato:  440.100-0ubuntu0.20.04.1
  Tabla de versión:
 440.100-0ubuntu0.20.04.1 500
500 http://ar.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 
Packages
 440.82+really.440.64-0ubuntu6 500
500 http://ar.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages

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

Title:
  Focal detects wrong driver version 440 for NVIDIA GTX 550

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  My desktop PC has an NVIDIA GeForce GTX 550 Ti. Just installed Focal 
selecting the option to install 3rd-party drivers during setup process, and 
after the first boot screen resolution is 800x600.
  I verified the detected version of NVIDIA driver and I realized it was 440, 
although correct version is 390. Finally I manually installed proper version 
(390) and now the graphics are working OK.

  This is the output for the command "$ lspci -nn":

  01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 
Ti] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio 
Controller (rev a1)

  
  This is the output for the command "# ubuntu-drivers devices":

  == /sys/devices/pci:00/:00:02.0/:01:00.0 ==
  modalias : pci:v10DEd1244sv1043sd83BEbc03sc00i00
  vendor   : NVIDIA Corporation
  model: GF116 [GeForce GTX 550 Ti]
  driver   : nvidia-driver-435 - distro non-free
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-440 - distro non-free recommended
  driver   : nvidia-340 - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  The version 440 is recommended, but it's not correct for this model
  (390 should be recommended instead)

  
  The issue was not present in previous versions (in both 19.10 and 18.04 
driver 390 was recommended correctly)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874874/+subscriptions

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

[Kernel-packages] [Bug 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550

[Pablo Carballo]

nvidia-driver-440 contains some invalid modaliases that cause to be
detected as a valid driver for the wrong card.

** Package changed: ubuntu-drivers-common (Ubuntu) => nvidia-graphics-
drivers-440 (Ubuntu)

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

Title:
  Focal detects wrong driver version 440 for NVIDIA GTX 550

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  New

Bug description:
  My desktop PC has an NVIDIA GeForce GTX 550 Ti. Just installed Focal 
selecting the option to install 3rd-party drivers during setup process, and 
after the first boot screen resolution is 800x600.
  I verified the detected version of NVIDIA driver and I realized it was 440, 
although correct version is 390. Finally I manually installed proper version 
(390) and now the graphics are working OK.

  This is the output for the command "$ lspci -nn":

  01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 
Ti] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio 
Controller (rev a1)

  
  This is the output for the command "# ubuntu-drivers devices":

  == /sys/devices/pci:00/:00:02.0/:01:00.0 ==
  modalias : pci:v10DEd1244sv1043sd83BEbc03sc00i00
  vendor   : NVIDIA Corporation
  model: GF116 [GeForce GTX 550 Ti]
  driver   : nvidia-driver-435 - distro non-free
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-440 - distro non-free recommended
  driver   : nvidia-340 - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  The version 440 is recommended, but it's not correct for this model
  (390 should be recommended instead)

  
  The issue was not present in previous versions (in both 19.10 and 18.04 
driver 390 was recommended correctly)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874874/+subscriptions

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

[Kernel-packages] [Bug 1881322] Re: Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing Ubuntu 20.04

[pablo josé blanco]

Hi, In my case it was solved after adding both parameters,
"i8042.nopnp=1 pci=nocrs" I tried adding  "i8042.nopnp" alone and it
didn't work.

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

Title:
  Touchpad not detected in 'Lenovo V15-IIL model 82C5' after installing
  Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 20.04 is installed in a brand new Lenovo V15-IIL alongside
  Windows 10. According to lenovo's support page, the driver for windows
  is Synaptics 19.5.10.149_Elan 22.4.18.1. In windows the touchpad works
  fine.

  This model has two options in BIOS regarding Fn Keys, a "Smart Fn key"
  that toogles the Fn key on/off each time you press it and a "Foolproof
  Fn Key" that maps the Fn key to Ctrl when you press a combinations of
  keys that does not have a Fn assigned. When I enable the "foolproof fn
  key" in the BIOS, the Fn + F1...F12 and the sound driver stop working
  (i dont have sound, i can't change the volume and the volume icon in
  the GUI does not show). Fn+F6 (to enable/disable touchpad) can't
  enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-33-generic 5.4.0-33.37
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fdadam 1434 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 13:08:24 2020
  InstallationDate: Installed on 2020-05-28 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 002: ID 0458:0186 KYE Systems Corp. (Mouse Systems) Genius 
DX-120 Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 82C5
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=fd0c8ed1-6032-467c-9902-3094e6740be8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-33-generic N/A
   linux-backports-modules-5.4.0-33-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL:
  dmi.product.family: V15-IIL
  dmi.product.name: 82C5
  dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL
  dmi.product.version: Lenovo V15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1880593] Re: TouchPad not working

[pablo josé blanco]

Hi, I don't know if this is related, but I just had an error with my a
program related to my keyboard.

Please find attached crash.png

Kind regards,
Pablo.

** Attachment added: "crash.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880593/+attachment/5384894/+files/crash.png

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

Title:
  TouchPad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Support team, in a fresh installation in a lenovo laptop, touchpad
  is not working. mouse is working fine though.

  Attaching /proc/bus/input/devices as per debugging wiki.

  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo

  Kind regards,
  Pablo.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pali   1214 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 15:05:38 2020
  InstallationDate: Installed on 2020-05-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. 2.4G Wireless 
Mouse
   Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 82C5
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=3b0502a4-3082-45eb-ac7e-12a3c6b934ee ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL:
  dmi.product.family: V15-IIL
  dmi.product.name: 82C5
  dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL
  dmi.product.version: Lenovo V15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1880593] Re: TouchPad not working

[pablo josé blanco]

attaching journal -b output

Thanks!

** Attachment added: "journal -b output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880593/+attachment/5376999/+files/journal-b.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/1880593

Title:
  TouchPad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi Support team, in a fresh installation in a lenovo laptop, touchpad
  is not working. mouse is working fine though.

  Attaching /proc/bus/input/devices as per debugging wiki.

  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo

  Kind regards,
  Pablo.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pali   1214 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 15:05:38 2020
  InstallationDate: Installed on 2020-05-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. 2.4G Wireless 
Mouse
   Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 82C5
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=3b0502a4-3082-45eb-ac7e-12a3c6b934ee ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL:
  dmi.product.family: V15-IIL
  dmi.product.name: 82C5
  dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL
  dmi.product.version: Lenovo V15-IIL
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1880593] [NEW] TouchPad not working

[pablo josé blanco]

Public bug reported:

Hi Support team, in a fresh installation in a lenovo laptop, touchpad is
not working. mouse is working fine though.

Attaching /proc/bus/input/devices as per debugging wiki.

https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo

Kind regards,
Pablo.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-31-generic 5.4.0-31.35
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pali   1214 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 15:05:38 2020
InstallationDate: Installed on 2020-05-25 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. 2.4G Wireless Mouse
 Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated Camera
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 82C5
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=3b0502a4-3082-45eb-ac7e-12a3c6b934ee ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-31-generic N/A
 linux-backports-modules-5.4.0-31-generic  N/A
 linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DKCN26WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo V15-IIL
dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL:
dmi.product.family: V15-IIL
dmi.product.name: 82C5
dmi.product.sku: LENOVO_MT_82C5_BU_idea_FM_V15-IIL
dmi.product.version: Lenovo V15-IIL
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

** Attachment added: "/proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/1880593/+attachment/5376598/+files/devices

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

Title:
  TouchPad not working

Status in linux package in Ubuntu:
  New

Bug description:
  Hi Support team, in a fresh installation in a lenovo laptop, touchpad
  is not working. mouse is working fine though.

  Attaching /proc/bus/input/devices as per debugging wiki.

  https://wiki.ubuntu.com/DebuggingTouchpadDetection#generalinfo

  Kind regards,
  Pablo.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-31-generic 5.4.0-31.35
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pali   1214 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 25 15:05:38 2020
  InstallationDate: Installed on 2020-05-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 062a:4102 MosArt Semiconductor Corp. 2.4G Wireless 
Mouse
   Bus 001 Device 002: ID 04f2:b624 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 82C5
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=3b0502a4-3082-45eb-ac7e-12a3c6b934ee ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-31-generic N/A
   linux-backports-modules-5.4.0-31-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V15-IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn82C5:pvrLenovoV15-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15-IIL:
  dmi.product.family: V15-IIL
  dmi.produc

[Kernel-packages] [Bug 1877422] Re: Wifi is not showing on my HP 15s 0091tu laptop

[Pablo]

I'm having the same experience.  I thought it might be a duplicate of
1838133 (a regression in this case, since that one has been fixed).

My wireless adapter is an RTL8822BE which shows up in lspci and lshw -C
network, although under the 5.4.0-28 kernel lshw shows it as disabled
(it appears to work for a few seconds after startup). dsmeg shows some
issues with changing the power mode of the device although I am too much
of a noob to understand it.

The issue is also present in the 20.04 live CD. In this case Wifi is
initially working and I can see wireless networks, but as soon as a I
connect to a network it dissappears.

Rolling back to 19.10 under kernel 5.3.0.51 fixes the issue.

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

Title:
  Wifi is not showing on my HP 15s 0091tu laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Wireless network is not showing on my HP 15s 0091tu laptop.
  I have installed rtl8822be wifi driver and insecure the boot mode. Still its 
not showing after restart

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tanvir 1432 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 23:14:04 2020
  InstallationDate: Installed on 2020-04-28 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IwConfig:
   ppp0  no wireless extensions.
   
   eno1  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   Bus 001 Device 002: ID 09da:2403 A4Tech Co., Ltd. 2.4G Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15s-du0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=a808b44a-d509-4cd9-a034-d16a74acf3ef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 85EF
  dmi.board.vendor: HP
  dmi.board.version: 36.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.05:bd03/22/2019:svnHP:pnHPLaptop15s-du0xxx:pvrType1ProductConfigId:rvnHP:rn85EF:rvr36.19:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15s-du0xxx
  dmi.product.sku: 7NH34PA#UUF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

[Pablo]

Bump.  Should this be filed as a new bug?

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

Title:
  realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.0-21

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek Wifi stops working after the driver changed from rtlwifi to
  rtw88.

  [Fix]
  Sync rtw88 to upstream version, and use MSI on the device.

  [Test]
  User confirmed the backport fixes the issue.

  [Regression Potential]
  Low. Currently only 8822be uses rtw88.

  === Original Bug Report ===
  On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the 
dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that 
wifi was no longer working because at work I exclusively use a wired Ethernet 
connection.

  Today, however, when I tried to use my realtek r8822be wireless card,
  I discovered that it was totally unresponsive and did not work with
  wpa_supplicant / wpa_cli even when invoked manually from the command
  line (let alone with NetworkManager). When the problem occurred, I was
  using 19.04's latest kernel 5.0.0-21.

  I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname
  -a" shows that I am using the previous kernel version:

  Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  With this kernel version as well as linux-headers-5.0.0.20, linux-
  headers-5.0.0-20-generic, my realtek wireless card works fine. While
  booted into 5.0.0-20 kernel, here are the realtek kernel modules that
  are loaded:

  # lsmod | grep r8
  r8822be   692224  0
  mac80211  806912  1 r8822be
  cfg80211  671744  2 mac80211,r8822be
  r8169  81920  0

  Hopefully this realtek wireless regression can get fixed in the next
  minor kernel version. Let me know if you need any more information.

  Best Regards,
  Jun

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

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

[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

[Pablo]

Correction to my prior post: 20.04 live CD has the same issue. Wireless
works for a little while, allowing to see and connect to networks, but
stops working shortly thereafter.

Further, just trying the 20.04 live CD appears to mess the wireless card
when returning to 19.10 (which is installed on a proper drive in my
laptop).  Needed to reinstall the kernel (same version:
5.3.0-51-generic) in 19.10 to get it working again.  I have no idea what
this means.

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

Title:
  realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.0-21

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek Wifi stops working after the driver changed from rtlwifi to
  rtw88.

  [Fix]
  Sync rtw88 to upstream version, and use MSI on the device.

  [Test]
  User confirmed the backport fixes the issue.

  [Regression Potential]
  Low. Currently only 8822be uses rtw88.

  === Original Bug Report ===
  On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the 
dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that 
wifi was no longer working because at work I exclusively use a wired Ethernet 
connection.

  Today, however, when I tried to use my realtek r8822be wireless card,
  I discovered that it was totally unresponsive and did not work with
  wpa_supplicant / wpa_cli even when invoked manually from the command
  line (let alone with NetworkManager). When the problem occurred, I was
  using 19.04's latest kernel 5.0.0-21.

  I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname
  -a" shows that I am using the previous kernel version:

  Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  With this kernel version as well as linux-headers-5.0.0.20, linux-
  headers-5.0.0-20-generic, my realtek wireless card works fine. While
  booted into 5.0.0-20 kernel, here are the realtek kernel modules that
  are loaded:

  # lsmod | grep r8
  r8822be   692224  0
  mac80211  806912  1 r8822be
  cfg80211  671744  2 mac80211,r8822be
  r8169  81920  0

  Hopefully this realtek wireless regression can get fixed in the next
  minor kernel version. Let me know if you need any more information.

  Best Regards,
  Jun

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

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

[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

[Pablo]

Some further info:
I rolled back to 19.10 using the 5.3.0-51-generic and rtwpci and rtw88 work 
well. But as stated before, when going to 5.4.0-28-generic (and -26) I am 
suffering from what appears to be this bug. 

My wireless adapter is an RTL8822BE which shows up in lspci and lshw -C
network, although under 5.4.0-28 lshw shows it as disabled (it appears
to work for a few seconds after startup).  dsmeg shows some issues with
changing the power mode of the device although I am too much of a noob
to understand it.

Interestingly, wireless seemed to work on the 20.04 live version (from
USB).

As I said, I rolled back from 20.04 so I no longer have access to a
20.04 machine, but can reinstall it if there is any useful debugging to
be done.

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

Title:
  realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.0-21

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek Wifi stops working after the driver changed from rtlwifi to
  rtw88.

  [Fix]
  Sync rtw88 to upstream version, and use MSI on the device.

  [Test]
  User confirmed the backport fixes the issue.

  [Regression Potential]
  Low. Currently only 8822be uses rtw88.

  === Original Bug Report ===
  On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the 
dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that 
wifi was no longer working because at work I exclusively use a wired Ethernet 
connection.

  Today, however, when I tried to use my realtek r8822be wireless card,
  I discovered that it was totally unresponsive and did not work with
  wpa_supplicant / wpa_cli even when invoked manually from the command
  line (let alone with NetworkManager). When the problem occurred, I was
  using 19.04's latest kernel 5.0.0-21.

  I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname
  -a" shows that I am using the previous kernel version:

  Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  With this kernel version as well as linux-headers-5.0.0.20, linux-
  headers-5.0.0-20-generic, my realtek wireless card works fine. While
  booted into 5.0.0-20 kernel, here are the realtek kernel modules that
  are loaded:

  # lsmod | grep r8
  r8822be   692224  0
  mac80211  806912  1 r8822be
  cfg80211  671744  2 mac80211,r8822be
  r8169  81920  0

  Hopefully this realtek wireless regression can get fixed in the next
  minor kernel version. Let me know if you need any more information.

  Best Regards,
  Jun

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

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

[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

[Pablo]

Hi all,
 I think my recent upgrade to Focal (20.04) using 5.4.0.28 version of the 
kernel still shows this problem.  Wifi was working properly under 19.10 (not 
sure which kernel I was using, I did a fresh install) but now using rtw88 and 
rtwpci I have no wireless connection.

I tried some of the suggestions here but none helped.  I have updated my
bios to the latest firmware but the problem persists.

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

Title:
  realtek r8822be kernel module fails after update to linux kernel-
  headers 5.0.0-21

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Realtek Wifi stops working after the driver changed from rtlwifi to
  rtw88.

  [Fix]
  Sync rtw88 to upstream version, and use MSI on the device.

  [Test]
  User confirmed the backport fixes the issue.

  [Regression Potential]
  Low. Currently only 8822be uses rtw88.

  === Original Bug Report ===
  On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the 
dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that 
wifi was no longer working because at work I exclusively use a wired Ethernet 
connection.

  Today, however, when I tried to use my realtek r8822be wireless card,
  I discovered that it was totally unresponsive and did not work with
  wpa_supplicant / wpa_cli even when invoked manually from the command
  line (let alone with NetworkManager). When the problem occurred, I was
  using 19.04's latest kernel 5.0.0-21.

  I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname
  -a" shows that I am using the previous kernel version:

  Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  With this kernel version as well as linux-headers-5.0.0.20, linux-
  headers-5.0.0-20-generic, my realtek wireless card works fine. While
  booted into 5.0.0-20 kernel, here are the realtek kernel modules that
  are loaded:

  # lsmod | grep r8
  r8822be   692224  0
  mac80211  806912  1 r8822be
  cfg80211  671744  2 mac80211,r8822be
  r8169  81920  0

  Hopefully this realtek wireless regression can get fixed in the next
  minor kernel version. Let me know if you need any more information.

  Best Regards,
  Jun

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

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

[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Pablo Catalina]

I installed Ubuntu 20.04 5 days ago (using the daily iso) and works fine
with Quadro P3200 Mobile and default proprietary drivers installed.

I installed it setting up the user with autologon from the installer.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : 

[Kernel-packages] [Bug 1873673] Re: Kernel Error IRQ

[Pablo Catalina]

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873673/+attachment/5356793/+files/syslog.xz

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

Title:
  Kernel Error IRQ

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo p52 with Thunderbolt dock (2 HDMIs - one connected, few USBs
  3.0 - one with an external HD connected, and one USB-C)

  I noted that the mouse and keyboard using one Logitech Unifying
  receiver (connected through USB on the Laptop, not dock) started to
  jump over the screen and responded bad. I noted on dmesg the following
  error:

  [  464.663455] [ cut here ]
  [  464.663483] irq 160 handler irq_default_primary_handler+0x0/0x10 enabled 
interrupts
  [  464.663499] WARNING: CPU: 4 PID: 318 at kernel/irq/handle.c:152 
__handle_irq_event_percpu+0x1a7/0x1b0
  [  464.663500] Modules linked in: snd_usb_audio snd_usbmidi_lib ccm cdc_ether 
usbnet r8152 mii rfcomm cmac algif_hash algif_skcipher af_alg bnep 
typec_displayport nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(PO) binfmt_misc 
mei_hdcp nls_iso8859_1 intel_rapl_msr nvidia(PO) snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_hda_codec_hdmi snd_sof_intel_ipc snd_sof uvcvideo x86_pkg_temp_thermal 
intel_powerclamp snd_sof_xtensa_dsp coretemp iwlmvm btusb snd_hda_ext_core 
videobuf2_vmalloc btrtl btbcm videobuf2_memops btintel snd_soc_acpi_intel_match 
videobuf2_v4l2 snd_soc_acpi kvm_intel snd_hda_codec_realtek videobuf2_common 
mac80211 snd_hda_codec_generic videodev bluetooth libarc4 snd_soc_core mc kvm 
joydev intel_cstate snd_compress intel_rapl_perf ac97_bus snd_pcm_dmaengine 
ecdh_generic ecc snd_hda_intel snd_intel_dspcfg snd_seq_midi input_leds 
snd_seq_midi_event thinkpad_acpi snd_hda_codec iwlwifi rtsx_pci_ms snd_hda_core 
wmi_bmof serio_raw snd_rawmidi
  [  464.663564]  elan_i2c memstick nvram snd_hwdep 8250_dw 
intel_wmi_thunderbolt ledtrig_audio mei_me snd_pcm snd_seq cfg80211 mei 
processor_thermal_device ipmi_devintf snd_seq_device intel_rapl_common 
ipmi_msghandler snd_timer intel_soc_dts_iosf intel_pch_thermal ucsi_acpi 
typec_ucsi snd typec soundcore int3403_thermal int340x_thermal_zone 
int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel parport_pc ppdev 
lp parport ip_tables x_tables autofs4 dm_crypt wacom hid_logitech_hidpp 
hid_logitech_dj hid_generic usbhid hid i915 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel i2c_algo_bit drm_kms_helper nvme rtsx_pci_sdmmc syscopyarea 
sysfillrect sysimgblt aesni_intel fb_sys_fops crypto_simd cryptd glue_helper 
psmouse intel_lpss_pci e1000e drm thunderbolt i2c_i801 nvme_core rtsx_pci 
intel_lpss idma64 virt_dma wmi pinctrl_cannonlake video pinctrl_intel
  [  464.663627] CPU: 4 PID: 318 Comm: irq/16-i801_smb Tainted: P   O   
   5.4.0-24-lowlatency #28-Ubuntu
  [  464.663630] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET50W 
(1.33 ) 01/15/2020
  [  464.663637] RIP: 0010:__handle_irq_event_percpu+0x1a7/0x1b0
  [  464.663641] Code: 48 0f ba 6b 40 01 0f 82 fd fe ff ff e9 87 02 00 00 48 8b 
13 44 89 e6 48 c7 c7 30 58 36 bb c6 05 99 5a 6f 01 01 e8 a4 9a f8 ff <0f> 0b eb 
c5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54
  [  464.663643] RSP: 0018:b37a40557d68 EFLAGS: 00010286
  [  464.663647] RAX:  RBX: 97bd37c54200 RCX: 
0006
  [  464.663649] RDX: 0007 RSI: 0096 RDI: 
97bd3c1178c0
  [  464.663651] RBP: b37a40557da0 R08: 0001 R09: 
054d
  [  464.663653] R10: 0001eb4c R11: 0004 R12: 
00a0
  [  464.663655] R13:  R14: 97bd3825c700 R15: 
0002
  [  464.663658] FS:  () GS:97bd3c10() 
knlGS:
  [  464.663661] CS:  0010 DS:  ES:  CR0: 80050033
  [  464.663663] CR2: 22850c710ba0 CR3: 00052100a005 CR4: 
003606e0
  [  464.663665] DR0:  DR1:  DR2: 

  [  464.663667] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  464.663669] Call Trace:
  [  464.663680]  ? irq_finalize_oneshot.part.0+0xe0/0xe0
  [  464.663686]  handle_irq_event_percpu+0x33/0x80
  [  464.663692]  handle_irq_event+0x39/0x58
  [  464.663697]  handle_simple_irq+0x6f/0xa0
  [  464.663703]  generic_handle_irq+0x28/0x40
  [  464.663709]  i2c_handle_smbus_host_notify+0x28/0x40
  [  464.663717]  i801_isr+0x1ee/0x300 [i2c_i801]
  [  464.663724]  irq_forced_thread_fn+0x33/0x80
  [  464.663729]  irq_thread+0xda/0x170
  [  464.663736]  ? wake_threads_waitq+0x30/0x30
  [  464.663741]  kthread+0x104/0x140
  [  464.663747]  ? irq_thread_check_affinity+0xe0/0xe0
  [  464.663750]  ? kthread_park+0x90/0x90
  [  464.663757]  ret_from_fork+0x35/0x40
  [  

[Kernel-packages] [Bug 1873673] [NEW] Kernel Error IRQ

[Pablo Catalina]

Public bug reported:

Lenovo p52 with Thunderbolt dock (2 HDMIs - one connected, few USBs 3.0
- one with an external HD connected, and one USB-C)

I noted that the mouse and keyboard using one Logitech Unifying receiver
(connected through USB on the Laptop, not dock) started to jump over the
screen and responded bad. I noted on dmesg the following error:

[  464.663455] [ cut here ]
[  464.663483] irq 160 handler irq_default_primary_handler+0x0/0x10 enabled 
interrupts
[  464.663499] WARNING: CPU: 4 PID: 318 at kernel/irq/handle.c:152 
__handle_irq_event_percpu+0x1a7/0x1b0
[  464.663500] Modules linked in: snd_usb_audio snd_usbmidi_lib ccm cdc_ether 
usbnet r8152 mii rfcomm cmac algif_hash algif_skcipher af_alg bnep 
typec_displayport nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(PO) binfmt_misc 
mei_hdcp nls_iso8859_1 intel_rapl_msr nvidia(PO) snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_hda_codec_hdmi snd_sof_intel_ipc snd_sof uvcvideo x86_pkg_temp_thermal 
intel_powerclamp snd_sof_xtensa_dsp coretemp iwlmvm btusb snd_hda_ext_core 
videobuf2_vmalloc btrtl btbcm videobuf2_memops btintel snd_soc_acpi_intel_match 
videobuf2_v4l2 snd_soc_acpi kvm_intel snd_hda_codec_realtek videobuf2_common 
mac80211 snd_hda_codec_generic videodev bluetooth libarc4 snd_soc_core mc kvm 
joydev intel_cstate snd_compress intel_rapl_perf ac97_bus snd_pcm_dmaengine 
ecdh_generic ecc snd_hda_intel snd_intel_dspcfg snd_seq_midi input_leds 
snd_seq_midi_event thinkpad_acpi snd_hda_codec iwlwifi rtsx_pci_ms snd_hda_core 
wmi_bmof serio_raw snd_rawmidi
[  464.663564]  elan_i2c memstick nvram snd_hwdep 8250_dw intel_wmi_thunderbolt 
ledtrig_audio mei_me snd_pcm snd_seq cfg80211 mei processor_thermal_device 
ipmi_devintf snd_seq_device intel_rapl_common ipmi_msghandler snd_timer 
intel_soc_dts_iosf intel_pch_thermal ucsi_acpi typec_ucsi snd typec soundcore 
int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad 
acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 dm_crypt wacom hid_logitech_hidpp hid_logitech_dj hid_generic usbhid 
hid i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit 
drm_kms_helper nvme rtsx_pci_sdmmc syscopyarea sysfillrect sysimgblt 
aesni_intel fb_sys_fops crypto_simd cryptd glue_helper psmouse intel_lpss_pci 
e1000e drm thunderbolt i2c_i801 nvme_core rtsx_pci intel_lpss idma64 virt_dma 
wmi pinctrl_cannonlake video pinctrl_intel
[  464.663627] CPU: 4 PID: 318 Comm: irq/16-i801_smb Tainted: P   O 
 5.4.0-24-lowlatency #28-Ubuntu
[  464.663630] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET50W (1.33 
) 01/15/2020
[  464.663637] RIP: 0010:__handle_irq_event_percpu+0x1a7/0x1b0
[  464.663641] Code: 48 0f ba 6b 40 01 0f 82 fd fe ff ff e9 87 02 00 00 48 8b 
13 44 89 e6 48 c7 c7 30 58 36 bb c6 05 99 5a 6f 01 01 e8 a4 9a f8 ff <0f> 0b eb 
c5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54
[  464.663643] RSP: 0018:b37a40557d68 EFLAGS: 00010286
[  464.663647] RAX:  RBX: 97bd37c54200 RCX: 0006
[  464.663649] RDX: 0007 RSI: 0096 RDI: 97bd3c1178c0
[  464.663651] RBP: b37a40557da0 R08: 0001 R09: 054d
[  464.663653] R10: 0001eb4c R11: 0004 R12: 00a0
[  464.663655] R13:  R14: 97bd3825c700 R15: 0002
[  464.663658] FS:  () GS:97bd3c10() 
knlGS:
[  464.663661] CS:  0010 DS:  ES:  CR0: 80050033
[  464.663663] CR2: 22850c710ba0 CR3: 00052100a005 CR4: 003606e0
[  464.663665] DR0:  DR1:  DR2: 
[  464.663667] DR3:  DR6: fffe0ff0 DR7: 0400
[  464.663669] Call Trace:
[  464.663680]  ? irq_finalize_oneshot.part.0+0xe0/0xe0
[  464.663686]  handle_irq_event_percpu+0x33/0x80
[  464.663692]  handle_irq_event+0x39/0x58
[  464.663697]  handle_simple_irq+0x6f/0xa0
[  464.663703]  generic_handle_irq+0x28/0x40
[  464.663709]  i2c_handle_smbus_host_notify+0x28/0x40
[  464.663717]  i801_isr+0x1ee/0x300 [i2c_i801]
[  464.663724]  irq_forced_thread_fn+0x33/0x80
[  464.663729]  irq_thread+0xda/0x170
[  464.663736]  ? wake_threads_waitq+0x30/0x30
[  464.663741]  kthread+0x104/0x140
[  464.663747]  ? irq_thread_check_affinity+0xe0/0xe0
[  464.663750]  ? kthread_park+0x90/0x90
[  464.663757]  ret_from_fork+0x35/0x40
[  464.663763] ---[ end trace 73ff5361b8214bea ]---


NOTES: Ubuntu Focal just installed, enabled the thunderbolt and allow it (I had 
to poweroff the laptop, otherwise the External displays connected to the 
Thunderbolt did not work)

NOTE: The mouse is still making jumps and does not respond when I
perform a file transfer from the Dock USB external drive (big files that
take long to copy).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: 

[Kernel-packages] [Bug 1873673] Re: Kernel Error IRQ

[Pablo Catalina]

** Attachment added: "lsusb --tree -vv"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873673/+attachment/5356792/+files/lsusb-tree-vv.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/1873673

Title:
  Kernel Error IRQ

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lenovo p52 with Thunderbolt dock (2 HDMIs - one connected, few USBs
  3.0 - one with an external HD connected, and one USB-C)

  I noted that the mouse and keyboard using one Logitech Unifying
  receiver (connected through USB on the Laptop, not dock) started to
  jump over the screen and responded bad. I noted on dmesg the following
  error:

  [  464.663455] [ cut here ]
  [  464.663483] irq 160 handler irq_default_primary_handler+0x0/0x10 enabled 
interrupts
  [  464.663499] WARNING: CPU: 4 PID: 318 at kernel/irq/handle.c:152 
__handle_irq_event_percpu+0x1a7/0x1b0
  [  464.663500] Modules linked in: snd_usb_audio snd_usbmidi_lib ccm cdc_ether 
usbnet r8152 mii rfcomm cmac algif_hash algif_skcipher af_alg bnep 
typec_displayport nvidia_uvm(O) nvidia_drm(PO) nvidia_modeset(PO) binfmt_misc 
mei_hdcp nls_iso8859_1 intel_rapl_msr nvidia(PO) snd_sof_pci 
snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt 
snd_hda_codec_hdmi snd_sof_intel_ipc snd_sof uvcvideo x86_pkg_temp_thermal 
intel_powerclamp snd_sof_xtensa_dsp coretemp iwlmvm btusb snd_hda_ext_core 
videobuf2_vmalloc btrtl btbcm videobuf2_memops btintel snd_soc_acpi_intel_match 
videobuf2_v4l2 snd_soc_acpi kvm_intel snd_hda_codec_realtek videobuf2_common 
mac80211 snd_hda_codec_generic videodev bluetooth libarc4 snd_soc_core mc kvm 
joydev intel_cstate snd_compress intel_rapl_perf ac97_bus snd_pcm_dmaengine 
ecdh_generic ecc snd_hda_intel snd_intel_dspcfg snd_seq_midi input_leds 
snd_seq_midi_event thinkpad_acpi snd_hda_codec iwlwifi rtsx_pci_ms snd_hda_core 
wmi_bmof serio_raw snd_rawmidi
  [  464.663564]  elan_i2c memstick nvram snd_hwdep 8250_dw 
intel_wmi_thunderbolt ledtrig_audio mei_me snd_pcm snd_seq cfg80211 mei 
processor_thermal_device ipmi_devintf snd_seq_device intel_rapl_common 
ipmi_msghandler snd_timer intel_soc_dts_iosf intel_pch_thermal ucsi_acpi 
typec_ucsi snd typec soundcore int3403_thermal int340x_thermal_zone 
int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel parport_pc ppdev 
lp parport ip_tables x_tables autofs4 dm_crypt wacom hid_logitech_hidpp 
hid_logitech_dj hid_generic usbhid hid i915 crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel i2c_algo_bit drm_kms_helper nvme rtsx_pci_sdmmc syscopyarea 
sysfillrect sysimgblt aesni_intel fb_sys_fops crypto_simd cryptd glue_helper 
psmouse intel_lpss_pci e1000e drm thunderbolt i2c_i801 nvme_core rtsx_pci 
intel_lpss idma64 virt_dma wmi pinctrl_cannonlake video pinctrl_intel
  [  464.663627] CPU: 4 PID: 318 Comm: irq/16-i801_smb Tainted: P   O   
   5.4.0-24-lowlatency #28-Ubuntu
  [  464.663630] Hardware name: LENOVO 20MAS0DF03/20MAS0DF03, BIOS N2CET50W 
(1.33 ) 01/15/2020
  [  464.663637] RIP: 0010:__handle_irq_event_percpu+0x1a7/0x1b0
  [  464.663641] Code: 48 0f ba 6b 40 01 0f 82 fd fe ff ff e9 87 02 00 00 48 8b 
13 44 89 e6 48 c7 c7 30 58 36 bb c6 05 99 5a 6f 01 01 e8 a4 9a f8 ff <0f> 0b eb 
c5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 55 41 54
  [  464.663643] RSP: 0018:b37a40557d68 EFLAGS: 00010286
  [  464.663647] RAX:  RBX: 97bd37c54200 RCX: 
0006
  [  464.663649] RDX: 0007 RSI: 0096 RDI: 
97bd3c1178c0
  [  464.663651] RBP: b37a40557da0 R08: 0001 R09: 
054d
  [  464.663653] R10: 0001eb4c R11: 0004 R12: 
00a0
  [  464.663655] R13:  R14: 97bd3825c700 R15: 
0002
  [  464.663658] FS:  () GS:97bd3c10() 
knlGS:
  [  464.663661] CS:  0010 DS:  ES:  CR0: 80050033
  [  464.663663] CR2: 22850c710ba0 CR3: 00052100a005 CR4: 
003606e0
  [  464.663665] DR0:  DR1:  DR2: 

  [  464.663667] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  464.663669] Call Trace:
  [  464.663680]  ? irq_finalize_oneshot.part.0+0xe0/0xe0
  [  464.663686]  handle_irq_event_percpu+0x33/0x80
  [  464.663692]  handle_irq_event+0x39/0x58
  [  464.663697]  handle_simple_irq+0x6f/0xa0
  [  464.663703]  generic_handle_irq+0x28/0x40
  [  464.663709]  i2c_handle_smbus_host_notify+0x28/0x40
  [  464.663717]  i801_isr+0x1ee/0x300 [i2c_i801]
  [  464.663724]  irq_forced_thread_fn+0x33/0x80
  [  464.663729]  irq_thread+0xda/0x170
  [  464.663736]  ? wake_threads_waitq+0x30/0x30
  [  464.663741]  kthread+0x104/0x140
  [  464.663747]  ? irq_thread_check_affinity+0xe0/0xe0
  [  464.663750]  ? kthread_park+0x90/0x90
  [  464.663757]  

[Kernel-packages] [Bug 1861463] [NEW] package nvidia-compute-utils-390 390.132-0ubuntu2 failed to install/upgrade: el subproceso instalado paquete nvidia-compute-utils-390 script post-installation dev

[PABLO MARCELO PEREYRA]

Public bug reported:

se encontraron errores en la instalacion de los paquetes relacionados con el 
controlador de nvidia que actualmente tengo:
root@ubuntu-G74Sx:/home/ubuntu# lspci -vnn | grep -i VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116M [GeForce GT 
560M] [10de:1251] (rev a1) (prog-if 00 [VGA controller])
root@ubuntu-G74Sx:/home/ubuntu#

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-compute-utils-390 390.132-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Thu Jan 30 20:59:40 2020
ErrorMessage: el subproceso instalado paquete nvidia-compute-utils-390 script 
post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2020-01-30 (0 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.8
SourcePackage: nvidia-graphics-drivers-390
Title: package nvidia-compute-utils-390 390.132-0ubuntu2 failed to 
install/upgrade: el subproceso instalado paquete nvidia-compute-utils-390 
script post-installation devolvió el código de salida de error 1
UpgradeStatus: Upgraded to focal on 2020-01-30 (0 days ago)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package nvidia-compute-utils-390 390.132-0ubuntu2 failed to
  install/upgrade: el subproceso instalado paquete nvidia-compute-
  utils-390 script post-installation devolvió el código de salida de
  error 1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  se encontraron errores en la instalacion de los paquetes relacionados con el 
controlador de nvidia que actualmente tengo:
  root@ubuntu-G74Sx:/home/ubuntu# lspci -vnn | grep -i VGA
  01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116M [GeForce 
GT 560M] [10de:1251] (rev a1) (prog-if 00 [VGA controller])
  root@ubuntu-G74Sx:/home/ubuntu#

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-compute-utils-390 390.132-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Thu Jan 30 20:59:40 2020
  ErrorMessage: el subproceso instalado paquete nvidia-compute-utils-390 script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.8
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-compute-utils-390 390.132-0ubuntu2 failed to 
install/upgrade: el subproceso instalado paquete nvidia-compute-utils-390 
script post-installation devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to focal on 2020-01-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1861463/+subscriptions

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Pablo Palácios]

I've got the same using archlinux latest kernel with a dell computer, i7
and an pcie network card as well. I've found this thread on redhat
bugzilla very helpful:

https://bugzilla.redhat.com/show_bug.cgi?id=681017

I was able to solve my problem by explicitly disabling aspm in my bios.
>From factory it was set to auto which perhaps could result in "device
has no support for aspm but let's enabled aspm anyway" behavior making
kernel confused.

** Bug watch added: Red Hat Bugzilla #681017
   https://bugzilla.redhat.com/show_bug.cgi?id=681017

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

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  WORKAROUND: add pci=noaer to your kernel command line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: BugDistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent 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.153SourcePackage: 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/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1220146] Re: Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box

[Pablo]

This is not fixed, here, asus X554L, ubuntu 18.04, can't find the
adapter.

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

Title:
  Ralink Mediatek 14c3:7630 wi-fi card isn't supported out of the box

Status in HWE Next:
  Fix Released
Status in HWE Next trusty series:
  Won't Fix
Status in Linux:
  Unknown
Status in vivid:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux package in Fedora:
  New

Bug description:
  This device is appearing in some OEM machines, but driver is not yet
  available in mainline.

  The driver seems to be present in machines with pre-installed OS, but
  isn't available on the download-and-install versions!

  The driver that upstream is working on can be found at
  https://github.com/lwfinger/mt7630.

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

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

[Kernel-packages] [Bug 1277959] Re: [Asus 1015E] Fn+F2 is not working for activating/deactivating wifi

[Pablo Rossy Bernardes Mozinho Ferreira]

I have this problem and I see another computer with this problem too. I
just create a file like this.

pablo@pablo-H14SU08:~$ cat /etc/modprobe.d/rtlwifi.conf 
###Evitar que a tecla Function (Fn) quebre o WIFI
options rtlwifi wapf=4
pablo@pablo-H14SU08:~$ 

lspci

03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE
Wireless Network Adapter (rev 01)

Using Trisquel 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/1277959

Title:
  [Asus 1015E] Fn+F2 is not working for activating/deactivating wifi

Status in linux package in Ubuntu:
  Expired

Bug description:
  Fn+F2 is not working for activating/deactivating wifi.
  Also wifi led is not working (led located on netbook case)
  I have an ASUS 1015E-DS03 netbook with Ubuntu 12.04 LTS.

  Linux ASUS-1015E-DS03 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan
  30 17:24:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  The problem maybe in asus_nb_wmi driver.
  Related to https://bugs.launchpad.net/bugs/1173681.

  description: Wireless interface
 product: AR9485 Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlan0
 version: 01
 serial: 6c:71:d9:7f:70:6b
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list rom ethernet 
physical wireless
 configuration: broadcast=yes driver=ath9k 
driverversion=3.8.0-35-generic firmware=N/A ip=192.168.1.47 latency=0 link=yes 
multicast=yes wireless=IEEE 802.11bgn
 resources: irq:17 memory:f7d0-f7d7 memory:f7d8-f7d8

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.8.0-35-generic 3.8.0-35.52~precise1
  ProcVersionSignature: Ubuntu 3.8.0-35.52~precise1-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-35-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1836 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e1 irq 44'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0269,1043115d,00100100 
HDA:80862806,80860101,0010'
 Controls  : 24
 Simple ctrls  : 9
  Date: Sat Feb  8 17:41:06 2014
  HibernationDevice: RESUME=UUID=046c9b4b-4f3f-45e2-8edf-e79abc412d11
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: ASUSTeK COMPUTER INC. 1015E
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic 
root=UUID=671caa58-b12e-4d13-a74e-a34bd55cff02 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-35-generic N/A
   linux-backports-modules-3.8.0-35-generic  N/A
   linux-firmware1.94
  SourcePackage: linux-lts-raring
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1015E.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 1015E
  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.:bvr1015E.303:bd03/15/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: 1015E
  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/1277959/+subscriptions

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

[Kernel-packages] [Bug 1811788] Re: Thermald 1.8 does not install default config

[Pablo Catalina]

Sorry, thermald works fine without this config file ;)

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

Title:
  Thermald 1.8 does not install default config

Status in thermald package in Ubuntu:
  Invalid

Bug description:
  I created a backport of the 1.8 package for Ubuntu Cosmic. After
  installing it, I noted that it does not install a default config file,
  so it renders and error:

  ene 15 10:29:25 pcatalin-lnx systemd[1]: Started Thermal Daemon Service.
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: 22 CPUID levels; 
family:model:stepping 0x6:9e:a (6:158:10)
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: Polling mode is enabled: 4
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sysfs open failed
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml

  
  I suggest to install a default configuration on /etc/thermald/thermal-conf.xml

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

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

[Kernel-packages] [Bug 1811788] [NEW] Thermald 1.8 does not install default config

[Pablo Catalina]

Public bug reported:

I created a backport of the 1.8 package for Ubuntu Cosmic. After
installing it, I noted that it does not install a default config file,
so it renders and error:

ene 15 10:29:25 pcatalin-lnx systemd[1]: Started Thermal Daemon Service.
ene 15 10:29:25 pcatalin-lnx thermald[22175]: 22 CPUID levels; 
family:model:stepping 0x6:9e:a (6:158:10)
ene 15 10:29:25 pcatalin-lnx thermald[22175]: Polling mode is enabled: 4
ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs for 
reading raw temp
ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs for 
reading raw temp
ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs for 
reading raw temp
ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
ene 15 10:29:25 pcatalin-lnx thermald[22175]: sysfs open failed
ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml


I suggest to install a default configuration on /etc/thermald/thermal-conf.xml

** Affects: thermald (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

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

Title:
  Thermald 1.8 does not install default config

Status in thermald package in Ubuntu:
  Invalid

Bug description:
  I created a backport of the 1.8 package for Ubuntu Cosmic. After
  installing it, I noted that it does not install a default config file,
  so it renders and error:

  ene 15 10:29:25 pcatalin-lnx systemd[1]: Started Thermal Daemon Service.
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: 22 CPUID levels; 
family:model:stepping 0x6:9e:a (6:158:10)
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: Polling mode is enabled: 4
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sensor id 12 : No temp sysfs 
for reading raw temp
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: sysfs open failed
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: I/O warning : failed to load 
external entity "/etc/thermald/thermal-conf.xml"
  ene 15 10:29:25 pcatalin-lnx thermald[22175]: error: could not parse file 
/etc/thermald/thermal-conf.xml

  
  I suggest to install a default configuration on /etc/thermald/thermal-conf.xml

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

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

[Kernel-packages] [Bug 1811730] [NEW] Thermald does not set max CPU after reseting the voltage using RAPL

[Pablo Catalina]

Public bug reported:

Hi,

I was using Ubuntu 18.10 thermald package, but I noted that, after few
seconds at max CPU usage (max temp), thermald send the signal to RALP to
reduce the voltage of the CPU. It set the freq to minimum (800MHz in my
case). But when the CPU is idle and temp is lowered (35-40ºC) it did not
send the signal to resume normal operation of the CPU.

I compiled the latest version of thermald from git
(https://github.com/intel/thermal_daemon) and now everything works fine.

I started to thought that the problem was the hardware or BIOS problem,
as I disabled the CPU scaling on the BIOS, but intel_pstate continued
doing freq scaling (I think for Turbo mode).

But the real problem was Thermald. The latest version from git works
really fine and it automatically disables and enable the Intel Turbo
state and balance the freqs and fan control fine.

My hardware is a Lenovo Thinkpad P52 with i7-8850H.

I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7
processor but with Ubuntu default config (except processor
family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low-
Latency Desktop)" and Timer frequency="1000HZ". (Only changed those
settings from make oldconfig and make deb-pkg).

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: thermald (not installed)
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 14 23:45:01 2019
InstallationDate: Installed on 2018-12-11 (34 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: thermald
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug 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/1811730

Title:
  Thermald does not set max CPU after reseting the voltage using RAPL

Status in thermald package in Ubuntu:
  New

Bug description:
  Hi,

  I was using Ubuntu 18.10 thermald package, but I noted that, after few
  seconds at max CPU usage (max temp), thermald send the signal to RALP
  to reduce the voltage of the CPU. It set the freq to minimum (800MHz
  in my case). But when the CPU is idle and temp is lowered (35-40ºC) it
  did not send the signal to resume normal operation of the CPU.

  I compiled the latest version of thermald from git
  (https://github.com/intel/thermal_daemon) and now everything works
  fine.

  I started to thought that the problem was the hardware or BIOS
  problem, as I disabled the CPU scaling on the BIOS, but intel_pstate
  continued doing freq scaling (I think for Turbo mode).

  But the real problem was Thermald. The latest version from git works
  really fine and it automatically disables and enable the Intel Turbo
  state and balance the freqs and fan control fine.

  My hardware is a Lenovo Thinkpad P52 with i7-8850H.

  I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7
  processor but with Ubuntu default config (except processor
  family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low-
  Latency Desktop)" and Timer frequency="1000HZ". (Only changed those
  settings from make oldconfig and make deb-pkg).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thermald (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 14 23:45:01 2019
  InstallationDate: Installed on 2018-12-11 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL

[Pablo Catalina]

Seems similar (but probably not the same):
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1769236

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

Title:
  Thermald does not set max CPU after reseting the voltage using RAPL

Status in thermald package in Ubuntu:
  New

Bug description:
  Hi,

  I was using Ubuntu 18.10 thermald package, but I noted that, after few
  seconds at max CPU usage (max temp), thermald send the signal to RALP
  to reduce the voltage of the CPU. It set the freq to minimum (800MHz
  in my case). But when the CPU is idle and temp is lowered (35-40ºC) it
  did not send the signal to resume normal operation of the CPU.

  I compiled the latest version of thermald from git
  (https://github.com/intel/thermal_daemon) and now everything works
  fine.

  I started to thought that the problem was the hardware or BIOS
  problem, as I disabled the CPU scaling on the BIOS, but intel_pstate
  continued doing freq scaling (I think for Turbo mode).

  But the real problem was Thermald. The latest version from git works
  really fine and it automatically disables and enable the Intel Turbo
  state and balance the freqs and fan control fine.

  My hardware is a Lenovo Thinkpad P52 with i7-8850H.

  I tested it using Ubuntu kernel and Kernel 4.20 optimized for i7
  processor but with Ubuntu default config (except processor
  family="Core2/newer Xeon", Preemption Model="Preemptible Kernel (Low-
  Latency Desktop)" and Timer frequency="1000HZ". (Only changed those
  settings from make oldconfig and make deb-pkg).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thermald (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 14 23:45:01 2019
  InstallationDate: Installed on 2018-12-11 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: thermald
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value

[Pablo Catalina]

Seems similar to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730

I fixed the problem using the latest version of thermald from git.

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

Title:
  CPU frequency stuck at minimum value

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

Bug description:
  I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13
  laptop.  Performance is poor.  The CPU (an i7-8550U) is running at
  400MHz, and never speeds up, even when running some of the Phoronix
  Test Suite benchmarks.

  I can use cpupower to switch to the "performance" cpufreq governor,
  but cannot change the frequency with either governor.

  Here is the output of some experiments I ran while Phoronix's c-ray test was 
running.
  __

  gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz
  cpu MHz : 400.008
  cpu MHz : 400.002
  cpu MHz : 400.002
  cpu MHz : 400.003
  cpu MHz : 400.005
  cpu MHz : 400.003
  cpu MHz : 400.001
  cpu MHz : 400.004

  gjditchf@copperplate:/var/log$ cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 400 MHz - 4.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 400 MHz and 1.60 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 400 MHz (asserted by call to kernel)
boost state support:
  Supported: yes
  Active: yes

  gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz
  Setting cpu: 0
  Error setting new values. Common errors:
  - Do you have proper administration rights? (super-user?)
  - Is the governor you requested available and modprobed?
  - Trying to set an invalid policy?
  - Trying to set a specific frequency, but userspace governor is not available,
 for example because of hardware which cannot be set to a specific frequency
 or because the userspace governor isn't loaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May  4 12:57:25 2018
  InstallationDate: Installed on 2018-04-28 (6 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gjditchf   1190 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-28 (10 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre Laptop 13-af0xx
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A2
  dmi.board.vendor: HP
  dmi.board.version: 55.24
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre Laptop 

[Kernel-packages] [Bug 1586195] Re: Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

[Pablo Fontoura]

Hi,

I have the same problem.  
I can perfectly use this key on a usb2 port.
The usb3 port is working, i can use pendrive on this port.

The outputs when the key is plugged on usb3 are:

1) dmesg

[40261.131061] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd
[40261.152025] usb 2-1: New USB device found, idVendor=0bda, idProduct=8153
[40261.152035] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[40261.152042] usb 2-1: Product: USB 10/100/1000 LAN
[40261.152048] usb 2-1: Manufacturer: Realtek
[40261.152053] usb 2-1: SerialNumber: 0100
[40261.283522] usb 2-1: reset SuperSpeed USB device number 6 using xhci_hcd
[40261.345831] r8152 2-1:1.0 eth0: v1.09.9
[40261.407779] r8152 2-1:1.0 enx9cebe85eac03: renamed from eth0
[40261.433452] IPv6: ADDRCONF(NETDEV_UP): enx9cebe85eac03: link is not ready
[40261.437807] IPv6: ADDRCONF(NETDEV_UP): enx9cebe85eac03: link is not ready
[40261.471953] usb 2-1: USB disconnect, device number 6
[40261.472042] r8152 2-1:1.0 enx9cebe85eac03: Stop submitting intr, status -108


2) lspci

00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 
08)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 08)
00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP 
Integrated Sensor Hub (rev 21)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network 
Adapter (rev 32)

3) lsb_release -a

LSB Version:
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

4) uname -a

Linux xxx-inspiron 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


5) lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04f3:2494 Elan Microelectronics Corp. 
Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc. 
Bus 001 Device 003: ID 0bda:58c2 Realtek Semiconductor Corp. 
Bus 001 Device 024: ID 045e:0797 Microsoft Corp. Optical Mouse 200
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  Realtek 8153-based ethernet adapter on usb3 eventually stops working
  requiring unplug/replug

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Xenial:
  Expired

Bug description:
  Continued in Bug #1622322.

  Seems to be paired with dmesg entries like this on the trusty kernel:

  [24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
  [24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
  [24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-:00:14.0-4.2, 
RTL8153 ECM Device
  [24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
  [24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
  [24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
  [24763.809953] .
  [24763.810579] usb 4-4.2: USB disconnect, device number 7
  [24763.940765] userif-1: sent link down event.
  [24763.940769] userif-1: sent link up event.

  And like this on mainline:

  [  259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
  [  259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
  [  259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=6
  [  259.752920] usb 4-3: Product: USB 10/100/1000 LAN
  [  259.752921] usb 4-3: Manufacturer: Realtek
  [  259.752922] usb 4-3: SerialNumber: 0100
  [  259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
  [  259.993254] r8152 4-3:1.0 eth0: v1.08.3
  [  260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not 

[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

[Pablo Abrudsky]

I just updated my system (sudo apt dist-upgrade), and still having the issue, 
latest kernel didn't fix it for me.
I am attaching the ``udevadm info -e`` for Dell Inspiron 15 5577, without any 
boot kernel params set.


** Attachment added: "``udevadm info -e`` for Dell Inspiron 15 5577"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+attachment/5197555/+files/dell-inspiron-15-5577-udevadm.info

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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

[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

[Pablo Abrudsky]

Attaching ``udevadm info -e`` for Dell Inspiron 15 5577

** Attachment added: "``udevadm info -e`` for Dell Inspiron 15 5577"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+attachment/5193559/+files/dell-inspiron-15-5577-udevadm.info

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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

[Kernel-packages] [Bug 1790341] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package

[pablo dagos]

Public bug reported:

Preparing to unpack .../89-nvidia-visual-profiler_9.1.85-3ubuntu1_amd64.deb ...
Unpacking nvidia-visual-profiler (9.1.85-3ubuntu1) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-2yadKg/18-libnvidia-compute-390_390.48-0ubuntu3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libnvidia-compute-390 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Sep  1 23:50:57 2018
DuplicateSignature:
 package:libnvidia-compute-390:(not installed)
 Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu3) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-2yadKg/18-libnvidia-compute-390_390.48-0ubuntu3_amd64.deb 
(--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.106-0ubuntu3
ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', 
which is also in package nvidia-340 340.106-0ubuntu3
InstallationDate: Installed on 2018-08-30 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: nvidia-graphics-drivers-390
Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also 
in package nvidia-340 340.106-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  package libnvidia-compute-390 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu
  /libnvidia-ml.so', which is also in package nvidia-340
  340.106-0ubuntu3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Preparing to unpack .../89-nvidia-visual-profiler_9.1.85-3ubuntu1_amd64.deb 
...
  Unpacking nvidia-visual-profiler (9.1.85-3ubuntu1) ...
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-2yadKg/18-libnvidia-compute-390_390.48-0ubuntu3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libnvidia-compute-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Sep  1 23:50:57 2018
  DuplicateSignature:
   package:libnvidia-compute-390:(not installed)
   Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2yadKg/18-libnvidia-compute-390_390.48-0ubuntu3_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-08-30 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-compute-390 (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1790341/+subscriptions

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

[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

[Pablo Abrudsky]

I think I've found a workaround for this issue, in my case adding 'acpi_osi=' 
to the linux kernel parameters solved it. 
I am running a Dell Inspiron 15 5577 (with latest BIOS, v1.1.0).

For a permanent solution, I changed this line at:

```/etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi="

```

and then you have to run:
```
$ sudo update-grub
```

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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

[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

[Pablo Abrudsky]

I am having the same issue, sadly I have a fresh 18.04 install, so I
cannot revert to an older kernel, let me know what I can do to avoid the
issue, or help you find a solution.

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Pablo]

How do you install test kernel?
I tried dpki -i linux-modules-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb 
linux-modules-extra-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb 
linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb

but I get error:

Preparing to unpack 
linux-modules-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb ...
Unpacking linux-modules-4.15.0-24-generic (4.15.0-24.26+crng4) over 
(4.15.0-24.26+crng4) ...
Preparing to unpack 
linux-modules-extra-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb ...
Unpacking linux-modules-extra-4.15.0-24-generic (4.15.0-24.26+crng4) over 
(4.15.0-24.26+crng4) ...
dpkg: regarding 
linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb containing 
linux-image-unsigned-4.15.0-24-generic:
 linux-image-unsigned-4.15.0-24-generic conflicts with 
linux-image-4.15.0-24-generic
  linux-image-4.15.0-24-generic (version 4.15.0-24.26) is present and installed.

dpkg: error processing archive 
linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb (--install):
 conflicting packages - not installing linux-image-unsigned-4.15.0-24-generic
Setting up linux-modules-4.15.0-24-generic (4.15.0-24.26+crng4) ...
Setting up linux-modules-extra-4.15.0-24-generic (4.15.0-24.26+crng4) ...
Processing triggers for linux-image-4.15.0-24-generic (4.15.0-24.26) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
Found linux image: /boot/vmlinuz-4.15.0-24-generic
Found initrd image: /boot/initrd.img-4.15.0-24-generic
Found linux image: /boot/vmlinuz-4.15.0-23-generic
Found initrd image: /boot/initrd.img-4.15.0-23-generic
Found linux image: /boot/vmlinuz-4.15.0-22-generic
Found initrd image: /boot/initrd.img-4.15.0-22-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
done
Errors were encountered while processing:
 linux-image-unsigned-4.15.0-24-generic_4.15.0-24.26+crng4_amd64.deb


Or how do I revert to previous working kernel (I don't have grub installed... 
long story).

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in The Bionic Beaver:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Pablo]

Same problem with Dell Precision M3800 with Ubunto 18.04
Updated yesterday July 3, when I booted today, July 4, boot process gets stuck
Last few lines of /var/log/boot.log:

[^[[0;32m  OK  ^[[0m] Reached target Network.
 Starting Permit User Sessions...
[^[[0;32m  OK  ^[[0m] Started Unattended Upgrades Shutdown.
 Starting OpenBSD Secure Shell server...
 Starting Network Manager Wait Online...
[^[[0;32m  OK  ^[[0m] Started Permit User Sessions.
 Starting GNOME Display Manager...
 Starting Hold until boot process finishes up...
 Starting Network Manager Script Dispatcher Service...
[^[[0;32m  OK  ^[[0m] Started Network Manager Script Dispatcher Service.
[^[[0;32m  OK  ^[[0m] Started GNOME Display Manager.
[^[[0;32m  OK  ^[[0m] Started OpenBSD Secure Shell server.

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

Title:
  failure to boot with linux-image-4.15.0-24-generic

Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in The Bionic Beaver:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  This was the last OK then my 18.04 hangs after an update this morning.
  07:00 AM CEST

  Last Ok in boot was Started gnome display manager. dispatcher service
  .. tem changes.pp link was shut down

  Tried install lightdm from command line and the  response was lastest
  already installed.

  Probably it is what is coming after the lastest OK which is to be the
  error. And here I have lots of guesses..

  Any Ideas ? I need to do some work and I may not be waiting long.

  Search and browsed and now close to give up. Yeah it is a Lenovo.

  Guys: turn of auto update it is a machine killer.

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

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

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

Marked as invalid, since it's not about the touchpad in ubuntu 17.10. Anyway, 
for the record, I meant the problems go as follows:
- everything works fine with nvida + propietary driver + acpi=on
- gnome+xorg freezes after login if intel gpu + acpi=on
- gnome+wayland works, but has many issues probably reported elsewhere...
- gnome+xorg works if intel gpu + acpi=off, but has the hardware issues I write 
in #23 (touchpad, battery ... )
Sorry for bothering, I didn't realize the acpi=off option made it to grub after 
installation of 17.10, so I was confused about the cause.

** Information type changed from Public to Private Security

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Invalid

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Invalid

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

Found the culprit: it's the Intel GPU.

If I use Intel IGP, the situation is as I described. If I use the nvidia
graphics card, everything works fine with gnome+org, acpi=on.

I've read that support on the IGP for i7-7700HQ on linux is still
ongoing work, so I guess I'll have to wait before I can use it, or do
without touchpad, suspend, etc.

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

It's all about ACPI.

I've tried several kernels from 4.10 to 4.13, and the following is true
for all of them:

- gnome+xorg freezes after login if acpi=on
- gnome+wayland works if acpi=on, but has many issues which make it unusable 
(for example, I cannot open synaptic or any other gksudo application)
- gnome+xorg works if acpi=on, but:
* touchpad does not work
* battery indicators does not work
* acpi -V says "No support for device type: power_supply"
* suspend does not work
* hibernate works only some of the time
* shutdown is not clean: it leaves the computer on, and a single press of 
the power button is required to complete the shutdown

So I don't know, how do I report this?

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

[Kernel-packages] [Bug 1693842] Re: USB 3.0 Disk Drive Not Recognized.

[Pablo]

Hi again,

I forgot to comment that this issue also appear in Debian 9 (my other
PC)...

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

Title:
  USB 3.0 Disk Drive Not Recognized.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  WD My Passport 2T USB 3.0 Disk Drive.
  External Plugable 7 port USB 3.0 hub.

  When I connect the WD drive to the external USB 3.0 hub it is not recognized.
  The drive led blinks one time and it is not in dmesg or in the output of 
lsusb.

  > sudo lsusb -v causes the drive led to blink several times and it is
  recognized.

  With Autosuspend good for this device, long access applications like dump 
fail.
  After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes 
and then dump asks for operator intervention.  Looking at dmesg the drive 
(initially sdf) was disconnected and reconnected as sdg.

    Bad  Autosuspend for USB device xHCI Host Controller [usb6]

  seems to correct this behavior but not the initial connection problem.

  Some discussion and testing in bug 1242321.

  If I connect the drive to a USB 3.0 port on the motherboard, it is
  recognized.

  There is no problem with an Plugable 7-port USB 2.0 hub.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-78-generic 4.4.0-78.99
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tomdean3698 F pulseaudio
   /dev/snd/controlC0:  tomdean3698 F pulseaudio
  Date: Fri May 26 09:05:20 2017
  HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a
  InstallationDate: Installed on 2016-05-15 (375 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=47d8903b-afb2-4432-bc92-b1f4e30209ef ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-78-generic N/A
   linux-backports-modules-4.4.0-78-generic  N/A
   linux-firmware1.157.8
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4801:bd07/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1693842] Re: USB 3.0 Disk Drive Not Recognized.

[Pablo]

Hi,

I have a USB 3.0 Disk 2TB (WD Elements).

When I plug in a 2.0 USB Port the disk is recognized, but when I plug in
a 3.0 USB Port the disk is not recognized and the dmesg not show
anything.

This is the exit of command "sudo lsusb":

Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 062a:4101 Creative Labs Wireless Keyboard/Mouse
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This is the exit of command "lsusb -v -d 1d6b:0003":

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.00
  bDeviceClass9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 3 
  bMaxPacketSize0 9
  idVendor   0x1d6b Linux Foundation
  idProduct  0x0003 3.0 root hub
  bcdDevice4.04
  iManufacturer   3 Linux 4.4.0-103-generic xhci-hcd
  iProduct2 xHCI Host Controller
  iSerial 1 :00:14.0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   31
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xe0
  Self Powered
  Remote Wakeup
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 9 Hub
  bInterfaceSubClass  0 Unused
  bInterfaceProtocol  0 Full speed (or root) hub
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0004  1x 4 bytes
bInterval  12
bMaxBurst   0
Hub Descriptor:
  bLength  12
  bDescriptorType  42
  nNbrPorts 2
  wHubCharacteristic 0x000a
No power switching (usb 1.0)
Per-port overcurrent protection
  bPwrOn2PwrGood   10 * 2 milli seconds
  bHubContrCurrent  0 milli Ampere
  bHubDecLat  0.0 micro seconds
  wHubDelay 0 nano seconds
  DeviceRemovable0x00
 Hub Port Status:
   Port 1: .02a0 5Gbps power Rx.Detect
   Port 2: .02a0 5Gbps power Rx.Detect
Binary Object Store Descriptor:
  bLength 5
  bDescriptorType15
  wTotalLength   15
  bNumDeviceCaps  1
  SuperSpeed USB Device Capability:
bLength10
bDescriptorType16
bDevCapabilityType  3
bmAttributes 0x02
  Latency Tolerance Messages (LTM) Supported
wSpeedsSupported   0x0008
  Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport   3
  Lowest fully-functional device speed is SuperSpeed (5Gbps)
bU1DevExitLat  10 micro seconds
bU2DevExitLat 512 micro seconds
Device Status: 0x0001
  Self Powered

This is the exit of command "uname -a":

Linux WorkStation 4.4.0-103-generic #126-Ubuntu SMP Mon Dec 4 16:23:28
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

This is the exit of command "cat /etc/os-release":

NAME="Ubuntu"
VERSION="16.04.3 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.3 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

I don't understand what's the problem...

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

Title:
  USB 3.0 Disk Drive Not Recognized.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  WD My Passport 2T USB 3.0 Disk Drive.
  External Plugable 7 port USB 3.0 hub.

  When I connect the WD drive to the external USB 3.0 hub it is not recognized.
  The drive led blinks one time and it is not in dmesg or in the output of 
lsusb.

  > sudo lsusb -v causes the drive led to blink several times and it is
  recognized.

  With Autosuspend good for this device, long access applications like dump 
fail.
  After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes 
and then dump asks for operator intervention.  Looking at dmesg the drive 
(initially sdf) was disconnected and reconnected as sdg.

    Bad  Autosuspend for USB device xHCI Host 

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

I just went through the info from apport: wow, do you really collect and
publish in the open that much info? It doesn't have passwords, but it
potentially has emails, paths, wireless networks IDs, attack vectors
etc. And it's irrevertible, I cannot hide that data from the internet
bots now. I think that's illegal in Europe, isn't it? You should at
least change the text of the ubuntu bot, something like: "the
information you provide might contain this and that info and will be
published to anyone and for ever, by running the command you accept
these terms, blah blah", but I think it's better to actually display
that message when running 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/1738560

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

However, if I run xinput list within 17.10 I get:

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ USB Optical Mouse id=7[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=8[slave  keyboard (3)]


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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

Installed apport, run apport-collect 1738560, changed status to
Confirmed.

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

I booted with a 16.10 usb disk, the touchpad works, the output of
xinput.list is:

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPadid=13   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Power Button  id=9[slave  keyboard (3)]
↳ Sleep Button  id=10   [slave  keyboard (3)]
↳ BisonCam, NB Pro  id=11   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=12   [slave  keyboard (3)]
↳ MSI WMI hotkeys   id=14   [slave  keyboard (3)]

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1738560/+attachment/5023493/+files/JournalErrors.txt

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1738560/+attachment/5023497/+files/ProcCpuinfoMinimal.txt

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

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

[Pablo Angulo]

apport information

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GP62M 7RD
  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/1738560/+subscriptions

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

[Kernel-packages] [Bug 1738560] Re: touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

apport information

** Tags added: apport-collected

** Description changed:

  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!
  
  Ubuntu 4.13.0-19.22-generic 4.13.13
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.6
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  pang   1303 F pulseaudio
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.10
+ HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
+ InstallationDate: Installed on 2017-12-16 (0 days ago)
+ InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
+ MachineType: Micro-Star International Co., Ltd. GP62M 7RD
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=es_ES.UTF-8
+  SHELL=/usr/bin/fish
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-19-generic N/A
+  linux-backports-modules-4.13.0-19-generic  N/A
+  linux-firmware 1.169.1
+ Tags:  artful
+ Uname: Linux 4.13.0-19-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 11/07/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: E16J9IMS.307
+ dmi.board.asset.tag: Default string
+ dmi.board.name: MS-16J9
+ 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.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP62M7RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
+ dmi.product.family: G
+ dmi.product.name: GP62M 7RD
+ dmi.product.version: REV:1.0
+ dmi.sys.vendor: Micro-Star International Co., Ltd.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1738560/+attachment/5023489/+files/AlsaInfo.txt

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pang   1303 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=65b6255b-4c34-4e30-9d05-593c937799df
  InstallationDate: Installed on 2017-12-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Micro-Star International Co., Ltd. GP62M 7RD
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=8017d51e-7307-4274-abbf-58a8ae17a3f8 ro acpi=off quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-19-generic N/A
   linux-backports-modules-4.13.0-19-generic  N/A
   linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.307
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  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: 

[Kernel-packages] [Bug 1738560] [NEW] touch pad stopped working after upgrade to artful 17.10

[Pablo Angulo]

Public bug reported:

The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

Ubuntu 4.13.0-19.22-generic 4.13.13

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


** Tags: artful

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

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

Title:
  touch pad stopped working after upgrade to artful 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touch pad worked fine on 16.10 and 17.04, but it stopped working after 
upgrade to artful 17.10.
  It doesn't appear with xinput list, and I cannot find any line in dmesg 
referring to the touchpad ... so I need help even to report the exact device id!

  Ubuntu 4.13.0-19.22-generic 4.13.13

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

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

[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

[Pablo Fontoura]

I got the same problem, but if disable splash on /etc/default/grub the
problem are solved.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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

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

[Kernel-packages] [Bug 1727154] [NEW] general protection fault: 0000 [#2] SMP

[Pablo Ivan Correa Loyola]

Public bug reported:

general protection fault:  [#2] SMP

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm 968 F pulseaudio
  pablo  1325 F pulseaudio
Date: Tue Oct 24 21:58:02 2017
Failure: oops
HibernationDevice: RESUME=UUID=fd80bb90-3239-4ef7-bb92-c5d84d63872d
InstallationDate: Installed on 2017-10-21 (4 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard HP ProBook 4530s
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=38f0f164-58d4-4d53-aa76-997d3a13f000 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: general protection fault:  [#2] SMP
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SRR Ver. F.09
dmi.board.name: 167C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 22.1A
dmi.chassis.asset.tag: CNU12301M3
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP ProBook 4530s
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops artful kernel-driver-i915 kernel-oops

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

Title:
  general protection fault:  [#2] SMP

Status in linux package in Ubuntu:
  New

Bug description:
  general protection fault:  [#2] SMP

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm 968 F pulseaudio
    pablo  1325 F pulseaudio
  Date: Tue Oct 24 21:58:02 2017
  Failure: oops
  HibernationDevice: RESUME=UUID=fd80bb90-3239-4ef7-bb92-c5d84d63872d
  InstallationDate: Installed on 2017-10-21 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP ProBook 4530s
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=38f0f164-58d4-4d53-aa76-997d3a13f000 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: general protection fault:  [#2] SMP
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SRR Ver. F.09
  dmi.board.name: 167C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 22.1A
  dmi.chassis.asset.tag: CNU12301M3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SRRVer.F.09:bd05/13/2011:svnHewlett-Packard:pnHPProBook4530s:pvrA0001D02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4530s
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1726259] [NEW] PMD 120dc8067

[Pablo Letona]

Public bug reported:

Delayed start. when starting, the pointer does not work and the screen
freezes.

ProblemType: KernelOops
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Sun Oct 22 23:42:06 2017
Failure: oops
InstallationDate: Installed on 2017-10-16 (7 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=51376ac7-4398-4e0c-9a49-50023cdb9b03 ro recovery nomodeset
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: PMD 120dc8067
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.0A
dmi.board.name: 30EA
dmi.board.vendor: Quanta
dmi.board.version: 86.09
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-kerneloops artful kernel-driver-nouveau kernel-oops

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

Title:
  PMD 120dc8067

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Delayed start. when starting, the pointer does not work and the screen
  freezes.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Oct 22 23:42:06 2017
  Failure: oops
  InstallationDate: Installed on 2017-10-16 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=51376ac7-4398-4e0c-9a49-50023cdb9b03 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: PMD 120dc8067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1704177] [NEW] Flood on syslog

[Pablo Rodríguez]

Public bug reported:

Flood with messages like this:

xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 8 with no TDs
queued?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-83-generic 4.4.0-83.106
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-83-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Date: Thu Jul 13 18:27:50 2017
HibernationDevice: RESUME=UUID=e0eca0c3-f13a-4513-abc6-62782fcb58a5
InstallationDate: Installed on 2017-05-30 (43 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
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 04e6:5116 SCM Microsystems, Inc. SCR331-LC1 / SCR3310 
SmartCard Reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GIGABYTE GB-BACE-3150
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed 
root=UUID=f47774e8-2041-4a23-88a2-49a3c28f345d ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-83-generic N/A
 linux-backports-modules-4.4.0-83-generic  N/A
 linux-firmware1.157.11
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MZBSWBP-00
dmi.board.vendor: GIGABYTE
dmi.board.version: 1.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd03/23/2016:svnGIGABYTE:pnGB-BACE-3150:pvr1.x:rvnGIGABYTE:rnMZBSWBP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: GB-BACE-3150
dmi.product.version: 1.x
dmi.sys.vendor: GIGABYTE

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


** Tags: amd64 apport-bug xenial

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

Title:
  Flood on syslog

Status in linux package in Ubuntu:
  New

Bug description:
  Flood with messages like this:

  xhci_hcd :00:14.0: WARN Event TRB for slot 1 ep 8 with no TDs
  queued?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-83-generic 4.4.0-83.106
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-83-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  Date: Thu Jul 13 18:27:50 2017
  HibernationDevice: RESUME=UUID=e0eca0c3-f13a-4513-abc6-62782fcb58a5
  InstallationDate: Installed on 2017-05-30 (43 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  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 04e6:5116 SCM Microsystems, Inc. SCR331-LC1 / SCR3310 
SmartCard Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE GB-BACE-3150
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed 

Re: [Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

[Pablo Saavedra]

Thanks, I'll look into it then

On Sun, Aug 7, 2016 at 3:35 PM Gery  wrote:

> Exactly the ones you linked in #17. Not sure why it didn't work for you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1572659
>
> Title:
>   bcmwl driver does not work with kernel 4.4.0-21 when secure boot
>   enabled
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1572659/+subscriptions
>

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

[Pablo Saavedra]

Gery, can you share the steps you took yo sign it?

Thanks

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

[Pablo Saavedra]

BTW, I am having the issue in 14.04, after upgrading to kernel
3.19.0-65-generic. Booting with 3.19.0-64-generic and reinstalling
bcmwl-kernel-source fixes the problem.

I think we need proper instructions to sign the module, or an automated
step that takes care of that for us.

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

[Pablo Saavedra]

I tried to solve it by following the instructions in
http://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-
upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur (with 'wl' as the
module) with no luck

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1341256] Re: Press caps lock on bluetooth keyboard then the keyboard go death

[Juan Pablo Villa Russell]

It's been more than a year but is there any news on this? Same problem
with:

Microsoft Sculpt Mobile Keyboard

The only line that I got from dmesg after turning the keyboard off and on again 
is:
unknown main item tag 0x0


Also, the bluetooth keyboard stops responding when pressing caps lock in the 
Bluetooth Keyboard or on a usb keyboard

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

Title:
  Press caps lock on bluetooth keyboard then the keyboard go death

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I am typing using the Apple wireless keyboard,When I press 'caps lock',the 
keyboard don't work any more!
  So I go use keyboard on the Macbook.The key case have change,but the light on 
the key do not light on.
  I have to off the bluetooth then make it on again.Then reconnect the wireless 
keyboard.
  Yes,It work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13
  ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 13 17:12:23 2014
  InstallationDate: Installed on 2014-03-08 (126 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140307)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Apple Inc. MacBookPro9,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic.efi.signed 
root=UUID=6510f595-2f49-4798-953a-ed186346c60d ro irqpoll
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D3.B08.1208081132
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-4B7AC7E43945597E
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-4B7AC7E43945597E
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
  dmi.product.name: MacBookPro9,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 7C:D1:C3:79:A7:25  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:119665 acl:5720 sco:0 events:2443 errors:0
TX bytes:13420 acl:640 sco:0 commands:718 errors:0

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

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

[Kernel-packages] [Bug 1525598] Re: aMule unable to connect to kad 3.13.0-71

[Pablo Merighi]

Bios updated but the issue is still there
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
P2.10
04/21/2010


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

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1525598] Re: aMule unable to connect to kad 3.13.0-71

[Pablo Merighi]

Yes Joseph,
 booting with 3.13.0-68-generic
aMule Kad connections are working Ok

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1525598] Re: aMule unable to connect to kad 3.13.0-71

[Pablo Merighi]

Yes Joseph,
 booting with 3.13.0-68-generic
aMule Kad connections are working Ok

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Pablo Merighi]

apport information

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

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1525598] Re: aMule unable to connect to kad 3.13.0-71

[Pablo Merighi]

apport information

** Tags added: apport-collected

** Description changed:

  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.19
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  pablo  3879 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
+ InstallationDate: Installed on 2014-03-25 (627 days ago)
+ InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
+ Lsusb:
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ NonfreeKernelModules: nvidia
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
+ ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-71-generic N/A
+  linux-backports-modules-3.13.0-71-generic  N/A
+  linux-firmware 1.127.19
+ RfKill:
+  
+ Tags:  trusty
+ Uname: Linux 3.13.0-71-generic x86_64
+ UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
+ _MarkForUpload: True
+ dmi.bios.date: 09/21/2009
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P1.60
+ dmi.board.name: N68-S
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1525598/+attachment/4533924/+files/AlsaInfo.txt

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O

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

[Pablo Merighi]

apport information

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

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Pablo Merighi]

apport information

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

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Pablo Merighi]

apport information

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

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

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

[Pablo Merighi]

apport information

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

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1525598] Re: aMule unable to connect to kad 3.13.0-71

[Pablo Merighi]

unable to run this command,
apport-collect 1525598

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

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

Title:
  aMule unable to connect to kad 3.13.0-71

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last kernel update: linux-image-3.13.0-71-generic   makes aMule unable to 
connect to kad
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  ---
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pablo  3879 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=673493a7-7052-4e00-a80f-affd1c8e3dfd
  InstallationDate: Installed on 2014-03-25 (627 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=ad896b46-db41-4c74-8757-5ff79df631f5 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-71-generic N/A
   linux-backports-modules-3.13.0-71-generic  N/A
   linux-firmware 1.127.19
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-71-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (570 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: N68-S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/21/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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