[Kernel-packages] [Bug 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot

[Ken Sharp]

Works fine on Debian Bookworm on GCP too.

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

Title:
  kernel cannot find lz4hc and z3fold modules on boot

Status in cloud-images:
  New
Status in linux-signed-hwe-6.2 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  I've been using zswap without any issues for a while, but fairly
  recently (can't be certain when) the kernel became unable to find the
  modules for lz4hc compression and the z3fold zpool.

  $ egrep 'lz4hc|z3fold' /var/log/syslog
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'lz4hc'
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'z3fold'
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc 
not available, using default lzo
  Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not 
available, using default zbud

  But the modules are in the initrd (as they always have been):

  $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold'
  usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko
  usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko
  usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko

  I'm at a complete loss. If the modules are there, why can't the kernel
  find them?

  Both modules can be loaded (obviously from a different location – not
  the initrd) and the relevant parameters changed with startup scripts
  but this is a workaround not a solution.

  From: https://askubuntu.com/q/1234721/170177

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Sun Dec 10 11:22:41 2023
  Ec2AMI: ami-0008be8e
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: vps2020-starter-1-2-20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2046059/+subscriptions


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

[Kernel-packages] [Bug 1626838] Re: yakkety compiling failed on ubuntu trusty

[Ken Sharp]

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

** Project changed: ubuntu-ubuntu-server => 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/1626838

Title:
  yakkety compiling failed on ubuntu trusty

Status in trusty-backports:
  Won't Fix
Status in Yakkety Backports:
  Won't Fix
Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Hi ubuntu kernel team,

  I am compiling my own ubuntu kernel on ubuntu trusty, and I git clone 
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety,  
the build almost success, but failed at the end with missing modules,  I 
haven't done any change for the source code :
  Then I start a docker container using xenial image,  try the same build 
steps,  I can successfullly build kernel deb pkgs .  Do you have idea why it 
throw missing module error on ubuntu trusty ?  Thanks .

  root@kbuild:~/yakkety# uname -a
  Linux kbuild 3.13.0-58-generic #97-Ubuntu SMP Wed Jul 8 02:56:15 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  root@kbuild:~/yakkety# apt-get build-dep linux-image-4.4.0-36-generic
  root@kbuild:~/yakkety# fakeroot debian/rules clean
  root@kbuild:~/yakkety# AUTOBUILD=1 fakeroot debian/rules binary-generic
  --ignore 
  make[2]: Leaving directory `/root/yakkety/debian/build/build-generic'
  make[1]: Leaving directory `/root/yakkety'
  Debug: module-check-generic
  install -d /root/yakkety/debian.master/abi/4.4.0-34.53/amd64
  find /root/yakkety/debian/build/build-generic/ -name \*.ko | \
  sed -e 's/.*\/\([^\/]*\)\.ko/\1/' | sort > 
/root/yakkety/debian.master/abi/4.4.0-34.53/amd64/generic.modules
  II: Checking modules for generic...
 reading new modules...read 4590 modules.
 reading old modules...
MISS: spl
MISS: splat
MISS: zavl
MISS: zcommon
MISS: zfs
MISS: znvpair
MISS: zpios
MISS: zunicode
read 4598 modules : new(0)  missing(8)
  EE: Missing modules (start begging for mercy)
  make: *** [module-check-generic] Error 1


  
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 23 03:51 seq
   crw-rw 1 root audio 116, 33 Sep 23 03:51 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: OpenStack Foundation OpenStack Nova
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic 
root=UUID=80575ee5-f6ee-41e2-bab6-e4af1c26d1c1 ro nofb nomodeset vga=normal 
console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-58-generic N/A
   linux-backports-modules-3.13.0-58-generic  N/A
   linux-firmware 1.127.16
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty uec-images
  Uname: Linux 3.13.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2015.1.2:cvnBochs:ct1:cvr:
  dmi.product.name: OpenStack Nova
  dmi.product.version: 2015.1.2
  dmi.sys.vendor: OpenStack Foundation

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1626838/+subscriptions


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

[Kernel-packages] [Bug 1727861] Re: kernel BUG at /build/linux-hwe-IJy1zi/linux-hwe-4.10.0/fs/cachefiles/namei.c:164!

[Ken Sharp]

** Tags added: trusty

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

Title:
  kernel BUG at /build/linux-hwe-IJy1zi/linux-
  hwe-4.10.0/fs/cachefiles/namei.c:164!

Status in Linux:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Fix Committed
Status in cachefilesd package in Debian:
  Fix Released

Bug description:
  I have just installed cachefilesd and rebooted. The only change I made
  was the location of the cache - everything else is set to default. The
  cache location exists and is writable.

  I thought I'd test so first attempt:

  $ cat /mnt/server/share/file > /dev/null

  No problem.

  Second attempt:

  $ cat /mnt/server/share/file > /dev/null

  [  471.283546] [ cut here ]
  [  471.288354] kernel BUG at 
/build/linux-hwe-IJy1zi/linux-hwe-4.10.0/fs/cachefiles/namei.c:164!
  [  471.296977] invalid opcode:  [#1] SMP
  [  471.301172] Modules linked in: arc4 md4 cachefiles cifs ccm fscache 
ip6table_filter ip6_tables iptable_filter ip_tables x_tables ppdev pvpanic 
input_leds parport_pc serio_raw parport autofs4 btrfs xor raid6_pq 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 
crypto_simd glue_helper cryptd psmouse virtio_net virtio_scsi
  [  471.332032] CPU: 0 PID: 5 Comm: kworker/u2:0 Not tainted 4.10.0-37-generic 
#41~16.04.1-Ubuntu
  [  471.340656] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [  471.350158] Workqueue: fscache_object fscache_object_work_func [fscache]
  [  471.356972] task: 8ddee426ad00 task.stack: bb3f401b
  [  471.363083] RIP: 0010:cachefiles_walk_to_object+0x718/0x890 [cachefiles]
  [  471.370055] RSP: 0018:bb3f401b3d18 EFLAGS: 00010202
  [  471.375385] RAX: 8ddee18a6201 RBX: 8ddee0b6bd28 RCX: 
00019523
  [  471.382897] RDX: 00019522 RSI: 8ddee621c720 RDI: 
8ddee4001280
  [  471.390234] RBP: bb3f401b3dc8 R08: 0001c720 R09: 
c0459068
  [  471.397468] R10: e66040862980 R11: 97c487ed R12: 
8ddee11750c0
  [  471.404704] R13: 8ddee0b6bd80 R14: 8ddee0b6bd28 R15: 
8ddee1175780
  [  471.411991] FS:  () GS:8ddee620() 
knlGS:
  [  471.420180] CS:  0010 DS:  ES:  CR0: 80050033
  [  471.426037] CR2: 025c4008 CR3: 20b6a000 CR4: 
001406f0
  [  471.433359] DR0:  DR1:  DR2: 

  [  471.440678] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  471.447921] Call Trace:
  [  471.450478]  ? wake_atomic_t_function+0x60/0x60
  [  471.455109]  cachefiles_lookup_object+0x51/0xf0 [cachefiles]
  [  471.460872]  fscache_look_up_object+0xa6/0x1c0 [fscache]
  [  471.466378]  fscache_object_work_func+0x9d/0x200 [fscache]
  [  471.472012]  process_one_work+0x16b/0x4a0
  [  471.476118]  worker_thread+0x4b/0x500
  [  471.479880]  kthread+0x109/0x140
  [  471.483294]  ? process_one_work+0x4a0/0x4a0
  [  471.487577]  ? kthread_create_on_node+0x60/0x60
  [  471.492208]  ret_from_fork+0x2c/0x40
  [  471.495879] Code: 78 ff ff ff 4c 89 f7 49 89 de 48 8b 00 ff 50 58 e9 b5 fc 
ff ff 48 c7 c7 68 b3 45 c0 e8 b5 75 75 d6 31 f6 4c 89 ef e8 bd 2c 00 00 <0f> 0b 
41 bc ff ff ff ff 48 8b 90 98 00 00 00 48 8b bd 78 ff ff 
  [  471.514854] RIP: cachefiles_walk_to_object+0x718/0x890 [cachefiles] RSP: 
bb3f401b3d18
  [  471.523171] ---[ end trace d57820f35931610a ]---

  I tried with the following builds but the result is the same:
  
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/linux-image-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb
  
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc6/linux-image-4.14.0-041400rc6-generic_4.14.0-041400rc6.201710230731_amd64.deb

  I tried setting the cache back to the default of /var/cache/fscache
  and it seemed to start working. I ran the test three or four times.
  Then it failed in the same way.

  I'm running Ubuntu 16.04 on Google Cloud Compute. In case it's a
  filesystem issue:

  $ sudo dumpe2fs -h /dev/sda1
  dumpe2fs 1.42.13 (17-May-2015)
  Filesystem volume name:   cloudimg-rootfs
  Last mounted on:  /
  Filesystem UUID:  67e1c0a6-cdc9-4247-b2e5-dd20ef042025
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery extent flex_bg sparse_super large_file huge_file 
uninit_bg dir_nlink extra_isize
  Filesystem flags: signed_directory_hash 
  Default mount options:user_xattr acl
  Filesystem state: clean
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  128
  Block count:  2621179
  Reserved block count: 0
  Free blocks:  1076375

[Kernel-packages] [Bug 2049317] Re: UBSAN array-index-out-of-bounds error in dmesg - amd gpu drivers

[Ken Sharp]

I've started seeing this for the Virtualbox modules. Could just be a
coincidence but thought I'd mention it.

** Tags added: jammy

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

Title:
  UBSAN array-index-out-of-bounds error in dmesg - amd gpu drivers

Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -a
  System info
  Distributor ID: Ubuntu
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  Codename:   jammy

  uname -a
  Linux dario-Aspire-E5-553G 6.5.0-14-generic #14~22.04.1-Ubuntu SMP 
PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

  
  At boot and in dmesg (and /var/log/syslog) this error appears, repeated 
multiple times, I don't remember seeing it in the past, If necessary I can 
provide the ful /var/log/syslog file:

  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.503732] 

  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.504707] UBSAN: 
array-index-out-of-bounds in 
/build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/processpptables.c:1502:42
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.506717] index 1 is out of 
range for type 'ATOM_PPLIB_CAC_Leakage_Record [1]'
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.507673] CPU: 1 PID: 136 
Comm: systemd-udevd Not tainted 6.5.0-14-generic #14~22.04.1-Ubuntu
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.507677] Hardware name: 
Acer Aspire E5-553G/Wasp_BR, BIOS V1.31 03/28/2018
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.507679] Call Trace:
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.507681]  
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.507684]  
dump_stack_lvl+0x48/0x70
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.507694]  
dump_stack+0x10/0x20
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.507696]  
__ubsan_handle_out_of_bounds+0xc6/0x110
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.507701]  
init_dpm2_parameters+0x2d6/0x360 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.509001]  
pp_tables_initialize+0x12c/0x440 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.510250]  ? 
amdgpu_ring_test_helper+0x83/0x90 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.511425]  
hwmgr_hw_init+0x7b/0x1e0 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.512733]  
pp_hw_init+0x16/0x50 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.513987]  
amdgpu_device_ip_init+0x48d/0x960 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.515143]  
amdgpu_device_init+0x9c8/0x1160 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.516313]  
amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.517507]  
amdgpu_pci_probe+0x182/0x450 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518678]  
local_pci_probe+0x47/0xb0
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518684]  
pci_call_probe+0x55/0x190
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518688]  
pci_device_probe+0x84/0x120
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518692]  
really_probe+0x1cc/0x430
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518696]  
__driver_probe_device+0x8c/0x190
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518709]  
driver_probe_device+0x24/0xd0
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518712]  
__driver_attach+0x10b/0x210
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518715]  ? 
__pfx___driver_attach+0x10/0x10
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518718]  
bus_for_each_dev+0x8d/0xf0
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518723]  
driver_attach+0x1e/0x30
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518727]  
bus_add_driver+0x127/0x240
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518731]  
driver_register+0x5e/0x130
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.518735]  ? 
__pfx_amdgpu_init+0x10/0x10 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.519866]  
__pci_register_driver+0x62/0x70
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.519871]  
amdgpu_init+0x69/0xff0 [amdgpu]
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.521048]  
do_one_initcall+0x5e/0x340
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.521056]  
do_init_module+0x68/0x260
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.521062]  
load_module+0xb85/0xcd0
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.521066]  ? 
security_kernel_post_read_file+0x75/0x90
  Jan 14 20:24:13 dario-Aspire-E5-553G kernel: [   12.521070]  ? 
security_kernel_post_read_file+0x75/0x90
  Jan 14 20:24:13 dario-Aspire-E5-553G 

[Kernel-packages] [Bug 2051418] Re: Error in removing linux-image-6.5.0-14-generic

[Ken Sharp]

** Project changed: subiquity => ubuntu

** Package changed: ubuntu => linux-meta-hwe-6.5 (Ubuntu)

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

Title:
  Error in removing linux-image-6.5.0-14-generic

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

Bug description:
  Here is the error when trying to upgrade Ubuntu:

  $ sudo apt-get autoremove
  [sudo] password for minisforum-um790pro-nicolas: 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
