[Kernel-packages] [Bug 2049993] Re: tcp has MSS=1460, but a segment with PUSH flag is overshooting maximum segment size

[Bernhard Riegler]

after turning OFF all HW features of the LANIC.
only CRC calculation remains in the LANIC.

I have not seen the effect in wireshark again.
I assume the LANIC was adding TCP segments together.

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

Title:
  tcp has MSS=1460, but a segment with PUSH flag is overshooting maximum
  segment size

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  a wireshark trace will follow.
  filter for "ip.len>1500" in the wireshark trace

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 21 08:41:18 2024
  Dependencies:
   
  InstallationDate: Installed on 2022-05-31 (599 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049993] Re: tcp has MSS=1460, but a segment with PUSH flag is overshooting maximum segment size

[Bernhard Riegler]

I monitor with wireshark and it can be any TCP payload.

the common TCP header part is flag PUSH is ON.
It happens in both directions.

** Summary changed:

- tcp has MSS=1460, but TLSv1.3 payload is overshooting maximum segment size
+ tcp has MSS=1460, but a segment with PUSH flag is overshooting maximum 
segment size

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

Title:
  tcp has MSS=1460, but a segment with PUSH flag is overshooting maximum
  segment size

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  a wireshark trace will follow.
  filter for "ip.len>1500" in the wireshark trace

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 21 08:41:18 2024
  Dependencies:
   
  InstallationDate: Installed on 2022-05-31 (599 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049993] Re: tcp has MSS=1460, but TLSv1.3 payload is overshooting maximum segment size

[Bernhard Riegler]

I have a stateless firewall (nft) which drops ip.len>1500 input ethernet frames.
therefore you see TCP flow control with resend data.

filter the wireshark trace with "ip.len>1500"
all the input ethernet frames (destination ipv4 10.0.0.2) seen in wireshark 
trace
are dropped in nft filter hook ingress.

filter the tcp connection.

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

Title:
  tcp has MSS=1460, but TLSv1.3 payload is overshooting maximum segment
  size

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  a wireshark trace will follow.
  filter for "ip.len>1500" in the wireshark trace

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 21 08:41:18 2024
  Dependencies:
   
  InstallationDate: Installed on 2022-05-31 (599 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049993] [NEW] tcp has MSS=1460, but TLSv1.3 payload is overshooting maximum segment size

[Bernhard Riegler]

Public bug reported:

a wireshark trace will follow.
filter for "ip.len>1500" in the wireshark trace

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-modules-6.5.0-14-generic 6.5.0-14.14~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 21 08:41:18 2024
Dependencies:
 
InstallationDate: Installed on 2022-05-31 (599 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: linux-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  tcp has MSS=1460, but TLSv1.3 payload is overshooting maximum segment
  size

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  a wireshark trace will follow.
  filter for "ip.len>1500" in the wireshark trace

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 21 08:41:18 2024
  Dependencies:
   
  InstallationDate: Installed on 2022-05-31 (599 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2049993] Re: tcp has MSS=1460, but TLSv1.3 payload is overshooting maximum segment size

[Bernhard Riegler]

** Attachment added: "snapcraft_tcp_over_MSS.pcapng"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2049993/+attachment/5741126/+files/snapcraft_tcp_over_MSS.pcapng

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

Title:
  tcp has MSS=1460, but TLSv1.3 payload is overshooting maximum segment
  size

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  a wireshark trace will follow.
  filter for "ip.len>1500" in the wireshark trace

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-modules-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 21 08:41:18 2024
  Dependencies:
   
  InstallationDate: Installed on 2022-05-31 (599 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-hwe-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2028662] Re: kernel boot time changed from 4 sec to 14 sec

[Bernhard Riegler]

"freeing initrd memory" pointed me in the right direction.

I have modified /etc/initramfs-tools/initramfs.conf short time before.
changed "COMPRESS=bzip2" and got a smaller file in the file-system

moved back to "COMPRESS=zstd" , update-initramfs -u and got the original 
filesize.
after reboot the effect with 10 sec delay was gone.

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

Title:
  kernel boot time changed from 4 sec to 14 sec

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

Bug description:
  root@prod:/home/bernie22/fw# journalctl -b |grep finished
  Jul 25 09:56:31 prod systemd[1]: Startup finished in 14.256s (kernel) + 
3.272s (userspace) = 17.529s.
  Jul 25 09:56:33 prod systemd[867]: Startup finished in 1.485s.
  Jul 25 09:56:50 prod systemd[1222]: Startup finished in 4.712s.

  I am talking about 14.256s (kernel), it was 4 second before fix level
  50

  journalctl -b -o short-monotonic
  ...
  [0.451483] prod kernel: Key type asymmetric registered
  [0.451488] prod kernel: Asymmetric key parser 'x509' registered
  [1.478283] prod kernel: tsc: Refined TSC clocksource calibration: 
2594.107 MHz
  [1.478295] prod kernel: clocksource: tsc: mask: 0x 
max_cycles: 0x25647d583cf, max_idle_ns: 440795304232 ns
  [1.478322] prod kernel: clocksource: Switched to clocksource tsc
  [   12.118386] prod kernel: Freeing initrd memory: 66872K
  [   12.122081] prod kernel: alg: self-tests for CTR-KDF (hmac(sha256)) passed
  [   12.122120] prod kernel: Block layer SCSI generic (bsg) driver version 0.4 
loaded (major 243)
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-50-generic 5.19.0-50.50
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 25 11:49:04 2023
  InstallationDate: Installed on 2022-05-31 (420 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-5.19
  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.19/+bug/2028662/+subscriptions


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

[Kernel-packages] [Bug 2028662] [NEW] kernel boot time changed from 4 sec to 14 sec

[Bernhard Riegler]

Public bug reported:

root@prod:/home/bernie22/fw# journalctl -b |grep finished
Jul 25 09:56:31 prod systemd[1]: Startup finished in 14.256s (kernel) + 3.272s 
(userspace) = 17.529s.
Jul 25 09:56:33 prod systemd[867]: Startup finished in 1.485s.
Jul 25 09:56:50 prod systemd[1222]: Startup finished in 4.712s.

I am talking about 14.256s (kernel), it was 4 second before fix level 50

journalctl -b -o short-monotonic
...
[0.451483] prod kernel: Key type asymmetric registered
[0.451488] prod kernel: Asymmetric key parser 'x509' registered
[1.478283] prod kernel: tsc: Refined TSC clocksource calibration: 2594.107 
MHz
[1.478295] prod kernel: clocksource: tsc: mask: 0x 
max_cycles: 0x25647d583cf, max_idle_ns: 440795304232 ns
[1.478322] prod kernel: clocksource: Switched to clocksource tsc
[   12.118386] prod kernel: Freeing initrd memory: 66872K
[   12.122081] prod kernel: alg: self-tests for CTR-KDF (hmac(sha256)) passed
[   12.122120] prod kernel: Block layer SCSI generic (bsg) driver version 0.4 
loaded (major 243)
...

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-50-generic 5.19.0-50.50
ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
Uname: Linux 5.19.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 25 11:49:04 2023
InstallationDate: Installed on 2022-05-31 (420 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: linux-signed-hwe-5.19
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  kernel boot time changed from 4 sec to 14 sec

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

Bug description:
  root@prod:/home/bernie22/fw# journalctl -b |grep finished
  Jul 25 09:56:31 prod systemd[1]: Startup finished in 14.256s (kernel) + 
3.272s (userspace) = 17.529s.
  Jul 25 09:56:33 prod systemd[867]: Startup finished in 1.485s.
  Jul 25 09:56:50 prod systemd[1222]: Startup finished in 4.712s.

  I am talking about 14.256s (kernel), it was 4 second before fix level
  50

  journalctl -b -o short-monotonic
  ...
  [0.451483] prod kernel: Key type asymmetric registered
  [0.451488] prod kernel: Asymmetric key parser 'x509' registered
  [1.478283] prod kernel: tsc: Refined TSC clocksource calibration: 
2594.107 MHz
  [1.478295] prod kernel: clocksource: tsc: mask: 0x 
max_cycles: 0x25647d583cf, max_idle_ns: 440795304232 ns
  [1.478322] prod kernel: clocksource: Switched to clocksource tsc
  [   12.118386] prod kernel: Freeing initrd memory: 66872K
  [   12.122081] prod kernel: alg: self-tests for CTR-KDF (hmac(sha256)) passed
  [   12.122120] prod kernel: Block layer SCSI generic (bsg) driver version 0.4 
loaded (major 243)
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-50-generic 5.19.0-50.50
  ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17
  Uname: Linux 5.19.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 25 11:49:04 2023
  InstallationDate: Installed on 2022-05-31 (420 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-5.19
  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.19/+bug/2028662/+subscriptions


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

[Kernel-packages] [Bug 2021563] acpidump.txt

[Bernhard Riegler]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676623/+files/acpidump.txt

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

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

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: 

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

[Bernhard Riegler]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676620/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 

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

[Bernhard Riegler]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676622/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 

[Kernel-packages] [Bug 2021563] ProcInterrupts.txt

[Bernhard Riegler]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676619/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  

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

[Bernhard Riegler]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2021563/+attachment/5676621/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb

[Kernel-packages] [Bug 2021563] ProcCpuinfo.txt

[Bernhard Riegler]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676616/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 

[Kernel-packages] [Bug 2021563] ProcCpuinfoMinimal.txt

[Bernhard Riegler]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676617/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not 

[Kernel-packages] [Bug 2021563] ProcEnviron.txt

[Bernhard Riegler]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676618/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 

[Kernel-packages] [Bug 2021563] PaInfo.txt

[Bernhard Riegler]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2021563/+attachment/5676615/+files/PaInfo.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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb

[Kernel-packages] [Bug 2021563] Lsusb-v.txt

[Bernhard Riegler]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676614/+files/Lsusb-v.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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 

[Kernel-packages] [Bug 2021563] Lsusb-t.txt

[Bernhard Riegler]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676613/+files/Lsusb-t.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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 

[Kernel-packages] [Bug 2021563] Lsusb.txt

[Bernhard Riegler]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2021563/+attachment/5676612/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  

[Kernel-packages] [Bug 2021563] Lspci-vt.txt

[Bernhard Riegler]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676611/+files/Lspci-vt.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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 

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

[Bernhard Riegler]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2021563/+attachment/5676610/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  

[Kernel-packages] [Bug 2021563] CurrentDmesg.txt

[Bernhard Riegler]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676608/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  

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

[Bernhard Riegler]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/2021563/+attachment/5676609/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 

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

[Bernhard Riegler]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/2021563/+attachment/5676607/+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/2021563

Title:
  Unknown kernel command line parameters

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1469 F wireplumber
   /dev/snd/seq:bernie 1464 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (364 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  

[Kernel-packages] [Bug 2021563] Re: Unknown kernel command line parameters

[Bernhard Riegler]

apport information

** Tags added: apport-collected

** Description changed:

  oot@prod:/home/bernie22# journalctl -b |grep lockdown
  Mai 30 08:25:44 prod kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Kernel is locked down from command line; see man 
kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
  Mai 30 08:25:44 prod kernel: Unknown kernel command line parameters 
"security_lockdown_lsm_early noplymouth 
BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic", will be passed to user space.
  Mai 30 08:25:44 prod kernel: Lockdown: swapper: use of tracefs is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer wakeup due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer function_graph due to 
lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Tracing disabled due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer mmiotrace due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer blk due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: use of tracefs is 
restricted; see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: Can not register tracer hwlat due to lockdown
  Mai 30 08:25:44 prod kernel: Lockdown: swapper/0: hibernation is restricted; 
see man kernel_lockdown.7
  Mai 30 08:25:44 prod kernel: security_lockdown_lsm_early
  Mai 30 08:25:50 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:09 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  Mai 30 08:26:13 prod kernel: Lockdown: fwupd: /dev/mem,kmem,port is 
restricted; see man kernel_lockdown.7
  Mai 30 08:27:44 prod kernel: Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  ro
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  bernie 1469 F wireplumber
+  /dev/snd/seq:bernie 1464 F pipewire
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-05-31 (364 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
+ MachineType: Hewlett-Packard HP EliteBook 8560p
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro security_lockdown_lsm_early 
lockdown=confidentiality ro quiet noplymouth ipv6.disable=1 
initcall_blacklist=serial8250_init
+ ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
+ PulseList: Error: command 

[Kernel-packages] [Bug 2009271] Re: Too many BDL entries regression

[Bernhard Riegler]

Hi all,

I am using Ubuntu 22.04LTS with kernel 5.19.0-41 and have this at bootup
journalctl:[8.778039] prod kernel: snd_hda_intel :00:1b.0: Too many BDL 
entries: buffer=2097152, period=65536
journalctl:[   19.134032] prod kernel: snd_hda_intel :00:1b.0: Too many BDL 
entries: buffer=2097152, period=65536

the HW is Intel High_Definition_Audio in the Intel chip-set.

As already mentioned above , fix this for LTS 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/2009271

Title:
  Too many BDL entries regression

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  Hello,

  Thanks for your hard work :)
  I got this error after kernel update to 5.19.0-35 as explained here :
  
https://askubuntu.com/questions/1457367/snd-hda-intel-001f-3-too-many-bdl-entries-messages-in-system-log
  and here :
  
https://lore.kernel.org/stable/cab1lbmv1ky+kuubwvxroe+mbqbjtjofvzb8smmbcuy2mdvg...@mail.gmail.com/T/#u

  A load of syslog "Too many BDL entries" appears.

  Have a nice week-end, best regards,
  Laurent Lyaudet

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  laurent5004 F wireplumber
   /dev/snd/controlC1:  laurent5004 F wireplumber
   /dev/snd/seq:laurent5000 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  4 16:47:55 2023
  InstallationDate: Installed on 2020-07-01 (976 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GL73 8SD
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (134 days ago)
  dmi.bios.date: 03/29/2019
  dmi.bios.release: 1.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C7IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C7
  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.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1:
  dmi.product.family: GL
  dmi.product.name: GL73 8SD
  dmi.product.sku: 17C7.1
  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/2009271/+subscriptions


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

[Kernel-packages] [Bug 1980590] Re: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress

[Bernhard Riegler]

looked into the source code of the kernel
there is include/uapi/linux/if_ether.h
inside are defines ETH_P_*
this brings me to the general question for nftables

how to build "ethernet level" firewall controlling all possible "ether
type" at hook "ingress" ?

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

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

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

[Bernhard Riegler]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605731/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] CurrentDmesg.txt

[Bernhard Riegler]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605730/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

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

[Bernhard Riegler]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1980590/+attachment/5605732/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

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

[Bernhard Riegler]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605742/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] Re: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress

[Bernhard Riegler]

and here is the catch of today


** Attachment added: "ether_type_0x800_miss_2022-07-28 08-28-24.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980590/+attachment/5605746/+files/ether_type_0x800_miss_2022-07-28%2008-28-24.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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

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

[Bernhard Riegler]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1980590/+attachment/5605743/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] ProcInterrupts.txt

[Bernhard Riegler]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605741/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] ProcEnviron.txt

[Bernhard Riegler]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605740/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] ProcCpuinfo.txt

[Bernhard Riegler]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605738/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] ProcCpuinfoMinimal.txt