linux-image-6.5.0-14-generic
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  2 not fully installed or removed.
  After this operation, 14.3 MB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 248924 files and directories currently installed.)
  Removing linux-image-6.5.0-14-generic (6.5.0-14.14) ...
  /etc/kernel/postrm.d/initramfs-tools:
  update-initramfs: Deleting /boot/initrd.img-6.5.0-14-generic
  /etc/kernel/postrm.d/zz-update-grub:
  Sourcing file `/etc/default/grub'
  /usr/sbin/grub-mkconfig: 12: /etc/default/grub: processor.max_cstate=1: not 
found
  run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
  dpkg: error processing package linux-image-6.5.0-14-generic (--remove):
   installed linux-image-6.5.0-14-generic package post-removal script 
subprocess returned error exit status 1
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   linux-image-6.5.0-14-generic
  Processing was halted because there were too many errors.
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/libnvidia-gl-535_535.113.01-0ubuntu3_amd64.deb
 ./casper/minimal.standard.live.squashfs
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 10:39:26 2024
  InstallationDate: Installed on 2023-10-29 (90 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  SourcePackage: subiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot

[Ken Sharp]

Noble on LXD works correctly too.

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

Title:
  kernel cannot find lz4hc and z3fold modules on boot

Status in cloud-images:
  New
Status in linux-signed-hwe-6.2 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  I've been using zswap without any issues for a while, but fairly
  recently (can't be certain when) the kernel became unable to find the
  modules for lz4hc compression and the z3fold zpool.

  $ egrep 'lz4hc|z3fold' /var/log/syslog
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'lz4hc'
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'z3fold'
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc 
not available, using default lzo
  Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not 
available, using default zbud

  But the modules are in the initrd (as they always have been):

  $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold'
  usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko
  usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko
  usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko

  I'm at a complete loss. If the modules are there, why can't the kernel
  find them?

  Both modules can be loaded (obviously from a different location – not
  the initrd) and the relevant parameters changed with startup scripts
  but this is a workaround not a solution.

  From: https://askubuntu.com/q/1234721/170177

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Sun Dec 10 11:22:41 2023
  Ec2AMI: ami-0008be8e
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: vps2020-starter-1-2-20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2046059/+subscriptions


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

[Kernel-packages] [Bug 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot

[Ken Sharp]

I tried again in Qemu with 16.04, 20.04, 22.04 and 24.04 and none of
them see this issue.

So I tried with Jammy on LXD and the issue does present itself. So the
issue appears to be with the UEC images.

I also tried Mantic on LXD and it works fine. So something has been
fixed between Jammy and Mantic. I can test others if it will help.

I cannot test Noble as there is no image available for LXD, though I'm
sure it can still be done (somehow).

If the documentation is up to date --> cloud-images.

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

Title:
  kernel cannot find lz4hc and z3fold modules on boot

Status in cloud-images:
  New
Status in linux-signed-hwe-6.2 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  I've been using zswap without any issues for a while, but fairly
  recently (can't be certain when) the kernel became unable to find the
  modules for lz4hc compression and the z3fold zpool.

  $ egrep 'lz4hc|z3fold' /var/log/syslog
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'lz4hc'
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'z3fold'
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc 
not available, using default lzo
  Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not 
available, using default zbud

  But the modules are in the initrd (as they always have been):

  $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold'
  usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko
  usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko
  usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko

  I'm at a complete loss. If the modules are there, why can't the kernel
  find them?

  Both modules can be loaded (obviously from a different location – not
  the initrd) and the relevant parameters changed with startup scripts
  but this is a workaround not a solution.

  From: https://askubuntu.com/q/1234721/170177

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Sun Dec 10 11:22:41 2023
  Ec2AMI: ami-0008be8e
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: vps2020-starter-1-2-20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2046059/+subscriptions


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

[Kernel-packages] [Bug 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot

[Ken Sharp]

I tried again in Qemu with 16.04, 20.04, 22.04 and 24.04 and none of
them see this issue.

So I tried with Jammy on LXD and the issue does present itself. So the
issue appears to be with the UEC images.

I also tried Mantic on LXD and it works fine. So something has been
fixed between Jammy and Mantic. I can test others if it will help.

I cannot test Noble as there is no image available for LXD, though I'm
sure it can still be done (somehow).

If the documentation is up to date --> cloud-image.

** Also affects: cloud-images
   Importance: Undecided
   Status: New

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

Title:
  kernel cannot find lz4hc and z3fold modules on boot

Status in cloud-images:
  New
Status in linux-signed-hwe-6.2 package in Ubuntu:
  New
Status in linux-signed-hwe-6.5 package in Ubuntu:
  New

Bug description:
  I've been using zswap without any issues for a while, but fairly
  recently (can't be certain when) the kernel became unable to find the
  modules for lz4hc compression and the z3fold zpool.

  $ egrep 'lz4hc|z3fold' /var/log/syslog
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'lz4hc'
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'z3fold'
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc 
not available, using default lzo
  Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not 
available, using default zbud

  But the modules are in the initrd (as they always have been):

  $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold'
  usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko
  usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko
  usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko

  I'm at a complete loss. If the modules are there, why can't the kernel
  find them?

  Both modules can be loaded (obviously from a different location – not
  the initrd) and the relevant parameters changed with startup scripts
  but this is a workaround not a solution.

  From: https://askubuntu.com/q/1234721/170177

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Sun Dec 10 11:22:41 2023
  Ec2AMI: ami-0008be8e
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: vps2020-starter-1-2-20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2046059/+subscriptions


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

[Kernel-packages] [Bug 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot

[Ken Sharp]

New kernel, no change.

** Description changed:

  I've been using zswap without any issues for a while, but fairly
  recently (can't be certain when) the kernel became unable to find the
  modules for lz4hc compression and the z3fold zpool.
  
- $ sudo dmesg | grep -E 'z3fold|lz4hc'
- [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
- [0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
- [1.099655] zswap: compressor lz4hc not available, using default lzo
- [1.101349] zswap: zpool z3fold not available, using default zbud
+ $ egrep 'lz4hc|z3fold' /var/log/syslog
+ Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'lz4hc'
+ Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'z3fold'
+ Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
+ Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
+ Jan 25 06:35:11 vps-5d014c2f kernel: [1.128588] zswap: compressor lz4hc 
not available, using default lzo
+ Jan 25 06:35:11 vps-5d014c2f kernel: [1.130368] zswap: zpool z3fold not 
available, using default zbud
  
  But the modules are in the initrd (as they always have been):
  
  $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold'
  usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko
  usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko
  usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko
  
  I'm at a complete loss. If the modules are there, why can't the kernel
  find them?
  
  Both modules can be loaded (obviously from a different location – not
  the initrd) and the relevant parameters changed with startup scripts but
  this is a workaround not a solution.
  
  From: https://askubuntu.com/q/1234721/170177
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Sun Dec 10 11:22:41 2023
  Ec2AMI: ami-0008be8e
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: vps2020-starter-1-2-20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago)

** Also affects: linux-signed-hwe-6.5 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  kernel cannot find lz4hc and z3fold modules on boot

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

Bug description:
  I've been using zswap without any issues for a while, but fairly
  recently (can't be certain when) the kernel became unable to find the
  modules for lz4hc compression and the z3fold zpool.

  $ egrep 'lz4hc|z3fold' /var/log/syslog
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'lz4hc'
  Jan 25 06:35:11 vps-5d014c2f systemd-modules-load[127]: Inserted module 
'z3fold'
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  Jan 25 06:35:11 vps-5d014c2f kernel: [0.020859] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 

[Kernel-packages] [Bug 2047042] Re: BUG: kernel NULL pointer dereference, address: 0000000000000008

[Ken Sharp]

So I ran multiple btrfs scrubs and they all reported no error, but for
some reason my system now works. I still have the incorrect extent
counts but there's no lock-ups. Additional scrubs find nothing wrong.

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

Title:
  BUG: kernel NULL pointer dereference, address: 0008

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

Bug description:
  Yet again my BTRFS root filesystem has failed. There is nothing wrong
  with my hardware - it's been tested over and over.

  I can boot fine (the gods know what damage is done when I do) but
  processes eventually succumb to disk-wait and the whole system ends up
  frozen. Trying to force a shutdown with sysrq+e/i doesn't help as the
  processes are stuck disk-wait.

  [   28.460735] BTRFS error (device sdb3): incorrect extent count for 
13631488; counted 0, expected 1
  [   28.476525] BTRFS error (device sdb3): incorrect extent count for 
431808839680; counted 0, expected 1
  [   28.510255] BTRFS error (device sdb3): incorrect extent count for 
646590758912; counted 5, expected 6
  [   28.512311] BTRFS error (device sdb3): incorrect extent count for 
656254435328; counted 10, expected 11
  [   28.517812] BTRFS error (device sdb3): incorrect extent count for 
684171722752; counted 1, expected 2
  [   28.518855] BTRFS error (device sdb3): incorrect extent count for 
692761657344; counted 0, expected 1
  [   28.787901] BTRFS error (device sdb3): incorrect extent count for 
1032064073728; counted 51, expected 52

  No idea how to fix this. Running a Live DVD, mounting and scrubbing
  shows no errors. Unmounting sticks at disk-wait.

  Running "btrfs check" in a Live DVD shows errors, but I daren't ask it
  to --repair as everyone advises not to, so why this is exists is
  anyone's guess.

  [   50.701078] BUG: kernel NULL pointer dereference, address: 0008
  [   50.701101] #PF: supervisor read access in kernel mode
  [   50.701112] #PF: error_code(0x) - not-present page
  [   50.701124] PGD 0 P4D 0 
  [   50.701134] Oops:  [#1] PREEMPT SMP PTI
  [   50.701146] CPU: 0 PID: 372 Comm: btrfs-transacti Tainted: P   OE  
6.5.0-14-generic #14~22.04.1-Ubuntu
  [   50.701166] Hardware name: LENOVO 0606AD5/LENOVO, BIOS A0KT60AUS 12/15/2016
  [   50.701180] RIP: 0010:assert_eb_page_uptodate+0x2b/0xd0 [btrfs]
  [   50.701317] Code: 1f 44 00 00 55 48 89 e5 41 55 41 54 53 48 8b 47 10 4c 8b 
6f 18 f6 c4 04 75 26 41 81 bd 90 0c 00 00 ff 0f 00 00 49 89 f4 76 2b <48> 8b 46 
08 a8 01 0f 85 82 00 00 00 66 90 49 8b 04 24 a8 04 74 3f
  [   50.701370] RSP: 0018:96de80c0b9d8 EFLAGS: 00010212
  [   50.701394] RAX: 0213 RBX:  RCX: 
1000
  [   50.701419] RDX: 4087 RSI:  RDI: 
8ab9d10a4870
  [   50.701443] RBP: 96de80c0b9f0 R08:  R09: 

  [   50.701468] R10:  R11:  R12: 

  [   50.701492] R13: 8ab9c1189000 R14: 8ab9d10a4870 R15: 
00d0
  [   50.701517] FS:  () GS:8ac8ffa0() 
knlGS:
  [   50.701554] CS:  0010 DS:  ES:  CR0: 80050033
  [   50.701577] CR2: 0008 CR3: 000118366001 CR4: 
000606f0
  [   50.701602] Call Trace:
  [   50.701621]  
  [   50.701640]  ? show_regs+0x6d/0x80
  [   50.701667]  ? __die+0x24/0x80
  [   50.701688]  ? page_fault_oops+0x99/0x1b0
  [   50.701713]  ? kernelmode_fixup_or_oops+0xb2/0x140
  [   50.701736]  ? __bad_area_nosemaphore+0x1a5/0x2c0
  [   50.701758]  ? bad_area_nosemaphore+0x16/0x30
  [   50.701780]  ? do_user_addr_fault+0x2c4/0x6b0
  [   50.701802]  ? exc_page_fault+0x83/0x1b0
  [   50.701826]  ? asm_exc_page_fault+0x27/0x30
  [   50.701852]  ? assert_eb_page_uptodate+0x2b/0xd0 [btrfs]
  [   50.701962]  ? btrfs_search_slot+0x98b/0x1030 [btrfs]
  [   50.702054]  extent_buffer_test_bit+0x51/0xa0 [btrfs]
  [   50.702163]  free_space_test_bit+0xa6/0xe0 [btrfs]
  [   50.702275]  modify_free_space_bitmap+0x106/0x400 [btrfs]
  [   50.702386]  __add_to_free_space_tree+0x88/0xe0 [btrfs]
  [   50.702502]  add_to_free_space_tree+0xaa/0x160 [btrfs]
  [   50.702611]  do_free_extent_accounting+0x52/0x230 [btrfs]
  [   50.702705]  __btrfs_free_extent+0x9df/0x1070 [btrfs]
  [   50.702799]  run_delayed_data_ref+0x8b/0x180 [btrfs]
  [   50.702892]  btrfs_run_delayed_refs_for_head+0x183/0x550 [btrfs]
  [   50.702986]  __btrfs_run_delayed_refs+0xc0/0x150 [btrfs]
  [   50.703080]  btrfs_run_delayed_refs+0x6d/0x1f0 [btrfs]
  [   50.703172]  ? start_transaction+0x252/0x630 [btrfs]
  [   50.703271]  btrfs_commit_transaction+0x6a/0xbb0 [btrfs]
  [   50.703369]  ? start_transaction+0xc8/0x630 [btrfs]
  [   50.703468]  

[Kernel-packages] [Bug 2047042] [NEW] BUG: kernel NULL pointer dereference, address: 0000000000000008

[Ken Sharp]

Public bug reported:

Yet again my BTRFS root filesystem has failed. There is nothing wrong
with my hardware - it's been tested over and over.

I can boot fine (the gods know what damage is done when I do) but
processes eventually succumb to disk-wait and the whole system ends up
frozen. Trying to force a shutdown with sysrq+e/i doesn't help as the
processes are stuck disk-wait.

[   28.460735] BTRFS error (device sdb3): incorrect extent count for 13631488; 
counted 0, expected 1
[   28.476525] BTRFS error (device sdb3): incorrect extent count for 
431808839680; counted 0, expected 1
[   28.510255] BTRFS error (device sdb3): incorrect extent count for 
646590758912; counted 5, expected 6
[   28.512311] BTRFS error (device sdb3): incorrect extent count for 
656254435328; counted 10, expected 11
[   28.517812] BTRFS error (device sdb3): incorrect extent count for 
684171722752; counted 1, expected 2
[   28.518855] BTRFS error (device sdb3): incorrect extent count for 
692761657344; counted 0, expected 1
[   28.787901] BTRFS error (device sdb3): incorrect extent count for 
1032064073728; counted 51, expected 52

No idea how to fix this. Running a Live DVD, mounting and scrubbing
shows no errors. Unmounting sticks at disk-wait.

Running "btrfs check" in a Live DVD shows errors, but I daren't ask it
to --repair as everyone advises not to, so why this is exists is
anyone's guess.

[   50.701078] BUG: kernel NULL pointer dereference, address: 0008
[   50.701101] #PF: supervisor read access in kernel mode
[   50.701112] #PF: error_code(0x) - not-present page
[   50.701124] PGD 0 P4D 0 
[   50.701134] Oops:  [#1] PREEMPT SMP PTI
[   50.701146] CPU: 0 PID: 372 Comm: btrfs-transacti Tainted: P   OE
  6.5.0-14-generic #14~22.04.1-Ubuntu
[   50.701166] Hardware name: LENOVO 0606AD5/LENOVO, BIOS A0KT60AUS 12/15/2016
[   50.701180] RIP: 0010:assert_eb_page_uptodate+0x2b/0xd0 [btrfs]
[   50.701317] Code: 1f 44 00 00 55 48 89 e5 41 55 41 54 53 48 8b 47 10 4c 8b 
6f 18 f6 c4 04 75 26 41 81 bd 90 0c 00 00 ff 0f 00 00 49 89 f4 76 2b <48> 8b 46 
08 a8 01 0f 85 82 00 00 00 66 90 49 8b 04 24 a8 04 74 3f
[   50.701370] RSP: 0018:96de80c0b9d8 EFLAGS: 00010212
[   50.701394] RAX: 0213 RBX:  RCX: 1000
[   50.701419] RDX: 4087 RSI:  RDI: 8ab9d10a4870
[   50.701443] RBP: 96de80c0b9f0 R08:  R09: 
[   50.701468] R10:  R11:  R12: 
[   50.701492] R13: 8ab9c1189000 R14: 8ab9d10a4870 R15: 00d0
[   50.701517] FS:  () GS:8ac8ffa0() 
knlGS:
[   50.701554] CS:  0010 DS:  ES:  CR0: 80050033
[   50.701577] CR2: 0008 CR3: 000118366001 CR4: 000606f0
[   50.701602] Call Trace:
[   50.701621]  
[   50.701640]  ? show_regs+0x6d/0x80
[   50.701667]  ? __die+0x24/0x80
[   50.701688]  ? page_fault_oops+0x99/0x1b0
[   50.701713]  ? kernelmode_fixup_or_oops+0xb2/0x140
[   50.701736]  ? __bad_area_nosemaphore+0x1a5/0x2c0
[   50.701758]  ? bad_area_nosemaphore+0x16/0x30
[   50.701780]  ? do_user_addr_fault+0x2c4/0x6b0
[   50.701802]  ? exc_page_fault+0x83/0x1b0
[   50.701826]  ? asm_exc_page_fault+0x27/0x30
[   50.701852]  ? assert_eb_page_uptodate+0x2b/0xd0 [btrfs]
[   50.701962]  ? btrfs_search_slot+0x98b/0x1030 [btrfs]
[   50.702054]  extent_buffer_test_bit+0x51/0xa0 [btrfs]
[   50.702163]  free_space_test_bit+0xa6/0xe0 [btrfs]
[   50.702275]  modify_free_space_bitmap+0x106/0x400 [btrfs]
[   50.702386]  __add_to_free_space_tree+0x88/0xe0 [btrfs]
[   50.702502]  add_to_free_space_tree+0xaa/0x160 [btrfs]
[   50.702611]  do_free_extent_accounting+0x52/0x230 [btrfs]
[   50.702705]  __btrfs_free_extent+0x9df/0x1070 [btrfs]
[   50.702799]  run_delayed_data_ref+0x8b/0x180 [btrfs]
[   50.702892]  btrfs_run_delayed_refs_for_head+0x183/0x550 [btrfs]
[   50.702986]  __btrfs_run_delayed_refs+0xc0/0x150 [btrfs]
[   50.703080]  btrfs_run_delayed_refs+0x6d/0x1f0 [btrfs]
[   50.703172]  ? start_transaction+0x252/0x630 [btrfs]
[   50.703271]  btrfs_commit_transaction+0x6a/0xbb0 [btrfs]
[   50.703369]  ? start_transaction+0xc8/0x630 [btrfs]
[   50.703468]  transaction_kthread+0x14b/0x1c0 [btrfs]
[   50.703564]  ? __pfx_transaction_kthread+0x10/0x10 [btrfs]
[   50.703662]  kthread+0xf2/0x120
[   50.703685]  ? __pfx_kthread+0x10/0x10
[   50.703707]  ret_from_fork+0x47/0x70
[   50.703730]  ? __pfx_kthread+0x10/0x10
[   50.703752]  ret_from_fork_asm+0x1b/0x30
[   50.703776]  
[   50.703793] Modules linked in: bridge stp llc snd_hda_codec_realtek 
snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio intel_rapl_msr 
intel_rapl_common snd_hda_intel sb_edac snd_intel_dspcfg snd_intel_sdw_acpi 
x86_pkg_temp_thermal intel_powerclamp snd_hda_codec snd_hda_core coretemp 
snd_hwdep crct10dif_pclmul crc32_pclmul polyval_clmulni snd_pcm polyval_generic 
ghash_clmulni_intel kvm_intel 

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

[Ken Sharp]

The mainline kernel mapping has no entry for 6.2
(https://people.canonical.com/~kernel/info/kernel-version-map.html) so I
took a guess and installed https://kernel.ubuntu.com/mainline/v6.2/
(AMD64). Testing this.

I also tried https://kernel.ubuntu.com/mainline/v6.7-rc5/ but the header
package requires a newer libc and so failed. Hence my Nvidia drivers
wouldn't build. So that wasn't an option.

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

Title:
  GpuWatchdog segfault in libcef.so

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the
  same crash can occur in Chrome and Brave.

  In my specific case this occurs when I have switched off my monitor
  and left the computer go idle for a while (I don't know the timings
  exactly and I don't know how to force the situation). The computer
  remains responsive until I log back in from the Mate lock screen
  [note: if I lock my screen I get the light-locker log-in so I do not
  know what causes the machine to choose the Mate lock screen].

  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog
  appears immediately on logging back in.

  For me, this first appears to have occured on Dec 2.

  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e

  I can find no earlier entry in the syslog. My apt history shows
  nothing obvious but I'll attach it anyway.

  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is
  possible (probable) there is a bug in the CEF, but equally it should
  not be able to make a system unresponsive unless there is a bug in the
  kernel or X – this occurs on all kinds of systems with all kinds of
  graphics so the graphics driver seems an unlikely cause. It is not
  unique to Ubuntu but I don't know where to start given all the
  possible components.

  The only upstream reported kernel bug was closed as not enough information 
was supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129

  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  https://askubuntu.com/q/1490916/170177
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  https://unix.stackexchange.com/q/658684/45386
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.

  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Dec  8 07:09:25 2023
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

To manage notifications about 

[Kernel-packages] [Bug 2042877] Re: kernel: r8169 0000:0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).

[Ken Sharp]

Please provide the dmesg log.

You may have better luck with the r8169 binary package.

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
   Status: New => Incomplete

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

Title:
  kernel: r8169 :0d:00.0 enp13s0: rtl_rxtx_empty_cond == 0 (loop:
  42, delay: 100).

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Incomplete

Bug description:
  I tried everything. Manually installed the latest kernel, no luck.

  
  Updated the driver, also no luck.

  Here is my lshw output:

  
  id:   network
  description:  Ethernet interface
  product:  RTL8125 2.5GbE Controller
  vendor:   Realtek Semiconductor Co., Ltd.
  physical id:  0
  bus info:   pci@:0d:00.0
  logical name: enp13s0
  version:  05
  serial:   XXX
  size: 1Gbit/s
  capacity: 1Gbit/s
  width:64 bits
  clock:33MHz
  capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
  configuration:
  autonegotiation   =   on
  broadcast =   yes
  driver=   r8169
  driverversion = 6.2.0-36-generic
  duplex=   full
  firmware  =   rtl8125b-2_0.0.2 07/13/20
  ip=   192.168.0.228
  latency   =   0
  link  =   yes
  multicast =   yes
  port  =   twisted pair
  speed =   1Gbit/s
  resources:
  irq   :   34
  ioport:   f000(size=256)
  memory:   fc70-fc70
  memory:   fc71-fc713fff

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Nov  6 22:37:44 2023
  InstallationDate: Installed on 2023-06-01 (158 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.2
  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-6.2/+bug/2042877/+subscriptions


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

[Kernel-packages] [Bug 2036287] Re: 6.2.0-32 kernel doesn't work with Asus Vivobook

[Ken Sharp]

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
   6.2.0-32 kernel doesn't work with Asus Vivobook

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Fix Released

Bug description:
  I have both kernel 6.2.0-32 and 6.2.0-26 installed on my Asus
  Vivobook. Since 6.2.0-32 install boot has been impossible. I think
  this may be a common problem as I'm seeing issues with Ubuntu:
  https://ubuntuforums.org/showthread.php?t=2490616 and Linux Mint:
  https://forums.linuxmint.com/viewtopic.php?t=403618

  https://askubuntu.com/questions/1485350/booting-ubuntu-22-with-
  kernel-6-2-0-32-is-impossible

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 20:38:11 2023
  InstallationDate: Installed on 2023-01-20 (238 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  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-6.2/+bug/2036287/+subscriptions


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

[Kernel-packages] [Bug 2046071] Re: Brightness control is inoperative

[Ken Sharp]

Which older kernels?

Also see https://wiki.ubuntu.com/Kernel/Bugs

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Brightness control is inoperative

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Incomplete

Bug description:
  I can't control the brightness at, be it from the fn buttons or the GUI.
  The brightness is set to the max level with any way to lower it or control it.
  This problem doesn't exist in older kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 10 17:48:35 2023
  InstallationDate: Installed on 2023-12-07 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-6.2
  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-6.2/+bug/2046071/+subscriptions


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

[Kernel-packages] [Bug 2039755] Re: kernel crashes in CIFS code

[Ken Sharp]

Have you tried the upstream kernel?

Also see https://wiki.ubuntu.com/Kernel/Bugs

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

Title:
  kernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 R12: 9d72ca687800
  Oct 19 13:25:47 1y51573u 

[Kernel-packages] [Bug 2046141] Re: os drivers error view in laptop so i want solution

[Ken Sharp]

What the hell is this supposed to be?

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
   Status: New => Invalid

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
 Assignee: AshimShaheer (ashimsha) => (unassigned)

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

Title:
  os drivers error view in laptop so i want solution

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Invalid

Bug description:
  The text in the image you sent is:

  **Send problem report to the developers?**

  **Package**

  linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1

  **✓ Problem Type**

  Bug

  **
  ApportVersion**

  2.20.11-0ubuntu82.5

  **
  Architecture**

  amd64

  **✓ CasperMD5CheckResult**

  pass

  **✓ CurrentDesktop**

  ubuntu:GNOME

  **  Date**

  Mon Dec 11 13:51:59 2023

  > Dependencies

  **
  DistroRelease**

  Ubuntu 22.04

  **✓ InstallationDate**

  Installed on 2023-12-04 (7 days ago)

  **  InstallationMedia**

  Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)

  **✓ PackageArchitecture**

  amd64

  > ProcCpuinfoMinimal

  > ProcEnviron

  **✓ ProcVersionSignature**

  Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16

  **
  SourcePackage**

  linux-signed-hwe-6.2

  **✓ Tags**

  jammy wayland-session

  **✓ Uname**

  Linux 6.2.0-37-generic x86_64

  **✓ UpgradeStatus**

  No upgrade log present (probably fresh install)

  **Note:** The `>` symbol at the beginning of two lines indicates that
  the information on those lines is optional.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 13:27:04 2023
  InstallationDate: Installed on 2023-12-04 (7 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  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-6.2/+bug/2046141/+subscriptions


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

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

[Ken Sharp]

I left the computer to lock itself and killed all steamwebhelper
processes before attempting to log in. The system once again became
unusable but no segault occurred.

It's possible the segfault is a symptom rather than a cure. Nonetheless
there are no logs to help debug any further.

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

Title:
  GpuWatchdog segfault in libcef.so

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the
  same crash can occur in Chrome and Brave.

  In my specific case this occurs when I have switched off my monitor
  and left the computer go idle for a while (I don't know the timings
  exactly and I don't know how to force the situation). The computer
  remains responsive until I log back in from the Mate lock screen
  [note: if I lock my screen I get the light-locker log-in so I do not
  know what causes the machine to choose the Mate lock screen].

  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog
  appears immediately on logging back in.

  For me, this first appears to have occured on Dec 2.

  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e

  I can find no earlier entry in the syslog. My apt history shows
  nothing obvious but I'll attach it anyway.

  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is
  possible (probable) there is a bug in the CEF, but equally it should
  not be able to make a system unresponsive unless there is a bug in the
  kernel or X – this occurs on all kinds of systems with all kinds of
  graphics so the graphics driver seems an unlikely cause. It is not
  unique to Ubuntu but I don't know where to start given all the
  possible components.

  The only upstream reported kernel bug was closed as not enough information 
was supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129

  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  https://askubuntu.com/q/1490916/170177
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  https://unix.stackexchange.com/q/658684/45386
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.

  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Dec  8 07:09:25 2023
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

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


-- 

[Kernel-packages] [Bug 2039755] Re: kernel crashes in CIFS code

[Ken Sharp]

** Summary changed:

- lernel crashes in CIFS code
+ kernel crashes in CIFS code

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

Title:
  kernel crashes in CIFS code

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  I've had several crashes like this on 2 different systems mounting the
  same SMB server.

  
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030468] [ cut here 
]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030477] WARNING: CPU: 2 PID: 5411 at 
fs/cifs/connect.c:1979 __cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030684] Modules linked in: nls_utf8 
cifs cifs_arc4 cifs_md4 fscache netfs ccm xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_u
  ser xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge 
stp llc rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_hda_codec_hdmi 
overlay zram snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel 
soundw
  ire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core 
snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus mei_pxp mei_hdcp 
snd_soc_core snd_ctl_
  led snd_compress intel_tcc_cooling ac97_bus snd_hda_codec_realtek 
snd_pcm_dmaengine snd_hda_codec_generic x86_pkg_temp_thermal intel_rapl_msr 
binfmt_misc intel_powerclamp joydev coretemp snd_hda_intel dell_rbtn 
snd_intel_dspcfg snd_inte
  l_sdw_acpi kvm_intel snd_hda_codec snd_hda_core snd_hwdep dell_laptop 
dell_smm_hwmon
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030844]  nls_iso8859_1 kvm snd_pcm 
irqbypass snd_seq_midi rapl snd_seq_midi_event intel_cstate dell_wmi 
snd_rawmidi serio_raw uvcvideo typec_displayport dell_wmi_sysman dell_smbios 
snd_seq iwlmvm
  btusb dcdbas btrtl snd_seq_device firmware_attributes_class ledtrig_audio 
dell_wmi_descriptor videobuf2_vmalloc wmi_bmof intel_wmi_thunderbolt btbcm 
mac80211 snd_timer videobuf2_memops cmdlinepart videobuf2_v4l2 btintel spi_nor 
snd btmt
  k mtd libarc4 soundcore videodev bluetooth 
processor_thermal_device_pci_legacy hid_sensor_custom_intel_hinge 
hid_sensor_als input_leds hid_sensor_gyro_3d videobuf2_common hid_multitouch 
processor_thermal_device iwlwifi hid_sensor_trigge
  r mc ecdh_generic processor_thermal_rfim industrialio_triggered_buffer 
processor_thermal_mbox kfifo_buf mei_me ecc hid_sensor_iio_common cfg80211 
processor_thermal_rapl mei industrialio intel_rapl_common intel_soc_dts_iosf 
intel_pch_the
  rmal int3403_thermal int340x_thermal_zone mac_hid int3400_thermal intel_hid 
sparse_keymap
  Oct 19 13:25:47 1y51573u kernel: [ 1103.030992]  soc_button_array 
acpi_thermal_rel acpi_pad sch_fq_codel msr parport_pc ppdev lp parport 
efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
libcrc32c r8153_ecm cdc_et
  her usbnet r8152 dm_crypt mii usbhid hid_sensor_custom hid_sensor_hub 
intel_ishtp_hid i915 drm_buddy i2c_algo_bit hid_generic ttm crct10dif_pclmul 
drm_display_helper crc32_pclmul cec polyval_clmulni rc_core polyval_generic 
ghash_clmulni
  _intel drm_kms_helper sha512_ssse3 syscopyarea aesni_intel sysfillrect 
rtsx_pci_sdmmc nvme sysimgblt intel_lpss_pci spi_intel_pc
  i i2c_i801 ucsi_acpi intel_lpss crypto_simd nvme_core i2c_smbus xhci_pci 
typec_ucsi spi_intel drm intel_ish_ipc psmouse thunderbolt nvme_common 
i2c_hid_acpi rtsx_pci xhci_pci_renesas idma64 cryptd typec intel_ishtp i2c_hid 
hid video wmi pinctrl_cannonlake z3fold zstd
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031153] CPU: 2 PID: 5411 Comm: 
kworker/2:1 Not tainted 6.2.0-34-generic #34~22.04.1-Ubuntu
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031162] Hardware name: Dell Inc. 
Latitude 7410/0M5G57, BIOS 1.24.0 07/06/2023
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031167] Workqueue: events 
delayed_mntput
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031180] RIP: 
0010:__cifs_put_smb_ses+0x3dd/0x4d0 [cifs]
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031364] Code: e8 48 c7 c1 70 32 fe c1 
48 c7 c2 30 e4 00 c2 41 89 c1 48 c7 c6 68 7f ff c1 48 c7 c7 d0 47 05 c2 e8 a8 
b5 4f de e9 21 ff ff ff <0f> 0b e9 a6 fc ff ff 49 8d 5e 20 48 89 df e8 00 47 d4 
de 48 c7 c6
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031371] RSP: 0018:b01c50b9bd38 
EFLAGS: 00010286
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031378] RAX:  RBX: 
9d72da1353c0 RCX: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031383] RDX:  RSI: 
 RDI: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031387] RBP: b01c50b9bd68 R08: 
 R09: 
  Oct 19 13:25:47 1y51573u kernel: [ 1103.031391] R10:  R11: 
 R12: 9d72ca687800
  Oct 19 13:25:47 1y51573u kernel: 

[Kernel-packages] [Bug 2046059] Re: kernel cannot find lz4hc and z3fold modules on boot

[Ken Sharp]

** Description changed:

- I've been using zswap without any issues for a while, but on upgrading
- from 18.04 to 22.04 (via 20.04) the kernel starting failing to find the
+ I've been using zswap without any issues for a while, but fairly
+ recently (can't be certain when) the kernel became unable to find the
  modules for lz4hc compression and the z3fold zpool.
  
  $ sudo dmesg | grep -E 'z3fold|lz4hc'
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  [0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  [1.099655] zswap: compressor lz4hc not available, using default lzo
  [1.101349] zswap: zpool z3fold not available, using default zbud
  
  But the modules are in the initrd (as they always have been):
  
  $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold'
  usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko
  usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko
  usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko
  
  I'm at a complete loss. If the modules are there, why can't the kernel
  find them?
  
  Both modules can be loaded (obviously from a different location – not
  the initrd) and the relevant parameters changed with startup scripts but
  this is a workaround not a solution.
  
  From: https://askubuntu.com/q/1234721/170177
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Sun Dec 10 11:22:41 2023
  Ec2AMI: ami-0008be8e
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: vps2020-starter-1-2-20
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago)

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

Title:
  kernel cannot find lz4hc and z3fold modules on boot

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

Bug description:
  I've been using zswap without any issues for a while, but fairly
  recently (can't be certain when) the kernel became unable to find the
  modules for lz4hc compression and the z3fold zpool.

  $ sudo dmesg | grep -E 'z3fold|lz4hc'
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  [0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  [1.099655] zswap: compressor lz4hc not available, using default lzo
  [1.101349] zswap: zpool z3fold not available, using default zbud

  But the modules are in the initrd (as they always have been):

  $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold'
  usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko
  usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko
  usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko

  I'm at a complete loss. If the modules are there, why can't the kernel
  find them?

  Both modules can be loaded (obviously from a different location – not
  the initrd) and the relevant parameters changed with startup scripts
  but this is a workaround not a solution.

  From: https://askubuntu.com/q/1234721/170177

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  

[Kernel-packages] [Bug 2036271] Re: Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

[Ken Sharp]

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Ubuntu 22.04.3 fails to boot with Linux Kernel 6.2.0-32-generic

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Fix Released

Bug description:
  My Ubuntu installation fails to boot with the kernel 6.2.0-32-generic
  on a Lenovo Ideapad Flex 5 14ALC05

  The Ubuntu splash screen appear with the loader but the boot process
  is stuck there (with the loader still animating)

  No problem when booting with the kernel 6.2.0-26-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 15 19:22:42 2023
  InstallationDate: Installed on 2021-08-26 (750 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (511 days ago)

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


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

[Kernel-packages] [Bug 2046059] [NEW] kernel cannot find lz4hc and z3fold modules on boot

[Ken Sharp]

Public bug reported:

I've been using zswap without any issues for a while, but on upgrading
from 18.04 to 22.04 (via 20.04) the kernel starting failing to find the
modules for lz4hc compression and the z3fold zpool.

$ sudo dmesg | grep -E 'z3fold|lz4hc'
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
[0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
[1.099655] zswap: compressor lz4hc not available, using default lzo
[1.101349] zswap: zpool z3fold not available, using default zbud

But the modules are in the initrd (as they always have been):

$ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold'
usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko
usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko
usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko

I'm at a complete loss. If the modules are there, why can't the kernel
find them?

Both modules can be loaded (obviously from a different location – not
the initrd) and the relevant parameters changed with startup scripts but
this is a workaround not a solution.

From: https://askubuntu.com/q/1234721/170177

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: openstack
CloudName: openstack
CloudPlatform: openstack
CloudSubPlatform: metadata (http://169.254.169.254)
Date: Sun Dec 10 11:22:41 2023
Ec2AMI: ami-0008be8e
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: vps2020-starter-1-2-20
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: Upgraded to jammy on 2022-08-15 (482 days ago)

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


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

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

Title:
  kernel cannot find lz4hc and z3fold modules on boot

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

Bug description:
  I've been using zswap without any issues for a while, but on upgrading
  from 18.04 to 22.04 (via 20.04) the kernel starting failing to find
  the modules for lz4hc compression and the z3fold zpool.

  $ sudo dmesg | grep -E 'z3fold|lz4hc'
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  [0.021736] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-37-generic 
root=PARTUUID=948a082e-cfd1-43af-bc7b-3e0b9b20370e ro console=tty1 
console=ttyS0 zswap.enabled=1 zswap.compressor=lz4hc zswap.max_pool_percent=60 
zswap.zpool=z3fold transparent_hugepage=always panic=-1
  [1.099655] zswap: compressor lz4hc not available, using default lzo
  [1.101349] zswap: zpool z3fold not available, using default zbud

  But the modules are in the initrd (as they always have been):

  $ lsinitramfs /boot/initrd.img | grep -E 'lz4hc|z3fold'
  usr/lib/modules/6.2.0-37-generic/kernel/crypto/lz4hc.ko
  usr/lib/modules/6.2.0-37-generic/kernel/lib/lz4/lz4hc_compress.ko
  usr/lib/modules/6.2.0-37-generic/kernel/mm/z3fold.ko

  I'm at a complete loss. If the modules are there, why can't the kernel
  find them?

  Both modules can be loaded (obviously from a different location – not
  the initrd) and the relevant parameters changed with startup scripts
  but this is a workaround not a solution.

  From: https://askubuntu.com/q/1234721/170177

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: openstack
  CloudName: openstack
  CloudPlatform: openstack
  CloudSubPlatform: metadata (http://169.254.169.254)
  Date: Sun Dec 10 11:22:41 2023
  Ec2AMI: ami-0008be8e
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

[Ken Sharp]

** Description changed:

  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded Framework
  (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash
  can occur in Chrome and Brave.
  
  In my specific case this occurs when I have switched off my monitor and
  left the computer go idle for a while (I don't know the timings exactly
  and I don't know how to force the situation). The computer remains
  responsive until I log back in from the Mate lock screen [note: if I
  lock my screen I get the light-locker log-in so I do not know what
  causes the machine to choose the Mate lock screen].
  
  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog appears
  immediately on logging back in.
  
  For me, this first appears to have occured on Dec 2.
  
  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e
  
  I can find no earlier entry in the syslog. My apt history shows nothing
  obvious but I'll attach it anyway.
  
  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is possible
  (probable) there is a bug in the CEF, but equally it should not be able
  to make a system unresponsive unless there is a bug in the kernel or X –
  this occurs on all kinds of systems with all kinds of graphics so the
  graphics driver seems an unlikely cause. It is not unique to Ubuntu but
  I don't know where to start given all the possible components.
  
- The only bug reported kernel bug was closed as not enough information was 
supplied:
+ The only upstream reported kernel bug was closed as not enough information 
was supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129
  
  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286
  
  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  https://askubuntu.com/q/1490916/170177
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  https://unix.stackexchange.com/q/658684/45386
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/
  
  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.
  
  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Dec  8 07:09:25 2023
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

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

Title:
  GpuWatchdog segfault in libcef.so

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Confirmed

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the
  same crash can occur in Chrome and Brave.

  In my specific case this occurs when I have 

[Kernel-packages] [Bug 2043136] Re: Bluetooth prpblem

[Ken Sharp]

** Changed in: linux-signed-hwe-6.2 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Bluetooth prpblem

Status in linux-signed-hwe-6.2 package in Ubuntu:
  Incomplete

Bug description:
  It is always disconnected, I tried with Shell and Blueman, but both
  are not good.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-36-generic 6.2.0-36.37~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 22:42:12 2023
  InstallationDate: Installed on 2023-08-10 (90 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: linux-signed-hwe-6.2
  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-6.2/+bug/2043136/+subscriptions


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

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

[Ken Sharp]

** Description changed:

  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded Framework
- (CEF) [Steam, Code, Spotify, Teams...]. Indeed the same crash can occur
- in Chrome and Brave.
+ (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash
+ can occur in Chrome and Brave.
  
  In my specific case this occurs when I have switched off my monitor and
  left the computer go idle for a while (I don't know the timings exactly
  and I don't know how to force the situation). The computer remains
  responsive until I log back in from the Mate lock screen [note: if I
  lock my screen I get the light-locker log-in so I do not know what
  causes the machine to choose the Mate lock screen].
  
  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog appears
  immediately on logging back in.
  
  For me, this first appears to have occured on Dec 2.
  
  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e
  
  I can find no earlier entry in the syslog. My apt history shows nothing
  obvious but I'll attach it anyway.
  
  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is possible
  (probable) there is a bug in the CEF, but equally it should not be able
  to make a system unresponsive unless there is a bug in the kernel or X –
  this occurs on all kinds of systems with all kinds of graphics so the
  graphics driver seems an unlikely cause. It is not unique to Ubuntu but
  I don't know where to start given all the possible components.
  
  The only bug reported kernel bug was closed as not enough information was 
supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129
  
  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286
  
  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  
https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  
https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/
  
  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.
  
  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Dec  8 07:09:25 2023
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

** Description changed:

  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded Framework
  (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the same crash
  can occur in Chrome and Brave.
  
  In my specific case this occurs when I have switched off my monitor and
  left the computer go idle for a while (I don't know the timings exactly
  and I don't know how to force the 

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

[Ken Sharp]

To make Electron aware:
https://github.com/electron/electron/issues/40732

** Bug watch added: github.com/electron/electron/issues #40732
   https://github.com/electron/electron/issues/40732

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

Title:
  GpuWatchdog segfault in libcef.so

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

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, Teams, Discord...]. Indeed the
  same crash can occur in Chrome and Brave.

  In my specific case this occurs when I have switched off my monitor
  and left the computer go idle for a while (I don't know the timings
  exactly and I don't know how to force the situation). The computer
  remains responsive until I log back in from the Mate lock screen
  [note: if I lock my screen I get the light-locker log-in so I do not
  know what causes the machine to choose the Mate lock screen].

  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog
  appears immediately on logging back in.

  For me, this first appears to have occured on Dec 2.

  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e

  I can find no earlier entry in the syslog. My apt history shows
  nothing obvious but I'll attach it anyway.

  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is
  possible (probable) there is a bug in the CEF, but equally it should
  not be able to make a system unresponsive unless there is a bug in the
  kernel or X – this occurs on all kinds of systems with all kinds of
  graphics so the graphics driver seems an unlikely cause. It is not
  unique to Ubuntu but I don't know where to start given all the
  possible components.

  The only bug reported kernel bug was closed as not enough information was 
supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129

  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  
https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  
https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.

  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Dec  8 07:09:25 2023
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2045951] Re: GpuWatchdog segfault in libcef.so

[Ken Sharp]

** Attachment added: "apt history.log.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2045951/+attachment/5727428/+files/history.log.1.gz

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

Title:
  GpuWatchdog segfault in libcef.so

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

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, Teams...]. Indeed the same
  crash can occur in Chrome and Brave.

  In my specific case this occurs when I have switched off my monitor
  and left the computer go idle for a while (I don't know the timings
  exactly and I don't know how to force the situation). The computer
  remains responsive until I log back in from the Mate lock screen
  [note: if I lock my screen I get the light-locker log-in so I do not
  know what causes the machine to choose the Mate lock screen].

  Upon logging back in the system becomes unresponsive. I can access the
  machine over SSH and force a reboot. The segfault in GpuWatchdog
  appears immediately on logging back in.

  For me, this first appears to have occured on Dec 2.

  Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 
ip 7efc77192336 sp 7efc6b9fd370 error 6 in 
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
  Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d 
cf 00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 
7d b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 
5d 41 5e

  I can find no earlier entry in the syslog. My apt history shows
  nothing obvious but I'll attach it anyway.

  This GpuWatchdog segfault in libcef.so seems to occur a surprising
  amount around the Internet but the trigger seems to vary. Nonetheless
  CEF shouldn't be causing systems to become unresponsive. It is
  possible (probable) there is a bug in the CEF, but equally it should
  not be able to make a system unresponsive unless there is a bug in the
  kernel or X – this occurs on all kinds of systems with all kinds of
  graphics so the graphics driver seems an unlikely cause. It is not
  unique to Ubuntu but I don't know where to start given all the
  possible components.

  The only bug reported kernel bug was closed as not enough information was 
supplied:
  https://bugzilla.kernel.org/show_bug.cgi?id=209129

  This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
  https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

  From around the Interwebs:
  https://bbs.archlinux.org/viewtopic.php?id=263124
  
https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
  https://github.com/ValveSoftware/steam-for-linux/issues/7370
  https://github.com/ValveSoftware/steam-for-linux/issues/9793
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
  
https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault
  
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

  For testing I tried the following but couldn't trigger this manually:
  Windows+L to lock screen, switch monitor off, switch back on and log back in.
  Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
  xset dpms force off then wake the screen up.

  Any ideas how to continue would be greatly appreciated.
  I'll test the upstream kernel and report back. Might take a day or two. I'm 
not 100% convinced it's a kernel bug at this point though.
  I also note the --disable-gpu-* options for CEF which I'll also test.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Dec  8 07:09:25 2023
  SourcePackage: linux-signed-hwe-6.2
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

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


-- 

[Kernel-packages] [Bug 2045951] [NEW] GpuWatchdog segfault in libcef.so

[Ken Sharp]

Public bug reported:

The GpuWatchdog can segfault when using apps that use Electron
(https://www.electronjs.org/) which uses the Chromium Embedded Framework
(CEF) [Steam, Code, Spotify, Teams...]. Indeed the same crash can occur
in Chrome and Brave.

In my specific case this occurs when I have switched off my monitor and
left the computer go idle for a while (I don't know the timings exactly
and I don't know how to force the situation). The computer remains
responsive until I log back in from the Mate lock screen [note: if I
lock my screen I get the light-locker log-in so I do not know what
causes the machine to choose the Mate lock screen].

Upon logging back in the system becomes unresponsive. I can access the
machine over SSH and force a reboot. The segfault in GpuWatchdog appears
immediately on logging back in.

For me, this first appears to have occured on Dec 2.

Dec  2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip 
7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000] 
likely on CPU 3 (core 3, socket 0)
Dec  2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf 
00 79 09 48 8b 7d b8 e8 be 65 2c 03 41 8b 84 24 e0 00 00 00 89 45 b8 48 8d 7d 
b8 e8 ca d7 b5 fb  04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 
41 5e

I can find no earlier entry in the syslog. My apt history shows nothing
obvious but I'll attach it anyway.

This GpuWatchdog segfault in libcef.so seems to occur a surprising
amount around the Internet but the trigger seems to vary. Nonetheless
CEF shouldn't be causing systems to become unresponsive. It is possible
(probable) there is a bug in the CEF, but equally it should not be able
to make a system unresponsive unless there is a bug in the kernel or X –
this occurs on all kinds of systems with all kinds of graphics so the
graphics driver seems an unlikely cause. It is not unique to Ubuntu but
I don't know where to start given all the possible components.

The only bug reported kernel bug was closed as not enough information was 
supplied:
https://bugzilla.kernel.org/show_bug.cgi?id=209129

This has been reported for Ubuntu a number of times but I thought it best to 
start fresh:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1896560
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294
https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1903203
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1921286

From around the Interwebs:
https://bbs.archlinux.org/viewtopic.php?id=263124
https://askubuntu.com/questions/1490916/gpuwatchdog-segfault-error-6-in-libcef-so-likely-on-cpu-15-core-7-socket-0
https://github.com/ValveSoftware/steam-for-linux/issues/7370
https://github.com/ValveSoftware/steam-for-linux/issues/9793
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040399
https://unix.stackexchange.com/questions/658684/ms-teams-makes-the-whole-gui-stall-gpuwatchdog-segfault
https://www.linuxquestions.org/questions/linux-software-2/kde-plasma-on-wayland-hardware-acceleration-lock-ups-4175718801/

For testing I tried the following but couldn't trigger this manually:
Windows+L to lock screen, switch monitor off, switch back on and log back in.
Windows+L to lock screen, switch monitor off, switch back on, choose "Switch 
user" and log back in.
xset dpms force off then wake the screen up.

Any ideas how to continue would be greatly appreciated.
I'll test the upstream kernel and report back. Might take a day or two. I'm not 
100% convinced it's a kernel bug at this point though.
I also note the --disable-gpu-* options for CEF which I'll also test.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.2.0-37-generic 6.2.0-37.38~22.04.1
ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Fri Dec  8 07:09:25 2023
SourcePackage: linux-signed-hwe-6.2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

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


** Tags: amd64 apport-bug jammy

** Attachment added: "apt history.log"
   
https://bugs.launchpad.net/bugs/2045951/+attachment/5727424/+files/history.log

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

Title:
  GpuWatchdog segfault in libcef.so

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

Bug description:
  The GpuWatchdog can segfault when using apps that use Electron
  (https://www.electronjs.org/) which uses the Chromium Embedded
  Framework (CEF) [Steam, Code, Spotify, 

[Kernel-packages] [Bug 1903203] Re: System becomes un-responsive due to gpu segfault

[Ken Sharp]

** Package changed: syslog-ng (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/1903203

Title:
  System becomes un-responsive due to gpu segfault

Status in linux package in Ubuntu:
  New

Bug description:
  I was using:
  Ubuntu 20.04 (installed a month ago, updated recently)
  Vmware Workstation 16 (Ubuntu 20.04 VM)
  Nvidia GTX 1080 TI Driver Version: 450.80.02 CUDA Version: 11.0

  What happened:
  System instantly became unresponsive. Mouse stopped moving, keyboard had no 
effect (tried ALT+F2). I had to press and hold the power button until the 
system hard reset. This is the second time I observed this type issue, but last 
time, the mouse would move with extreme lag.

  /var/log/syslog:
  Nov  5 11:54:37 eypc crash_20201105115437_38.dmp[0]: Uploading dump 
(out-of-process)#012/tmp/dumps/crash_20201105115437_38.dmp
  Nov  5 11:54:38 eypc crash_20201105115437_38.dmp[0]: Finished uploading 
minidump (out-of-process): success = yes
  Nov  5 11:54:38 eypc crash_20201105115437_38.dmp[0]: response: 
CrashID=bp-373c5190-00a9-43c1-aa4c-80c4a2201105
  Nov  5 11:54:38 eypc crash_20201105115437_38.dmp[0]: file 
''/tmp/dumps/crash_20201105115437_38.dmp'', upload yes: 
''CrashID=bp-373c5190-00a9-43c1-aa4c-80c4a2201105''
  Nov  5 11:55:02 eypc kernel: [47695.080487] GpuWatchdog[35222]: segfault at 0 
ip 7f3832af62dd sp 7f38278c34d0 error 6 in 
libcef.so[7f382ed7+69a4000]
  Nov  5 11:55:02 eypc kernel: [47695.080492] Code: 00 79 09 48 8b 7d a0 e8 21 
80 c1 02 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 ef be 
01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 c1 a5 37 03 01 80 
bd 7f ff

  Since the computer restarted, the log saved in /tmp is gone.

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


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

[Kernel-packages] [Bug 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu

[Ken Sharp]

Are you still having this issue?

** Tags added: amd64 bionic

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

Title:
  Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060
  intel gpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell
  Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630
  (Coffeelake 3x8 GT2).

  I had chrome, slack and vmware-player running in Gnome. While doing
  some git clone, screen+mouse+keyboard froze for 2 minutes after which
  xorg and everything else recovered. I saw this in dmesg:

  kernel: show_signal_msg: 2 callbacks suppressed
  kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 
7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000]
  kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 
5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30  04 25 00 00 
00 00 37 13 00 00 c6 05 c1 6d 
  kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting
  kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: Abort status: 0x0
  kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller
  kernel: nvme nvme0: 12/0/0 default/read/poll queues

  While writing this bug report, the system froze again, and this time
  it didn't recover. After a cold reset I didn't see any other
  GpuWatchdog messages in journalctl.

  Ubuntu applied a BIOS firmware update before the first freeze, so my
  BIOS was updated as part of the cold reset I did. Not sure if this is
  relevant to reproducing the freeze.

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


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

[Kernel-packages] [Bug 2027846] Re: tmpfs: Deleted files keep reappearing

[Ken Sharp]

Stupidity on my part. Pure stupidity.

/tmp/wine/wine64/wine is a symlink back into the git directory!

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

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

Title:
  tmpfs: Deleted files keep reappearing

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I am trying to do a number of compilations, including bisects, etc. As
  part of the process I delete all the files from a compilation so that
  everything is nice and clean. However, some of these files keep
  reappearing!

  In this case I am bisecting Wine. To help I added an ltrace to the
  Wine shell script...

  I am compiling to /tmp/wine.
  /tmp is a tmpfs mount.

  I added ltrace to /tmp/wine/wine64/wine, which is a shell script. The last 
line of that script being:
  exec ltrace "$WINELOADER" "$@"

  I have then deleted everything in this directory (multiple times).

  When attempting to access /tmp/wine/wine64/wine I am told that the
  file does not exist, as expected.

  I then run a compilation.

  On checking /tmp/wine/wine64/wine it contains the ltrace:
  exec ltrace "$WINELOADER" "$@"

  I thought it might just be bash, but I checked with Pluma and this
  file contains ltrace – data I have deleted multiple times and should
  have been overwritten.

  I tried multiple "sync"s and dropping the caches, but it makes no
  difference.

  Why does this data keep reappearing? Why can't I delete a file? What
  kind of madness is this?

  There are no words for just how bad this is. In particular: this is
  definitely a security issue.

  If a user deletes a file, all I have to do is recreate a file with the
  same name and I have access to all that user's data.

  I've spent hours bisecting, but it turns out I cannot trust any of the
  results as I have no guarantee that any of the files have actually
  changed.

  I haven't checked the upstream kernel yet, but I am aware that this is
  required. It could take many hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-76-generic 5.15.0-76.83
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ken8889 F pulseaudio
   /dev/snd/controlC1:  ken8889 F pulseaudio
   /dev/snd/pcmC1D7p:   ken8889 F...m pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat Jul 15 06:32:07 2023
  MachineType: LENOVO 0606AD5
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-76-generic 
root=UUID=bc8de7a2-4160-4017-937e-3d4126551687 ro rootflags=subvol=@ 
root=/dev/sdb10 quiet splash zswap.enabled=1 zswap.compressor=lz4 
zswap.max_pool_percent=50 zswap.zpool=z3fold module_blacklist=mei_me 
hugepagesz=1G hugepages=3 hugepagesz=2M hugepages=100 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-76-generic N/A
   linux-backports-modules-5.15.0-76-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.14
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-09-26 (291 days ago)
  dmi.bios.date: 12/15/2016
  dmi.bios.release: 0.60
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A0KT60AUS
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NONE
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA0KT60AUS:bd12/15/2016:br0.60:svnLENOVO:pn0606AD5:pvrThinkStationS30:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct7:cvrNONE:skuLENOVO_BI_A0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 0606AD5
  dmi.product.sku: LENOVO_BI_A0
  dmi.product.version: ThinkStation S30
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382

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


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

[Kernel-packages] [Bug 2027667] Re: Certain website floods syslog

[Ken Sharp]

** Package changed: linux (Ubuntu) => firefox (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/2027667

Title:
  Certain website floods syslog

Status in firefox package in Ubuntu:
  New

Bug description:
  When viewing
  
https://paris2024.sapsailing.com/gwt/RaceBoard.html?regattaName=OSG2024TEV2023+-+Men%27s+Windsurfing=iQFOiL+men+-+R4=OSG2024TEV2023+-+Men%27s+Windsurfing=83eb5c2a-d3ab-4e22-8422-1e4ab154ed34=b8220cee-9ec7-4640-b8d8-f40e079456d5=FULL_ANALYSIS

  syslog is flooded with hundreds of lines like these:

  Jul 13 11:24:47 moshe kernel: [12492.404743] audit: type=1326 
audit(1689236687.177:2451): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:24:47 moshe kernel: [12492.405092] audit: type=1326 
audit(1689236687.177:2452): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:24:47 moshe kernel: [12492.407568] audit: type=1326 
audit(1689236687.181:2453): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:24:47 moshe kernel: [12492.407827] audit: type=1326 
audit(1689236687.181:2454): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:24:47 moshe kernel: [12492.408397] audit: type=1326 
audit(1689236687.181:2455): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:24:47 moshe kernel: [12492.408622] audit: type=1326 
audit(1689236687.181:2456): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:24:47 moshe kernel: [12492.409197] audit: type=1326 
audit(1689236687.181:2457): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:24:47 moshe kernel: [12492.409429] audit: type=1326 
audit(1689236687.181:2458): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:24:47 moshe kernel: [12492.410412] audit: type=1326 
audit(1689236687.185:2459): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:24:47 moshe kernel: [12492.410696] audit: type=1326 
audit(1689236687.185:2460): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:25:39 moshe kernel: [12544.337807] kauditd_printk_skb: 9 callbacks 
suppressed
  Jul 13 11:25:39 moshe kernel: [12544.337809] audit: type=1326 
audit(1689236739.112:2470): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:25:39 moshe kernel: [12544.337928] audit: type=1326 
audit(1689236739.112:2471): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:25:39 moshe kernel: [12544.338412] audit: type=1326 
audit(1689236739.112:2472): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7f61d497873d code=0x5
  Jul 13 11:25:39 moshe kernel: [12544.338602] audit: type=1326 
audit(1689236739.116:2473): auid=1000 uid=1000 gid=1000 ses=12 
subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" 
exe="/snap/firefox/2880/usr/lib/firefox/firefox" 

[Kernel-packages] [Bug 1920707] Re: AMD A4-5300: no sound

[Ken Sharp]

I started running a bisect but it takes hours for one step. It's not a
realistic option.

Adding snd_hda_intel to /etc/modules doesn't work, so a crappy workaround is to 
add
@reboot /sbin/modprobe snd_hda_intel
to root's crontab, until I can be bothered to come back to this, but I just 
don't have the time right now.

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

Title:
  AMD A4-5300: no sound

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting with linux-4.15.0-137-generic, there is no sound at all on a
  system with an AMD A4-5300.

  From a working kernel:

  Mar 22 05:00:29 richie kernel: [   33.029621] snd_hda_intel :00:01.1: 
Force to non-snoop mode
  [...]
  Mar 22 05:00:29 richie kernel: [   33.589291] input: HDA ATI HDMI 
HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input5
  Mar 22 05:00:29 richie kernel: [   33.601773] snd_hda_codec_realtek 
hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) 
type:line
  Mar 22 05:00:29 richie kernel: [   33.601776] snd_hda_codec_realtek 
hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
  Mar 22 05:00:29 richie kernel: [   33.601779] snd_hda_codec_realtek 
hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
  Mar 22 05:00:29 richie kernel: [   33.601781] snd_hda_codec_realtek 
hdaudioC1D0:mono: mono_out=0x0
  Mar 22 05:00:29 richie kernel: [   33.601782] snd_hda_codec_realtek 
hdaudioC1D0:inputs:
  Mar 22 05:00:29 richie kernel: [   33.601784] snd_hda_codec_realtek 
hdaudioC1D0:  Front Mic=0x19
  Mar 22 05:00:29 richie kernel: [   33.601786] snd_hda_codec_realtek 
hdaudioC1D0:  Rear Mic=0x18
  Mar 22 05:00:29 richie kernel: [   33.601787] snd_hda_codec_realtek 
hdaudioC1D0:  Line=0x1a
  Mar 22 05:00:29 richie kernel: [   33.614365] input: HD-Audio Generic Front 
Mic as /devices/pci:00/:00:14.2/sound/card1/input6
  Mar 22 05:00:29 richie kernel: [   33.614426] input: HD-Audio Generic Rear 
Mic as /devices/pci:00/:00:14.2/sound/card1/input7
  Mar 22 05:00:29 richie kernel: [   33.614481] input: HD-Audio Generic Line as 
/devices/pci:00/:00:14.2/sound/card1/input8
  Mar 22 05:00:29 richie kernel: [   33.614536] input: HD-Audio Generic Line 
Out as /devices/pci:00/:00:14.2/sound/card1/input9
  Mar 22 05:00:29 richie kernel: [   33.614597] input: HD-Audio Generic Front 
Headphone as /devices/pci:00/:00:14.2/sound/card1/input10

  $ lsmod | grep -F snd
  snd81920  21 
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
  snd_hda_codec 126976  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
  snd_hda_codec_generic73728  1 snd_hda_codec_realtek
  snd_hda_codec_hdmi 49152  1
  snd_hda_codec_realtek   106496  1
  snd_hda_core   81920  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
  snd_hda_intel  45056  5
  snd_hwdep  20480  1 snd_hda_codec
  snd_pcm98304  4 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
  snd_rawmidi32768  1 snd_seq_midi
  snd_seq65536  2 snd_seq_midi,snd_seq_midi_event
  snd_seq_device 16384  3 snd_seq,snd_seq_midi,snd_rawmidi
  snd_seq_midi   16384  0
  snd_seq_midi_event 16384  1 snd_seq_midi
  snd_timer  32768  2 snd_seq,snd_pcm

  On a broken kernel, dmesg contains no information about the snd_*
  modules, and lsmod shows that none have loaded.

  In both cases lspci -v gives the same details:

  00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI 
Audio Controller
   Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity HDMI Audio 
Controller
   Flags: bus master, fast devsel, latency 0, IRQ 5
   Memory at feb44000 (32-bit, non-prefetchable) [size=16K]
   Capabilities: [50] Power Management version 3
   Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
   Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
   Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 
   Kernel modules: snd_hda_intel

  `sudo modprobe snd_hda_intel` loads all the correct modules and brings
  sound back.

  For some reason the newer kernels aren't loading snd_hda_intel (or
  something related) when it should be.

  Will update after testing mainline kernels, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-139-generic 4.15.0-139.143
  ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18
  Uname: Linux 4.15.0-139-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Mon Mar 22 04:42:26 2021
  HibernationDevice: RESUME=UUID=5d6634dd-fb1b-49f6-b17a-4197a3814382
 

[Kernel-packages] [Bug 1920707] Re: AMD A4-5300: no sound

[Ken Sharp]

Tested 5.12.0-051200rc4-generic and the problem still occurs.

Could this be an issue in another package? Would udev be involved?

Otherwise the next step is for me to file upstream.

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

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

Title:
  AMD A4-5300: no sound

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting with linux-4.15.0-137-generic, there is no sound at all on a
  system with an AMD A4-5300.

  From a working kernel:

  Mar 22 05:00:29 richie kernel: [   33.029621] snd_hda_intel :00:01.1: 
Force to non-snoop mode
  [...]
  Mar 22 05:00:29 richie kernel: [   33.589291] input: HDA ATI HDMI 
HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input5
  Mar 22 05:00:29 richie kernel: [   33.601773] snd_hda_codec_realtek 
hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) 
type:line
  Mar 22 05:00:29 richie kernel: [   33.601776] snd_hda_codec_realtek 
hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
  Mar 22 05:00:29 richie kernel: [   33.601779] snd_hda_codec_realtek 
hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
  Mar 22 05:00:29 richie kernel: [   33.601781] snd_hda_codec_realtek 
hdaudioC1D0:mono: mono_out=0x0
  Mar 22 05:00:29 richie kernel: [   33.601782] snd_hda_codec_realtek 
hdaudioC1D0:inputs:
  Mar 22 05:00:29 richie kernel: [   33.601784] snd_hda_codec_realtek 
hdaudioC1D0:  Front Mic=0x19
  Mar 22 05:00:29 richie kernel: [   33.601786] snd_hda_codec_realtek 
hdaudioC1D0:  Rear Mic=0x18
  Mar 22 05:00:29 richie kernel: [   33.601787] snd_hda_codec_realtek 
hdaudioC1D0:  Line=0x1a
  Mar 22 05:00:29 richie kernel: [   33.614365] input: HD-Audio Generic Front 
Mic as /devices/pci:00/:00:14.2/sound/card1/input6
  Mar 22 05:00:29 richie kernel: [   33.614426] input: HD-Audio Generic Rear 
Mic as /devices/pci:00/:00:14.2/sound/card1/input7
  Mar 22 05:00:29 richie kernel: [   33.614481] input: HD-Audio Generic Line as 
/devices/pci:00/:00:14.2/sound/card1/input8
  Mar 22 05:00:29 richie kernel: [   33.614536] input: HD-Audio Generic Line 
Out as /devices/pci:00/:00:14.2/sound/card1/input9
  Mar 22 05:00:29 richie kernel: [   33.614597] input: HD-Audio Generic Front 
Headphone as /devices/pci:00/:00:14.2/sound/card1/input10

  $ lsmod | grep -F snd
  snd81920  21 
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
  snd_hda_codec 126976  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
  snd_hda_codec_generic73728  1 snd_hda_codec_realtek
  snd_hda_codec_hdmi 49152  1
  snd_hda_codec_realtek   106496  1
  snd_hda_core   81920  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
  snd_hda_intel  45056  5
  snd_hwdep  20480  1 snd_hda_codec
  snd_pcm98304  4 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
  snd_rawmidi32768  1 snd_seq_midi
  snd_seq65536  2 snd_seq_midi,snd_seq_midi_event
  snd_seq_device 16384  3 snd_seq,snd_seq_midi,snd_rawmidi
  snd_seq_midi   16384  0
  snd_seq_midi_event 16384  1 snd_seq_midi
  snd_timer  32768  2 snd_seq,snd_pcm

  On a broken kernel, dmesg contains no information about the snd_*
  modules, and lsmod shows that none have loaded.

  In both cases lspci -v gives the same details:

  00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI 
Audio Controller
   Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity HDMI Audio 
Controller
   Flags: bus master, fast devsel, latency 0, IRQ 5
   Memory at feb44000 (32-bit, non-prefetchable) [size=16K]
   Capabilities: [50] Power Management version 3
   Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
   Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
   Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 
   Kernel modules: snd_hda_intel

  `sudo modprobe snd_hda_intel` loads all the correct modules and brings
  sound back.

  For some reason the newer kernels aren't loading snd_hda_intel (or
  something related) when it should be.

  Will update after testing mainline kernels, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-139-generic 4.15.0-139.143
  ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18
  Uname: Linux 4.15.0-139-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Mon Mar 22 04:42:26 2021
  HibernationDevice: RESUME=UUID=5d6634dd-fb1b-49f6-b17a-4197a3814382
  InstallationDate: Installed on 2015-11-28 (1940 days ago)
  

[Kernel-packages] [Bug 1920707] Re: AMD Trinity HDMI Audio Controller: no sound

[Ken Sharp]

Tested the mainline kernel 4.15.18-041518-generic and the problem still
occurs.

** Summary changed:

- AMD Trinity HDMI Audio Controller: no sound
+ AMD A4-5300: no sound

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

Title:
  AMD A4-5300: no sound

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting with linux-4.15.0-137-generic, there is no sound at all on a
  system with an AMD A4-5300.

  From a working kernel:

  Mar 22 05:00:29 richie kernel: [   33.029621] snd_hda_intel :00:01.1: 
Force to non-snoop mode
  [...]
  Mar 22 05:00:29 richie kernel: [   33.589291] input: HDA ATI HDMI 
HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input5
  Mar 22 05:00:29 richie kernel: [   33.601773] snd_hda_codec_realtek 
hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) 
type:line
  Mar 22 05:00:29 richie kernel: [   33.601776] snd_hda_codec_realtek 
hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
  Mar 22 05:00:29 richie kernel: [   33.601779] snd_hda_codec_realtek 
hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
  Mar 22 05:00:29 richie kernel: [   33.601781] snd_hda_codec_realtek 
hdaudioC1D0:mono: mono_out=0x0
  Mar 22 05:00:29 richie kernel: [   33.601782] snd_hda_codec_realtek 
hdaudioC1D0:inputs:
  Mar 22 05:00:29 richie kernel: [   33.601784] snd_hda_codec_realtek 
hdaudioC1D0:  Front Mic=0x19
  Mar 22 05:00:29 richie kernel: [   33.601786] snd_hda_codec_realtek 
hdaudioC1D0:  Rear Mic=0x18
  Mar 22 05:00:29 richie kernel: [   33.601787] snd_hda_codec_realtek 
hdaudioC1D0:  Line=0x1a
  Mar 22 05:00:29 richie kernel: [   33.614365] input: HD-Audio Generic Front 
Mic as /devices/pci:00/:00:14.2/sound/card1/input6
  Mar 22 05:00:29 richie kernel: [   33.614426] input: HD-Audio Generic Rear 
Mic as /devices/pci:00/:00:14.2/sound/card1/input7
  Mar 22 05:00:29 richie kernel: [   33.614481] input: HD-Audio Generic Line as 
/devices/pci:00/:00:14.2/sound/card1/input8
  Mar 22 05:00:29 richie kernel: [   33.614536] input: HD-Audio Generic Line 
Out as /devices/pci:00/:00:14.2/sound/card1/input9
  Mar 22 05:00:29 richie kernel: [   33.614597] input: HD-Audio Generic Front 
Headphone as /devices/pci:00/:00:14.2/sound/card1/input10

  $ lsmod | grep -F snd
  snd81920  21 
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
  snd_hda_codec 126976  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
  snd_hda_codec_generic73728  1 snd_hda_codec_realtek
  snd_hda_codec_hdmi 49152  1
  snd_hda_codec_realtek   106496  1
  snd_hda_core   81920  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
  snd_hda_intel  45056  5
  snd_hwdep  20480  1 snd_hda_codec
  snd_pcm98304  4 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
  snd_rawmidi32768  1 snd_seq_midi
  snd_seq65536  2 snd_seq_midi,snd_seq_midi_event
  snd_seq_device 16384  3 snd_seq,snd_seq_midi,snd_rawmidi
  snd_seq_midi   16384  0
  snd_seq_midi_event 16384  1 snd_seq_midi
  snd_timer  32768  2 snd_seq,snd_pcm

  On a broken kernel, dmesg contains no information about the snd_*
  modules, and lsmod shows that none have loaded.

  In both cases lspci -v gives the same details:

  00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI 
Audio Controller
   Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity HDMI Audio 
Controller
   Flags: bus master, fast devsel, latency 0, IRQ 5
   Memory at feb44000 (32-bit, non-prefetchable) [size=16K]
   Capabilities: [50] Power Management version 3
   Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
   Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
   Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 
   Kernel modules: snd_hda_intel

  `sudo modprobe snd_hda_intel` loads all the correct modules and brings
  sound back.

  For some reason the newer kernels aren't loading snd_hda_intel (or
  something related) when it should be.

  Will update after testing mainline kernels, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-139-generic 4.15.0-139.143
  ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18
  Uname: Linux 4.15.0-139-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Mon Mar 22 04:42:26 2021
  HibernationDevice: RESUME=UUID=5d6634dd-fb1b-49f6-b17a-4197a3814382
  InstallationDate: Installed on 2015-11-28 (1940 days ago)
  InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  

[Kernel-packages] [Bug 1920707] [NEW] AMD Trinity HDMI Audio Controller: no sound

[Ken Sharp]

Public bug reported:

Starting with linux-4.15.0-137-generic, there is no sound at all on a
system with an AMD A4-5300.

>From a working kernel:

Mar 22 05:00:29 richie kernel: [   33.029621] snd_hda_intel :00:01.1: Force 
to non-snoop mode
[...]
Mar 22 05:00:29 richie kernel: [   33.589291] input: HDA ATI HDMI HDMI/DP,pcm=3 
as /devices/pci:00/:00:01.1/sound/card0/input5
Mar 22 05:00:29 richie kernel: [   33.601773] snd_hda_codec_realtek 
hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) 
type:line
Mar 22 05:00:29 richie kernel: [   33.601776] snd_hda_codec_realtek 
hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Mar 22 05:00:29 richie kernel: [   33.601779] snd_hda_codec_realtek 
hdaudioC1D0:hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Mar 22 05:00:29 richie kernel: [   33.601781] snd_hda_codec_realtek 
hdaudioC1D0:mono: mono_out=0x0
Mar 22 05:00:29 richie kernel: [   33.601782] snd_hda_codec_realtek 
hdaudioC1D0:inputs:
Mar 22 05:00:29 richie kernel: [   33.601784] snd_hda_codec_realtek 
hdaudioC1D0:  Front Mic=0x19
Mar 22 05:00:29 richie kernel: [   33.601786] snd_hda_codec_realtek 
hdaudioC1D0:  Rear Mic=0x18
Mar 22 05:00:29 richie kernel: [   33.601787] snd_hda_codec_realtek 
hdaudioC1D0:  Line=0x1a
Mar 22 05:00:29 richie kernel: [   33.614365] input: HD-Audio Generic Front Mic 
as /devices/pci:00/:00:14.2/sound/card1/input6
Mar 22 05:00:29 richie kernel: [   33.614426] input: HD-Audio Generic Rear Mic 
as /devices/pci:00/:00:14.2/sound/card1/input7
Mar 22 05:00:29 richie kernel: [   33.614481] input: HD-Audio Generic Line as 
/devices/pci:00/:00:14.2/sound/card1/input8
Mar 22 05:00:29 richie kernel: [   33.614536] input: HD-Audio Generic Line Out 
as /devices/pci:00/:00:14.2/sound/card1/input9
Mar 22 05:00:29 richie kernel: [   33.614597] input: HD-Audio Generic Front 
Headphone as /devices/pci:00/:00:14.2/sound/card1/input10

$ lsmod | grep -F snd
snd81920  21 
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
snd_hda_codec 126976  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hda_codec_generic73728  1 snd_hda_codec_realtek
snd_hda_codec_hdmi 49152  1
snd_hda_codec_realtek   106496  1
snd_hda_core   81920  5 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_hda_intel  45056  5
snd_hwdep  20480  1 snd_hda_codec
snd_pcm98304  4 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
snd_rawmidi32768  1 snd_seq_midi
snd_seq65536  2 snd_seq_midi,snd_seq_midi_event
snd_seq_device 16384  3 snd_seq,snd_seq_midi,snd_rawmidi
snd_seq_midi   16384  0
snd_seq_midi_event 16384  1 snd_seq_midi
snd_timer  32768  2 snd_seq,snd_pcm

On a broken kernel, dmesg contains no information about the snd_*
modules, and lsmod shows that none have loaded.

In both cases lspci -v gives the same details:

00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio 
Controller
 Subsystem: Micro-Star International Co., Ltd. [MSI] Trinity HDMI Audio 
Controller
 Flags: bus master, fast devsel, latency 0, IRQ 5
 Memory at feb44000 (32-bit, non-prefetchable) [size=16K]
 Capabilities: [50] Power Management version 3
 Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
 Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 
 Kernel modules: snd_hda_intel

`sudo modprobe snd_hda_intel` loads all the correct modules and brings
sound back.

For some reason the newer kernels aren't loading snd_hda_intel (or
something related) when it should be.

Will update after testing mainline kernels, etc.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-139-generic 4.15.0-139.143
ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18
Uname: Linux 4.15.0-139-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
Date: Mon Mar 22 04:42:26 2021
HibernationDevice: RESUME=UUID=5d6634dd-fb1b-49f6-b17a-4197a3814382
InstallationDate: Installed on 2015-11-28 (1940 days ago)
InstallationMedia: Kubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IwConfig:
 eth0  no wireless extensions.

 lono wireless extensions.
MachineType: MSI MS-7721
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-139-generic 
root=UUID=6c84fef8-256e-4a5c-9033-28e0b9342a56 ro zswap.enabled=1 quiet splash 
zswap.compressor=lz4hc zswap.max_pool_percent=20 zswap.zpool=z3fold vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 

[Kernel-packages] [Bug 1917245] Re: HP and Canon support ubuntu LTS linux systems

[Ken Sharp]

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

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

Title:
  HP and Canon support ubuntu LTS linux systems

Status in linux package in Ubuntu:
  Invalid

Bug description:
  HP and Canon and epson printers and scanners support ubuntu LTS linux systems
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1917110] Re: deus ex mankind divide working too slow linux ubuntu 20.04 LTS

[Ken Sharp]

What makes you think that this is a Linux bug? Did you bother reporting
this to Steam?

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

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

Title:
  deus ex mankind divide working too slow linux ubuntu 20.04 LTS

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  deus ex mankind divide working too slow my linux ubuntu 20.04 LTS desktop
  openGL 3.0 and openGL 2.1 working too slow linux ubuntu 20.04 LTS desktop
  MSI MS 7817
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1430 F pulseaudio
   /dev/snd/controlC0:  snowden1430 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (11 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tessetessu   1400 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-20 (7 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq 6000 Pro MT PC
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=2a4fb579-9676-4e2a-8293-120b9188db54 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-44-generic N/A
   linux-backports-modules-5.8.0-44-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.8.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/25/2009
  dmi.bios.release: 1.9
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G2 v01.09
  dmi.board.asset.tag: CZC0195QPD
  dmi.board.name: 3048h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC0195QPD
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G2v01.09:bd08/25/2009:br1.9:svnHewlett-Packard:pnHPCompaq6000ProMTPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6000 Pro MT PC
  dmi.product.sku: VN784ET#UUW
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tessetessu   1414 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-20 (7 days 

[Kernel-packages] [Bug 1917112] Re: deus ex human revolution director cut working too slow steam proton

[Ken Sharp]

What makes you think that this is a Linux bug? Did you bother reporting
this to Steam?

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

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

Title:
  deus ex human revolution director cut working too slow steam proton

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  deus ex human revolution director cut working too slow steam proton 
experimental
  same is deus ex the fall and deus mandkind divide all deus ex games working 
too
  slow working too slow linux kernels 5.4 and linux kernels 5.8 working too 
slow 

  Computer Information:
  Manufacturer:  Unknown
  Model:  Unknown
  Form Factor: Desktop
  No Touch Input Detected

  Processor Information:
  CPU Vendor:  GenuineIntel
  CPU Brand:  Intel(R) Pentium(R) CPU G3420 @ 3.20GHz
  CPU Family:  0x6
  CPU Model:  0x3c
  CPU Stepping:  0x3
  CPU Type:  0x0
  Speed:  3200 Mhz
  2 logical processors
  2 physical processors
  HyperThreading:  Unsupported
  FCMOV:  Supported
  SSE2:  Supported
  SSE3:  Supported
  SSSE3:  Supported
  SSE4a:  Unsupported
  SSE41:  Supported
  SSE42:  Supported
  AES:  Unsupported
  AVX:  Unsupported
  AVX2:  Unsupported
  AVX512F:  Unsupported
  AVX512PF:  Unsupported
  AVX512ER:  Unsupported
  AVX512CD:  Unsupported
  AVX512VNNI:  Unsupported
  SHA:  Unsupported
  CMPXCHG16B:  Supported
  LAHF/SAHF:  Supported
  PrefetchW:  Unsupported

  Operating System Version:
  Ubuntu 20.04.2 LTS (64 bit)
  Kernel Name:  Linux
  Kernel Version:  5.4.0-66-generic
  X Server Vendor:  The X.Org Foundation
  X Server Release:  12009000
  X Window Manager:  GNOME Shell
  Steam Runtime Version:  steam-runtime_0.20201203.1

  Video Card:
  Driver:  Intel Open Source Technology Center Mesa DRI Intel(R) HD 
Graphics (HSW GT1)
  Driver Version:  3.0 Mesa 20.2.6
  OpenGL Version: 3.0
  Desktop Color Depth: 24 bits per pixel
  Monitor Refresh Rate: 60 Hz
  VendorID:  0x8086
  DeviceID:  0x402
  Revision Not Detected
  Number of Monitors:  1
  Number of Logical Video Cards:  1
  Primary Display Resolution:  1280 x 1024
  Desktop Resolution: 1280 x 1024
  Primary Display Size: 13.39" x 10.63" (17.09" diag)
  34.0cm x 27.0cm (43.4cm diag)
  Primary VRAM Not Detected

  Sound card:
  Audio device: Intel Haswell HDMI

  Memory:
  RAM:  3798 Mb

  VR Hardware:
  VR Headset: None detected

  Miscellaneous:
  UI Language:  English
  LANG:  fi_FI.UTF-8
  Total Hard Disk Space Available:  937366 Mb
  Largest Free Hard Disk Block:  851473 Mb

  The runtime information tool is preparing a report, please wait...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1430 F pulseaudio
   /dev/snd/controlC0:  snowden1430 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (11 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 

[Kernel-packages] [Bug 1917264] Re: HP and Canon and Epson printers inks status

[Ken Sharp]

What debugging have you done to determine that this is a Linux bug,
because I very much doubt it is?

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

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

Title:
   HP and Canon and Epson printers inks status

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  HP and Canon and Epson printers inks status information 
  how much is colours and black inks status
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  snowden1435 F pulseaudio
   /dev/snd/controlC0:  snowden1435 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-15 (13 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-66-generic N/A
   linux-backports-modules-5.4.0-66-generic  N/A
   linux-firmware1.187.9
  RfKill:
   
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tessetessu   1381 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-20 (8 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. E402SA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=32c14ba7-6abd-49ad-b9b6-25073031646a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-44-generic N/A
   linux-backports-modules-5.8.0-44-generic  N/A
   linux-firmware1.187.9
  Tags:  focal
  Uname: Linux 5.8.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2015
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E402SA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E402SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE402SA.208:bd12/14/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: E
  dmi.product.name: E402SA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tessetessu   1398 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-02-20 (8 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - 

[Kernel-packages] [Bug 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0

[Ken Sharp]

** Tags added: bionic focal regression-update

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

Title:
  Missing Commit for 5.4-Kernel breaks  xen Dom0

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.4 package in Ubuntu:
  New

Bug description:
  You commited "xen: Fix event channel callback via INTX/GSI" for kernel 
5.4.0-67 for HWE 18.04 and 20.04.
  This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also 
Commit "xen: Fix XenStore initialisation for XS_LOCAL"

  See https://lkml.org/lkml/2021/1/28/1235
  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195

  Upstream:
  Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2
  Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1

  5.10:
  Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11)
  Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13)

  5.4:
  Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93)
  Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95)

  Without this patch you cannot start guests (DomU) on this machine!

  Error message while creating DomU:
  libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to 
add device with path /
  libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add 
disk devices

  See:
  - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14
  - 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f
  - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95
  - 
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195

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

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

[Kernel-packages] [Bug 1910900] Re: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi

[Ken Sharp]

You need to provide /var/lib/dkms/nvidia/390.141/build/make.log

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Incomplete

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

Title:
  package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to
  install/upgrade: installed nvidia-dkms-390 package post-installation
  script subprocess returned error exit status 10

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

Bug description:
  sometimes works great

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: nvidia-dkms-390 390.141-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jan 10 02:36:18 2021
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.141-0ubuntu0.20.10.1 failed to 
install/upgrade: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1501972] Re: nvidia kernel module failed to build [/bin/sh: 1: cc: not found]

[Ken Sharp]

"Fix:
sudo apt install -y --reinstall gcc g++ gcc-7 g++-7"

How on Earth is that a fix? Does an updated package do this for you? I'm
doubting it very much.

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

Title:
  nvidia kernel module failed to build [/bin/sh: 1: cc: not found]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-352-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  I really have no idea of this issue, i just booted up and ubuntu
  notified me that there was a problem... hopefully ubuntu is self
  reporting enough information.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-346 346.96-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.19.0-30.33~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-65-generic
  Date: Thu Oct  1 18:17:00 2015
  InstallationDate: Installed on 2015-09-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 346.96-0ubuntu0.0.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-346
  Title: nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.346.hybrid.conf: [deleted]

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

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

[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3

[Ken Sharp]

All good here too with 390.116-0ubuntu0.18.04.3

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

Title:
  nvidia-drivers-390 fail to build with kernel 5.3

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe source package in Bionic:
  Confirmed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed

Bug description:
  nvidia-graphics-drivers-390 fails to build against linux 5.3.

  SRU Request:

  [Test Case]
  1) Enable the -proposed repository, and install the new 390 NVIDIA driver 
(nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2).

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The update only fixes build issues with Linux versions 5.3.
  __
  With linux-image-5.0.0-23 I had no problems. Following an update 
linux-image-5.3.0-19 was installed, the DKMS build failed, and the system 
became unusable.

  Removing 5.3.0 brings the system back.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Nov  3 19:55:57 2019
  InstallationDate: Installed on 2019-06-09 (147 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with kernel 5.3

[Ken Sharp]

Updated Bionic with all the latest packages before adding -proposed.

Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=5.3.0-26-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/lib/modules/5.3.0-26-generic/build LD=/usr/bin/ld.bfd modules..(bad 
exit status: 2)
Error! Bad return status for module build on kernel: 5.3.0-26-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.116/build/make.log for more information.
   ...done.

It seems to try twice during the update:

Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=5.3.0-26-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/lib/modules/5.3.0-26-generic/build LD=/usr/bin/ld.bfd modules..(bad 
exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/nvidia-kernel-source-390.0.crash'
Error! Bad return status for module build on kernel: 5.3.0-26-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.116/build/make.log for more information.
   ...done.

Build log attached.

** Attachment added: "/var/lib/dkms/nvidia/390.116/build/make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+attachment/5322038/+files/make.log

** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic

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

Title:
  nvidia-drivers-390 fail to build with kernel 5.3

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New
Status in linux-hwe source package in Bionic:
  New
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed

Bug description:
  nvidia-graphics-drivers-390 fails to build against linux 5.3.

  SRU Request:

  [Test Case]
  1) Enable the -proposed repository, and install the new 390 NVIDIA driver 
(nvidia-graphics-drivers-390_390.116-0ubuntu0.18.04.2).

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The update only fixes build issues with Linux versions 5.3.
  __
  With linux-image-5.0.0-23 I had no problems. Following an update 
linux-image-5.3.0-19 was installed, the DKMS build failed, and the system 
became unusable.

  Removing 5.3.0 brings the system back.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Nov  3 19:55:57 2019
  InstallationDate: Installed on 2019-06-09 (147 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1843385] Re: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status

[Ken Sharp]

Probably the same as Bug #1851162

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

Title:
  package nvidia-dkms-390 (not installed) failed to install/upgrade:
  installed nvidia-dkms-390 package post-installation script subprocess
  returned error exit status 10

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

Bug description:
  Just upgraded the distro to 19.10 (dev)

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-dkms-390 (not installed)
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 10 08:08:26 2019
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2016-02-03 (1314 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.3
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: 
installed nvidia-dkms-390 package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to eoan on 2019-09-10 (0 days ago)

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

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

[Kernel-packages] [Bug 1853196] Re: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build

[Ken Sharp]

*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162

** This bug has been marked a duplicate of bug 1851162
   nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19

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

Title:
  nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed
  to build

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

Bug description:
  i tried to install nvidia drivers from this link 
https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-19-10-eoan-ermine-linux
 . 
  My video card is nvdia Gforce GT610. Sometimes on boot there is pixel 
"scratches" (on the pink screen).

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-kernel-source-390 390.129-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DKMSKernelVersion: 5.3.0-23-generic
  Date: Tue Nov 19 22:29:16 2019
  Dependencies:
   
  PackageVersion: 390.129-0ubuntu2
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1844613] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status

[Ken Sharp]

*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162

** This bug has been marked a duplicate of bug 1851162
   nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19

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

Title:
  package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade:
  installed nvidia-dkms-390 package post-installation script subprocess
  returned error exit status 10

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

Bug description:
  each time the pc starts, the error message is shown, but if i close
  that i can work w/o any problem

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-dkms-390 390.129-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 17 23:42:51 2019
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2018-02-09 (587 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.3
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: 
installed nvidia-dkms-390 package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago)

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

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

[Kernel-packages] [Bug 1846995] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status

[Ken Sharp]

Did you build a custom kernel?

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

Title:
  package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade:
  installed nvidia-dkms-390 package post-installation script subprocess
  returned error exit status 10

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

Bug description:
  Doing a do-release-upgrade -d from 19.04 to 19.10. 
  The upgrade crashed out part way through, automatically reporting this bug.

  update-initramfs: Generating /boot/initrd.img-5.3.0-13-generic
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.39.2-3) ...
  Processing triggers for libc-bin (2.30-0ubuntu2) ...
  Processing triggers for menu (2.1.47ubuntu3) ...
  Errors were encountered while processing:
   nvidia-dkms-390
   nvidia-driver-390
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (624.7 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-dkms-390 390.129-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm 
nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Oct  7 01:17:46 2019
  ErrorMessage: installed nvidia-dkms-390 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2018-04-23 (531 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180421.1)
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: 
installed nvidia-dkms-390 package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to eoan on 2019-10-07 (0 days ago)

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

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

[Kernel-packages] [Bug 1857378] Re: Please drop i386 dkms package, as there are no i386 kernel

[Ken Sharp]

Or don't.
https://discourse.ubuntu.com/t/intel-32bit-packages-on-ubuntu-from-19-10-onwards/11263/90

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Invalid

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

Title:
  Please drop i386 dkms package, as there are no i386 kernel

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

Bug description:
  Please drop i386 dkms package, as there are no i386 kernel

  Systems should enable amd64 archive and install amd64 kernel & the
  amd64 dkms package.

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

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

[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19

[Ken Sharp]

The HWE package now force-upgrades to 5.3.0, rendering that entire
package useless.

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

Title:
  nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19

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

Bug description:
  With linux-image-5.0.0-23 I had no problems. Following an update
  linux-image-5.3.0-19 was installed, the DKMS build failed, and the
  system became unusable.

  Removing 5.3.0 brings the system back.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Nov  3 19:55:57 2019
  InstallationDate: Installed on 2019-06-09 (147 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1851162] Re: nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19

[Ken Sharp]

Build log attached.

** Attachment added: "DKMS build log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+attachment/5302550/+files/make.log

** Description changed:

- With linux-image-5.0.0-23 I had no problems. Following an update 5.3.0
- was installed, the DKMS failed, and the system became unusable.
+ With linux-image-5.0.0-23 I had no problems. Following an update linux-
+ image-5.3.0-19 was installed, the DKMS build failed, and the system
+ became unusable.
  
  Removing 5.3.0 brings the system back.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Nov  3 19:55:57 2019
  InstallationDate: Installed on 2019-06-09 (147 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19

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

Bug description:
  With linux-image-5.0.0-23 I had no problems. Following an update
  linux-image-5.3.0-19 was installed, the DKMS build failed, and the
  system became unusable.

  Removing 5.3.0 brings the system back.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Nov  3 19:55:57 2019
  InstallationDate: Installed on 2019-06-09 (147 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1851162] [NEW] nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19

[Ken Sharp]

Public bug reported:

With linux-image-5.0.0-23 I had no problems. Following an update linux-
image-5.3.0-19 was installed, the DKMS build failed, and the system
became unusable.

Removing 5.3.0 brings the system back.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Nov  3 19:55:57 2019
InstallationDate: Installed on 2019-06-09 (147 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
SourcePackage: nvidia-graphics-drivers-390
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19

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

Bug description:
  With linux-image-5.0.0-23 I had no problems. Following an update
  linux-image-5.3.0-19 was installed, the DKMS build failed, and the
  system became unusable.

  Removing 5.3.0 brings the system back.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.116-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Nov  3 19:55:57 2019
  InstallationDate: Installed on 2019-06-09 (147 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1804040] Re: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed to build [ERROR: Kernel configuration is invalid.]

[Ken Sharp]

I've marked this as affecting me but I've just realised that I'm using a
different kernel. In my case 5.0.x works fine, 5.3.0 fails in
(apparently) the same way:

DKMS make.log for nvidia-390.116 for kernel 5.3.0-19-generic (x86_64)
Sun  3 Nov 19:50:42 GMT 2019
make[1]: Entering directory '/usr/src/linux-headers-5.3.0-19-generic'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (
\
echo >&2;   \
echo >&2 "  ERROR: Kernel configuration is invalid.";   \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are 
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix 
it.";  \
echo >&2 ;  \

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

Title:
  nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed
  to build [ERROR: Kernel configuration is invalid.]

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

Bug description:
  failed to update my system

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-dkms-390 390.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-39-generic
  Date: Mon Nov 19 23:00:47 2018
  InstallationDate: Installed on 2018-09-16 (64 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageVersion: 390.77-0ubuntu0.18.04.1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: nvidia-dkms-390 390.77-0ubuntu0.18.04.1: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1814874] Re: NULL pointer dereference when using z3fold and zswap

[Ken Sharp]

I don't recall seeing a soft lockup at all, not a related one anyway.
Sadly I don't have a specific command but I did find it triggered when:

1. Memory is overcommited. It doesn't have to be heavily overcommitted.
2. I/O is very high.
3. I “leave“ an SSH session, releasing a small amount of memory.

The patch seems to suggest that it is this release that causes the
problem. My guess would be that part of the session is already in the
compressed cache, and it is released while another process attempts to
enter the compressed cache. I don't even know if that makes sense.

To add to the confusion: it crashes fairly consistently across VMs and
bare metal, but occasionally a server under the same sort of stress, and
otherwise identical setup, can run weeks or months without issue.

At this point, though, I know of no specific command to trigger it. If I
get time I can have a play around but that may never happen.

I usually have zswap.max_pool_percent=50, but everything else can vary
and the result is the same.

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

Title:
  NULL pointer dereference when using z3fold and zswap

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

Bug description:
  Under memory pressure, my VM locks up. This has been reported upstream
  though I don't know how far any solution has progressed.

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

  Feb  6 07:15:42 vps632258 kernel: [151336.450064] z3fold: unknown buddy id 0
  Feb  6 07:15:42 vps632258 kernel: [151336.454450] BUG: unable to handle 
kernel NULL pointer dereference at 0008

  The little bit of log I managed to salvage is attached.

  This has happened to two identical VMs. Unusually it has not occurred
  on a third VM which is configured the same but has less RAM (fingers
  crossed it won't).

  Irrelevant information:
  I thought the lock-ups were due to me using a BTRFS filesystem, however I 
swapped over to NILFS2 and this still occurs. The only difference seems to be 
that I am now able to grab some of the kernel output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-14-generic 4.18.0-14.15~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Feb  6 10:55:05 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1785234] Re: Kernel panic softlockup with z3fold while running bitcoind

[Ken Sharp]

Update: I could not recreate this bug using zbud as the allocator.

I need to test newer kernels and see if there's an easier way to trigger
this.

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

Title:
  Kernel panic softlockup with z3fold while running bitcoind

Status in linux-gcp package in Ubuntu:
  New

Bug description:
  So far I have only triggered this while running bitcoind (or bitcoin-
  qt) with the z3fold module loaded. I will do further testing to see if
  I can trigger it any other ways.

  [54075.373045] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:41]
  [54075.377042] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
[bitcoin-msghand:7509]
  [54075.377042] Modules linked in: cachefiles ip6table_filter ip6_tables 
fscache iptable_filter ip_tables x_tables crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_rapl_perf psmouse serio_raw virtio_net pvpanic 
i2c_piix4 nfsd auth_rpcgss nfs_acl lockd grace sunrpc autofs4 aesni_intel 
aes_x86_64 crypto_simd cryptd glue_helper z3fold lz4hc lz4hc_compress
  [54075.377068] CPU: 1 PID: 7509 Comm: bitcoin-msghand Not tainted 
4.15.0-1014-gcp #14~16.04.1-Ubuntu
  [54075.377069] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [54075.377076] RIP: 0010:native_queued_spin_lock_slowpath+0x25/0x1a0
  [54075.377077] RSP: :aec7c13b7420 EFLAGS: 0202 ORIG_RAX: 
ff11
  [54075.377079] RAX: 0001 RBX: db7b82e96a80 RCX: 

  [54075.377080] RDX: 0001 RSI: 0001 RDI: 
8c687a5aa010
  [54075.377081] RBP: aec7c13b7420 R08: 8c6879c749d8 R09: 
0002
  [54075.377082] R10: aec7c13b74d8 R11: aec7c13b7628 R12: 
8c687a5aa000
  [54075.377083] R13: 8c687a5aa010 R14: 8c687a5aa000 R15: 
db7b82de7580
  [54075.377084] FS:  7f133e7fc700() GS:8c687fd0() 
knlGS:
  [54075.377086] CS:  0010 DS:  ES:  CR0: 80050033
  [54075.377087] CR2: 7f3c521ba000 CR3: b4d24006 CR4: 
003606e0
  [54075.377090] DR0:  DR1:  DR2: 

  [54075.377091] DR3:  DR6: fffe0ff0 DR7: 
0400
  [54075.377092] Call Trace:
  [54075.377099]  _raw_spin_lock+0x20/0x30
  [54075.377104]  z3fold_zpool_map+0x72/0xf0 [z3fold]
  [54075.377108]  zpool_map_handle+0x1c/0x20
  [54075.377111]  zswap_writeback_entry+0x47/0x350
  [54075.377114]  z3fold_zpool_evict+0x2b/0x40 [z3fold]
  [54075.377116]  z3fold_zpool_shrink+0x2a5/0x350 [z3fold]
  [54075.377118]  zpool_shrink+0x1c/0x20
  [54075.377119]  zswap_frontswap_store+0x271/0x4d0
  [54075.377123]  __frontswap_store+0x78/0x100
  [54075.377125]  swap_writepage+0x3f/0x80
  [54075.377128]  pageout.isra.53+0x1e6/0x340
  [54075.377131]  shrink_page_list+0x992/0xbe0
  [54075.377133]  shrink_inactive_list+0x296/0x5e0
  [54075.377135]  ? __switch_to_asm+0x40/0x70
  [54075.377137]  ? syscall_return_via_sysret+0x5/0x75
  [54075.377140]  shrink_node_memcg+0x367/0x7e0
  [54075.377142]  ? __switch_to_asm+0x40/0x70
  [54075.377144]  ? __switch_to_asm+0x40/0x70
  [54075.377146]  shrink_node+0xe1/0x310
  [54075.377147]  ? shrink_node+0xe1/0x310
  [54075.377149]  do_try_to_free_pages+0xee/0x360
  [54075.377152]  try_to_free_pages+0xf1/0x1c0
  [54075.377155]  __alloc_pages_slowpath+0x405/0xec0
  [54075.377158]  __alloc_pages_nodemask+0x265/0x280
  [54075.377162]  alloc_pages_current+0x6a/0xe0
  [54075.377165]  __page_cache_alloc+0x86/0x90
  [54075.377167]  generic_file_read_iter+0x817/0xb60
  [54075.377169]  ? __switch_to_asm+0x40/0x70
  [54075.377170]  ? __switch_to_asm+0x34/0x70
  [54075.377172]  ? __switch_to_asm+0x40/0x70
  [54075.377173]  ? __switch_to_asm+0x34/0x70
  [54075.377174]  ? __switch_to_asm+0x40/0x70
  [54075.377176]  ? __switch_to_asm+0x34/0x70
  [54075.377177]  ? __switch_to_asm+0x40/0x70
  [54075.377178]  ? __switch_to_asm+0x34/0x70
  [54075.377181]  ext4_file_read_iter+0x56/0xf0
  [54075.377184]  new_sync_read+0xe2/0x130
  [54075.377187]  __vfs_read+0x29/0x40
  [54075.377188]  vfs_read+0x93/0x130
  [54075.377190]  SyS_read+0x55/0xc0
  [54075.377194]  do_syscall_64+0x7b/0x150
  [54075.377196]  entry_SYSCALL_64_after_hwframe+0x42/0xb7
  [54075.377197] RIP: 0033:0x7f1360bed27d
  [54075.377198] RSP: 002b:7f133e7f8a00 EFLAGS: 0293 ORIG_RAX: 

  [54075.377200] RAX: ffda RBX: 7f128e42c7d0 RCX: 
7f1360bed27d
  [54075.377201] RDX: 1000 RSI: 7f128dfe27d0 RDI: 
0014
  [54075.377201] RBP: 004f R08: 228def3009585ceb R09: 
60c81007fca0c815
  [54075.377202] R10: 6156858af7255092 R11: 0293 R12: 
003c
  [54075.377203] R13: 008b R14: 7f128d6d03cf R15: 
008b
  [54075.377205] Code: 84 00 00 00 00 00 0f 1f 44 00 00 55 

[Kernel-packages] [Bug 1785234] [NEW] Kernel panic softlockup with z3fold while running bitcoind

[Ken Sharp]

Public bug reported:

So far I have only triggered this while running bitcoind (or bitcoin-qt)
with the z3fold module loaded. I will do further testing to see if I can
trigger it any other ways.

[54075.373045] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:41]
[54075.377042] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
[bitcoin-msghand:7509]
[54075.377042] Modules linked in: cachefiles ip6table_filter ip6_tables fscache 
iptable_filter ip_tables x_tables crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel intel_rapl_perf psmouse serio_raw virtio_net pvpanic 
i2c_piix4 nfsd auth_rpcgss nfs_acl lockd grace sunrpc autofs4 aesni_intel 
aes_x86_64 crypto_simd cryptd glue_helper z3fold lz4hc lz4hc_compress
[54075.377068] CPU: 1 PID: 7509 Comm: bitcoin-msghand Not tainted 
4.15.0-1014-gcp #14~16.04.1-Ubuntu
[54075.377069] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
[54075.377076] RIP: 0010:native_queued_spin_lock_slowpath+0x25/0x1a0
[54075.377077] RSP: :aec7c13b7420 EFLAGS: 0202 ORIG_RAX: 
ff11
[54075.377079] RAX: 0001 RBX: db7b82e96a80 RCX: 
[54075.377080] RDX: 0001 RSI: 0001 RDI: 8c687a5aa010
[54075.377081] RBP: aec7c13b7420 R08: 8c6879c749d8 R09: 0002
[54075.377082] R10: aec7c13b74d8 R11: aec7c13b7628 R12: 8c687a5aa000
[54075.377083] R13: 8c687a5aa010 R14: 8c687a5aa000 R15: db7b82de7580
[54075.377084] FS:  7f133e7fc700() GS:8c687fd0() 
knlGS:
[54075.377086] CS:  0010 DS:  ES:  CR0: 80050033
[54075.377087] CR2: 7f3c521ba000 CR3: b4d24006 CR4: 003606e0
[54075.377090] DR0:  DR1:  DR2: 
[54075.377091] DR3:  DR6: fffe0ff0 DR7: 0400
[54075.377092] Call Trace:
[54075.377099]  _raw_spin_lock+0x20/0x30
[54075.377104]  z3fold_zpool_map+0x72/0xf0 [z3fold]
[54075.377108]  zpool_map_handle+0x1c/0x20
[54075.377111]  zswap_writeback_entry+0x47/0x350
[54075.377114]  z3fold_zpool_evict+0x2b/0x40 [z3fold]
[54075.377116]  z3fold_zpool_shrink+0x2a5/0x350 [z3fold]
[54075.377118]  zpool_shrink+0x1c/0x20
[54075.377119]  zswap_frontswap_store+0x271/0x4d0
[54075.377123]  __frontswap_store+0x78/0x100
[54075.377125]  swap_writepage+0x3f/0x80
[54075.377128]  pageout.isra.53+0x1e6/0x340
[54075.377131]  shrink_page_list+0x992/0xbe0
[54075.377133]  shrink_inactive_list+0x296/0x5e0
[54075.377135]  ? __switch_to_asm+0x40/0x70
[54075.377137]  ? syscall_return_via_sysret+0x5/0x75
[54075.377140]  shrink_node_memcg+0x367/0x7e0
[54075.377142]  ? __switch_to_asm+0x40/0x70
[54075.377144]  ? __switch_to_asm+0x40/0x70
[54075.377146]  shrink_node+0xe1/0x310
[54075.377147]  ? shrink_node+0xe1/0x310
[54075.377149]  do_try_to_free_pages+0xee/0x360
[54075.377152]  try_to_free_pages+0xf1/0x1c0
[54075.377155]  __alloc_pages_slowpath+0x405/0xec0
[54075.377158]  __alloc_pages_nodemask+0x265/0x280
[54075.377162]  alloc_pages_current+0x6a/0xe0
[54075.377165]  __page_cache_alloc+0x86/0x90
[54075.377167]  generic_file_read_iter+0x817/0xb60
[54075.377169]  ? __switch_to_asm+0x40/0x70
[54075.377170]  ? __switch_to_asm+0x34/0x70
[54075.377172]  ? __switch_to_asm+0x40/0x70
[54075.377173]  ? __switch_to_asm+0x34/0x70
[54075.377174]  ? __switch_to_asm+0x40/0x70
[54075.377176]  ? __switch_to_asm+0x34/0x70
[54075.377177]  ? __switch_to_asm+0x40/0x70
[54075.377178]  ? __switch_to_asm+0x34/0x70
[54075.377181]  ext4_file_read_iter+0x56/0xf0
[54075.377184]  new_sync_read+0xe2/0x130
[54075.377187]  __vfs_read+0x29/0x40
[54075.377188]  vfs_read+0x93/0x130
[54075.377190]  SyS_read+0x55/0xc0
[54075.377194]  do_syscall_64+0x7b/0x150
[54075.377196]  entry_SYSCALL_64_after_hwframe+0x42/0xb7
[54075.377197] RIP: 0033:0x7f1360bed27d
[54075.377198] RSP: 002b:7f133e7f8a00 EFLAGS: 0293 ORIG_RAX: 

[54075.377200] RAX: ffda RBX: 7f128e42c7d0 RCX: 7f1360bed27d
[54075.377201] RDX: 1000 RSI: 7f128dfe27d0 RDI: 0014
[54075.377201] RBP: 004f R08: 228def3009585ceb R09: 60c81007fca0c815
[54075.377202] R10: 6156858af7255092 R11: 0293 R12: 003c
[54075.377203] R13: 008b R14: 7f128d6d03cf R15: 008b
[54075.377205] Code: 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 0f 1f 44 00 
00 ba 01 00 00 00 8b 07 85 c0 75 0a f0 0f b1 17 85 c0 75 f2 5d c3 f3 90  ec 
81 fe 00 01 00 00 0f 84 92 00 00 00 41 b8 01 01 00 00 b9 
[54075.377234] Kernel panic - not syncing: softlockup: hung tasks
[54075.377236] CPU: 1 PID: 7509 Comm: bitcoin-msghand Tainted: G L  
 4.15.0-1014-gcp #14~16.04.1-Ubuntu
[54075.377237] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
[54075.377237] Call Trace:
[54075.377239]  
[54075.377241]  dump_stack+0x85/0xcb
[54075.377244]  panic+0xe9/0x254
[54075.377248]  

[Kernel-packages] [Bug 997825] Re: Missing nls_utf8.ko kernel module

[Ken Sharp]

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

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

Title:
  Missing nls_utf8.ko kernel module

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I think I can't mount a CIFS share since I don't have the nls_utf8
  module in the kernel linux-image-virtual.

  May 10 17:41:30 kickseed kernel: [ 6319.282908] CIFS VFS: CIFS mount
  error: iocharset utf8 not found

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-virtual 3.2.0.24.26
  ProcVersionSignature: Ubuntu 3.2.0-24.37-virtual 3.2.14
  Uname: Linux 3.2.0-24-virtual i686
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 mai 10 15:56 seq
   crw-rw---T 1 root audio 116, 33 mai 10 15:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Date: Thu May 10 17:51:10 2012
  HibernationDevice: RESUME=UUID=fb76e125-6895-456c-a2c4-0a2979a0de1b
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release i386 
(20120424.1)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=fr_CA:fr
   TERM=screen
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-virtual 
root=UUID=191ae0c4-da2c-4772-bff3-7ff22378389c ro
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-virtual N/A
   linux-backports-modules-3.2.0-24-virtual  N/A
   linux-firmware1.79
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/13/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd10/13/2009:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1074110] Re: wakeonlan fails if pm-hibernate used

[Ken Sharp]

Machine no longer available for testing.

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

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

Title:
  wakeonlan fails if pm-hibernate used

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After issuing halt -p, wakeonlan works fine. after issuing pm-
  hibernate, the machine will not wake up.

  interfaces:
  auto eth0
  iface eth0 inet dhcp
  up ethtool -s eth0 wol g
  down ethtool -s eth0 wol g

  Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes:  10baseT/Half 10baseT/Full 
 100baseT/Half 100baseT/Full 
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

  01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL-8139/8139C/8139C+ (rev 10)

  Not sure what else might be needed here, but apport-bug refuses to collect 
data for some reason.
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1073830

  Same is true of the latest upstream kernel:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc3-raring/
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  LiveMediaBuild: Ubuntu 7.10 "Gutsy Gibbon" - Release i386 (20071016)
  Package: linux 3.2.0.32.35
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.7.0-030700rc3-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups:

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

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

[Kernel-packages] [Bug 1413332] Re: eject command has to be issued twice

[Ken Sharp]

Precise is EOL. Works on Trusty+.

** Changed in: eject (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  eject command has to be issued twice

Status in eject package in Ubuntu:
  Fix Released

Bug description:
  eject has to be issued twice, as it will fail the first time,
  succeeding the second time.

  $ sudo eject /dev/sr0
  eject: unable to eject, last error: Inappropriate ioctl for device
  $ sudo eject /dev/sr0

  It should simply eject. I don't know what the first eject does
  different to the second. Nothing in the syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: eject 2.1.5+deb1+cvs20081104-9
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Wed Jan 21 16:46:45 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: eject
  UpgradeStatus: Upgraded to precise on 2014-12-07 (45 days ago)

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

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

[Kernel-packages] [Bug 1670315] Re: Ubuntu 17.04: Guest does not reflect all the cpus hotplugged

[Ken Sharp]

** Tags added: zesty

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

Title:
  Ubuntu 17.04: Guest does not reflect all the cpus hotplugged

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2017-02-28 
06:00:53 ==
  ---Problem Description---
  Guest does not reflect all the cpus hotplugged,
  Holpug vcpus using setvcpu with initial less number of cpus(1) to a greater 
cpus(~256), though
  setvcpu(libvirt) returns no error, guest does not reflect all cpus inside.

   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  Linux ltc-test-ci1 4.10.0-9-generic #11-Ubuntu SMP Mon Feb 20 13:45:11 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = power 8 ppc64le 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Start the guest(Ubuntu 17.04) with 1 current vcpu and 255 maxvcpus
  ...
   255
  ...
   
  

  

  # lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):1
  On-line CPU(s) list:   0
  Thread(s) per core:1
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  Hypervisor vendor: KVM
  Virtualization type:   para
  L1d cache: 64K
  L1i cache: 32K
  NUMA node0 CPU(s): 0
   
  2.# time virsh setvcpus virt-tests-vm1 255 --live --config

  
  real0m4.460s
  user0m0.012s
  sys 0m0.000s
  
root@ltc-test-ci1:/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper#
 echo $?
  0

  3. Check inside the guest after some time (10-15 mins) (
  dmesg of guest shows all the RTAS(255) events,but the guest showed only 90 
vcpus(it consistent around ~ 100 always).

  root@ubuntu:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):97
  On-line CPU(s) list:   0-96
  Thread(s) per core:1
  Core(s) per socket:97
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  Hypervisor vendor: KVM
  Virtualization type:   para
  L1d cache: 64K
  L1i cache: 32K
  NUMA node0 CPU(s): 0-96
  root@ubuntu:~# tail /proc/cpuinfo 

  processor : 96
  cpu   : POWER8E (raw), altivec supported
  clock : 3425.00MHz
  revision  : 2.1 (pvr 004b 0201)

  timebase  : 51200
  platform  : pSeries
  model : IBM pSeries (emulated by qemu)
  machine   : CHRP IBM pSeries (emulated by qemu)


  Userspace tool common name: libvirt, qemu 
   
  The userspace tool has the following bit modes: both 

  Userspace rpm: qemu-kvm   1:2.8+dfsg-
  2ubuntu1   ppc64el,ii  libvirt-bin
  2.5.0-3ubuntu2ppc64el

  Userspace tool obtained from project website:  na 
   
  Guest Details:
  #cat /etc/os-release |grep VERSION=
  VERSION="17.04 (Zesty Zapus)"
  # uname -a
  Linux ubuntu 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:00:06 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@ubuntu:~# dpkg -l |grep rtas
  ii  librtas-dev2.0.0-2
   ppc64el  userspace RTAS library development files
  ii  librtas2   2.0.0-2
   ppc64el  userspace RTAS library
  ii  librtasevent-dev   2.0.0-2
   ppc64el  RTAS events library development files
  ii  librtasevent2  2.0.0-2
   ppc64el  RTAS events library
  ii  ppc64-diag 2.7.1-6
   ppc64el  Platform error log analysis tool and rtas_errd daemon

  
  *Additional Instructions for sathe...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach ltrace and strace of userspace application.

  
  == Comment: #9 - BHARATA BHASKER RAO  - 2017-03-03 
04:32:14 ==
  When a large number of hotplug requests are generated too quickly, guest will 
miss the handling of a few RTAS events due to buffer overrun. Because of this, 
guest will not see all the hotplugged CPUs. This was raised earlier in bz 
142499 with the following resolution:

  - We need in-kernel CPU hotplug feature in the guest for this to work.
  - Until in-kernel CPU hotplug is available in the guest kernel, user should 
be careful not to overload the guest with so many successive hotplug requests.

  I reproduced the problem with ubuntu-1704 guest 

[Kernel-packages] [Bug 1399064] Re: bridges cannot have a mtu > 1500 by themselves

[Ken Sharp]

LXC displays similar behavious in Xenial. The "solution" was to set the
MTUs for all the slave interfaces, and all the interfaces within the
guests, then finally set the bridge MTU, otherwise it will simply
refuse. Worked fine.

Haven't yet looked into the configs to see if I can do this permanently.

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

Title:
  bridges cannot have a mtu > 1500 by themselves

Status in linux package in Ubuntu:
  Triaged

Bug description:
  A linux bridge always adopts the smallest MTU of the enslaved devices.
  When no device are enslaved, it defaults to a MTU of 1500 and refuses
  to use a larger one. This is problematic when using bridges enslaving
  only virtual NICs (vnetX) like it's common with KVM guests.

  Steps to reproduce the problem

  1) sudo ip link add br-test0 type bridge # create an empty bridge
  2) sudo ip link set br-test0 mtu 9000# attempt to set MTU > 1500
  3) ip link show dev br-test0 # confirm MTU

  Here, 2) returns "RTNETLINK answers: Invalid argument". One
  (cumbersome) way around this is:

  4) sudo modprobe dummy
  5) sudo ip link set dummy0 mtu 9000 master br-test0

  Then the bridge's MTU can be changed from anywhere to 9000.

  This bug is especially annoying for the virtualization case because
  the KVM's tap driver will by default adopt the bridge's MTU on startup
  making it impossible (without the workaround) to use a large MTU on
  the guest VMs.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $ apt-cache policy linux-image-3.13.0-41-generic iproute2
  linux-image-3.13.0-41-generic:
    Installed: 3.13.0-41.70
    Candidate: 3.13.0-41.70
    Version table:
   *** 3.13.0-41.70 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  iproute2:
    Installed: 3.12.0-2
    Candidate: 3.12.0-2
    Version table:
   *** 3.12.0-2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  4594 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: dmesg: klogctl failed: Operation not permitted
  Date: Wed Dec  3 23:02:25 2014
  HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f
  InstallationDate: Installed on 2014-01-26 (311 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic 
root=/dev/mapper/crypt-root ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 
nmi_watchdog=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-41-generic N/A
   linux-backports-modules-3.13.0-41-generic  N/A
   linux-firmware 1.127.10
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1399064] Re: bridges cannot have a mtu > 1500 by themselves

[Ken Sharp]

** Tags added: xenial

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

Title:
  bridges cannot have a mtu > 1500 by themselves

Status in linux package in Ubuntu:
  Triaged

Bug description:
  A linux bridge always adopts the smallest MTU of the enslaved devices.
  When no device are enslaved, it defaults to a MTU of 1500 and refuses
  to use a larger one. This is problematic when using bridges enslaving
  only virtual NICs (vnetX) like it's common with KVM guests.

  Steps to reproduce the problem

  1) sudo ip link add br-test0 type bridge # create an empty bridge
  2) sudo ip link set br-test0 mtu 9000# attempt to set MTU > 1500
  3) ip link show dev br-test0 # confirm MTU

  Here, 2) returns "RTNETLINK answers: Invalid argument". One
  (cumbersome) way around this is:

  4) sudo modprobe dummy
  5) sudo ip link set dummy0 mtu 9000 master br-test0

  Then the bridge's MTU can be changed from anywhere to 9000.

  This bug is especially annoying for the virtualization case because
  the KVM's tap driver will by default adopt the bridge's MTU on startup
  making it impossible (without the workaround) to use a large MTU on
  the guest VMs.

  Additional information:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  $ apt-cache policy linux-image-3.13.0-41-generic iproute2
  linux-image-3.13.0-41-generic:
    Installed: 3.13.0-41.70
    Candidate: 3.13.0-41.70
    Version table:
   *** 3.13.0-41.70 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
  iproute2:
    Installed: 3.12.0-2
    Candidate: 3.12.0-2
    Version table:
   *** 3.12.0-2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-41-generic 3.13.0-41.70
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  4594 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: dmesg: klogctl failed: Operation not permitted
  Date: Wed Dec  3 23:02:25 2014
  HibernationDevice: RESUME=UUID=8e7a3220-158f-413b-81b2-55b236bb1f3f
  InstallationDate: Installed on 2014-01-26 (311 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-41-generic 
root=/dev/mapper/crypt-root ro quiet splash 
cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-root possible_cpus=4 
nmi_watchdog=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-41-generic N/A
   linux-backports-modules-3.13.0-41-generic  N/A
   linux-firmware 1.127.10
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1421490] Re: Hyperthreading not always detected

[Ken Sharp]

"while your statement on how your graphics card is not supported by the
proprietary nvidia drivers in linux-lts-trusty was noticed, I'm not
seeing evidence to this"

Try building it then.

So far so good. I haven't seen this happen for a good while now. I've
upgraded to Trusty today. I'll leave this to expire and reopen if it
does reppear.

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

Title:
  Hyperthreading not always detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  From a cold boot (power off --> power on), this system doesn't always
  detect the presence of Hyperthreading on the processor. Note: warm
  reboot has very different problems so cannot be tested.

  It *usually* does, but on occasion for no obvious reason the system
  reports a single CPU (HT systems report two CPUs to increase
  performance).

  Despite all the articles claiming the opposite; this noticeably
  reduces performance of the system, especially in multi-threaded
  applications such as Google Chrome (in the case of Chrome the
  difference in response is considerable!)

  linux-lts-trusty is NOT an option as it is incompatible with my
  graphics drivers (no longer supported).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-26-generic 3.11.0-26.45~precise1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-26-generic.
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ken3021 F pulseaudio
   /dev/snd/pcmC0D0p:   ken3021 F...m pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'ICH5'/'Intel ICH5 with AD1980 at irq 17'
 Mixer name : 'Analog Devices AD1980'
 Components : 'AC97a:41445370'
 Controls  : 40
 Simple ctrls  : 29
  Date: Fri Feb 13 02:00:00 2015
  HibernationDevice: RESUME=UUID=e4687e6f-fa60-4155-bdd5-a1b94870204a
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: Dell Computer Corporation Dimension 8300
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic 
root=UUID=9c013c53-e232-4e09-8235-315a373bac88 ro zswap.enabled=1
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-26-generic N/A
   linux-backports-modules-3.11.0-26-generic  N/A
   linux-firmware 1.79.18
  RfKill:
   
  SourcePackage: linux-lts-saucy
  UpgradeStatus: Upgraded to precise on 2014-12-07 (67 days ago)
  dmi.bios.date: 09/27/2004
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A07
  dmi.board.name: 0W2562
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA07:bd09/27/2004:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0W2562:rvr:cvnDellComputerCorporation:ct6:cvr:
  dmi.product.name: Dimension 8300
  dmi.sys.vendor: Dell Computer Corporation

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

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

[Kernel-packages] [Bug 1413332] Re: eject command has to be issued twice

[Ken Sharp]

This appears to be fixed in Trusty.

Version: 2.1.5+deb1+cvs20081104-13.1

** Changed in: eject (Ubuntu)
   Status: New => Fix Committed

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

Title:
  eject command has to be issued twice

Status in eject package in Ubuntu:
  Fix Committed

Bug description:
  eject has to be issued twice, as it will fail the first time,
  succeeding the second time.

  $ sudo eject /dev/sr0
  eject: unable to eject, last error: Inappropriate ioctl for device
  $ sudo eject /dev/sr0

  It should simply eject. I don't know what the first eject does
  different to the second. Nothing in the syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: eject 2.1.5+deb1+cvs20081104-9
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Wed Jan 21 16:46:45 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: eject
  UpgradeStatus: Upgraded to precise on 2014-12-07 (45 days ago)

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

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

[Kernel-packages] [Bug 1452513] [NEW] Keyboard sleep button makes system unusable

[Ken Sharp]

Public bug reported:

The sleep button on my keyboard apparently attempts to put my computer
to sleep. The system then fails to respond to any attempt to wake it and
it has to be powered off. The screen goes off and there is no network
response to requests from another computer. Other than that it is not
clear what has happened. During reboot the file system is recovered by
fsck.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.11.0-26-generic 3.11.0-26.45~precise1
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-26-generic.
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ken2329 F pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Card0.Amixer.info:
 Card hw:0 'ICH5'/'Intel ICH5 with AD1980 at irq 17'
   Mixer name   : 'Analog Devices AD1980'
   Components   : 'AC97a:41445370'
   Controls  : 40
   Simple ctrls  : 29
Date: Thu May  7 01:44:15 2015
HibernationDevice: RESUME=UUID=e4687e6f-fa60-4155-bdd5-a1b94870204a
IwConfig:
 lono wireless extensions.
 
 eth1  no wireless extensions.
MachineType: Dell Computer Corporation Dimension 8300
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic 
root=UUID=9c013c53-e232-4e09-8235-315a373bac88 ro zswap.enabled=1 reboot=warm 
swapaccount=1
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-26-generic N/A
 linux-backports-modules-3.11.0-26-generic  N/A
 linux-firmware 1.79.18
RfKill:
 
SourcePackage: linux-lts-saucy
UpgradeStatus: Upgraded to precise on 2014-12-07 (150 days ago)
dmi.bios.date: 09/27/2004
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A07
dmi.board.name: 0W2562
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA07:bd09/27/2004:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0W2562:rvr:cvnDellComputerCorporation:ct6:cvr:
dmi.product.name: Dimension 8300
dmi.sys.vendor: Dell Computer Corporation

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


** Tags: apport-bug i386 precise qa-kernel-lts-testing resume suspend

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

Title:
  Keyboard sleep button makes system unusable

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

Bug description:
  The sleep button on my keyboard apparently attempts to put my computer
  to sleep. The system then fails to respond to any attempt to wake it
  and it has to be powered off. The screen goes off and there is no
  network response to requests from another computer. Other than that it
  is not clear what has happened. During reboot the file system is
  recovered by fsck.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-26-generic 3.11.0-26.45~precise1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-26-generic.
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ken2329 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'ICH5'/'Intel ICH5 with AD1980 at irq 17'
 Mixer name : 'Analog Devices AD1980'
 Components : 'AC97a:41445370'
 Controls  : 40
 Simple ctrls  : 29
  Date: Thu May  7 01:44:15 2015
  HibernationDevice: RESUME=UUID=e4687e6f-fa60-4155-bdd5-a1b94870204a
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: Dell Computer Corporation Dimension 8300
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic 
root=UUID=9c013c53-e232-4e09-8235-315a373bac88 ro zswap.enabled=1 reboot=warm 
swapaccount=1
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-26-generic N/A
   linux-backports-modules-3.11.0-26-generic  N/A
   linux-firmware 1.79.18
  RfKill:
   
  SourcePackage: linux-lts-saucy
  UpgradeStatus: Upgraded to precise on 2014-12-07 (150 days ago)
  dmi.bios.date: 09/27/2004
  dmi.bios.vendor: Dell Computer Corporation
  

[Kernel-packages] [Bug 1298611] Re: [FFe] apparmor signal and ptrace mediation

[Ken Sharp]

Thanks for clearing that up, Seth!

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

Title:
  [FFe] apparmor signal and ptrace mediation

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Background: kernel and apparmor userspace updates to support signal
  and ptrace mediation. These packages are listed in one bug because
  they are related, but the FFes may be granted and the uploads may
  happen at different times.

  = linux =
  Summary:
  This feature freeze exception is requested for signal and ptrace mediation 
via apparmor in the kernel. When used with a compatible apparmor userspace, 
signals and ptrace rules are supported. When used without a compatible apparmor 
userspace (eg, on a precise system with a trusty backport kernel), signal and 
ptrace mediation is not enforced (ie, you can use this kernel with an old 
userspace without any issues).

  The fine grained mediation of signals and ptraces also incorporates improved
  versioning support that allows this kernel to better support older and newer
  userspaces. This allows for this version of the kernel to work as a backport
  kernel unmodified (currently a patch and config are used to provide backport
  kernels).

  The kernel patch is available at git://kernel.ubuntu.com/jj/ubuntu-trusty.git
  in the trusty-alpha6 branch apparmor-alpha6-sync

  Testing:
  * 12.04 system with backported kernel: DONE
   * test-apparmor.py: PASS (runs extensive tests (upstream and distro))
   * exploratory manual testing: PASS (networking, aa-enforce with firefox, 
firefox works, apparmor blocks access, etc)
   * aa-status: PASS
   * lxc: PASS (containers can be created, started, shutdown)
   * libvirt: PASS (VMs started via openstack, and test-libvirt.py from QRT 
passes all tests)
  * 14.04 system (non-Touch) with current apparmor userspace: DONE (relevant 
parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor)
   * test-apparmor.py: PASS (runs extensive tests (upstream and distro))
   * exploratory manual testing: PASS (networking, aa-enforce with firefox, 
firefox works, apparmor blocks access, etc)
   * aa-status: PASS
   * lxc: PASS (containers can be created, started, shutdown)
   * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures 
unrelated to apparmor))
   * click-apparmor QRT touch image tests: PASS
   * apparmor-easyprof-ubuntu QRT touch image tests: PASS
  * 14.04 system (non-Touch) with updated apparmor userspace capable of 
supporting signal and ptrace mediation: DONE (relevant parts of 
https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor. Note: this is marked 
'done' from the kernel perspective-- the apparmor userspace upload is being 
prepared and tests assume userspace is using latest patches on the list)
   * test-apparmor.py: PASS (runs extensive tests (upstream and distro))
   * exploratory manual testing: PASS (networking, aa-enforce with firefox, 
firefox works, apparmor blocks access, etc)
   * aa-status: PASS
   * lxc: PASS (containers can be created, started, shutdown)
   * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures 
unrelated to apparmor))
   * click-apparmor QRT touch image tests: PASS
   * apparmor-easyprof-ubuntu QRT touch image tests: PASS

  Justification:
  This feature is required to support comprehensive application confinement on 
Ubuntu Touch. This feature adds a significant security benefit to libvirt's 
qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This 
feature also adds a welcome improvement to administrators wishing to further 
protect their systems.

  = apparmor userspace =
  Summary:
  This feature freeze exception is requested for signal and ptrace mediation 
for apparmor userspace. When used with a compatible kernel, signals and ptrace 
rules are supported. When used without a compatible kernel (eg, on Ubuntu Touch 
for a few weeks or with upstream kernels), signal and ptrace rules are skipped 
(ie, you can use this userspace with other kernels without issue).

  Testing:
  * 14.04 system with current kernel (Touch, kernel doesn't have signal and 
ptrace mediation yet):
   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: PASS (includes 
click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc)
  * 14.04 system with previous kernel lacking signal and ptrace mediation 
(non-Touch):
   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: PASS 
(exploratory manual testing, lxc, libvirt (3 failures unrelated to apparmor), 
etc)
   * test-apparmor.py: PASS
   * lightdm guest session: PASS 

[Kernel-packages] [Bug 1298611] Re: [FFe] apparmor signal and ptrace mediation

[Ken Sharp]

Did these changes end up in Precise? I see no sensible way to tell
AppArmor to allow a ptrace. The parser is totally confused by this.

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

Title:
  [FFe] apparmor signal and ptrace mediation

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Background: kernel and apparmor userspace updates to support signal
  and ptrace mediation. These packages are listed in one bug because
  they are related, but the FFes may be granted and the uploads may
  happen at different times.

  = linux =
  Summary:
  This feature freeze exception is requested for signal and ptrace mediation 
via apparmor in the kernel. When used with a compatible apparmor userspace, 
signals and ptrace rules are supported. When used without a compatible apparmor 
userspace (eg, on a precise system with a trusty backport kernel), signal and 
ptrace mediation is not enforced (ie, you can use this kernel with an old 
userspace without any issues).

  The fine grained mediation of signals and ptraces also incorporates improved
  versioning support that allows this kernel to better support older and newer
  userspaces. This allows for this version of the kernel to work as a backport
  kernel unmodified (currently a patch and config are used to provide backport
  kernels).

  The kernel patch is available at git://kernel.ubuntu.com/jj/ubuntu-trusty.git
  in the trusty-alpha6 branch apparmor-alpha6-sync

  Testing:
  * 12.04 system with backported kernel: DONE
   * test-apparmor.py: PASS (runs extensive tests (upstream and distro))
   * exploratory manual testing: PASS (networking, aa-enforce with firefox, 
firefox works, apparmor blocks access, etc)
   * aa-status: PASS
   * lxc: PASS (containers can be created, started, shutdown)
   * libvirt: PASS (VMs started via openstack, and test-libvirt.py from QRT 
passes all tests)
  * 14.04 system (non-Touch) with current apparmor userspace: DONE (relevant 
parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor)
   * test-apparmor.py: PASS (runs extensive tests (upstream and distro))
   * exploratory manual testing: PASS (networking, aa-enforce with firefox, 
firefox works, apparmor blocks access, etc)
   * aa-status: PASS
   * lxc: PASS (containers can be created, started, shutdown)
   * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures 
unrelated to apparmor))
   * click-apparmor QRT touch image tests: PASS
   * apparmor-easyprof-ubuntu QRT touch image tests: PASS
  * 14.04 system (non-Touch) with updated apparmor userspace capable of 
supporting signal and ptrace mediation: DONE (relevant parts of 
https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor. Note: this is marked 
'done' from the kernel perspective-- the apparmor userspace upload is being 
prepared and tests assume userspace is using latest patches on the list)
   * test-apparmor.py: PASS (runs extensive tests (upstream and distro))
   * exploratory manual testing: PASS (networking, aa-enforce with firefox, 
firefox works, apparmor blocks access, etc)
   * aa-status: PASS
   * lxc: PASS (containers can be created, started, shutdown)
   * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures 
unrelated to apparmor))
   * click-apparmor QRT touch image tests: PASS
   * apparmor-easyprof-ubuntu QRT touch image tests: PASS

  Justification:
  This feature is required to support comprehensive application confinement on 
Ubuntu Touch. This feature adds a significant security benefit to libvirt's 
qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This 
feature also adds a welcome improvement to administrators wishing to further 
protect their systems.

  = apparmor userspace =
  Summary:
  This feature freeze exception is requested for signal and ptrace mediation 
for apparmor userspace. When used with a compatible kernel, signals and ptrace 
rules are supported. When used without a compatible kernel (eg, on Ubuntu Touch 
for a few weeks or with upstream kernels), signal and ptrace rules are skipped 
(ie, you can use this userspace with other kernels without issue).

  Testing:
  * 14.04 system with current kernel (Touch, kernel doesn't have signal and 
ptrace mediation yet):
   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: PASS (includes 
click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc)
  * 14.04 system with previous kernel lacking signal and ptrace mediation 
(non-Touch):
   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: PASS 
(exploratory manual testing, lxc, libvirt (3 

[Kernel-packages] [Bug 1414363] Re: Computer cannot reboot

[Ken Sharp]

Adding reboot=warm to the Linux boot options allows the reboot to work
correctly. I don't know therefore if this counts as a valid bug.

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

Title:
  Computer cannot reboot

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

Bug description:
  The computer boots fine. It shuts down fine. The problem is that when
  rebooting it hangs shortly after the Grub screen.

  To add insult to injury none of the kernel output is ever printed,
  normal boot or broken reboot. quiet splash has been removed from the
  boot options.

  Tried reboot=bios but it made no difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-26-generic 3.11.0-26.45~precise1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Jan 24 20:40 seq
   crw-rw---T 1 root audio 116, 33 Jan 24 20:40 timer
  AplayDevices: aplay: device_list:204: no soundcards found...
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  ArecordDevices: arecord: device_list:204: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sat Jan 24 20:44:34 2015
  HibernationDevice: RESUME=UUID=e4687e6f-fa60-4155-bdd5-a1b94870204a
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: Dell Computer Corporation Dimension 8300
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic 
root=UUID=9c013c53-e232-4e09-8235-315a373bac88 ro zswap.enabled=1 reboot=rst 
vga_mode=800x600
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-26-generic N/A
   linux-backports-modules-3.11.0-26-generic  N/A
   linux-firmware 1.79.18
  RfKill:
   
  SourcePackage: linux-lts-saucy
  UpgradeStatus: Upgraded to precise on 2014-12-07 (48 days ago)
  dmi.bios.date: 09/27/2004
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A07
  dmi.board.name: 0W2562
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA07:bd09/27/2004:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0W2562:rvr:cvnDellComputerCorporation:ct6:cvr:
  dmi.product.name: Dimension 8300
  dmi.sys.vendor: Dell Computer Corporation

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

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

[Kernel-packages] [Bug 1421490] [NEW] Hyperthreading not always detected

[Ken Sharp]

Public bug reported:

From a cold boot (power off -- power on), this system doesn't always
detect the presence of Hyperthreading on the processor. Note: warm
reboot has very different problems so cannot be tested.

It *usually* does, but on occasion for no obvious reason the system
reports a single CPU (HT systems report two CPUs to increase
performance).

Despite all the articles claiming the opposite; this noticeably reduces
performance of the system, especially in multi-threaded applications
such as Google Chrome (in the case of Chrome the difference in response
is considerable!)

linux-lts-trusty is NOT an option as it is incompatible with my graphics
drivers (no longer supported).

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.11.0-26-generic 3.11.0-26.45~precise1
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-26-generic.
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ken3021 F pulseaudio
 /dev/snd/pcmC0D0p:   ken3021 F...m pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not 
found.
Card0.Amixer.info:
 Card hw:0 'ICH5'/'Intel ICH5 with AD1980 at irq 17'
   Mixer name   : 'Analog Devices AD1980'
   Components   : 'AC97a:41445370'
   Controls  : 40
   Simple ctrls  : 29
Date: Fri Feb 13 02:00:00 2015
HibernationDevice: RESUME=UUID=e4687e6f-fa60-4155-bdd5-a1b94870204a
IwConfig:
 lono wireless extensions.
 
 eth1  no wireless extensions.
MachineType: Dell Computer Corporation Dimension 8300
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-26-generic 
root=UUID=9c013c53-e232-4e09-8235-315a373bac88 ro zswap.enabled=1
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-26-generic N/A
 linux-backports-modules-3.11.0-26-generic  N/A
 linux-firmware 1.79.18
RfKill:
 
SourcePackage: linux-lts-saucy
UpgradeStatus: Upgraded to precise on 2014-12-07 (67 days ago)
dmi.bios.date: 09/27/2004
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A07
dmi.board.name: 0W2562
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA07:bd09/27/2004:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0W2562:rvr:cvnDellComputerCorporation:ct6:cvr:
dmi.product.name: Dimension 8300
dmi.sys.vendor: Dell Computer Corporation

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


** Tags: apport-bug i386 performance precise qa-kernel-lts-testing

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

Title:
  Hyperthreading not always detected

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

Bug description:
  From a cold boot (power off -- power on), this system doesn't always
  detect the presence of Hyperthreading on the processor. Note: warm
  reboot has very different problems so cannot be tested.

  It *usually* does, but on occasion for no obvious reason the system
  reports a single CPU (HT systems report two CPUs to increase
  performance).

  Despite all the articles claiming the opposite; this noticeably
  reduces performance of the system, especially in multi-threaded
  applications such as Google Chrome (in the case of Chrome the
  difference in response is considerable!)

  linux-lts-trusty is NOT an option as it is incompatible with my
  graphics drivers (no longer supported).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-26-generic 3.11.0-26.45~precise1
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-26-generic.
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ken3021 F pulseaudio
   /dev/snd/pcmC0D0p:   ken3021 F...m pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'ICH5'/'Intel ICH5 with AD1980 at irq 17'
 Mixer name : 'Analog Devices AD1980'
 Components : 'AC97a:41445370'
 Controls  : 40
 Simple ctrls  : 29
  Date: Fri Feb 13 02:00:00 2015
  HibernationDevice: RESUME=UUID=e4687e6f-fa60-4155-bdd5-a1b94870204a
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: Dell Computer 

[Kernel-packages] [Bug 1413332] [NEW] eject command has to be issued twice

[Ken Sharp]

Public bug reported:

eject has to be issued twice, as it will fail the first time, succeeding
the second time.

$ sudo eject /dev/sr0
eject: unable to eject, last error: Inappropriate ioctl for device
$ sudo eject /dev/sr0

It should simply eject. I don't know what the first eject does different
to the second. Nothing in the syslog.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: eject 2.1.5+deb1+cvs20081104-9
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Wed Jan 21 16:46:45 2015
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: eject
UpgradeStatus: Upgraded to precise on 2014-12-07 (45 days ago)

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


** Tags: apport-bug i386 precise

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

Title:
  eject command has to be issued twice

Status in eject package in Ubuntu:
  New

Bug description:
  eject has to be issued twice, as it will fail the first time,
  succeeding the second time.

  $ sudo eject /dev/sr0
  eject: unable to eject, last error: Inappropriate ioctl for device
  $ sudo eject /dev/sr0

  It should simply eject. I don't know what the first eject does
  different to the second. Nothing in the syslog.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: eject 2.1.5+deb1+cvs20081104-9
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Wed Jan 21 16:46:45 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: eject
  UpgradeStatus: Upgraded to precise on 2014-12-07 (45 days ago)

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

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

[Kernel-packages] [Bug 442282] Re: CDROM door does not open

[Ken Sharp]

** Tags added: karmic lucid

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

Title:
  CDROM door does not open

Status in eject package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: eject

  root@dell-desktop:~# eject -v /dev/sr0
  eject: device name is `/dev/sr0'
  eject: expanded name is `/dev/sr0'
  eject: `/dev/sr0' is not mounted
  eject: `/dev/sr0' is not a mount point
  eject: `/dev/sr0' is not a multipartition device
  eject: trying to eject `/dev/sr0' using CD-ROM eject command
  eject: CD-ROM eject command failed
  eject: trying to eject `/dev/sr0' using SCSI commands
  eject: SCSI eject succeeded

  However, nothing happens and the door remains shut.

  ProblemType: Bug
  Architecture: i386
  Date: Sun Oct  4 07:33:11 2009
  DistroRelease: Ubuntu 9.10
  Package: eject 2.1.5+deb1+cvs20081104-6
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  SourcePackage: eject
  Uname: Linux 2.6.31-11-generic i686

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

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

[Kernel-packages] [Bug 1011175] Re: Unable to eject broken dvd

[Ken Sharp]

Possible duplicate of #726785

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

Title:
  Unable to eject broken dvd

Status in eject package in Ubuntu:
  New

Bug description:
  Normally, I can eject my DVDs simply using eject from the command
  line or using the context menu in dolphin (right-click on the DVD -
  eject).

  However, today I came across a broken DVD. broken in this case
  means: Probably something went wrong while burning the CD; whatsoever
  the exact reasonmight be, the result is that the DVD can not be
  mounted.

  If I now try to eject the DVD using sudo eject -v, I receive the
  following output:

  eject: using default device `cdrom'
  eject: device name is `cdrom'
  eject: expanded name is `/dev/cdrom'
  eject: `/dev/cdrom' is a link to `/dev/sr1'
  eject: `/dev/sr1' is not mounted
  eject: `/dev/sr1' is not a mount point
  eject: `/dev/sr1' is not a multipartition device
  eject: trying to eject `/dev/sr1' using CD-ROM eject command
  eject: CD-ROM eject command failed

  
  eject: trying to eject `/dev/sr1' using SCSI commands 

  
  eject: SCSI eject failed  

  
  eject: trying to eject `/dev/sr1' using floppy eject command  

  
  eject: floppy eject command failed

  
  eject: trying to eject `/dev/sr1' using tape offline command  

  
  eject: tape offline command failed

  
  eject: unable to eject, last error: Inappropriate ioctl for device

  A normal eject -v with an unbroken DVD inserted looks like this:

  eject: using default device `cdrom'
  eject: device name is `cdrom'
  eject: expanded name is `/dev/cdrom'
  eject: `/dev/cdrom' is a link to `/dev/sr1'
  eject: `/dev/sr1' is not mounted
  eject: `/dev/sr1' is not a mount point
  eject: `/dev/sr1' is not a multipartition device
  eject: trying to eject `/dev/sr1' using CD-ROM eject command
  eject: CD-ROM eject command failed
  eject: trying to eject `/dev/sr1' using SCSI commands
  eject: SCSI eject succeeded

  I can't find any possibility to eject the broken DVD. In dolphin it
  doesn't even show up, and the eject button on the drive itself is also
  not working. I need to restart my PC and eject the DVD while booting!

  In KInfocenter, the device is displayed with the following information:
  Vendor: HL-DT-ST Model: DVD-ROM GDR8164B Rev: 0L06

  Is there any further information I can provide on the problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: eject 2.1.5+deb1+cvs20081104-8
  ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
  Uname: Linux 3.0.0-20-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sun Jun 10 16:07:48 2012
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  ProcEnviron:
   LANGUAGE=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eject
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (237 days ago)

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

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

[Kernel-packages] [Bug 298567] Re: No Permission to Eject CD

[Ken Sharp]

** Tags added: i386 intrepid precise

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

Title:
  No Permission to Eject CD

Status in eject package in Ubuntu:
  New

Bug description:
  Binary package hint: eject

  I have two logins running.  The one in the background is idle.  When I
  am in my current login and inserting CD's, copying contents to home
  and then ejecting the CD, it will often report I do not have
  permissions to eject the CD.

  When I look at the details it shows the other login with permission.
  I then switch to find the CD folder open on that desktop.

  I have to force it to eject from my current login with sudo eject.  I
  would think whichever is the currently active login, that it would the
  permissions to eject/umount the CD.

  I am running Intrepid 2.6.27-7.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /usr/bin/yelp
  NonfreeKernelModules: nvidia
  Package: yelp 2.24.0-0ubuntu2
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  Uname: Linux 2.6.27-7-generic i686

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

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

[Kernel-packages] [Bug 542959] Re: does not terminate at computer shutdown

[Ken Sharp]

You have not provided a description at all.

** Tags removed: shutdown-hang

** Changed in: eject (Ubuntu)
   Status: New = Incomplete

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

Title:
  does not terminate at computer shutdown

Status in eject package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: eject

  ?

  ProblemType: Bug
  Architecture: i386
  Date: Sat Mar 20 21:55:45 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/eject
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100224.1)
  OmitPids: 4966 4985 925
  Package: eject 2.1.5+deb1+cvs20081104-7
  ProcCmdline: eject -T
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
  SourcePackage: eject
  Title: does not terminate at computer shutdown
  Uname: Linux 2.6.32-14-generic i686

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

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

[Kernel-packages] [Bug 489427] Re: can not eject DVD drive

[Ken Sharp]

** Tags added: karmic

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

Title:
  can not eject DVD drive

Status in eject package in Ubuntu:
  New

Bug description:
  Binary package hint: eject

  I had a DVD+RW inserted that I unmounted and mounted several times (as
  bug data collection for another bug).

  After that right clicked the DVD icon in Places/Computer as selected
  to blank it.

  Then I tried to burn an iso image to it, but brasero complained there
  is no space in the blank DVD...

  So I decided to do the old trick of eject-and-reinsert, but I can't eject it.
  The hardware eject button has no effect.
  In the GUI, the context menu has no Eject item.

  cmd line gives:
  $ sudo eject -v  /dev/sr0 
  eject: device name is `/dev/sr0'
  eject: expanded name is `/dev/sr0'
  eject: `/dev/sr0' is not mounted
  eject: `/dev/sr0' is not a mount point
  eject: `/dev/sr0' is not a multipartition device
  eject: trying to eject `/dev/sr0' using CD-ROM eject command
  eject: CD-ROM eject command failed
  eject: trying to eject `/dev/sr0' using SCSI commands
  eject: SCSI eject succeeded

  But is does not eject.

  The drive is:
   ata5.00: ATAPI: TSSTcorpCD/DVDW TS-L632D, HH15, max MWDMA2

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Nov 28 00:28:55 2009
  DistroRelease: Ubuntu 9.10
  LiveMediaBuild: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  Package: eject 2.1.5+deb1+cvs20081104-6
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: eject
  Uname: Linux 2.6.31-14-generic x86_64

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

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