[Bernhard Riegler]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605739/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] PaInfo.txt

[Bernhard Riegler]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1980590/+attachment/5605737/+files/PaInfo.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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] Lsusb-v.txt

[Bernhard Riegler]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605736/+files/Lsusb-v.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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] Lsusb.txt

[Bernhard Riegler]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1980590/+attachment/5605734/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] Lsusb-t.txt

[Bernhard Riegler]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605735/+files/Lsusb-t.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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] Lspci-vt.txt

[Bernhard Riegler]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605733/+files/Lspci-vt.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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] acpidump.txt

[Bernhard Riegler]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605745/+files/acpidump.txt

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

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

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

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

[Bernhard Riegler]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605744/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

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

[Bernhard Riegler]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1980590/+attachment/5605729/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Hewlett-Packard HP EliteBook 8560p
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-41-generic N/A
   linux-backports-modules-5.15.0-41-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  jammy
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/06/2017
  dmi.bios.release: 15.101
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 1618
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 151.78
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560p
  dmi.product.sku: LG731EA#ABD
  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/1980590/+subscriptions


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

[Kernel-packages] [Bug 1980590] Re: SECURITY leak in dpkg "nftables" kernel code family netdev hook ingress

[Bernhard Riegler]

apport information

** Tags added: apport-collected jammy

** Description changed:

  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.
  
  platform: Ubuntu 22.04LTS, latest patches installed
  
  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413
  
  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,
  
  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.
  
  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  bernie 1324 F pulseaudio
+ CasperMD5CheckResult: pass
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-05-31 (58 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
+ MachineType: Hewlett-Packard HP EliteBook 8560p
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic 
root=UUID=6f01374f-146b-402e-b36b-23f040ef48d2 ro ro quiet noplymouth 
ipv6.disable=1 initcall_blacklist=serial8250_init
+ ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-41-generic N/A
+  linux-backports-modules-5.15.0-41-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.3
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: yes
+   Hard blocked: no
+ Tags:  jammy
+ Uname: Linux 5.15.0-41-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 04/06/2017
+ dmi.bios.release: 15.101
+ dmi.bios.vendor: Hewlett-Packard
+ dmi.bios.version: 68SCF Ver. F.65
+ dmi.board.name: 1618
+ dmi.board.vendor: Hewlett-Packard
+ dmi.board.version: KBC Version 97.4E
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Hewlett-Packard
+ dmi.ec.firmware.release: 151.78
+ dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:br15.101:efr151.78:svnHewlett-Packard:pnHPEliteBook8560p:pvrA0001D02:rvnHewlett-Packard:rn1618:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:skuLG731EA#ABD:
+ dmi.product.family: 103C_5336AN
+ dmi.product.name: HP EliteBook 8560p
+ dmi.product.sku: LG731EA#ABD
+ dmi.product.version: A0001D02
+ dmi.sys.vendor: Hewlett-Packard

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1980590/+attachment/5605728/+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/1980590

Title:
  SECURITY leak in dpkg "nftables" kernel code family netdev hook
  ingress

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  an android app is sending big UDP datagrams, this generates IPv4 fragments
  this IPv4 fragments can not be controlled in firewall nftables family netdev 
hook ingress.

  platform: Ubuntu 22.04LTS, latest patches installed

  I documented 2 screenshots
  fragment1.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, more frags, 
frag-offset=0, total=1500
  fragment2.png
  wireshark: ethernet header type=0x800, ipv4 header ID=0x2466, 
frag-offset=1480, total=413

  at the bottom of the screenshots is "/usr/sbin/nft monitor trace"
  family "netdev" hook "ingress" @nh,0,160 is the raw ipv4 data
  total=0x765=1893, ID=0x2466,

  glueing the two ipv4 fragments together = 1500 + 413 - 20 = 1893, oops
  the nftables TRACE shows an already processed bigger ipv4 packet.

  there is a race condition!
  the ipv4 processing has to WAIT for all the rules in family "netdev" hook 
"ingress"
  I cannot control ether type 0x800 completely in family "netdev" hook "ingress"
  this is a security vulnerability!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1324 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-05-31 (58 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy 

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[Fabian Bernhard]

Hello, thanks for the fast update.

Unfortunately my personal problem isn't fixed with it. I'm using a Ryzen 7 
5700U (on a hp envy x360-15eu000), with ubuntu 21.10. 
I use full disk encryption with luks, and when I try to boot with the new 
kernel (5.13.0-23, or now the newer 5.13.0-25) I type in the correct password 
and get stuck after this (last appearing message: [...] successfully decypted).
Usually (e.g with the 5.13.0-22 kernel), after decrypting the partition the 
system boots up and a row of instructions appear. With this kernel(s) it's 
completely stuck and nothing happens.

Is anyone else experiencing this 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/1956401

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

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


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

[Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot

[Bernhard Übelacker]

I can report that this device seems also affected:
Lenovo V15-IIL Iron Grey, Core i5-1035G1, 8GB RAM, 512GB SSD, DE (82C500JUGE)

This is with running a Debian testing kernel 5.10.0-7-amd64/5.10.40-1.

Adding the pci=nocrs makes the touchpad work, but unfortunately this does
not survive a standby or hibernate cycle.

@j-w-r-degoede: Do you still need your patch to be tested?


** Attachment added: "dmesg-without-pci-nocrs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1878279/+attachment/5507603/+files/dmesg-without-pci-nocrs.txt

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

Title:
  MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
  from any given boot

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  In Progress
Status in linux-signed-hwe package in Fedora:
  New

Bug description:
  Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
  at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
  14IIL05 81YH' from first system start on.

  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:  tilman 1607 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:22:22 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DSCN23WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
  dmi.product.family: IdeaPad 5 14IIL05
  dmi.product.name: 81YH
  dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
  dmi.product.version: IdeaPad 5 14IIL05
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1856372] Re: Wifi drops, particularly under load

[Bernhard]

I am affected by this bug as well. It happens in Fedora 33 and in
Kubuntu 20.10. Is there any fix for this problem (I don't care in which
distribution)?

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

Title:
  Wifi drops, particularly under load

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 18.04.3 LTS with Qualcomm Atheros QCA6174 wireless card,
  internet drops out, particularly when downloading at speeds ~1MB/s say
  via P2P torrent or ooka speedtest. The wifi connection (at least
  reported by wicd) remains active, but I cannot ping the router or
  access the internet. No error message is logged in journalctl after
  the internet drops. Details on my card, firmware and dmesg given below
  I'm not the only one with this issue:
  https://askubuntu.com/questions/1171813/wifi-randomly-or-under-load-
  disconnects-on-ubuntu-18-04-with-qualcomm-atheros

  The issue DOES NOT occur with wired connection (ethernet).
  
-
    *-network
     description: Wireless interface
     product: QCA6174 802.11ac Wireless Network Adapter
     vendor: Qualcomm Atheros
     physical id: 0
     bus info: pci@:3a:00.0
     logical name: wlp58s0
     version: 32
     serial: 9c:b6:d0:d4:9b:33
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.4.0-050400rc8-generic firmware=WLAN.RM.4.4.1-00140-QCARMSWPZ-1 
latency=0 link=no multicast=yes wireless=IEEE 802.11

     resources: irq:135 memory:dc00-dc1f
  
-
  $ dmesg | grep ath10k

  [2.662000] ath10k_pci :3a:00.0: enabling device ( -> 0002)
  [2.665299] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [2.950979] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
  [2.950982] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [2.951390] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [3.029754] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A crc32 
4ed3569e
  [3.108957] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [3.128068] ath10k_pci :3a:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [3.216750] ath10k_pci :3a:00.0 wlp58s0: renamed from wlan0
  [3.828149] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [   14.519059] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [   15.014705] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [ 1054.860682] ath10k_pci :3a:00.0: unsupported HTC service id: 1536
  [ 1055.385335] ath10k_pci :3a:00.0: unsupported HTC service id: 1536

  
-
  $ dmesg | grep pcieport

  [0.959817] pcieport :00:1c.0: AER: enabled with IRQ 122
  [0.960121] pcieport :00:1c.4: AER: enabled with IRQ 123
  [0.960397] pcieport :00:1c.5: AER: enabled with IRQ 124
  [0.960657] pcieport :00:1d.0: AER: enabled with IRQ 125
  [6.644709] pcieport :02:01.0: bridge window [io  0x1000-0x0fff] to 
[bus 04-38] add_size 1000
  [6.644711] pcieport :02:02.0: bridge window [io  0x1000-0x0fff] to 
[bus 39] add_size 1000
  [6.644713] pcieport :02:02.0: bridge window [mem 
0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10
  [6.644716] pcieport :01:00.0: bridge window [io  0x1000-0x0fff] to 
[bus 02-39] add_size 3000
  [6.644719] pcieport :01:00.0: BAR 13: no space for [io  size 0x3000]
  [6.644721] pcieport :01:00.0: BAR 13: failed to assign [io  size 
0x3000]
  [6.644723] pcieport :01:00.0: BAR 13: no space for [io  size 0x3000]
  [6.644724] pcieport :01:00.0: BAR 13: failed to assign [io  size 
0x3000]
  [6.644728] pcieport :02:02.0: BAR 15: no space for [mem size 
0x0020 64bit pref]
  [6.644729] pcieport :02:02.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [6.644731] pcieport :02:01.0: BAR 13: no space for [io  size 0x1000]
  [6.644732] pcieport :02:01.0: BAR 13: failed to assign [io  size 
0x1000]
  [6.644734] pcieport :02:02.0: BAR 13: no space for [io  size 0x1000]
  [6.644735] pcieport :02:02.0: BAR 13: failed to assign [io  size 
0x1000]
  [6.644738] pcieport :02:02.0: BAR 15: no space for [mem size 
0x0020 64bit 

[Kernel-packages] [Bug 1858299] Re: This laptop contains a touchpadwhich is not recognized.

[Bernhard Schmidt]

I have to correct me, it works with the kernel you linked. I plugged out
my USB mouse and now the touchpad is recognized perfectly. Thank you
very much, Kai-Heng!

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

Title:
  This laptop contains a touchpadwhich is not recognized.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This laptop contains a touchpad which is not recognized. The laptop is
  the Trekstore Surfbook E11B.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  deathmetal   1119 F pulseaudio
  CurrentDesktop: LXQt
  Date: Sat Jan  4 23:09:34 2020
  InstallationDate: Installed on 2020-01-04 (0 days ago)
  InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TREKSTOR SURFBOOK E11B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=c3bcb5e6-3626-422a-b348-dbdb31c269d9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BIOS_V1.1.5
  dmi.board.asset.tag: Default string
  dmi.board.name: Gemini_Lake_Celeron_V01
  dmi.board.vendor: TS_EMDOOR
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBIOS_V1.1.5:bd08/30/2018:svnTREKSTOR:pnSURFBOOKE11B:pvrDefaultstring:rvnTS_EMDOOR:rnGemini_Lake_Celeron_V01:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Surfbook
  dmi.product.name: SURFBOOK E11B
  dmi.product.sku: NFCN4SW03
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

[Kernel-packages] [Bug 1858299] Re: This laptop contains a touchpadwhich is not recognized.

[Bernhard Schmidt]

Thank you for your quick response. I installed the Linux Kernel Linux
5.3.0-27-generic you linked but there is no change. The touchpad still
doesn't work. Please let me know if I can provide you with some specific
log files.

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

Title:
  This laptop contains a touchpadwhich is not recognized.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This laptop contains a touchpad which is not recognized. The laptop is
  the Trekstore Surfbook E11B.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  deathmetal   1119 F pulseaudio
  CurrentDesktop: LXQt
  Date: Sat Jan  4 23:09:34 2020
  InstallationDate: Installed on 2020-01-04 (0 days ago)
  InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TREKSTOR SURFBOOK E11B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=c3bcb5e6-3626-422a-b348-dbdb31c269d9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BIOS_V1.1.5
  dmi.board.asset.tag: Default string
  dmi.board.name: Gemini_Lake_Celeron_V01
  dmi.board.vendor: TS_EMDOOR
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBIOS_V1.1.5:bd08/30/2018:svnTREKSTOR:pnSURFBOOKE11B:pvrDefaultstring:rvnTS_EMDOOR:rnGemini_Lake_Celeron_V01:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Surfbook
  dmi.product.name: SURFBOOK E11B
  dmi.product.sku: NFCN4SW03
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

[Kernel-packages] [Bug 1858299] [NEW] This laptop contains a touchpadwhich is not recognized.

[Bernhard Schmidt]

Public bug reported:

This laptop contains a touchpad which is not recognized. The laptop is
the Trekstore Surfbook E11B.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  deathmetal   1119 F pulseaudio
CurrentDesktop: LXQt
Date: Sat Jan  4 23:09:34 2020
InstallationDate: Installed on 2020-01-04 (0 days ago)
InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB Camera
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: TREKSTOR SURFBOOK E11B
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=c3bcb5e6-3626-422a-b348-dbdb31c269d9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-18-generic N/A
 linux-backports-modules-5.3.0-18-generic  N/A
 linux-firmware1.183
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: BIOS_V1.1.5
dmi.board.asset.tag: Default string
dmi.board.name: Gemini_Lake_Celeron_V01
dmi.board.vendor: TS_EMDOOR
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBIOS_V1.1.5:bd08/30/2018:svnTREKSTOR:pnSURFBOOKE11B:pvrDefaultstring:rvnTS_EMDOOR:rnGemini_Lake_Celeron_V01:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.family: Surfbook
dmi.product.name: SURFBOOK E11B
dmi.product.sku: NFCN4SW03
dmi.product.version: Default string
dmi.sys.vendor: TREKSTOR

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


** Tags: amd64 apport-bug eoan

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

Title:
  This laptop contains a touchpadwhich is not recognized.

Status in linux package in Ubuntu:
  New

Bug description:
  This laptop contains a touchpad which is not recognized. The laptop is
  the Trekstore Surfbook E11B.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  deathmetal   1119 F pulseaudio
  CurrentDesktop: LXQt
  Date: Sat Jan  4 23:09:34 2020
  InstallationDate: Installed on 2020-01-04 (0 days ago)
  InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB Camera
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: TREKSTOR SURFBOOK E11B
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=c3bcb5e6-3626-422a-b348-dbdb31c269d9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BIOS_V1.1.5
  dmi.board.asset.tag: Default string
  dmi.board.name: Gemini_Lake_Celeron_V01
  dmi.board.vendor: TS_EMDOOR
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBIOS_V1.1.5:bd08/30/2018:svnTREKSTOR:pnSURFBOOKE11B:pvrDefaultstring:rvnTS_EMDOOR:rnGemini_Lake_Celeron_V01:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Surfbook
  dmi.product.name: SURFBOOK E11B
  dmi.product.sku: NFCN4SW03
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR

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

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

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Bernhard G]

Just updated to 4.8.0-49.61 from yakkety-updates. The issue is solved, there.
Thank you all!

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin kernel: [  190.648972] usbcore: registered new 

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Bernhard G]

For these kernel version you need to enable the proposed repository.
See here: https://wiki.ubuntu.com/Testing/EnableProposed how it's 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/1666421

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 07:17:03 orin 

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Bernhard G]

I can confirm that 4.8.0-47.50 from proposed does not freeze in Yakkety.

Should we set the tags to verification-done-* again? Or should we wait
for the next proposed version to see, if the patch remains there this
time...

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi 

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Bernhard G]