[Kernel-packages] [Bug 926925] Re: eject -i 1 fails to lock drive eject button

[Ken Sharp]

*** This bug is a duplicate of bug 885051 ***
https://bugs.launchpad.net/bugs/885051

** This bug has been marked a duplicate of bug 885051
   eject -i no longer works

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

Title:
  eject -i 1 fails to lock drive eject button

Status in eject package in Ubuntu:
  New

Bug description:
  Running `eject -i 1` is supposed to lock the cd drive so it can't be
  ejected:

  $ eject -i 1
  CD-Drive may NOT be ejected with device button

  Until a few weeks ago, this worked properly: after this command,
  neither running `eject` nor pressing the device eject button would
  open the drive.  However, recently the device eject button has been
  able to eject the drive:

  $ eject -i 1
  CD-Drive may NOT be ejected with device button
  $ eject 
  eject: unable to eject, last error: Inappropriate ioctl for device
  $ #press eject button:  now the device _ejects_, which is incorrect.  After 
closing the drive:
  $ eject 
  $ #The drive now opens.

  This is running Ubuntu 11.10, eject 2.1.5+deb1+cvs20081104-8, and
  kernel 3.0.0-15.26 generic x86_64.

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

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

[Kernel-packages] [Bug 885051] Re: eject stop working