Yakkety 4.8.0-46 is broken.

@Muelli: 4.4.0-69 from the xenial proposed and 4.8.0-43 from the yakkety
proposed repository contained a patch that fixed the issue. For unknown
reasons this patch was reverted in 4.4.0-70 and 4.8.0-44. Several non
proposed kernel updates have been released since then, all broken.

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Bernhard G]

Confirm, broken again with 4.8.0-44. So as I assume 4.4.0-70 was also
fetched from xenial-proposed I set the tags back to verification-needed-
yakkety.

Summary: 
  4.4.0-69 worked (verified)
  4.4.0-70 broken
  4.8.0-43 worked (verified)
  4.8.0-44 broken

** Tags removed: verification-done-xenial verification-done-yakkety
** Tags added: verification-needed-xenial verification-needed-yakkety

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin 

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Bernhard G]

Confirm fix works for yakkety. At least kernel does not panic anymore.

** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21 

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Bernhard G]

apt wants to remove lubuntu-desktop if I try to install the linux-image-
generic. Is there any way to avoid that?

$ sudo apt-get install linux-image-generic/yakkety-proposed
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.   
Statusinformationen werden eingelesen Fertig
Version »4.8.0.43.55« (Ubuntu:16.10/yakkety-proposed [amd64]) für 
»linux-image-generic« gewählt.
Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
  linux-headers-generic
Verwenden Sie »sudo apt autoremove«, um es zu entfernen.
Die folgenden zusätzlichen Pakete werden Installiert
  linux-image-4.8.0-43-generic linux-image-extra-4.8.0-43-generic
Vorgeschlagene Pakete:
  fdutils linux-doc-4.8.0 | linux-source-4.8.0 linux-tools 
linux-headers-4.8.0-43-generic
Empfohlene Pakete:
  thermald
Die folgenden Pakete werden ENTFERNT:
  linux-generic lubuntu-desktop snapd
Die folgenden NEUEN Pakete werden installiert:
  linux-image-4.8.0-43-generic linux-image-extra-4.8.0-43-generic
Die folgenden Pakete werden aktualisiert (Upgrade):
  linux-image-generic
1 aktualisiert, 2 neu installiert, 3 zu entfernen und 0 nicht aktualisiert.
Es müssen 61,0 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 183 MB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n]

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

[Bernhard G]

I can confirm that the test kernel posted in comment #7 solved the issue for me.
See comment 5 of bug #1669815 (duplicate of this one).

Any information when the bugfix will be part of the 4.8.0 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/1666421

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device 

[Kernel-packages] [Bug 1669815] Re: Kernel panic when plugging in USB Wifi USB adapter

[Bernhard G]

I installed the kernel 4.4.0 provided by jsalisbury. This works for me:

$ uname -a
Linux media-desktop 4.4.0-64-generic #85~lp1666421 SMP Wed Feb 22 21:37:35 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

$ lsusb | grep "Edimax"
Bus 001 Device 002: ID 7392:7822 Edimax Technology Co., Ltd 

$ ifconfig wlx74da3894b952
wlx74da3894b952: flags=4163  mtu 1500
inet 192.168.1.52  netmask 255.255.255.0  broadcast 192.168.1.255
ether 74:da:38:94:b9:52  txqueuelen 1000  (Ethernet)
RX packets 3327  bytes 2122333 (2.1 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2755  bytes 370569 (370.5 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I don't know much about the different kernel versions. Would It be
possible to apply the modification to the 4.8.0 kernel as well, so I can
test that, too?

I tested 
 * booting without device attached, then attaching it after boot.
 * booting with device attached.
Both works fine. Should I test anything else?

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

Title:
  Kernel panic when plugging in USB Wifi USB adapter

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  Since updating my Lubuntu 16.10 system (linux-image-4.8.0-37-generic to 
linux-image-4.8.0-38-generic) the kernel panics as soon as I plug in the Wifi 
adapter (Edimax EW-7612UAn Wifi USB Adapter).
  The coredump logs
  BUG: unable to handle kernel NULL pointer dereference @0048
  IP: [] rtl_lps_leave+0x17/0x50 [rtlwifi]
  PGD 0
  Ooops:  [#1] SMP
  This is followed by the Modules linked in, Hardware info, Stack trace.
  At the end of the trace it says:
  Kernel panic - not syncing: Fatal exception in interrupt.

  I uploaded a console screenshot here: IMG_20170222_230239.jpg
  and I didn't find anything suspicious in syslog or kernel log, most probably 
because the kernel panics almost instantly after plugging the usb adapter in.

  Updating to linux-image-4.8.0-39-generic does not solve the issue as
  well.

  Only way to work around the issue is to select the 4.8.0-37 image from the 
grub bootmenu.
  The problem is not related to a specific USB port.

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

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

[Kernel-packages] [Bug 1669815] Re: Kernel panic when plugging in USB Wifi USB adapter

[Bernhard G]

** Attachment added: "IMG_20170222_230239.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669815/+attachment/4830787/+files/IMG_20170222_230239.jpg

** Description changed:

  Since updating my Lubuntu 16.10 system (linux-image-4.8.0-37-generic to 
linux-image-4.8.0-38-generic) the kernel panics as soon as I plug in the Wifi 
adapter (Edimax EW-7612UAn Wifi USB Adapter).
  The coredump logs
  BUG: unable to handle kernel NULL pointer dereference @0048
  IP: [] rtl_lps_leave+0x17/0x50 [rtlwifi]
  PGD 0
  Ooops:  [#1] SMP
  This is followed by the Modules linked in, Hardware info, Stack trace.
  At the end of the trace it says:
  Kernel panic - not syncing: Fatal exception in interrupt.
  
- I uploaded a console screenshot to my google drive: https://goo.gl/medcXj
+ I uploaded a console screenshot here: IMG_20170222_230239.jpg
  and I didn't find anything suspicious in syslog or kernel log, most probably 
because the kernel panics almost instantly after plugging the usb adapter in.
  
  Updating to linux-image-4.8.0-39-generic does not solve the issue as
  well.
  
  Only way to work around the issue is to select the 4.8.0-37 image from the 
grub bootmenu.
  The problem is not related to a specific USB port.

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

Title:
  Kernel panic when plugging in USB Wifi USB adapter

Status in linux package in Ubuntu:
  New

Bug description:
  Since updating my Lubuntu 16.10 system (linux-image-4.8.0-37-generic to 
linux-image-4.8.0-38-generic) the kernel panics as soon as I plug in the Wifi 
adapter (Edimax EW-7612UAn Wifi USB Adapter).
  The coredump logs
  BUG: unable to handle kernel NULL pointer dereference @0048
  IP: [] rtl_lps_leave+0x17/0x50 [rtlwifi]
  PGD 0
  Ooops:  [#1] SMP
  This is followed by the Modules linked in, Hardware info, Stack trace.
  At the end of the trace it says:
  Kernel panic - not syncing: Fatal exception in interrupt.

  I uploaded a console screenshot here: IMG_20170222_230239.jpg
  and I didn't find anything suspicious in syslog or kernel log, most probably 
because the kernel panics almost instantly after plugging the usb adapter in.

  Updating to linux-image-4.8.0-39-generic does not solve the issue as
  well.

  Only way to work around the issue is to select the 4.8.0-37 image from the 
grub bootmenu.
  The problem is not related to a specific USB port.

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

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

[Kernel-packages] [Bug 1669815] Re: Kernel panic when plugging in USB Wifi USB adapter

[Bernhard G]

** Summary changed:

- Kernel panic when plugging in USB Wifi USB Adapter
+ Kernel panic when plugging in USB Wifi USB adapter

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

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

Title:
  Kernel panic when plugging in USB Wifi USB adapter

Status in linux package in Ubuntu:
  New

Bug description:
  Since updating my Lubuntu 16.10 system (linux-image-4.8.0-37-generic to 
linux-image-4.8.0-38-generic) the kernel panics as soon as I plug in the Wifi 
adapter (Edimax EW-7612UAn Wifi USB Adapter).
  The coredump logs
  BUG: unable to handle kernel NULL pointer dereference @0048
  IP: [] rtl_lps_leave+0x17/0x50 [rtlwifi]
  PGD 0
  Ooops:  [#1] SMP
  This is followed by the Modules linked in, Hardware info, Stack trace.
  At the end of the trace it says:
  Kernel panic - not syncing: Fatal exception in interrupt.

  I uploaded a console screenshot here: IMG_20170222_230239.jpg
  and I didn't find anything suspicious in syslog or kernel log, most probably 
because the kernel panics almost instantly after plugging the usb adapter in.

  Updating to linux-image-4.8.0-39-generic does not solve the issue as
  well.

  Only way to work around the issue is to select the 4.8.0-37 image from the 
grub bootmenu.
  The problem is not related to a specific USB port.

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

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

[Kernel-packages] [Bug 1584597] Re: Hyper-V Memory Ballooning re-broken in 16.04

[Bernhard]

I seem to experience a kernel crash (or application crash in early
moments of this bug) due to Hyper-V ballooning (or at least dynamic
memory). I am using Xenial on Hyper-V on Windows Server 2012 64bit. I
started using dynamic memory (1024 Kb start memory, allowed growing to
3072 Kb). Apparently this worked fine; I saw memory rise during demand
and memory was released back to the host when not needed. But the
releasing of memory apparently causes memory corruption. I noticed this
my using the stress tool that was called like this:

bme@zabbix:~$ stress --vm-bytes $(awk '/MemFree/{printf "%d\n", $2 * 0.9;}' < 
/proc/meminfo)k --vm-keep -m 1
stress: info: [3698] dispatching hogs: 0 cpu, 0 io, 1 vm, 0 hdd
stress: FAIL: [3699] (522) memory corruption at: 0x7fd801e00010
stress: FAIL: [3698] (394) <-- worker 3699 returned error 1
stress: WARN: [3698] (396) now reaping child worker processes
stress: FAIL: [3698] (451) failed run completed in 0s

The memory corruption only occured when Hyper-V had reclaimed memory
(balloning). Disabling dynamic memory has removed the memory
corruptions.

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

Title:
  Hyper-V Memory Ballooning re-broken in 16.04

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

Bug description:
  Regression: #1294283 fixed memory ballooning in Hyper-V in 14.04, but
  the bug has returned in 16.04.

  
  Steps to reproduce:

  1. Create Gen2 Hyper-V VM
  2. Install Ubuntu 16.04
  3. modprobe hv_balloon
  Memory usage according to Hyper-V Manager will not change

  
  This has been reproduced on 2 fresh Ubuntu Server 16.04 instances.

  I installed linux-generic-xenial on a 14.04 instance, rebooted,
  modprobe'd hv_balloon and memory usage in Hyper-V Manager reduced to
  the correct level.

  Environment:
  Host: Windows NanoServer 2016

  Ubuntu Server 16.04 version_signature: `Ubuntu 4.4.0-21.37-generic 4.4.6`
  Ubuntu Server 14.04 version_signature: `Ubuntu 4.4.0-22.40~14.04.1-generic 
4.4.8`

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

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

[Kernel-packages] [Bug 1559643] Re: kswapd0 high cpu

[Bernhard Czapp]

After commenting out the first two line 2 lines:
**
# On Hyper-V and Xen Virtual Machines we want to add memory and cpus as soon as 
they appear
#ATTR{[dmi/id]sys_vendor}=="Microsoft Corporation", 
ATTR{[dmi/id]product_name}=="Virtual Machine", GOTO="vm_hotadd_apply"
#ATTR{[dmi/id]sys_vendor}=="Xen", GOTO="vm_hotadd_apply"
**
in file
/lib/udev/rules.d/40-vm-hotadd.rules

and rebooting the system in working normally again.

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

Title:
  kswapd0 high cpu

Status in linux package in Ubuntu:
  New

Bug description:
  kswapd0 high cpu load.
  System doesn't have swap partition / swap file.

  Using AWS t2.nano

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39
  ProcVersionSignature: User Name 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 07:35 seq
   crw-rw 1 root audio 116, 33 Mar 20 07:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Mar 20 07:57:52 2016
  Ec2AMI: ami-b7443fc0
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 cirrusdrmfb
   1 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=b079c5f1-8fc8-4bb0-aa26-31610f9c5615 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-34-generic N/A
   linux-backports-modules-4.2.0-34-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-13 (127 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1559643] [NEW] kswapd0 high cpu

[Bernhard Czapp]

Public bug reported:

kswapd0 high cpu load.
System doesn't have swap partition / swap file.

Using AWS t2.nano

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-34-generic 4.2.0-34.39
ProcVersionSignature: User Name 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 20 07:35 seq
 crw-rw 1 root audio 116, 33 Mar 20 07:35 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Sun Mar 20 07:57:52 2016
Ec2AMI: ami-b7443fc0
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1a
Ec2InstanceType: t2.nano
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
MachineType: Xen HVM domU
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 cirrusdrmfb
 1 xen
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=b079c5f1-8fc8-4bb0-aa26-31610f9c5615 ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-34-generic N/A
 linux-backports-modules-4.2.0-34-generic  N/A
 linux-firmware1.149.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-11-13 (127 days ago)
dmi.bios.date: 12/07/2015
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen

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


** Tags: amd64 apport-bug ec2-images wily

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

Title:
  kswapd0 high cpu

Status in linux package in Ubuntu:
  New

Bug description:
  kswapd0 high cpu load.
  System doesn't have swap partition / swap file.

  Using AWS t2.nano

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-34-generic 4.2.0-34.39
  ProcVersionSignature: User Name 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 07:35 seq
   crw-rw 1 root audio 116, 33 Mar 20 07:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sun Mar 20 07:57:52 2016
  Ec2AMI: ami-b7443fc0
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 cirrusdrmfb
   1 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=b079c5f1-8fc8-4bb0-aa26-31610f9c5615 ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-34-generic N/A
   linux-backports-modules-4.2.0-34-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-11-13 (127 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/07/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1488719] Re: dmesg shows "[drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"

[Bernhard Schussek]

Same problem here on Lenovo T450s with kernel 4.2.0-27.

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

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

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

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

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

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

  Maybe related:

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

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

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

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

[Kernel-packages] [Bug 1457187] Re: [DVB] dib0700 DVB devices not working with kernels >= 3.19.x (vivid + trusty) <= 4.2.x (wily)

[Bernhard]

I have tested lts-wily kernel for precise => kernel 4.2 (4.2.0-7-generic
#7~14.04.1).

With this kernel the usb dvb-t stick works again.

** Summary changed:

- [DVB] dib0700 DVB devices not working with kernels >= 3.19.x (vivid + trusty)
+ [DVB] dib0700 DVB devices not working with kernels >= 3.19.x (vivid + trusty) 
<= 4.2.x (wily)

** Summary changed:

- [DVB] dib0700 DVB devices not working with kernels >= 3.19.x (vivid + trusty) 
<= 4.2.x (wily)
+ [DVB] dib0700 DVB devices not working with kernels >= 3.19.x (vivid + trusty) 
< 4.2.x (wily)

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

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

Title:
  [DVB] dib0700 DVB devices not working with kernels >= 3.19.x (vivid +
  trusty) < 4.2.x (wily)

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

Bug description:
  Hello,

  starting with kernel >= 3.19 (vivid) my USB TV-Stick DVB-T "Terratec Cinergy 
DT XS Diversity" stopped working. 
  => BUG: unable to handle kernel NULL pointer dereference

  This problem was not in kernel 3.16.x. (Utopic)

  System: Kubuntu 14.04.2 64bit, kernel 3.19.x (lts-vivid,
  3.19.0-18-generic #18~14.04.1-Ubuntu )

  There is a bugreport available, where I have added my device-problem
  too and a patch is available.

  https://bugzilla.kernel.org/show_bug.cgi?id=92301

  Patch:
  http://permalink.gmane.org/gmane.linux.kernel.stable/135755

  Please add this patch to kernels >= 3.19 (LTS HWE Vivid kernel Trusty
  14.04, Vivid 15.04 and newer; linux-generic-lts-vivid, linux-image-
  generic-lts-vivid, ... )

  Thank you for your support!

  Best regards, Bernhard

  - log messsages:

  
  Apr  9 18:01:03 stargazer kernel: [   70.017022] usb 3-2.4.1: new high-speed 
USB device number 4 using xhci_hcd
  Apr  9 18:01:03 stargazer kernel: [   70.107491] usb 3-2.4.1: New USB device 
found, idVendor=0ccd, idProduct=005a
  Apr  9 18:01:03 stargazer kernel: [   70.107494] usb 3-2.4.1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Apr  9 18:01:03 stargazer kernel: [   70.107495] usb 3-2.4.1: Product: 
Cinergy DT XS
  Apr  9 18:01:03 stargazer kernel: [   70.107497] usb 3-2.4.1: Manufacturer: 
TerraTec
  Apr  9 18:01:03 stargazer kernel: [   70.107498] usb 3-2.4.1: SerialNumber: 
07020100
  Apr  9 18:01:03 stargazer mtp-probe: checking bus 3, device 4: 
"/sys/devices/pci:00/:00:1c.0/:06:00.0/:07:09.0/:0b:00.0/usb3/3-2/3-2.4/3-2.4.1"
  Apr  9 18:01:03 stargazer mtp-probe: bus: 3, device: 4 was not an MTP device
  Apr  9 18:01:03 stargazer kernel: [   70.139371] dvb-usb: found a 'Terratec 
Cinergy DT XS Diversity' in cold state, will try to load a firmware
  Apr  9 18:01:03 stargazer kernel: [   70.139617] dvb-usb: downloading 
firmware from file 'dvb-usb-dib0700-1.20.fw'
  Apr  9 18:01:03 stargazer kernel: [   70.543833] dib0700: firmware started 
successfully.
  Apr  9 18:01:04 stargazer kernel: [   71.047012] dvb-usb: found a 'Terratec 
Cinergy DT XS Diversity' in warm state.
  Apr  9 18:01:04 stargazer kernel: [   71.047309] dvb-usb: will pass the 
complete MPEG2 transport stream to the software demuxer.
  Apr  9 18:01:04 stargazer kernel: [   71.047746] DVB: registering new adapter 
(Terratec Cinergy DT XS Diversity)
  Apr  9 18:01:04 stargazer kernel: [   71.057441] BUG: unable to handle kernel 
NULL pointer dereference at 0080
  Apr  9 18:01:04 stargazer kernel: [   71.057450] IP: [] 
dib7000p_attach+0x11/0xa0 [dib7000p]
  Apr  9 18:01:04 stargazer kernel: [   71.057457] PGD cd4be067 PUD cd4e4067 
PMD 0
  Apr  9 18:01:04 stargazer kernel: [   71.057463] Oops: 0002 [#1] SMP
  Apr  9 18:01:04 stargazer kernel: [   71.057466] Modules linked in: dib7000p 
dvb_usb_dib0700(+) dib7000m dib0090 dib0070 dib3000mc dibx000_common dvb_usb 
dvb_core rc_core dm_crypt nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter 
ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables snd_hda_codec_hdmi snd_usb_audio joydev 
snd_usbmidi_lib gpio_ich mxm_wmi hid_logitech_hidpp snd_hda_codec_via 
snd_hda_codec_generic nvidia(POE) snd_hda_intel kvm_intel snd_hda_controller 
snd_hda_codec kvm snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
serio_raw i7core_edac edac_core snd_seq snd_seq_device snd_timer snd drm 
soundcore lpc_ich shpchp rfcomm bnep bluetooth wmi mac_hid binfmt_misc 
parport_pc ppdev coretemp lp parport pata_acpi hid_logitech_dj hid_generic 
usbhid hid psmouse firewire_ohci firewire_core r8169 ahci crc_itu_t 
pata_jmicron mii libahci
  Apr  9 18:01:04 stargazer kernel: [   71.057531] CPU: 2 PID: 3496 Comm: 
systemd-udevd Tainted: P   OE  3.19.0-12-generic #12~14.04.1-Ubuntu
  Apr  9 18:01:04 stargazer kernel: [   71.057533] Hardware name: System 
manufact

[Kernel-packages] [Bug 1457187] Re: [DVB] dib0700 DVB devices not working with kernels = 3.19.x (vivid + trusty)

[Bernhard]

Furthermore I have tested kernels 4.0.6 and 4.1, but the problem is not
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/1457187

Title:
  [DVB] dib0700 DVB devices not working with kernels = 3.19.x (vivid +
  trusty)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  starting with kernel = 3.19 (vivid) my USB TV-Stick DVB-T Terratec Cinergy 
DT XS Diversity stopped working. 
  = BUG: unable to handle kernel NULL pointer dereference

  This problem was not in kernel 3.16.x. (Utopic)

  System: Kubuntu 14.04.2 64bit, kernel 3.19.x (lts-vivid,
  3.19.0-18-generic #18~14.04.1-Ubuntu )

  There is a bugreport available, where I have added my device-problem
  too and a patch is available.

  https://bugzilla.kernel.org/show_bug.cgi?id=92301

  Patch:
  http://permalink.gmane.org/gmane.linux.kernel.stable/135755

  Please add this patch to kernels = 3.19 (LTS HWE Vivid kernel Trusty
  14.04, Vivid 15.04 and newer; linux-generic-lts-vivid, linux-image-
  generic-lts-vivid, ... )

  Thank you for your support!

  Best regards, Bernhard

  - log messsages:

  
  Apr  9 18:01:03 stargazer kernel: [   70.017022] usb 3-2.4.1: new high-speed 
USB device number 4 using xhci_hcd
  Apr  9 18:01:03 stargazer kernel: [   70.107491] usb 3-2.4.1: New USB device 
found, idVendor=0ccd, idProduct=005a
  Apr  9 18:01:03 stargazer kernel: [   70.107494] usb 3-2.4.1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Apr  9 18:01:03 stargazer kernel: [   70.107495] usb 3-2.4.1: Product: 
Cinergy DT XS
  Apr  9 18:01:03 stargazer kernel: [   70.107497] usb 3-2.4.1: Manufacturer: 
TerraTec
  Apr  9 18:01:03 stargazer kernel: [   70.107498] usb 3-2.4.1: SerialNumber: 
07020100
  Apr  9 18:01:03 stargazer mtp-probe: checking bus 3, device 4: 
/sys/devices/pci:00/:00:1c.0/:06:00.0/:07:09.0/:0b:00.0/usb3/3-2/3-2.4/3-2.4.1
  Apr  9 18:01:03 stargazer mtp-probe: bus: 3, device: 4 was not an MTP device
  Apr  9 18:01:03 stargazer kernel: [   70.139371] dvb-usb: found a 'Terratec 
Cinergy DT XS Diversity' in cold state, will try to load a firmware
  Apr  9 18:01:03 stargazer kernel: [   70.139617] dvb-usb: downloading 
firmware from file 'dvb-usb-dib0700-1.20.fw'
  Apr  9 18:01:03 stargazer kernel: [   70.543833] dib0700: firmware started 
successfully.
  Apr  9 18:01:04 stargazer kernel: [   71.047012] dvb-usb: found a 'Terratec 
Cinergy DT XS Diversity' in warm state.
  Apr  9 18:01:04 stargazer kernel: [   71.047309] dvb-usb: will pass the 
complete MPEG2 transport stream to the software demuxer.
  Apr  9 18:01:04 stargazer kernel: [   71.047746] DVB: registering new adapter 
(Terratec Cinergy DT XS Diversity)
  Apr  9 18:01:04 stargazer kernel: [   71.057441] BUG: unable to handle kernel 
NULL pointer dereference at 0080
  Apr  9 18:01:04 stargazer kernel: [   71.057450] IP: [c0ded141] 
dib7000p_attach+0x11/0xa0 [dib7000p]
  Apr  9 18:01:04 stargazer kernel: [   71.057457] PGD cd4be067 PUD cd4e4067 
PMD 0
  Apr  9 18:01:04 stargazer kernel: [   71.057463] Oops: 0002 [#1] SMP
  Apr  9 18:01:04 stargazer kernel: [   71.057466] Modules linked in: dib7000p 
dvb_usb_dib0700(+) dib7000m dib0090 dib0070 dib3000mc dibx000_common dvb_usb 
dvb_core rc_core dm_crypt nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter 
ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables snd_hda_codec_hdmi snd_usb_audio joydev 
snd_usbmidi_lib gpio_ich mxm_wmi hid_logitech_hidpp snd_hda_codec_via 
snd_hda_codec_generic nvidia(POE) snd_hda_intel kvm_intel snd_hda_controller 
snd_hda_codec kvm snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
serio_raw i7core_edac edac_core snd_seq snd_seq_device snd_timer snd drm 
soundcore lpc_ich shpchp rfcomm bnep bluetooth wmi mac_hid binfmt_misc 
parport_pc ppdev coretemp lp parport pata_acpi hid_logitech_dj hid_generic 
usbhid hid psmouse firewire_ohci firewire_core r8169 ahci crc_itu_t 
pata_jmicron mii libahci
  Apr  9 18:01:04 stargazer kernel: [   71.057531] CPU: 2 PID: 3496 Comm: 
systemd-udevd Tainted: P   OE  3.19.0-12-generic #12~14.04.1-Ubuntu
  Apr  9 18:01:04 stargazer kernel: [   71.057533] Hardware name: System 
manufacturer System Product Name/P7P55D-E PRO, BIOS 170306/26/2012
  Apr  9 18:01:04 stargazer kernel: [   71.057535] task: 880036275850 ti: 
8800cd548000 task.ti: 8800cd548000
  Apr  9 18:01:04 stargazer kernel: [   71.057537] RIP: 
0010:[c0ded141]  [c0ded141] dib7000p_attach+0x11/0xa0 
[dib7000p]
  Apr  9 18:01:04 stargazer kernel: [   71.057541] RSP: 0018:8800cd54ba68  
EFLAGS: 00010202
  Apr  9 18:01:04 stargazer kernel: [   71.057543] RAX: 0010 RBX: 
8803e0aed278 RCX: 0001
  Apr  9 18:01:04 stargazer kernel: [   71.057545] RDX: 0001 RSI: 
c0df4758 RDI

[Kernel-packages] [Bug 1457187] Re: [DVB] dib0700 DVB devices not working with kernels = 3.19.x (vivid + trusty)

[Bernhard]

See bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=92301

- Question from me:

Do you know when the patch will be included in the latest kernel and
lts-kernels; 3.18, 4.0, 4.1?

- The writer of the patch, Thomas Reitmayr, answered the following:

I found the patch only in the linux-next tree, so that probably means
4.2, although it was forwarded to the linux-stable mailing list. Not
sure how the process looks like for getting it into an lts kernel.

- Other posts from Thomas Reitmayr:

I submitted a patch to linux-me...@vger.kernel.org. As described in the commit 
message the problem was introduced in kernel version 3.17 and concerns a few 
device types handled by dvb_usb_dib0700. 
See 
http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/90691

Patch landed in linux-stable mailing list, see
http://permalink.gmane.org/gmane.linux.kernel.stable/135755

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

Title:
  [DVB] dib0700 DVB devices not working with kernels = 3.19.x (vivid +
  trusty)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  starting with kernel = 3.19 (vivid) my USB TV-Stick DVB-T Terratec Cinergy 
DT XS Diversity stopped working. 
  = BUG: unable to handle kernel NULL pointer dereference

  This problem was not in kernel 3.16.x. (Utopic)

  System: Kubuntu 14.04.2 64bit, kernel 3.19.x (lts-vivid,
  3.19.0-18-generic #18~14.04.1-Ubuntu )

  There is a bugreport available, where I have added my device-problem
  too and a patch is available.

  https://bugzilla.kernel.org/show_bug.cgi?id=92301

  Patch:
  http://permalink.gmane.org/gmane.linux.kernel.stable/135755

  Please add this patch to kernels = 3.19 (LTS HWE Vivid kernel Trusty
  14.04, Vivid 15.04 and newer; linux-generic-lts-vivid, linux-image-
  generic-lts-vivid, ... )

  Thank you for your support!

  Best regards, Bernhard

  - log messsages:

  
  Apr  9 18:01:03 stargazer kernel: [   70.017022] usb 3-2.4.1: new high-speed 
USB device number 4 using xhci_hcd
  Apr  9 18:01:03 stargazer kernel: [   70.107491] usb 3-2.4.1: New USB device 
found, idVendor=0ccd, idProduct=005a
  Apr  9 18:01:03 stargazer kernel: [   70.107494] usb 3-2.4.1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Apr  9 18:01:03 stargazer kernel: [   70.107495] usb 3-2.4.1: Product: 
Cinergy DT XS
  Apr  9 18:01:03 stargazer kernel: [   70.107497] usb 3-2.4.1: Manufacturer: 
TerraTec
  Apr  9 18:01:03 stargazer kernel: [   70.107498] usb 3-2.4.1: SerialNumber: 
07020100
  Apr  9 18:01:03 stargazer mtp-probe: checking bus 3, device 4: 
/sys/devices/pci:00/:00:1c.0/:06:00.0/:07:09.0/:0b:00.0/usb3/3-2/3-2.4/3-2.4.1
  Apr  9 18:01:03 stargazer mtp-probe: bus: 3, device: 4 was not an MTP device
  Apr  9 18:01:03 stargazer kernel: [   70.139371] dvb-usb: found a 'Terratec 
Cinergy DT XS Diversity' in cold state, will try to load a firmware
  Apr  9 18:01:03 stargazer kernel: [   70.139617] dvb-usb: downloading 
firmware from file 'dvb-usb-dib0700-1.20.fw'
  Apr  9 18:01:03 stargazer kernel: [   70.543833] dib0700: firmware started 
successfully.
  Apr  9 18:01:04 stargazer kernel: [   71.047012] dvb-usb: found a 'Terratec 
Cinergy DT XS Diversity' in warm state.
  Apr  9 18:01:04 stargazer kernel: [   71.047309] dvb-usb: will pass the 
complete MPEG2 transport stream to the software demuxer.
  Apr  9 18:01:04 stargazer kernel: [   71.047746] DVB: registering new adapter 
(Terratec Cinergy DT XS Diversity)
  Apr  9 18:01:04 stargazer kernel: [   71.057441] BUG: unable to handle kernel 
NULL pointer dereference at 0080
  Apr  9 18:01:04 stargazer kernel: [   71.057450] IP: [c0ded141] 
dib7000p_attach+0x11/0xa0 [dib7000p]
  Apr  9 18:01:04 stargazer kernel: [   71.057457] PGD cd4be067 PUD cd4e4067 
PMD 0
  Apr  9 18:01:04 stargazer kernel: [   71.057463] Oops: 0002 [#1] SMP
  Apr  9 18:01:04 stargazer kernel: [   71.057466] Modules linked in: dib7000p 
dvb_usb_dib0700(+) dib7000m dib0090 dib0070 dib3000mc dibx000_common dvb_usb 
dvb_core rc_core dm_crypt nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter 
ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables snd_hda_codec_hdmi snd_usb_audio joydev 
snd_usbmidi_lib gpio_ich mxm_wmi hid_logitech_hidpp snd_hda_codec_via 
snd_hda_codec_generic nvidia(POE) snd_hda_intel kvm_intel snd_hda_controller 
snd_hda_codec kvm snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
serio_raw i7core_edac edac_core snd_seq snd_seq_device snd_timer snd drm 
soundcore lpc_ich shpchp rfcomm bnep bluetooth wmi mac_hid binfmt_misc 
parport_pc ppdev coretemp lp parport pata_acpi hid_logitech_dj hid_generic 
usbhid hid psmouse firewire_ohci firewire_core r8169 ahci crc_itu_t 
pata_jmicron mii libahci
  Apr  9 18:01:04 stargazer kernel: [   71.057531] CPU: 2 PID: 3496

[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

[Bernhard]

Trusty LTS Kernel 3.13.0-57 works for me too for a Samsung SSD 840 Pro.

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
  set xfermode (err_mask=0x40) on upstream kernels = 3.12

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * Users with Samsung 8** SSD drives see miscellaneous errors and
  warning messages in the logs depending on the firmware level of the
  drive while booting or after running trim.

  [Test Case]

   * Run this script, and then check logs for errors.
  #!/bin/bash

  git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  for i in {0..10} ; do
   cp -r linux linux$i
  done
  rm -rf linux*
  echo sudo fstrim requires your password
  sudo fstrim ./

  [Regression Potential]

   * There is very little regression potential as this change simply
  prevents NCQ trim from being used on Samsung 8** drives.

  [Other Info]

   * Commit is upstream.
   * Greatly increasing the timeout for the drives seems to relieve the timeout 
errors.  This may be due to trimming large numbers of sectors with single 
commands.  It may be prudent for future upstream to break up large trims into 
multiple requests on smaller regions.

  ===Original Bug description ==
  Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2131 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  7 20:01:28 2014
  HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
  InstallationDate: Installed on 2014-06-22 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic 
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x: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/1338706/+subscriptions

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

[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

[Bernhard]

Trusty LTS Vivid Kernel 3.19.0-22.22 works for me too for a Samsung SSD
840 Pro.

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

Title:
  Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
  set xfermode (err_mask=0x40) on upstream kernels = 3.12

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * Users with Samsung 8** SSD drives see miscellaneous errors and
  warning messages in the logs depending on the firmware level of the
  drive while booting or after running trim.

  [Test Case]

   * Run this script, and then check logs for errors.
  #!/bin/bash

  git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  for i in {0..10} ; do
   cp -r linux linux$i
  done
  rm -rf linux*
  echo sudo fstrim requires your password
  sudo fstrim ./

  [Regression Potential]

   * There is very little regression potential as this change simply
  prevents NCQ trim from being used on Samsung 8** drives.

  [Other Info]

   * Commit is upstream.
   * Greatly increasing the timeout for the drives seems to relieve the timeout 
errors.  This may be due to trimming large numbers of sectors with single 
commands.  It may be prudent for future upstream to break up large trims into 
multiple requests on smaller regions.

  ===Original Bug description ==
  Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2131 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  7 20:01:28 2014
  HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
  InstallationDate: Installed on 2014-06-22 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic 
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x: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/1338706/+subscriptions

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

[Kernel-packages] [Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12

[Bernhard]

You can modify single ata channels too like I do, it works fine:

/etc/default/grub
GRUB_CMDLINE_LINUX=libata.force=10:noncq,9:noncq

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

Title:
  Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to
  set xfermode (err_mask=0x40) on upstream kernels = 3.12

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  [Impact]

   * Users with Samsung 8** SSD drives see miscellaneous errors and
  warning messages in the logs depending on the firmware level of the
  drive while booting or after running trim.

  [Test Case]

   * Run this script, and then check logs for errors.
  #!/bin/bash

  git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  for i in {0..10} ; do
   cp -r linux linux$i
  done
  rm -rf linux*
  echo sudo fstrim requires your password
  sudo fstrim ./

  [Regression Potential]

   * There is very little regression potential as this change simply
  prevents NCQ trim from being used on Samsung 8** drives.

  [Other Info]

   * Commit is upstream.
   * Greatly increasing the timeout for the drives seems to relieve the timeout 
errors.  This may be due to trimming large numbers of sectors with single 
commands.  It may be prudent for future upstream to break up large trims into 
multiple requests on smaller regions.

  ===Original Bug description ==
  Samsung SSD 840 Series failed to get NCQ Send/Recv Log Emask 0x1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2131 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul  7 20:01:28 2014
  HibernationDevice: RESUME=UUID=685afcb7-7aa6-4048-af15-091d3bcd3b35
  InstallationDate: Installed on 2014-06-22 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic 
root=UUID=d7c2e1cb-d046-460c-83b8-0cfbb330d095 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3N78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd09/10/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78-EM:rvrRevX.0x: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/1338706/+subscriptions

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

[Kernel-packages] [Bug 1402551] [NEW] High memory usage of Xorg and kwin after Xorg security updates [nvidia]

[Bernhard]

Public bug reported:

Hello,

since the Xorg/nvidia security updates last week, I encounter a problem with 
growing Xorg and kwin memory usage.
In one hour the memory consumption is at Xorg ~ 270 MiB and at kwin: 300 MB , 
so the system responds slowly and scrolling is very slow in in dolphin, kwrite, 
firefox, etc.
After several hours the system is so slow, that only a restart helps, and then 
the growing of memory starts again.

*** My Tests;

I tried several nvidia drivers, but without success (from:
https://launchpad.net/~xorg-
edgers/+archive/ubuntu/ppa/+index?field.series_filter=precise)

304.125-0ubuntu0.0.1~xedgers12.04.1 
331.113-0ubuntu0.0.1~xedgers12.04.1 
346.22-0ubuntu1~xedgers12.04.1
(With purging each nvidia driver and fresh installing it)

*** My configuration;

Two Kubuntu 12.04.5 PCs with a nvidia card; 
nvidia driver 331.113-0ubuntu0.0.0.3 and 304.125-0ubuntu0.0.0.1
One pc with the Trusty Xstack (HWE) with Trusty kernel (3.13.0-43.72~precise1) 
and the other one with the stock kernel (3.2.0-74-generic #109) and stock 
xstack.


I use one pc in my office, so it disturbs my work because of the slowness and 
restarts.

Thank you for your help!

Best regards, Bernhard


*** Problematic packages and other Xorg deps

nvidia-graphics-drivers-331 (331.113-0ubuntu0.0.0.3) precise-security;
urgency=medium

  [ Alberto Milone ]
  * debian/substvars:
- Add support for video ABIs up to 19.
  * debian/templates/dkms_nvidia.conf.in:
- Drop all the patches.
  * SECURITY UPDATE:
- CVE-2014-8091, CVE-2014-8098, CVE-2014-8298 (LP: #1400673).
 -- Alberto Milone email address hidden Tue, 09 Dec 2014 12:10:46 +0100

CVE-2014-8298   RESERVED
CVE-2014-8098   out of bounds access in GLX extension
CVE-2014-8091   denial of service due to unchecked malloc in client 
authentication

nvidia-graphics-drivers-304-updates (304.125-0ubuntu0.0.0.1) 
  
xorg-server-lts-trusty (2:1.15.1-0ubuntu2~precise4) precise-security; 
urgency=medium

  * SECURITY UPDATE: Dec 2014 security issues - additional fixes
- debian/patches/CVE-2014-8xxx/003[4567]*.patch: add additional
  fixes not included in original pre-advisory bundle.
 -- Marc Deslauriers email address hidden Tue, 09 Dec 2014 17:25:15 -0500
 
xorg-server-lts-trusty (2:1.15.1-0ubuntu2~precise3) precise-security; 
urgency=medium

  * SECURITY UPDATE: Dec 2014 protocol handling security issues
- debian/patches/CVE-2014-8xxx/*.patch: patches from upstream to fix
  a multitude of security issues, including a couple of pre-requisite
  fixes from git.
- CVE-2014-8091
- CVE-2014-8092
- CVE-2014-8093
- CVE-2014-8094
- CVE-2014-8095
- CVE-2014-8096
- CVE-2014-8097
- CVE-2014-8098
- CVE-2014-8099
- CVE-2014-8100
- CVE-2014-8101
- CVE-2014-8102
- CVE-2014-8103
 -- Marc Deslauriers email address hidden Sat, 06 Dec 2014 10:28:55 -0500

CVE-2014-8091   denial of service due to unchecked malloc in client 
authentication
CVE-2014-8092   intger overflows in X11 core protocol requests
CVE-2014-8093   integer overflows in GLX extension
CVE-2014-8094   integer overflows in DRI2 extensions
CVE-2014-8095   out of bounds access in XInput extensions
CVE-2014-8096   out of bounds access in XC-MISC extension
CVE-2014-8097   out of bounds access in DBE extension
CVE-2014-8098   out of bounds access in GLX extension
CVE-2014-8099   out of bounds access in XVideo extension
CVE-2014-8100   out of bounds access in Render extension
CVE-2014-8101   out of bounds access in RandR extension
CVE-2014-8102   out of bounds access in XFixes extension
CVE-2014-8103   out of bounds access in DRI3  Present extensions
 
and other Xorg deps

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

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

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xorg-server-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: high kde kwin memory nvidia usage xorg

** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: linux-firmware (Ubuntu) = xorg-server-lts-trusty
(Ubuntu)

** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  High memory usage of Xorg and kwin after Xorg security updates
  [nvidia]

Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  New
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-lts-trusty package in Ubuntu:
  New

[Kernel-packages] [Bug 1402551] Re: High memory usage of Xorg and kwin after Xorg security updates [nvidia]

[Bernhard]

I'm currently testing kernel 3.2.0-73.108 (latest kernel: 3.2.0-74.109). 
So far no problems after two hours, maybe the kernel is the culprit.

*** Changes
linux (3.2.0-74.109) precise; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1400709

  [ Upstream Kernel Changes ]

  * x86_64, traps: Stop using IST for #SS
- LP: #1398795
- CVE-2014-9090
  * x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C
- LP: #1398795
- CVE-2014-9090
  * x86_64, traps: Rework bad_iret
- LP: #1398795
- CVE-2014-9090
  * x86, kvm: Clear paravirt_enabled on KVM guests for espfix32's benefit
- LP: #1400314
- CVE-2014-8134

 -- Luis Henriques luis.henriq...@canonical.com  Tue, 09 Dec 2014
13:55:21 +

linux-lts-trusty (3.13.0-43.72~precise1) precise; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1399807

  [ Upstream Kernel Changes ]

  * x86_64, traps: Fix the espfix64 #DF fixup and rewrite it in C
- LP: #1398795
- CVE-2014-9090
  * x86_64, traps: Rework bad_iret
- LP: #1398795
- CVE-2014-9090
  * x86, kvm: Clear paravirt_enabled on KVM guests for espfix32's benefit
- LP: #1400314
- CVE-2014-8134

 -- Luis Henriques luis.henriq...@canonical.com  Tue, 09 Dec 2014
11:09:22 +

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-8134

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-9090

** Also 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/1402551

Title:
  High memory usage of Xorg and kwin after Xorg security updates
  [nvidia]

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg-server-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  since the Xorg/nvidia security updates last week, I encounter a problem with 
growing Xorg and kwin memory usage.
  In one hour the memory consumption is at Xorg ~ 270 MiB and at kwin: 300 MB , 
so the system responds slowly and scrolling is very slow in in dolphin, kwrite, 
firefox, etc.
  After several hours the system is so slow, that only a restart helps, and 
then the growing of memory starts again.

  *** My Tests;

  I tried several nvidia drivers, but without success (from:
  https://launchpad.net/~xorg-
  edgers/+archive/ubuntu/ppa/+index?field.series_filter=precise)

  304.125-0ubuntu0.0.1~xedgers12.04.1 
  331.113-0ubuntu0.0.1~xedgers12.04.1 
  346.22-0ubuntu1~xedgers12.04.1
  (With purging each nvidia driver and fresh installing it)

  *** My configuration;

  Two Kubuntu 12.04.5 PCs with a nvidia card; 
  nvidia driver 331.113-0ubuntu0.0.0.3 and 304.125-0ubuntu0.0.0.1
  One pc with the Trusty Xstack (HWE) with Trusty kernel 
(3.13.0-43.72~precise1) and the other one with the stock kernel 
(3.2.0-74-generic #109) and stock xstack.

  
  I use one pc in my office, so it disturbs my work because of the slowness and 
restarts.

  Thank you for your help!

  Best regards, Bernhard

  
  *** Problematic packages and other Xorg deps

  nvidia-graphics-drivers-331 (331.113-0ubuntu0.0.0.3) precise-security;
  urgency=medium

[ Alberto Milone ]
* debian/substvars:
  - Add support for video ABIs up to 19.
* debian/templates/dkms_nvidia.conf.in:
  - Drop all the patches.
* SECURITY UPDATE:
  - CVE-2014-8091, CVE-2014-8098, CVE-2014-8298 (LP: #1400673).
   -- Alberto Milone email address hidden Tue, 09 Dec 2014 12:10:46 +0100

  CVE-2014-8298 RESERVED
  CVE-2014-8098 out of bounds access in GLX extension
  CVE-2014-8091 denial of service due to unchecked malloc in client 
authentication

  nvidia-graphics-drivers-304-updates (304.125-0ubuntu0.0.0.1) 

  xorg-server-lts-trusty (2:1.15.1-0ubuntu2~precise4) precise-security; 
urgency=medium

* SECURITY UPDATE: Dec 2014 security issues - additional fixes
  - debian/patches/CVE-2014-8xxx/003[4567]*.patch: add additional
fixes not included in original pre-advisory bundle.
   -- Marc Deslauriers email address hidden Tue, 09 Dec 2014 17:25:15 -0500
   
  xorg-server-lts-trusty (2:1.15.1-0ubuntu2~precise3) precise-security; 
urgency=medium

* SECURITY UPDATE: Dec 2014 protocol handling security issues
  - debian/patches/CVE-2014-8xxx/*.patch: patches from upstream to fix
a multitude of security issues, including a couple of pre-requisite
fixes from git.
  - CVE-2014-8091
  - CVE-2014-8092
  - CVE-2014-8093
  - CVE-2014-8094
  - CVE-2014-8095
  - CVE-2014-8096
  - CVE-2014-8097
  - CVE-2014-8098
  - CVE-2014-8099
  - CVE-2014-8100
  - CVE-2014-8101
  - CVE

[Kernel-packages] [Bug 1402551] Re: High memory usage of Xorg and kwin after Xorg security updates [nvidia]

[Bernhard]

Unfortunately the same problem occurs with kernel 3.2.0-73.108.

Which log files shall I provide?

Sorry, I do not want to grant access/link the pc with launchpad.

** No longer affects: linux (Ubuntu)

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

Title:
  High memory usage of Xorg and kwin after Xorg security updates
  [nvidia]

Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg-server-lts-trusty package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  since the Xorg/nvidia security updates last week, I encounter a problem with 
growing Xorg and kwin memory usage.
  In one hour the memory consumption is at Xorg ~ 270 MiB and at kwin: 300 MB , 
so the system responds slowly and scrolling is very slow in in dolphin, kwrite, 
firefox, etc.
  After several hours the system is so slow, that only a restart helps, and 
then the growing of memory starts again.

  *** My Tests;

  I tried several nvidia drivers, but without success (from:
  https://launchpad.net/~xorg-
  edgers/+archive/ubuntu/ppa/+index?field.series_filter=precise)

  304.125-0ubuntu0.0.1~xedgers12.04.1 
  331.113-0ubuntu0.0.1~xedgers12.04.1 
  346.22-0ubuntu1~xedgers12.04.1
  (With purging each nvidia driver and fresh installing it)

  *** My configuration;

  Two Kubuntu 12.04.5 PCs with a nvidia card; 
  nvidia driver 331.113-0ubuntu0.0.0.3 and 304.125-0ubuntu0.0.0.1
  One pc with the Trusty Xstack (HWE) with Trusty kernel 
(3.13.0-43.72~precise1) and the other one with the stock kernel 
(3.2.0-74-generic #109) and stock xstack.

  
  I use one pc in my office, so it disturbs my work because of the slowness and 
restarts.

  Thank you for your help!

  Best regards, Bernhard

  
  *** Problematic packages and other Xorg deps

  nvidia-graphics-drivers-331 (331.113-0ubuntu0.0.0.3) precise-security;
  urgency=medium

[ Alberto Milone ]
* debian/substvars:
  - Add support for video ABIs up to 19.
* debian/templates/dkms_nvidia.conf.in:
  - Drop all the patches.
* SECURITY UPDATE:
  - CVE-2014-8091, CVE-2014-8098, CVE-2014-8298 (LP: #1400673).
   -- Alberto Milone email address hidden Tue, 09 Dec 2014 12:10:46 +0100

  CVE-2014-8298 RESERVED
  CVE-2014-8098 out of bounds access in GLX extension
  CVE-2014-8091 denial of service due to unchecked malloc in client 
authentication

  nvidia-graphics-drivers-304-updates (304.125-0ubuntu0.0.0.1) 

  xorg-server-lts-trusty (2:1.15.1-0ubuntu2~precise4) precise-security; 
urgency=medium

* SECURITY UPDATE: Dec 2014 security issues - additional fixes
  - debian/patches/CVE-2014-8xxx/003[4567]*.patch: add additional
fixes not included in original pre-advisory bundle.
   -- Marc Deslauriers email address hidden Tue, 09 Dec 2014 17:25:15 -0500
   
  xorg-server-lts-trusty (2:1.15.1-0ubuntu2~precise3) precise-security; 
urgency=medium

* SECURITY UPDATE: Dec 2014 protocol handling security issues
  - debian/patches/CVE-2014-8xxx/*.patch: patches from upstream to fix
a multitude of security issues, including a couple of pre-requisite
fixes from git.
  - CVE-2014-8091
  - CVE-2014-8092
  - CVE-2014-8093
  - CVE-2014-8094
  - CVE-2014-8095
  - CVE-2014-8096
  - CVE-2014-8097
  - CVE-2014-8098
  - CVE-2014-8099
  - CVE-2014-8100
  - CVE-2014-8101
  - CVE-2014-8102
  - CVE-2014-8103
   -- Marc Deslauriers email address hidden Sat, 06 Dec 2014 10:28:55 -0500

  CVE-2014-8091 denial of service due to unchecked malloc in client 
authentication
  CVE-2014-8092 intger overflows in X11 core protocol requests
  CVE-2014-8093 integer overflows in GLX extension
  CVE-2014-8094 integer overflows in DRI2 extensions
  CVE-2014-8095 out of bounds access in XInput extensions
  CVE-2014-8096 out of bounds access in XC-MISC extension
  CVE-2014-8097 out of bounds access in DBE extension
  CVE-2014-8098 out of bounds access in GLX extension
  CVE-2014-8099 out of bounds access in XVideo extension
  CVE-2014-8100 out of bounds access in Render extension
  CVE-2014-8101 out of bounds access in RandR extension
  CVE-2014-8102 out of bounds access in XFixes extension
  CVE-2014-8103 out of bounds access in DRI3  Present extensions
   
  and other Xorg deps

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

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

[Kernel-packages] [Bug 1392829] Re: bluez-test-discovery ERROR:dbus.connection:Exception

[Huck-bernhard]

addition:

if you call bluez-test-discovery few  times stops discoverry of devices  
complete.
I can see a similar behavior at StartDiscovery  with DBUS org.bluez.Adapter 
with QT5 and QDBusInterface
after connecting a device and disconnect because of distance device to long is 
Discovery also stopt. 
after calling: hciconfig reset  is Discovery working again.
this error is only at Ubuntu 14.10. with 14.04 is it working

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

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in “bluez” package in Ubuntu:
  New

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
  Trusted = 0
  Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
File /usr/lib/python3/dist-packages/dbus/connection.py, line 230, in 
maybe_handle_message
  self._handler(*args, **kwargs)
File /usr/bin/bluez-test-discovery, line 15, in device_found
  value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

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

[Kernel-packages] [Bug 1392829] [NEW] bluez-test-discovery ERROR:dbus.connection:Exception

[Huck-bernhard]

Public bug reported:

~$ bluez-test-discovery 
[ 50:85:69:EF:9B:23 ]
Trusted = 0
Class = 0x08043c
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
  File /usr/lib/python3/dist-packages/dbus/connection.py, line 230, in 
maybe_handle_message
self._handler(*args, **kwargs)
  File /usr/bin/bluez-test-discovery, line 15, in device_found
value = unicode(value).encode('ascii', 'replace')
NameError: name 'unicode' is not defined

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: bluez 4.101-0ubuntu20
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Nov 14 19:24:49 2014
InstallationDate: Installed on 2014-11-14 (0 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
InterestingModules: btusb rfcomm bnep bluetooth
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
rfkill:
 1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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


** Tags: amd64 apport-bug utopic

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

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in “bluez” package in Ubuntu:
  New

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
  Trusted = 0
  Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
File /usr/lib/python3/dist-packages/dbus/connection.py, line 230, in 
maybe_handle_message
  self._handler(*args, **kwargs)
File /usr/bin/bluez-test-discovery, line 15, in device_found
  value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To 

[Kernel-packages] [Bug 1392829] Re: bluez-test-discovery ERROR:dbus.connection:Exception

[Huck-bernhard]

this error is only at Ubuntu 14.10 at 14.04 is it working

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

Title:
  bluez-test-discovery ERROR:dbus.connection:Exception

Status in “bluez” package in Ubuntu:
  New

Bug description:
  ~$ bluez-test-discovery 
  [ 50:85:69:EF:9B:23 ]
  Trusted = 0
  Class = 0x08043c
  ERROR:dbus.connection:Exception in handler for D-Bus signal:
  Traceback (most recent call last):
File /usr/lib/python3/dist-packages/dbus/connection.py, line 230, in 
maybe_handle_message
  self._handler(*args, **kwargs)
File /usr/bin/bluez-test-discovery, line 15, in device_found
  value = unicode(value).encode('ascii', 'replace')
  NameError: name 'unicode' is not defined

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluez 4.101-0ubuntu20
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Nov 14 19:24:49 2014
  InstallationDate: Installed on 2014-11-14 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  InterestingModules: btusb rfcomm bnep bluetooth
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. 
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=22d86bc8-8f82-4594-8e4b-10cd3b3ed488 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:02:72:CD:03:2A  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:1318 acl:0 sco:0 events:55 errors:0
TX bytes:1016 acl:0 sco:0 commands:47 errors:0
  rfkill:
   1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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

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

[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep

[Bernhard]

Update to the black-screen-issue after hibernate for the nvidia-driver;

Since kernel update 3.13.0-37.64 I can use MSI-interrupts with the
nvidia module again and the black-screen-issue after hibernate is gone.

Please try this kernel or test kernel parameter nomsi !

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

Title:
  [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from
  sleep

Status in The Linux Kernel:
  Unknown
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Suspend the device
  2. Wake it up

  EXPECTED BEHAVIOUR

  - The device to resume normally

  REAL BEHAVIOUR

  - The screen goes blank

  RELEVANT DETAILS

  - In the /etc/default/grub file; changing quiet splash option to
  nomodeset allows the wakeup, but the computer gets so slow it is
  unusable.

  **
   SOLUTION
  **

  WORK-AROUND

  - Installing the fglrx proprietary package.

  FIX

  - https://bugzilla.kernel.org/show_bug.cgi?id=76761#c3

  REGRESSION POTENTIAL

  - Since this affects an essential hardware component, the regression
  potential is high.

  
   TECHNICAL INFO
  

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

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

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

[Kernel-packages] [Bug 1319457] Re: usb headset causes retire_playback_urb ... callbacks suppressed spam in dmesg

[Bernhard]

For 12.04.x and 14.04 the kernel 3.13.0-32.56 and 31.55 is working!

No messages retire_playback_urb: 829 callbacks suppressed anymore!

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  usb headset causes retire_playback_urb ... callbacks suppressed spam
  in dmesg

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Committed

Bug description:
  With my USB headset plugged in to my computer. When the headset is plugged 
in, I get tens of messages like the following in dmesg and syslog:
  May 14 11:25:24 aether kernel: [  315.447988] retire_playback_urb: 829 
callbacks suppressed
  May 14 11:25:29 aether kernel: [  320.458042] retire_playback_urb: 831 
callbacks suppressed

  The following patch was written to supress these rate-limited messages
  in syslog https://lkml.org/lkml/2014/5/2/156 .

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-26-generic 3.13.0-26.48
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  steve  2643 F pulseaudio
   /dev/snd/controlC1:  steve  2643 F pulseaudio
   /dev/snd/controlC0:  steve  2643 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May 14 11:29:19 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=79084358-087f-4cee-a0be-e2f78361873f
  InstallationDate: Installed on 2013-12-02 (162 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-26-generic 
root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-26-generic N/A
   linux-backports-modules-3.13.0-26-generic  N/A
   linux-firmware 1.127.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (90 days ago)
  dmi.bios.date: 11/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep

[Bernhard]

@Rostislav Stříbrný (rstribrn)

Thank you! 
Adding HIBERNATE_RESUME_POST_VIDEO=no to /etc/pm/config.d/hibernate solved 
for me the problem too.
(Hibernate with 12.04 and NVIDIA driver nvidia-331-updates, kernel 3.13.x)

Best regards, Bernhard

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

Title:
  [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from
  sleep

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  In 14.04 after wakeup from suspend, the notebook screen goes blank
  while the OS and the hardware is awake (I can also press Ctrl+F1 and
  Ctrl+Alt+Del to reboot the system).

  Changeing quiet splash to nomodeset in /etc/default/grub allows
  the wakeup, but the pc is really slow (can't be used).

  WORKAROUND: This problem is not happening with the AMD property
  drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

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

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

[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep

[Bernhard]

Further tests of versions of kernels 3.11 and 3.13, and Xstacks saucy and 
trusty on 12.04 showed only black screens. 
= Now saucy too !!

But I've found a workaround for my config/setup 
(12.04 with kernel and Xstack from trusty with nvidia driver, lightdm with kde, 
and only hibernate used);

Boot your system to lightdm, then login to your Desktop Environment , let it 
finish ...
After that logout back to lightdm screen and login again !
= Now try to hibernate, after the resume there is no black screen anymore and 
you can unlock the screen and use your desktop!!

My résumé after testing is that maybe there is a race condition in the 
services/daemons (acpid, dbus, lightdm) or different bugs are playing together 
(Kernel, X, drivers, daemons). 
That's why I've downgraded lightdm's version in 12.04, but without success, 
only the workaround, described above, helps for me.

Please help to solve this nasty bug, because it is now in 12.04 too !

Maybe lightdm changes? Or system components like dbus? 
= Browsing the lightdm versions in 12.04

lightdm (1.2.3-0ubuntu2.4) precise-proposed; urgency=low

  [ Robert Ancell ]
  * debian/patches/06_config_directory.patch:
- Backport conf.d configuration support (LP: #1190425)

  [ Alberto Milone ]
  * debian/patches/07_add_display-stopped-script.patch:
- Backport support for the display-stopped-script entry
  in the configuration file (LP: #1259237)
 -- Alberto Milone email address hidden Wed, 18 Dec 2013 14:31:49 +0100

lightdm (1.2.3-0ubuntu2.3) precise; urgency=low

  * debian/guest-account: disable screen locking in a more reliable way.
Rather than trying to write a key for another user, while setting up the
guest user account, just set up an autostart desktop that will set it
during the login (lp: #951000)
 -- Sebastien Bacher email address hidden Mon, 08 Jul 2013 13:47:53 +0200

Thanks, Bernhard

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

Title:
  [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from
  sleep

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  In 14.04 after wakeup from suspend, the notebook screen goes blank
  while the OS and the hardware is awake (I can also press Ctrl+F1 and
  Ctrl+Alt+Del to reboot the system).

  Changeing quiet splash to nomodeset in /etc/default/grub allows
  the wakeup, but the pc is really slow (can't be used).

  WORKAROUND: This problem is not happening with the AMD property
  drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri

[Kernel-packages] [Bug 1283938] Re: [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from sleep

[Bernhard]

I have the same problem on 12.04 64bit after installing the trusty
Xstack with

apt-get install -V libglapi-mesa-lts-trusty libgl1-mesa-glx-lts-trusty
xserver-xorg-lts-trusty xserver-xorg-input-all-lts-trusty xserver-xorg-
video-all-lts-trusty libgl1-mesa-dri-lts-trusty x11-xserver-utils-lts-
trusty libglapi-mesa-lts-trusty:i386 libgl1-mesa-dri-lts-trusty:i386
libgl1-mesa-glx-lts-trusty:i386 libgles2-mesa-lts-trusty libglapi-mesa-
lts-trusty mesa-vdpau-drivers-lts-trusty

kernel 3.13.0-30-generic #54~precise2, nvidia-331-updates 331.38-0ubuntu0.0.1 
Xorg message after black screen: (after wake up from hibernate)

(EE) NVIDIA(GPU-0): WAIT: (E, 0, 0x857d)

It seems to be a combination of kernel, Xorg-server, X-components, which
triggers this bug, because without the trusty Xstack there was no black
screen issue with this kernel version.

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

Title:
  [Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after wakeup from
  sleep

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  In 14.04 after wakeup from suspend, the notebook screen goes blank
  while the OS and the hardware is awake (I can also press Ctrl+F1 and
  Ctrl+Alt+Del to reboot the system).

  Changeing quiet splash to nomodeset in /etc/default/grub allows
  the wakeup, but the pc is really slow (can't be used).

  WORKAROUND: This problem is not happening with the AMD property
  drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

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

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

[Kernel-packages] [Bug 258446] Re: 197b:2381 [Acer Aspire 5930] JMicron internal card reader recognizes SD only when inserted at startup

[Bernhard Reiter]

Still not fixed in 3.15-rc8.

uname -a
Linux razor 3.15.0-031500rc8-generic #201406012235 SMP Mon Jun 2 02:36:11 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

What I doe see in dmesg after inserting an SDXC card is:

[ 2847.188289] ACPI: \_SB_.PCI0.RP04: ACPI_NOTIFY_BUS_CHECK event
[ 2847.188349] ACPI: \_SB_.PCI0.RP04: Bus check in hotplug_event()

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

Title:
  197b:2381 [Acer Aspire 5930] JMicron internal card reader recognizes
  SD only when inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 258446] Re: 197b:2381 [Acer Aspire 5930] JMicron internal card reader recognizes SD only when inserted at startup

[Bernhard Reiter]

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

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

Title:
  197b:2381 [Acer Aspire 5930] JMicron internal card reader recognizes
  SD only when inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1319457] Re: usb headset causes retire_playback_urb ... callbacks suppressed spam in dmesg

[Bernhard]

@Joseph Salisbury (jsalisbury);

The kernel, posted in comment #4, fixes the bug! Tested with  Logitech,
Inc. H600 [Wireless Headset].

Please submit an SRU request to include the commit in Trusty stable.

Thanks, Bernhard


** Tags added: verification-done

** Changed in: linux (Ubuntu)
   Status: Incomplete = In Progress

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

Title:
  usb headset causes retire_playback_urb ... callbacks suppressed spam
  in dmesg

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  With my USB headset plugged in to my computer. When the headset is plugged 
in, I get tens of messages like the following in dmesg and syslog:
  May 14 11:25:24 aether kernel: [  315.447988] retire_playback_urb: 829 
callbacks suppressed
  May 14 11:25:29 aether kernel: [  320.458042] retire_playback_urb: 831 
callbacks suppressed

  The following patch was written to supress these rate-limited messages
  in syslog https://lkml.org/lkml/2014/5/2/156 .

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-26-generic 3.13.0-26.48
  ProcVersionSignature: Ubuntu 3.13.0-26.48-generic 3.13.11
  Uname: Linux 3.13.0-26-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  steve  2643 F pulseaudio
   /dev/snd/controlC1:  steve  2643 F pulseaudio
   /dev/snd/controlC0:  steve  2643 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May 14 11:29:19 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=79084358-087f-4cee-a0be-e2f78361873f
  InstallationDate: Installed on 2013-12-02 (162 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-26-generic 
root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-26-generic N/A
   linux-backports-modules-3.13.0-26-generic  N/A
   linux-firmware 1.127.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-02-12 (90 days ago)
  dmi.bios.date: 11/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 258446] Re: 197b:2381 [Acer Aspire 5930] JMicron internal card reader recognizes SD only when inserted at startup

[Bernhard Reiter]

I might've started the party too early.

Now the SD is back to not working unless inserted at startup. Maybe last
time I hadn't really shut down but rebooted from a state in which I had
the SD inserted before, and that lead to a false positive.

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

Title:
  197b:2381 [Acer Aspire 5930] JMicron internal card reader recognizes
  SD only when inserted at startup

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 258446] Re: 197b:2381 [Acer Aspire 5930] JMicron internal card reader recognizes SD only when inserted at startup

[Bernhard Reiter]

Okay, I'm amazed. Updating the BIOS *did* indeed fix my 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/258446

Title:
  197b:2381 [Acer Aspire 5930] JMicron internal card reader recognizes
  SD only when inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 258446] Re: 197b:2381 JMicron internal card reader recognizes SD only when inserted at startup

[Bernhard Reiter]

apport information

** Tags added: apport-collected trusty

** Description changed:

  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with an
  SD card (no alternative media available), the reader is only listed by
  lspci if the SD card is present in the reader at boot time. Boot time
  dmesg attached.
  
  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report
  
  [  164.613053] mmc0: card db81 removed
  
  If I reinsert it, dmesg will say
  
  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1
  
  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.
  
- But nothing of all that happens if the SD card was not already in the
- card reader at boot time!
+ But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  bernie 1491 F pulseaudio
+  /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 14.04
+ HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
+ InstallationDate: Installed on 2013-10-20 (194 days ago)
+ InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
+ MachineType: Acer Aspire 5930
+ Package: linux (not installed)
+ ProcFB: 0 nouveaufb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
+ RelatedPackageVersions:
+  linux-restricted-modules-3.13.0-24-generic N/A
+  linux-backports-modules-3.13.0-24-generic  N/A
+  linux-firmware 1.127
+ Tags:  trusty
+ Uname: Linux 3.13.0-24-generic x86_64
+ UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/13/2008
+ dmi.bios.vendor: Phoenix Technologies LTD
+ dmi.bios.version: V1.15
+ dmi.board.name: Eiger
+ dmi.board.vendor: Acer
+ dmi.board.version: Rev
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Acer
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
+ dmi.product.name: Aspire 5930
+ dmi.product.version: 0100
+ dmi.sys.vendor: Acer

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/258446/+attachment/4104093/+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/258446

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies 

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

[Bernhard Reiter]

apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/258446/+attachment/4104094/+files/BootDmesg.txt

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

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 258446] CurrentDmesg.txt

[Bernhard Reiter]

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/258446/+attachment/4104096/+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/258446

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

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

[Bernhard Reiter]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/258446/+attachment/4104097/+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/258446

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

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

[Bernhard Reiter]

apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/258446/+attachment/4104095/+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/258446

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

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

[Bernhard Reiter]

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/258446/+attachment/4104098/+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/258446

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

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

[Bernhard Reiter]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/258446/+attachment/4104103/+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/258446

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 258446] UdevLog.txt

[Bernhard Reiter]

apport information

** Attachment added: UdevLog.txt
   https://bugs.launchpad.net/bugs/258446/+attachment/4104107/+files/UdevLog.txt

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

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

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

[Bernhard Reiter]

apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/258446/+attachment/4104106/+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/258446

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 258446] Lsusb.txt

[Bernhard Reiter]

apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/258446/+attachment/4104099/+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/258446

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

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

[Bernhard Reiter]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/258446/+attachment/4104108/+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/258446

Title:
  197b:2381 JMicron internal card reader recognizes SD only when
  inserted at startup

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  My Acer Aspire 5930G has an internal 5-in-1 card reader. Testing with
  an SD card (no alternative media available), the reader is only listed
  by lspci if the SD card is present in the reader at boot time. Boot
  time dmesg attached.

  Now if an SD card was present at boot time, I can remove the SD, and
  dmesg will report

  [  164.613053] mmc0: card db81 removed

  If I reinsert it, dmesg will say

  [  179.271670] mmc0: new SD card at address db81
  [  179.276522] mmcblk0: mmc0:db81 SD512 500224KiB 
  [  179.276522]  mmcblk0: p1

  and gnome will display an SD drive icon on my desktop and ask if any
  files should be imported.

  But nothing of all that happens if the SD card was not already in the card 
reader at boot time!
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1491 F pulseaudio
   /dev/snd/pcmC0D0p:   bernie 1491 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4bd38682-1149-4117-8e58-bc8d174dd659
  InstallationDate: Installed on 2013-10-20 (194 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Acer Aspire 5930
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=a23edec1-cabc-4c0b-bdeb-43a79387ed2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.15
  dmi.board.name: Eiger
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.15:bd06/13/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5930
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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