[Ken Sharp]

** Tags added: natty precise

** Summary changed:

- eject stop working
+ eject -i no longer works

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

Title:
  eject -i no longer works

Status in eject package in Ubuntu:
  Confirmed

Bug description:
  I used to run eject -i 1 to lock my cd-rom, but it stopped working
  after upgrading to 11.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: eject 2.1.5+deb1+cvs20081104-8
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Nov  1 23:26:38 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eject
  UpgradeStatus: Upgraded to oneiric on 2011-11-02 (0 days ago)

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

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

[Kernel-packages] [Bug 980472] Re: Inappropriate ioctl for device when ejecting USB flash drive

[Ken Sharp]

Please stop spamming this report with every type of media that has
trouble ejecting.

Is the ORIGINAL issue (USB drive) still a problem?

** Tags added: precise

** Changed in: eject (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  Inappropriate ioctl for device when ejecting USB flash drive

Status in eject package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 12.04 beta 2 (eject version 2.1.5+deb1+cvs20081104-9), when
  I eject a flash drive using sudo eject, I get this error message:

  not an sg device, or old sg driver
  eject: unable to eject, last error: Inappropriate ioctl for device

  Previously, I had no problems ejecting using the same version of
  eject.  The problem came up when I formatted the flash drive so that
  it would be encrypted.  Also, I change the file system from the
  default (FAT32, I think) to NTFS.  On another drive which I formatted
  to ext4, the same problem occurs -- again, it is now an encrypted file
  system.

  The drive is successfully unmounted, though, since it no longer
  appears under df.  However, it is still on since the light is
  still on.

  sudo umount gives no problems.

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

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

[Kernel-packages] [Bug 726785] Re: Cannot eject CDROM with bad media inserted - IO error

[Ken Sharp]

Confirming.

[21281.116107] Volume set (in), Read cd: be 00 00 02 3d 13 00 00 01 f8 00 00
[21281.116130] ata2.00: cmd a0/01:00:00:30:09/00:00:00:00:00/a0 tag 19 dma 2352 
in
[21281.116130]  res 40/00:02:00:38:00/00:00:00:00:00/a0 Emask 0x4 
(timeout)
[21281.116135] ata2.00: status: { DRDY }
[21286.156034] ata2: link is slow to respond, please be patient (ready=0)
[21291.140036] ata2: device not ready (errno=-16), forcing hardreset
[21291.140049] ata2: soft resetting link
[21296.336067] ata2: link is slow to respond, please be patient (ready=0)
[21301.152050] ata2: SRST failed (errno=-16)
[21301.152067] ata2: soft resetting link
[21306.348090] ata2: link is slow to respond, please be patient (ready=0)
[21311.164039] ata2: SRST failed (errno=-16)
[21311.164053] ata2: soft resetting link
[21316.360103] ata2: link is slow to respond, please be patient (ready=0)
[21346.208037] ata2: SRST failed (errno=-16)
[21346.208052] ata2: soft resetting link
[21351.236034] ata2: SRST failed (errno=-16)
[21351.247334] ata2: reset failed, giving up
[21351.247349] ata2.00: disabled
[21351.247357] ata2.01: disabled
[21351.247441] ata2: EH complete

$ sudo eject -v /dev/sr0
eject: device name is `/dev/sr0'
eject: expanded name is `/dev/sr0'
eject: `/dev/sr0' is not mounted
eject: `/dev/sr0' is not a mount point
eject: `/dev/sr0' is not a multipartition device
eject: trying to eject `/dev/sr0' using CD-ROM eject command
eject: CD-ROM eject command failed
eject: trying to eject `/dev/sr0' using SCSI commands
eject: SCSI eject failed
eject: trying to eject `/dev/sr0' using floppy eject command
eject: floppy eject command failed
eject: trying to eject `/dev/sr0' using tape offline command
eject: tape offline command failed
eject: unable to eject, last error: Inappropriate ioctl for device

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

Title:
  Cannot eject CDROM with bad media inserted - IO error

Status in eject package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: eject

  I have media which cannot be read
  [ 7707.154066] Buffer I/O error on device sr0, logical block 1024
  [ 7707.154070] Buffer I/O error on device sr0, logical block 1025
  During read error I cant eject media even with eject command.
  I know about /proc/sys/dev/cdrom/lock and /proc/sys/dev/cdrom/autoclose 
variables but they need to be set before inserting media, and only way to fast 
remove is hard reset system. Eject should have --force option not as a feature 
but as solution of critical bug - in my case Cdrom gave strange sound and there 
was a risk it will brake.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: eject 2.1.5+deb1+cvs20081104-7
  Uname: Linux 2.6.34-02063407-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Feb 28 21:43:17 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LANGUAGE=pl_PL
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: eject

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

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

[Kernel-packages] [Bug 726785] Re: Cannot eject CDROM with bad media inserted - IO error

[Ken Sharp]

** Tags added: i386 precise

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

Title:
  Cannot eject CDROM with bad media inserted - IO error

Status in eject package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: eject

  I have media which cannot be read
  [ 7707.154066] Buffer I/O error on device sr0, logical block 1024
  [ 7707.154070] Buffer I/O error on device sr0, logical block 1025
  During read error I cant eject media even with eject command.
  I know about /proc/sys/dev/cdrom/lock and /proc/sys/dev/cdrom/autoclose 
variables but they need to be set before inserting media, and only way to fast 
remove is hard reset system. Eject should have --force option not as a feature 
but as solution of critical bug - in my case Cdrom gave strange sound and there 
was a risk it will brake.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: eject 2.1.5+deb1+cvs20081104-7
  Uname: Linux 2.6.34-02063407-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Feb 28 21:43:17 2011
  EcryptfsInUse: Yes
  ProcEnviron:
   LANGUAGE=pl_PL
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: eject

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

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

[Kernel-packages] [Bug 1035923] Re: eject -i 0. while being accepted no longer has any effect, drive remains locked

[Ken Sharp]

*** This bug is a duplicate of bug 885051 ***
https://bugs.launchpad.net/bugs/885051

** This bug has been marked a duplicate of bug 885051
   eject -i no longer works

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

Title:
  eject -i 0. while being accepted no longer has any effect, drive
  remains locked

Status in eject package in Ubuntu:
  New

Bug description:
  Test case
  with No disk in drive run eject -i 0
  will return - CD-Drive may be ejected with device button
  Insert a disk, let drive 'settle', try to eject with device button
  The disk is not ejected.

  One reason for wanting - 
  Many older cd/dvd drives on laptops, particularly slot loading slimline, can  
occassionaly not recognize one disk or another.
  Without an unlocked drive there is no way to eject except reboot  eject from 
during the reboot process.

  Additionally really don't follow the logic of setting locked as
  default in the 1st. place, apps that are using the drive should lock
  it themselces  can't see the possibility of inadvertent ejection in a
  travel scenario as being all that likely

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: eject 2.1.5+deb1+cvs20081104-11
  ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0
  Uname: Linux 3.5.0-9-generic x86_64
  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  Date: Sun Aug 12 14:06:39 2012
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120707)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eject
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1085746] Re: Cannot eject flash memory card

[Ken Sharp]

** Tags removed: eject permissions
** Tags added: maverick natty oneiric precise quantal

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

Title:
  Cannot eject flash memory card

Status in eject package in Ubuntu:
  New

Bug description:
  As a normal user, insert SDHC flash memory card, it mounts ok, but
  there is an error when trying to eject it:

   $ eject /media/00F0-82C2
  eject: unable to open `/dev/mmcblk0p1'

   $ eject --version
  eject version 2.1.5 by Jeff Tranter (tran...@pobox.com)

   $ dpkg -l | dpkg-grep eject
  eject-2.1.5+deb1+cvs20081104-9

  This is happening in all recent versions of Ubuntu from Maverick to
  Quantal.

  sudo eject works ok, and the device permissions are:
    brw-rw 1 root disk 179, 1 Oct  1 12:00 /dev/mmcblk0p1

  Looks like the permissions handling needs to be changed.
  Either the insert and the eject should both work, or they both should not 
work. Being able to insert, but not eject is inconsistent and ridiculous.

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

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

[Kernel-packages] [Bug 1011175] Re: Unable to eject broken dvd

[Ken Sharp]

Possible duplicate of Bug #726785

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

Title:
  Unable to eject broken dvd

Status in eject package in Ubuntu:
  New

Bug description:
  Normally, I can eject my DVDs simply using eject from the command
  line or using the context menu in dolphin (right-click on the DVD -
  eject).

  However, today I came across a broken DVD. broken in this case
  means: Probably something went wrong while burning the CD; whatsoever
  the exact reasonmight be, the result is that the DVD can not be
  mounted.

  If I now try to eject the DVD using sudo eject -v, I receive the
  following output:

  eject: using default device `cdrom'
  eject: device name is `cdrom'
  eject: expanded name is `/dev/cdrom'
  eject: `/dev/cdrom' is a link to `/dev/sr1'
  eject: `/dev/sr1' is not mounted
  eject: `/dev/sr1' is not a mount point
  eject: `/dev/sr1' is not a multipartition device
  eject: trying to eject `/dev/sr1' using CD-ROM eject command
  eject: CD-ROM eject command failed

  
  eject: trying to eject `/dev/sr1' using SCSI commands 

  
  eject: SCSI eject failed  

  
  eject: trying to eject `/dev/sr1' using floppy eject command  

  
  eject: floppy eject command failed

  
  eject: trying to eject `/dev/sr1' using tape offline command  

  
  eject: tape offline command failed

  
  eject: unable to eject, last error: Inappropriate ioctl for device

  A normal eject -v with an unbroken DVD inserted looks like this:

  eject: using default device `cdrom'
  eject: device name is `cdrom'
  eject: expanded name is `/dev/cdrom'
  eject: `/dev/cdrom' is a link to `/dev/sr1'
  eject: `/dev/sr1' is not mounted
  eject: `/dev/sr1' is not a mount point
  eject: `/dev/sr1' is not a multipartition device
  eject: trying to eject `/dev/sr1' using CD-ROM eject command
  eject: CD-ROM eject command failed
  eject: trying to eject `/dev/sr1' using SCSI commands
  eject: SCSI eject succeeded

  I can't find any possibility to eject the broken DVD. In dolphin it
  doesn't even show up, and the eject button on the drive itself is also
  not working. I need to restart my PC and eject the DVD while booting!

  In KInfocenter, the device is displayed with the following information:
  Vendor: HL-DT-ST Model: DVD-ROM GDR8164B Rev: 0L06

  Is there any further information I can provide on the problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: eject 2.1.5+deb1+cvs20081104-8
  ProcVersionSignature: Ubuntu 3.0.0-20.34-generic 3.0.30
  Uname: Linux 3.0.0-20-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sun Jun 10 16:07:48 2012
  InstallationMedia: Kubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  ProcEnviron:
   LANGUAGE=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eject
  UpgradeStatus: Upgraded to oneiric on 2011-10-16 (237 days ago)

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

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

[Kernel-packages] [Bug 500069] Re: USB file transfer causes system freezes; ops take hours instead of minutes

[Ken Sharp]

Is this not fixed now? It was fixed upstream a while ago.

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

Title:
  USB file transfer causes system freezes; ops take hours instead of
  minutes

Status in The Linux Kernel:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Fedora:
  Unknown

Bug description:
  USB Drive is a MP3 Player 2GB

  sbec@Diamant:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 002: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse 
Receiver
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 004: ID 0402:5661 ALi Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  sbec@Diamant:~$

  Linux Diamant 2.6.31-15-generic #50-Ubuntu SMP Tue Nov 10 14:54:29 UTC 2009 
i686 GNU/Linux
  Ubuntu 2.6.31-15.50-generic

  to test, i issued dd command:
  dd if=/dev/zero of=/media/usb-disk/test-file bs=32

  while dd is running i run dstat this is in the log file attached.

  other logs are also in the tar.gz file...

  there is a huge USB performance Bug report #1972262. this Report is
  something simular

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

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

[Kernel-packages] [Bug 1274349] Re: Fix-compat_sys_recvmsg-on-x32-archs

[Ken Sharp]

** Tags added: bot-stop-nagging

** Changed in: linux (Ubuntu Trusty)
   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/1274349

Title:
  Fix-compat_sys_recvmsg-on-x32-archs

Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-lts-raring” package in Ubuntu:
  Invalid
Status in “linux-lts-saucy” package in Ubuntu:
  Invalid
Status in “linux” source package in Precise:
  Invalid
Status in “linux-lts-raring” source package in Precise:
  Fix Released
Status in “linux-lts-saucy” source package in Precise:
  Fix Released
Status in “linux” source package in Saucy:
  Fix Released
Status in “linux-lts-raring” source package in Saucy:
  Invalid
Status in “linux-lts-saucy” source package in Saucy:
  Invalid
Status in “linux” source package in Trusty:
  Confirmed
Status in “linux-lts-raring” source package in Trusty:
  Invalid
Status in “linux-lts-saucy” source package in Trusty:
  Invalid

Bug description:
  Reported by pageexec

  asmlinkage long compat_sys_recvmmsg(int fd, struct compat_mmsghdr __user 
*mmsg,
  unsigned int vlen, unsigned int flags,
  struct compat_timespec __user *timeout)
  {
  int datagrams;
  struct timespec ktspec;

  if (flags  MSG_CMSG_COMPAT)
  return -EINVAL;

  if (COMPAT_USE_64BIT_TIME)
  return __sys_recvmmsg(fd, (struct mmsghdr __user *)mmsg, vlen,
flags | MSG_CMSG_COMPAT,
(struct timespec *) timeout);
  /*...*/

  The timeout pointer parameter is provided by userland (hence the
  __user annotation) but for x32 syscalls it's simply cast to a kernel
  pointer and is passed to __sys_recvmmsg which will eventually directly
  dereference it for both reading and writing. Other callers to
  __sys_recvmmsg properly copy from userland to the kernel first.

  The impact is a sort of arbitrary kernel write-where-what primitive by
  unprivileged users where the to-be-written area must contain valid
  timespec data initially (the first 64 bit long field must be positive
  and the second one must be  1G).

  The bug was introduced by commit
  http://git.kernel.org/linus/ee4fa23c4b (other uses of
  COMPAT_USE_64BIT_TIME seem fine) and should affect all kernels since
  3.4 (and perhaps vendor kernels if they backported x32 support along
  with this code). Note that CONFIG_X86_X32_ABI gets enabled at build
  time and only if CONFIG_X86_X32 is enabled and ld can build x32
  executables.

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

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

[Kernel-packages] [Bug 1073804] Re: pm-suspend powers off the computer

[Ken Sharp]

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

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

Title:
  pm-suspend powers off the computer

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Running pm-suspend on my Precise i386 machine powers it off, which
  it obviously shouldn't do.  It's not clear if a shutdown is completed,
  or whether the power is simply cut.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pm-utils 1.4.1-9
  Uname: Linux 3.2.0-32-generic-pae i686
  Architecture: i386
  Date: Thu Nov  1 04:37:53 2012
  LiveMediaBuild: Ubuntu 7.10 Gutsy Gibbon - Release i386 (20071016)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  LiveMediaBuild: Ubuntu 7.10 Gutsy Gibbon - Release i386 (20071016)
  Package: pm-utils 1.4.1-9
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.7.0-030700rc3-generic i686
  UserGroups:

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

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

[Kernel-packages] [Bug 1074110] Re: wakeonlan fails if pm-hibernate used

[Ken Sharp]

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

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

Title:
  wakeonlan fails if pm-hibernate used

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

Bug description:
  After issuing halt -p, wakeonlan works fine. after issuing pm-
  hibernate, the machine will not wake up.

  interfaces:
  auto eth0
  iface eth0 inet dhcp
  up ethtool -s eth0 wol g
  down ethtool -s eth0 wol g

  Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes:  10baseT/Half 10baseT/Full 
 100baseT/Half 100baseT/Full 
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

  01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL-8139/8139C/8139C+ (rev 10)

  Not sure what else might be needed here, but apport-bug refuses to collect 
data for some reason.
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1073830

  Same is true of the latest upstream kernel:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc3-raring/
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  LiveMediaBuild: Ubuntu 7.10 Gutsy Gibbon - Release i386 (20071016)
  Package: linux 3.2.0.32.35
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.7.0-030700rc3-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups:

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

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

[Kernel-packages] [Bug 1252102] Re: [BCM4311] Segmentation fault when building bcmwl-kernel-source

[Ken Sharp]

I have since moved this machine to the Raring HWE (linux-generic-lts-
raring) and the package builds with or without zram (which I have
removed altogether).

I guess the issue is with the 3.2 kernel. I'll reopen if I get round to
testing further with that kernel, but I have a feeling nobody is
particularly interested in that scenario so will leave to expire for
now.

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

Title:
  [BCM4311] Segmentation fault when building bcmwl-kernel-source

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  While attempting to build bcmwl-kernel-source with DKMS (all
  automatic) a segmentation fault occurs and the system claims there is
  a bug in the kernel.

  Copy/paste not possible and logs aren't saved so will update soon
  (testing upstream kernels).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-56-generic-pae 3.2.0-56.86
  ProcVersionSignature: Ubuntu 3.2.0-56.86-generic-pae 3.2.51
  Uname: Linux 3.2.0-56-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices: aplay: device_list:252: no soundcards found...
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  ArecordDevices: arecord: device_list:252: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Nov 13 17:25:10 2013
  HibernationDevice: RESUME=UUID=113e73a6-3c10-4fbc-a9a4-5160e676d325
  InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release 
i386 (20120817.3)
  IwConfig:
   lono wireless extensions.
   
   teredono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc. MM061
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-56-generic-pae 
root=UUID=0c3228e5-3952-43c1-b666-1c790f791025 ro persistent
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-56-generic-pae N/A
   linux-backports-modules-3.2.0-56-generic-pae  N/A
   linux-firmware1.79.7
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   Nov 13 13:26:27 homeserver dhclient: DHCPREQUEST of 192.168.0.15 on eth0 to 
192.168.0.254 port 67
   Nov 13 13:26:27 homeserver dhclient: DHCPACK of 192.168.0.15 from 
192.168.0.254
   Nov 13 13:26:27 homeserver dhclient: bound to 192.168.0.15 -- renewal in 
41175 seconds.
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0KD882
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1256503] Re: Please enable zcache in Trusty

[Ken Sharp]

Thanks Tim! As you can see I did ask but all I got was attitude.
Hopefully we'll see it back soon.

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

Title:
  Please enable zcache in Trusty

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  CONFIG_ZCACHE is missing from the Trusty kernels. Can this be added for 
further testing?
  https://answers.launchpad.net/ubuntu/+source/linux/+question/240079

  It would also be helpful if you could get people to answer questions
  who don't have an attitude problem.

  Thanks.

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

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

[Kernel-packages] [Bug 1256503] [NEW] Please enable zcache in Trusty

[Ken Sharp]

Public bug reported:

CONFIG_ZCACHE is missing from the Trusty kernels. Can this be added for further 
testing?
https://answers.launchpad.net/ubuntu/+source/linux/+question/240079

It would also be helpful if you could get people to answer questions who
don't have an attitude problem.

Thanks.

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


** Tags: 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/1256503

Title:
  Please enable zcache in Trusty

Status in “linux” package in Ubuntu:
  New

Bug description:
  CONFIG_ZCACHE is missing from the Trusty kernels. Can this be added for 
further testing?
  https://answers.launchpad.net/ubuntu/+source/linux/+question/240079

  It would also be helpful if you could get people to answer questions
  who don't have an attitude problem.

  Thanks.

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

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

[Kernel-packages] [Bug 1256503] Re: Please enable zcache in Trusty

[Ken Sharp]

** Tags added: bot-stop-nagging

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

Title:
  Please enable zcache in Trusty

Status in “linux” package in Ubuntu:
  New

Bug description:
  CONFIG_ZCACHE is missing from the Trusty kernels. Can this be added for 
further testing?
  https://answers.launchpad.net/ubuntu/+source/linux/+question/240079

  It would also be helpful if you could get people to answer questions
  who don't have an attitude problem.

  Thanks.

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

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

[Kernel-packages] [Bug 1256503] Re: Please enable zcache in Trusty

[Ken Sharp]

** Tags added: kernel-bot-stop-nagging

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

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

Title:
  Please enable zcache in Trusty

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  CONFIG_ZCACHE is missing from the Trusty kernels. Can this be added for 
further testing?
  https://answers.launchpad.net/ubuntu/+source/linux/+question/240079

  It would also be helpful if you could get people to answer questions
  who don't have an attitude problem.

  Thanks.

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

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

[Kernel-packages] [Bug 730212] Re: Toshiba NB100 CPU stepping (frequency scaling) does not work

[Ken Sharp]

Comment #21 already answered this.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  Toshiba NB100 CPU stepping (frequency scaling) does not work

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  I have a Toshiba NB100 netbook (Intel Atom N270 CPU) and my processor
  is always running at 0.8GHz even when it is under load. The last
  kernel version that worked appropriately on my netbook was the
  2.6.32-24 kernel in Lucid. All the newer kernel versions seem to be
  affected by this bug - I've tested newer Lucid kernels, the Maverick
  kernels, and the latest kernel in Natty Alpha 3 (2.6.38-5).

  This problem is especially annoying because Toshiba NB100 is an Ubuntu 
certified netbook: www.ubuntu.com/certification/hardware/200901-1471
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd000 irq 44'
 Mixer name : 'Realtek ALC262'
 Components : 'HDA:10ec0262,1179ff7b,00100302'
 Controls  : 17
 Simple ctrls  : 9
  DistroRelease: Ubuntu 11.04
  LiveMediaBuild: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110302)
  MachineType: TOSHIBA TOSHIBA NB100
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- console-setup/layoutcode=hu
  ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
  Regression: Yes
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-5-generic N/A
   linux-backports-modules-2.6.38-5-generic  N/A
   linux-firmware1.47
  Reproducible: Yes
  Tags:  natty running-unity kernel-uncat regression-update 
needs-upstream-testing
  Uname: Linux 2.6.38-5-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 10/23/2008
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.20:bd10/23/2008:svnTOSHIBA:pnTOSHIBANB100:pvrPLL10E-00K020HU:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnInsyde:ct10:cvrNone:
  dmi.product.name: TOSHIBA NB100
  dmi.product.version: PLL10E-00K020HU
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1074110] wakeonlan fails if pm-hibernate used

[Ken Sharp]

Forwarding as per https://bugzilla.kernel.org/show_bug.cgi?id=65361#c1

On 08/08/13 14:15, Ken Sharp wrote:
 wakeonlan fails if pm-hibernate used

 After issuing halt -p, wakeonlan works fine. after issuing pm-hibernate,
 the machine will not wake up.

 interfaces:
 auto eth0
 iface eth0 inet dhcp
 up ethtool -s eth0 wol g
 down ethtool -s eth0 wol g

 Settings for eth0:
   Supported ports: [ TP MII ]
   Supported link modes: 10baseT/Half 10baseT/Full
   100baseT/Half 100baseT/Full
   Supported pause frame use: No
   Supports auto-negotiation: Yes
   Advertised link modes: 10baseT/Half 10baseT/Full
   100baseT/Half 100baseT/Full
   Advertised pause frame use: No
   Advertised auto-negotiation: Yes
   Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
   Link partner advertised pause frame use: Symmetric
   Link partner advertised auto-negotiation: Yes
   Speed: 100Mb/s
   Duplex: Full
   Port: MII
   PHYAD: 32
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: pumbg
   Wake-on: g
   Current message level: 0x0007 (7)
drv probe link
   Link detected: yes

 01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
 RTL-8139/8139C/8139C+ (rev 10

 Reported on Launchpad
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1074110

 $ cat /proc/version
 Linux version 3.11.0-999-generic (apw@gomeisa) (gcc version 4.6.3
 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201308070514 SMP Wed Aug 7 09:24:40
 UTC 2013

 $ lsb_release -rd
 Description:Ubuntu 12.04.2 LTS
 Release:12.04

 $ ./ver_linux
 If some fields are empty or look unusual you may have an old version.
 Compare to the current minimal requirements in Documentation/Changes.

 Linux oldhomeserver 3.11.0-999-generic #201308070514 SMP Wed Aug 7
 09:24:40 UTC 2013 i686 i686 i386 GNU/Linux

 Gnu C  4.6
 Gnu make   3.81
 binutils   2.22
 util-linux 2.20.1
 mount  support
 module-init-tools  3.16
 e2fsprogs  1.42
 pcmciautils018
 Linux C Library2.15
 Dynamic linker (ldd)   2.15
 Procps 3.2.8
 Net-tools  1.60
 Kbd1.15.2
 Sh-utils   8.13
 Modules Loaded zram dm_crypt nfsd nfs_acl auth_rpcgss nfs
 fscache lockd binfmt_misc sunrpc gpio_ich lpc_ich serio_raw shpchp
 intel_rng mac_hid hwmon_vid lp parport 8139too 8139cp mii

 $ cat /proc/cpuinfo
 processor: 0
 vendor_id: GenuineIntel
 cpu family: 6
 model: 8
 model name: Pentium III (Coppermine)
 stepping: 3
 microcode: 0x10
 cpu MHz: 734.956
 cache size: 256 KB
 fdiv_bug: no
 f00f_bug: no
 coma_bug: no
 fpu: yes
 fpu_exception: yes
 cpuid level: 2
 wp: yes
 flags: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
 pse36 mmx fxsr sse
 bogomips: 1469.91
 clflush size: 32
 cache_alignment: 32
 address sizes: 36 bits physical, 32 bits virtual
 power management:

 $ cat /proc/modules
 zram 18166 1 - Live 0x (C)
 dm_crypt 22524 0 - Live 0x
 nfsd 246709 13 - Live 0x
 nfs_acl 12771 1 nfsd, Live 0x
 auth_rpcgss 49253 1 nfsd, Live 0x
 nfs 162863 0 - Live 0x
 fscache 52016 1 nfs, Live 0x
 lockd 79198 2 nfsd,nfs, Live 0x
 binfmt_misc 17268 1 - Live 0x
 sunrpc 236600 23 nfsd,nfs_acl,auth_rpcgss,nfs,lockd, Live 0x
 gpio_ich 13278 0 - Live 0x
 lpc_ich 16987 0 - Live 0x
 serio_raw 13189 0 - Live 0x
 shpchp 32265 0 - Live 0x
 intel_rng 12700 0 - Live 0x
 mac_hid 13077 0 - Live 0x
 hwmon_vid 12723 0 - Live 0x
 lp 13359 0 - Live 0x
 parport 40930 1 lp, Live 0x
 8139too 32770 0 - Live 0x
 8139cp 27168 0 - Live 0x
 mii 13693 2 8139too,8139cp, Live 0x

 $ cat /proc/ioports
 -001f : dma1
 0020-0021 : pic1
 0040-0043 : timer0
 0050-0053 : timer1
 0060-0060 : keyboard
 0064-0064 : keyboard
 0070-0071 : rtc0
 0080-008f : dma page reg
 00a0-00a1 : pic2
 00c0-00df : dma2
 00f0-00ff : fpu
 0170-0177 : :00:1f.1
0170-0177 : ata_piix
 01f0-01f7 : :00:1f.1
01f0-01f7 : ata_piix
 0376-0376 : :00:1f.1
0376-0376 : ata_piix
 03c0-03df : vga+
 03f6-03f6 : :00:1f.1
03f6-03f6 : ata_piix
 0400-0403 : ACPI PM1a_EVT_BLK
 0404-0405 : ACPI PM1a_CNT_BLK
 0408-040b : ACPI PM_TMR
 0410-0415 : ACPI CPU throttle
 0428-042b : ACPI GPE0_BLK
 042c-042f : ACPI GPE1_BLK
 0430-0433 : iTCO_wdt
 0460-047f : iTCO_wdt
 0480-04bf : gpio_ich
0480-04bf : :00:1f.0
 04c0-04cf : :00:1f.3
 0cf8-0cff : PCI conf1
 c000-cfff : PCI Bus :01
cc00-ccff : :01:03.0
  cc00-ccff : 8139too
 de00-de1f : :00:1f.2
de00-de1f : uhci_hcd
 ff00-ff0f : :00:1f.1
ff00-ff0f : ata_piix

 $ cat /proc/iomem
 

[Kernel-packages] [Bug 1074110] wakeonlan fails if pm-hibernate used

[Ken Sharp]

Forwarding as per https://bugzilla.kernel.org/show_bug.cgi?id=65361#c1

On 08/08/13 14:15, Ken Sharp wrote:
 wakeonlan fails if pm-hibernate used

 After issuing halt -p, wakeonlan works fine. after issuing pm-hibernate,
 the machine will not wake up.

 interfaces:
 auto eth0
 iface eth0 inet dhcp
 up ethtool -s eth0 wol g
 down ethtool -s eth0 wol g

 Settings for eth0:
   Supported ports: [ TP MII ]
   Supported link modes: 10baseT/Half 10baseT/Full
   100baseT/Half 100baseT/Full
   Supported pause frame use: No
   Supports auto-negotiation: Yes
   Advertised link modes: 10baseT/Half 10baseT/Full
   100baseT/Half 100baseT/Full
   Advertised pause frame use: No
   Advertised auto-negotiation: Yes
   Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
   Link partner advertised pause frame use: Symmetric
   Link partner advertised auto-negotiation: Yes
   Speed: 100Mb/s
   Duplex: Full
   Port: MII
   PHYAD: 32
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: pumbg
   Wake-on: g
   Current message level: 0x0007 (7)
drv probe link
   Link detected: yes

 01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
 RTL-8139/8139C/8139C+ (rev 10

 Reported on Launchpad
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1074110

 $ cat /proc/version
 Linux version 3.11.0-999-generic (apw@gomeisa) (gcc version 4.6.3
 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201308070514 SMP Wed Aug 7 09:24:40
 UTC 2013

 $ lsb_release -rd
 Description:Ubuntu 12.04.2 LTS
 Release:12.04

 $ ./ver_linux
 If some fields are empty or look unusual you may have an old version.
 Compare to the current minimal requirements in Documentation/Changes.

 Linux oldhomeserver 3.11.0-999-generic #201308070514 SMP Wed Aug 7
 09:24:40 UTC 2013 i686 i686 i386 GNU/Linux

 Gnu C  4.6
 Gnu make   3.81
 binutils   2.22
 util-linux 2.20.1
 mount  support
 module-init-tools  3.16
 e2fsprogs  1.42
 pcmciautils018
 Linux C Library2.15
 Dynamic linker (ldd)   2.15
 Procps 3.2.8
 Net-tools  1.60
 Kbd1.15.2
 Sh-utils   8.13
 Modules Loaded zram dm_crypt nfsd nfs_acl auth_rpcgss nfs
 fscache lockd binfmt_misc sunrpc gpio_ich lpc_ich serio_raw shpchp
 intel_rng mac_hid hwmon_vid lp parport 8139too 8139cp mii

 $ cat /proc/cpuinfo
 processor: 0
 vendor_id: GenuineIntel
 cpu family: 6
 model: 8
 model name: Pentium III (Coppermine)
 stepping: 3
 microcode: 0x10
 cpu MHz: 734.956
 cache size: 256 KB
 fdiv_bug: no
 f00f_bug: no
 coma_bug: no
 fpu: yes
 fpu_exception: yes
 cpuid level: 2
 wp: yes
 flags: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
 pse36 mmx fxsr sse
 bogomips: 1469.91
 clflush size: 32
 cache_alignment: 32
 address sizes: 36 bits physical, 32 bits virtual
 power management:

 $ cat /proc/modules
 zram 18166 1 - Live 0x (C)
 dm_crypt 22524 0 - Live 0x
 nfsd 246709 13 - Live 0x
 nfs_acl 12771 1 nfsd, Live 0x
 auth_rpcgss 49253 1 nfsd, Live 0x
 nfs 162863 0 - Live 0x
 fscache 52016 1 nfs, Live 0x
 lockd 79198 2 nfsd,nfs, Live 0x
 binfmt_misc 17268 1 - Live 0x
 sunrpc 236600 23 nfsd,nfs_acl,auth_rpcgss,nfs,lockd, Live 0x
 gpio_ich 13278 0 - Live 0x
 lpc_ich 16987 0 - Live 0x
 serio_raw 13189 0 - Live 0x
 shpchp 32265 0 - Live 0x
 intel_rng 12700 0 - Live 0x
 mac_hid 13077 0 - Live 0x
 hwmon_vid 12723 0 - Live 0x
 lp 13359 0 - Live 0x
 parport 40930 1 lp, Live 0x
 8139too 32770 0 - Live 0x
 8139cp 27168 0 - Live 0x
 mii 13693 2 8139too,8139cp, Live 0x

 $ cat /proc/ioports
 -001f : dma1
 0020-0021 : pic1
 0040-0043 : timer0
 0050-0053 : timer1
 0060-0060 : keyboard
 0064-0064 : keyboard
 0070-0071 : rtc0
 0080-008f : dma page reg
 00a0-00a1 : pic2
 00c0-00df : dma2
 00f0-00ff : fpu
 0170-0177 : :00:1f.1
0170-0177 : ata_piix
 01f0-01f7 : :00:1f.1
01f0-01f7 : ata_piix
 0376-0376 : :00:1f.1
0376-0376 : ata_piix
 03c0-03df : vga+
 03f6-03f6 : :00:1f.1
03f6-03f6 : ata_piix
 0400-0403 : ACPI PM1a_EVT_BLK
 0404-0405 : ACPI PM1a_CNT_BLK
 0408-040b : ACPI PM_TMR
 0410-0415 : ACPI CPU throttle
 0428-042b : ACPI GPE0_BLK
 042c-042f : ACPI GPE1_BLK
 0430-0433 : iTCO_wdt
 0460-047f : iTCO_wdt
 0480-04bf : gpio_ich
0480-04bf : :00:1f.0
 04c0-04cf : :00:1f.3
 0cf8-0cff : PCI conf1
 c000-cfff : PCI Bus :01
cc00-ccff : :01:03.0
  cc00-ccff : 8139too
 de00-de1f : :00:1f.2
de00-de1f : uhci_hcd
 ff00-ff0f : :00:1f.1
ff00-ff0f : ata_piix

 $ cat /proc/iomem
 

[Kernel-packages] [Bug 1074110] wakeonlan fails if pm-hibernate used

[Ken Sharp]

Forwarding as per https://bugzilla.kernel.org/show_bug.cgi?id=65361#c1

On 08/08/13 14:15, Ken Sharp wrote:
 wakeonlan fails if pm-hibernate used

 After issuing halt -p, wakeonlan works fine. after issuing pm-hibernate,
 the machine will not wake up.

 interfaces:
 auto eth0
 iface eth0 inet dhcp
 up ethtool -s eth0 wol g
 down ethtool -s eth0 wol g

 Settings for eth0:
   Supported ports: [ TP MII ]
   Supported link modes: 10baseT/Half 10baseT/Full
   100baseT/Half 100baseT/Full
   Supported pause frame use: No
   Supports auto-negotiation: Yes
   Advertised link modes: 10baseT/Half 10baseT/Full
   100baseT/Half 100baseT/Full
   Advertised pause frame use: No
   Advertised auto-negotiation: Yes
   Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
   Link partner advertised pause frame use: Symmetric
   Link partner advertised auto-negotiation: Yes
   Speed: 100Mb/s
   Duplex: Full
   Port: MII
   PHYAD: 32
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: pumbg
   Wake-on: g
   Current message level: 0x0007 (7)
drv probe link
   Link detected: yes

 01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
 RTL-8139/8139C/8139C+ (rev 10

 Reported on Launchpad
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1074110

 $ cat /proc/version
 Linux version 3.11.0-999-generic (apw@gomeisa) (gcc version 4.6.3
 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201308070514 SMP Wed Aug 7 09:24:40
 UTC 2013

 $ lsb_release -rd
 Description:Ubuntu 12.04.2 LTS
 Release:12.04

 $ ./ver_linux
 If some fields are empty or look unusual you may have an old version.
 Compare to the current minimal requirements in Documentation/Changes.

 Linux oldhomeserver 3.11.0-999-generic #201308070514 SMP Wed Aug 7
 09:24:40 UTC 2013 i686 i686 i386 GNU/Linux

 Gnu C  4.6
 Gnu make   3.81
 binutils   2.22
 util-linux 2.20.1
 mount  support
 module-init-tools  3.16
 e2fsprogs  1.42
 pcmciautils018
 Linux C Library2.15
 Dynamic linker (ldd)   2.15
 Procps 3.2.8
 Net-tools  1.60
 Kbd1.15.2
 Sh-utils   8.13
 Modules Loaded zram dm_crypt nfsd nfs_acl auth_rpcgss nfs
 fscache lockd binfmt_misc sunrpc gpio_ich lpc_ich serio_raw shpchp
 intel_rng mac_hid hwmon_vid lp parport 8139too 8139cp mii

 $ cat /proc/cpuinfo
 processor: 0
 vendor_id: GenuineIntel
 cpu family: 6
 model: 8
 model name: Pentium III (Coppermine)
 stepping: 3
 microcode: 0x10
 cpu MHz: 734.956
 cache size: 256 KB
 fdiv_bug: no
 f00f_bug: no
 coma_bug: no
 fpu: yes
 fpu_exception: yes
 cpuid level: 2
 wp: yes
 flags: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
 pse36 mmx fxsr sse
 bogomips: 1469.91
 clflush size: 32
 cache_alignment: 32
 address sizes: 36 bits physical, 32 bits virtual
 power management:

 $ cat /proc/modules
 zram 18166 1 - Live 0x (C)
 dm_crypt 22524 0 - Live 0x
 nfsd 246709 13 - Live 0x
 nfs_acl 12771 1 nfsd, Live 0x
 auth_rpcgss 49253 1 nfsd, Live 0x
 nfs 162863 0 - Live 0x
 fscache 52016 1 nfs, Live 0x
 lockd 79198 2 nfsd,nfs, Live 0x
 binfmt_misc 17268 1 - Live 0x
 sunrpc 236600 23 nfsd,nfs_acl,auth_rpcgss,nfs,lockd, Live 0x
 gpio_ich 13278 0 - Live 0x
 lpc_ich 16987 0 - Live 0x
 serio_raw 13189 0 - Live 0x
 shpchp 32265 0 - Live 0x
 intel_rng 12700 0 - Live 0x
 mac_hid 13077 0 - Live 0x
 hwmon_vid 12723 0 - Live 0x
 lp 13359 0 - Live 0x
 parport 40930 1 lp, Live 0x
 8139too 32770 0 - Live 0x
 8139cp 27168 0 - Live 0x
 mii 13693 2 8139too,8139cp, Live 0x

 $ cat /proc/ioports
 -001f : dma1
 0020-0021 : pic1
 0040-0043 : timer0
 0050-0053 : timer1
 0060-0060 : keyboard
 0064-0064 : keyboard
 0070-0071 : rtc0
 0080-008f : dma page reg
 00a0-00a1 : pic2
 00c0-00df : dma2
 00f0-00ff : fpu
 0170-0177 : :00:1f.1
0170-0177 : ata_piix
 01f0-01f7 : :00:1f.1
01f0-01f7 : ata_piix
 0376-0376 : :00:1f.1
0376-0376 : ata_piix
 03c0-03df : vga+
 03f6-03f6 : :00:1f.1
03f6-03f6 : ata_piix
 0400-0403 : ACPI PM1a_EVT_BLK
 0404-0405 : ACPI PM1a_CNT_BLK
 0408-040b : ACPI PM_TMR
 0410-0415 : ACPI CPU throttle
 0428-042b : ACPI GPE0_BLK
 042c-042f : ACPI GPE1_BLK
 0430-0433 : iTCO_wdt
 0460-047f : iTCO_wdt
 0480-04bf : gpio_ich
0480-04bf : :00:1f.0
 04c0-04cf : :00:1f.3
 0cf8-0cff : PCI conf1
 c000-cfff : PCI Bus :01
cc00-ccff : :01:03.0
  cc00-ccff : 8139too
 de00-de1f : :00:1f.2
de00-de1f : uhci_hcd
 ff00-ff0f : :00:1f.1
ff00-ff0f : ata_piix

 $ cat /proc/iomem
 

[Kernel-packages] [Bug 1074110] Re: wakeonlan fails if pm-hibernate used

[Ken Sharp]

STOP CHANGING THIS BLOODY BUG! YOU CAN CLEARLY SEE THAT IT HAS ALREADY
BEEN TESTED UPSTREAM AND IT IS LOGGED UPSTREAM.

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

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

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

Title:
  wakeonlan fails if pm-hibernate used

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

Bug description:
  After issuing halt -p, wakeonlan works fine. after issuing pm-
  hibernate, the machine will not wake up.

  interfaces:
  auto eth0
  iface eth0 inet dhcp
  up ethtool -s eth0 wol g
  down ethtool -s eth0 wol g

  Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes:  10baseT/Half 10baseT/Full 
 100baseT/Half 100baseT/Full 
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

  01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL-8139/8139C/8139C+ (rev 10)

  Not sure what else might be needed here, but apport-bug refuses to collect 
data for some reason.
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1073830

  Same is true of the latest upstream kernel:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc3-raring/
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  LiveMediaBuild: Ubuntu 7.10 Gutsy Gibbon - Release i386 (20071016)
  Package: linux 3.2.0.32.35
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.7.0-030700rc3-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups:

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

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

[Kernel-packages] [Bug 1074110] Re: wakeonlan fails if pm-hibernate used

[Ken Sharp]

Your ego is utterly irrelevant. The CORRECT PROCEDURE has been followed
according to the Wiki written by people with a lot more experience than
you, and now it is logged in the correct place, correctly.

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

** Tags removed: needs-upstream-testing
** Tags added: unwarranted-self-importance

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

Title:
  wakeonlan fails if pm-hibernate used

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

Bug description:
  After issuing halt -p, wakeonlan works fine. after issuing pm-
  hibernate, the machine will not wake up.

  interfaces:
  auto eth0
  iface eth0 inet dhcp
  up ethtool -s eth0 wol g
  down ethtool -s eth0 wol g

  Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes:  10baseT/Half 10baseT/Full 
 100baseT/Half 100baseT/Full 
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

  01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL-8139/8139C/8139C+ (rev 10)

  Not sure what else might be needed here, but apport-bug refuses to collect 
data for some reason.
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1073830

  Same is true of the latest upstream kernel:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc3-raring/
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  LiveMediaBuild: Ubuntu 7.10 Gutsy Gibbon - Release i386 (20071016)
  Package: linux 3.2.0.32.35
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.7.0-030700rc3-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups:

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

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

[Kernel-packages] [Bug 1074110] Re: wakeonlan fails if pm-hibernate used

[Ken Sharp]

** Bug watch added: Linux Kernel Bug Tracker #65361
   http://bugzilla.kernel.org/show_bug.cgi?id=65361

** Also affects: linux via
   http://bugzilla.kernel.org/show_bug.cgi?id=65361
   Importance: Unknown
   Status: Unknown

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

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

Title:
  wakeonlan fails if pm-hibernate used

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

Bug description:
  After issuing halt -p, wakeonlan works fine. after issuing pm-
  hibernate, the machine will not wake up.

  interfaces:
  auto eth0
  iface eth0 inet dhcp
  up ethtool -s eth0 wol g
  down ethtool -s eth0 wol g

  Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full 
100baseT/Half 100baseT/Full 
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes:  10baseT/Half 10baseT/Full 
 100baseT/Half 100baseT/Full 
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

  01:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL-8139/8139C/8139C+ (rev 10)

  Not sure what else might be needed here, but apport-bug refuses to collect 
data for some reason.
  https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1073830

  Same is true of the latest upstream kernel:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc3-raring/
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  LiveMediaBuild: Ubuntu 7.10 Gutsy Gibbon - Release i386 (20071016)
  Package: linux 3.2.0.32.35
  PackageArchitecture: i386
  ProcEnviron:
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Uname: Linux 3.7.0-030700rc3-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UserGroups:

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

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