[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2062667

** Tags added: iso-testing

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Kernel-packages] [Bug 2063300] Re: On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not detected

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2063300

** Tags added: iso-testing

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

Title:
  On LicheeRV Dock 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter not
  detected

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  A 0fe6:9700 ICS Advent DM9601 Fast Ethernet Adapter was only detected
  after reconnecting the USB Hub. It should have been detected while
  booting.

  $ lsusb -t
  /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
  |__ Port 001: Dev 008, If 0, Class=Hub, Driver=hub/4p, 480M
  |__ Port 002: Dev 009, If 0, Class=[unknown], Driver=dm9601, 12M
  |__ Port 004: Dev 010, If 0, Class=Human Interface Device, 
Driver=usbhid, 1.5M
  /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M
  /:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
  /:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M
  /:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=musb-hdrc/1p, 480M

  $ dmesg | grep -i usb
  [0.200341] usbcore: registered new interface driver usbfs
  [0.200487] usbcore: registered new interface driver hub
  [0.200635] usbcore: registered new device driver usb
  [   54.280232] ehci-platform 420.usb: EHCI Host Controller
  [   54.280305] ehci-platform 420.usb: new USB bus registered, assigned 
bus number 1
  [   54.280729] ehci-platform 420.usb: irq 224, io mem 0x0420
  [   54.280897] ehci-platform 4101000.usb: EHCI Host Controller
  [   54.280986] ehci-platform 4101000.usb: new USB bus registered, assigned 
bus number 2
  [   54.281606] ehci-platform 4101000.usb: irq 223, io mem 0x04101000
  [   54.300035] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00
  [   54.302412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
  [   54.302448] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   54.302466] usb usb1: Product: EHCI Host Controller
  [   54.302480] usb usb1: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
  [   54.302495] usb usb1: SerialNumber: 420.usb
  [   54.312820] hub 1-0:1.0: USB hub found
  [   54.321384] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00
  [   54.329391] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 6.08
  [   54.329426] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   54.329444] usb usb2: Product: EHCI Host Controller
  [   54.329459] usb usb2: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
  [   54.329474] usb usb2: SerialNumber: 4101000.usb
  [   54.340294] hub 2-0:1.0: USB hub found
  [   54.577549] usb 1-1: new high-speed USB device number 2 using ehci-platform
  [   54.767079] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, 
bcdDevice= 1.00
  [   54.767115] usb 1-1: New USB device strings: Mfr=0, Product=1, 
SerialNumber=0
  [   54.767133] usb 1-1: Product: USB2.0 HUB
  [   54.769892] hub 1-1:1.0: USB hub found
  [   55.201407] usb 1-1.2: new full-speed USB device number 3 using 
ehci-platform
  [   55.429317] usb 1-1.2: device descriptor read/all, error -32
  [   55.641464] usb 1-1.2: new full-speed USB device number 4 using 
ehci-platform
  [   55.709568] ohci-platform 4101400.usb: Generic Platform OHCI controller
  [   55.709638] ohci-platform 4101400.usb: new USB bus registered, assigned 
bus number 3
  [   55.709960] ohci-platform 4101400.usb: irq 225, io mem 0x04101400
  [   55.746077] ohci-platform 4200400.usb: Generic Platform OHCI controller
  [   55.746145] ohci-platform 4200400.usb: new USB bus registered, assigned 
bus number 4
  [   55.746450] ohci-platform 4200400.usb: irq 226, io mem 0x04200400
  [   55.794102] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
  [   55.794138] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   55.794158] usb usb3: Product: Generic Platform OHCI controller
  [   55.794173] usb usb3: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
  [   55.794189] usb usb3: SerialNumber: 4101400.usb
  [   55.802158] hub 3-0:1.0: USB hub found
  [   55.841520] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 6.08
  [   55.841556] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [   55.841574] usb usb4: Product: Generic Platform OHCI controller
  [   55.841590] usb usb4: Manufacturer: Linux 6.8.0-31-generic ohci_hcd
  [   55.841605] usb usb4: SerialNumber: 4200400.usb
  [   55.849788] hub 4-0:1.0: USB hub found
  [   57.570642] usb_phy_generic usb_phy_generic.1.auto: dummy supplies not 
allowed for exclusive requests
  [   57.572184] musb-hdrc 

[Kernel-packages] [Bug 2060868] Re: Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2060868

** Tags added: iso-testing

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

Title:
  Lenovo X13s fails to boot on 6.8.0-20-generic and 6.8.0-22-generic

Status in linux package in Ubuntu:
  New
Status in linux source package in Noble:
  New

Bug description:
  The last kernel that successfully boots on my Lenovo X13s system is
  6.5.0-1004-laptop.

  With 6.8.0-20-generic no output whatsoever is shown.
  --- 
  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:zfsdt  2886 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 24.04
  InstallationDate: Installed on 2023-12-12 (120 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily arm64+x13s 
(20231212)
  Lspci-vt:
   -[0002:00]---00.0-[01-ff]00.0  KIOXIA Corporation NVMe SSD Controller 
BG5 (DRAM-less)
   -[0004:00]---00.0-[01-ff]00.0  Foxconn International, Inc. T99W175 5G 
Modem [Snapdragon X55]
   -[0006:00]---00.0-[01-ff]00.0  Qualcomm Technologies, Inc QCNFA765 
Wireless Network Adapter
  MachineType: LENOVO 21BXCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 msmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-1004-laptop 
root=UUID=7695b3a4-a033-451f-ba6b-56e81a873b79 ro quiet splash 
clk_ignore_unused pd_ignore_unused vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-1004.7-laptop 6.5.3
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-1004-laptop N/A
   linux-backports-modules-6.5.0-1004-laptop  N/A
   linux-firmware 20240318.git3b128b60-0ubuntu2
  Tags: noble
  Uname: Linux 6.5.0-1004-laptop aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  dmi.bios.date: 12/05/2023
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3HET87W (1.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version:
   SDK0T76463 WIN
   ptal8
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3HET87W(1.59):bd12/05/2023:br1.59:efr1.23:svnLENOVO:pn21BXCTO1WW:pvrThinkPadX13sGen1:rvnLENOVO:rn21BXCTO1WW:rvrSDK0T76463WINptal8:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BX_BU_Think_FM_ThinkPadX13sGen1:
  dmi.product.family: ThinkPad X13s Gen 1
  dmi.product.name: 21BXCTO1WW
  dmi.product.sku: LENOVO_MT_21BX_BU_Think_FM_ThinkPad X13s Gen 1
  dmi.product.version: ThinkPad X13s Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2056491

** Tags added: iso-testing

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

Title:
  not able to install noble on PowerVM LPARs `Kernel panic - not
  syncing: VFS: Unable to mount root fs on unknown-block`

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le
  Power9 or Power10 :

  error: out of memory.

  Press any key to continue...
  OF stdout device is: /vdevice/vty@3000
  Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) 
(powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 
6.8.0-11.11-generic 6.8.0-rc4)
  Detected machine type: 0101
  command line: BOOT_IMAGE=/casper/vmlinux quiet ---
  Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
  Calling ibm,client-architecture-support... done
  memory layout at init:
memory_limit :  (16 MB aligned)
alloc_bottom : 0e67
alloc_top: 2000
alloc_top_hi : 2000
rmo_top  : 2000
ram_top  : 2000
  instantiating rtas at 0x1ec3... done
  prom_hold_cpus: skipped
  copying OF device tree...
  Building dt strings...
  Building dt structure...
  Device tree strings 0x1078 -> 0x1078179e
  Device tree struct  0x1079 -> 0x107a
  Quiescing Open Firmware ...
  Booting Linux via __start() @ 0x0a75 ...
  [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled
  [0.114052] SED: plpks not available
  [0.114507] /dev/root: Can't open blockdev
  [0.114520] List of all bdev filesystems:
  [0.114523]  ext3
  [0.114523]  ext2
  [0.114525]  ext4
  [0.114527]  squashfs
  [0.114529]  vfat
  [0.114531]  fuseblk
  [0.114532] 
  [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
  [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic 
#11-Ubuntu
  [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 
of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries
  [0.114551] Call Trace:
  [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 
(unreliable)
  [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524
  [0.114568] [c6403c10] [c301146c] 
mount_root_generic+0x208/0x448
  [0.114574] [c6403ce0] [c30118d8] 
prepare_namespace+0x98/0x430
  [0.114580] [c6403d70] [c3010820] 
kernel_init_freeable+0x32c/0x37c
  [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298
  [0.114591] [c6403e50] [c000dfbc] 
ret_from_kernel_user_thread+0x14/0x1c
  [0.114596] --- interrupt: 0 at 0x0
  [0.117006] pstore: backend (nvram) writing error (-1)
  [0.119362] Rebooting in 10 seconds..

  This is the message from a Power10(9080-HEX), but the same is
  happening on a PowrerVM-Power9 (9009-22A)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+subscriptions


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

[Kernel-packages] [Bug 2054325] Re: nouveau 0000:05:00.0: timeout on HiFive SiFive Unmatched

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2054325

** Tags added: iso-testing

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

Title:
  nouveau :05:00.0: timeout on HiFive SiFive Unmatched

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

Bug description:
  Booting the SiFive Unmatched no output on the monitor was shown.
  Zillions of messages like the following were written:

  [  +0.007867] [ cut here ]
  [  +0.13] nouveau :05:00.0: timeout
  [  +0.000374] WARNING: CPU: 2 PID: 2028 at 
drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:35 g84_bar_flush+0x11a/0x12a 
[nouveau]
  [  +0.008579] Modules linked in: tls binfmt_misc nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core 
snd_hwdep snd_pcm snd_timer snd soundc>
  [  +0.000245] CPU: 2 PID: 2028 Comm: kworker/2:3 Tainted: GW  
6.5.0-17-generic #17.1.1~22.04.1-Ubuntu
  [  +0.11] Hardware name: SiFive HiFive Unmatched A00 (DT)
  [  +0.07] Workqueue: events drm_fb_helper_damage_work [drm_kms_helper]
  [  +0.000715] epc : g84_bar_flush+0x11a/0x12a [nouveau]
  [  +0.006843]  ra : g84_bar_flush+0x11a/0x12a [nouveau]
  [  +0.006368] epc : 026becf8 ra : 026becf8 sp : 
ffc80172b6c0
  [  +0.08]  gp : 822603c8 tp : ffd89ae05100 t0 : 
820bd738
  [  +0.06]  t1 :  t2 : 2d2d2d2d2d2d2d2d s0 : 
ffc80172b720
  [  +0.05]  s1 : ffd887482000 a0 :  a1 : 

  [  +0.06]  a2 :  a3 :  a4 : 

  [  +0.06]  a5 :  a6 :  a7 : 

  [  +0.05]  s2 : 0007 s3 : ffd89d6d19b8 s4 : 
00020022
  [  +0.06]  s5 : 0046 s6 : 0046 s7 : 

  [  +0.06]  s8 : 1000 s9 : 1000 s10: 
ffc80172b9c8
  [  +0.06]  s11: ffd887144000 t3 :  t4 : 

  [  +0.06]  t5 :  t6 : ffc80172b4b8
  [  +0.04] status: 00020100 badaddr: 0058 cause: 
0003
  [  +0.10] [] g84_bar_flush+0x11a/0x12a [nouveau]
  [  +0.006810] [] nvkm_bar_flush+0x1a/0x2c [nouveau]
  [  +0.006619] [] nv50_instobj_release+0x34/0x90 [nouveau]
  [  +0.006681] [] gf100_vmm_pgt_mem+0x11a/0x1c0 [nouveau]
  [  +0.006721] [] nvkm_vmm_iter.constprop.0+0x37e/0x44e 
[nouveau]
  [  +0.006638] [] nvkm_vmm_ptes_get_map+0x36/0x98 [nouveau]
  [  +0.006891] [] nvkm_vmm_map_locked+0x190/0x2bc [nouveau]
  [  +0.006817] [] nvkm_vmm_map+0x46/0x7e [nouveau]
  [  +0.006676] [] nvkm_vram_map+0x68/0x98 [nouveau]
  [  +0.006690] [] gf100_mem_map+0x98/0x12c [nouveau]
  [  +0.006985] [] nvkm_umem_map+0x50/0xc4 [nouveau]
  [  +0.007003] [] nvkm_object_map+0x1e/0x42 [nouveau]
  [  +0.006670] [] nvkm_ioctl_map+0x76/0xf2 [nouveau]
  [  +0.007303] [] nvkm_ioctl+0xaa/0x208 [nouveau]
  [  +0.006766] [] nvkm_client_ioctl+0x18/0x26 [nouveau]
  [  +0.006833] [] nvif_object_map_handle+0x90/0xf6 [nouveau]
  [  +0.007200] [] nouveau_ttm_io_mem_reserve+0x13a/0x222 
[nouveau]
  [  +0.007131] [] ttm_bo_vmap+0x82/0x120 [ttm]
  [  +0.000263] [] drm_gem_ttm_vmap+0x18/0x22 [drm_ttm_helper]
  [  +0.24] [] drm_gem_vmap+0x1e/0x40 [drm]
  [  +0.001963] [] drm_gem_vmap_unlocked+0x30/0x50 [drm]
  [  +0.000915] [] drm_client_buffer_vmap+0x26/0x44 [drm]
  [  +0.001034] [] 
drm_fbdev_generic_helper_fb_dirty+0xa2/0x190 [drm_kms_helper]
  [  +0.000717] [] drm_fb_helper_fb_dirty+0x86/0x174 
[drm_kms_helper]
  [  +0.000286] [] drm_fb_helper_damage_work+0x1c/0x26 
[drm_kms_helper]
  [  +0.000272] [] process_one_work+0x1f6/0x390
  [  +0.24] [] worker_thread+0x8a/0x456
  [  +0.11] [] kthread+0xc4/0xe4
  [  +0.12] [] ret_from_fork+0xe/0x20
  [  +0.14] ---[ end trace  ]---
  [  +0.133717] nouveau :05:00.0: timer: stalled at 
  [  +0.007740] [ cut here ]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-17-generic 6.5.0-17.17.1.1~22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-17.17.1.1~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic riscv64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Mon Feb 19 15:47:49 2024
  SourcePackage: linux-riscv-6.5
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Kernel-packages] [Bug 2044592] Re: installed system + new install refuse to show GUI (Lubuntu, Xubuntu & Ubuntu Desktop noble)

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2044592

** Tags added: iso-testing

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

Title:
  installed system + new install refuse to show GUI (Lubuntu, Xubuntu &
  Ubuntu Desktop noble)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Please read comment #3, this issue maybe switched to INCOMPLETE

  A couple of days ago I suffered a brownout, causing my noble install to 
shutdown (uncleanly) on this box
  - hp prodesk 600 g3 sff (i5-7500, 8gb, nvidia geforce gt710 (gk208b) + intel 
graphics 630)

  On power restore, the system would not allow GUI login, I noted an
  Xorg crash in the /var/crash/ directory; but I was unable to ubuntu-
  bug file it (out of date packages; though I `apt update; apt full-
  upgrade` and nothing changed).

  I've attempted a re-install today, and after install the system boots,
  I get to see the plymouth screen (xubuntu) then blank screen and
  cursor top left.

  If I switch to text terminal; I can login and see screen for a few
  seconds; before the flashing cursor returns (ie. I'm taken away from
  ctrl+alt+f4 terminal and to lightdm trying to restart I suspect).

  This is the same behavior I had before this install; ie. I believe the
  issue is related to a recent package upgrade (this box is only
  rebooted about fornightly; so the power outage was the first reboot in
  maybe ten days).

  My original install was Lubuntu noble (actually a mantic ISO; as noble
  ISOs hadn't started then, but using an updated calamares for noble
  installed that tsimonq2 requested I test, that upgraded calamares
  caused the installed system to use noble sources & become noble not
  mantic)

  I'm convinced this is a regression due to upgrade; but it also occurs
  on recent ISOs too; I also suspect it maybe related to graphic gpus
  (intel & nvidia)

  FYI:  There is a Xorg crash file in /var/crash/ on this box too, it
  likewise won't let me `ubuntu-bug` install it, again reporting out of
  date packages (libsepol2)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guiverc1015 F wireplumber
   /dev/snd/controlC1:  guiverc1015 F wireplumber
   /dev/snd/seq:guiverc1012 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Nov 25 18:05:14 2023
  InstallationDate: Installed on 2023-11-25 (0 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231125)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0e8f:0020 GreenAsia Inc. USB to PS/2 Adapter
   Bus 001 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=1aef793d-b806-4b39-9b05-baea27c51b5e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.2
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2018
  dmi.bios.release: 2.15
  dmi.bios.vendor: HP
  dmi.bios.version: P07 Ver. 02.15
  dmi.board.name: 82B4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 06.21
  dmi.chassis.asset.tag: AUD8130DCW
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 6.33
  dmi.modalias: 
dmi:bvnHP:bvrP07Ver.02.15:bd01/30/2018:br2.15:efr6.33:svnHP:pnHPProDesk600G3SFF:pvr:rvnHP:rn82B4:rvrKBCVersion06.21:cvnHP:ct3:cvr:sku1MF39PA#ABG:
  dmi.product.family: 103C_53307F HP ProDesk
  dmi.product.name: HP ProDesk 600 G3 SFF
  dmi.product.sku: 1MF39PA#ABG
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 2038539] Re: bluetooth connections are unstable with linux-image-6.5.0-6-generic and above (MANTIC)

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038539

** Tags added: iso-testing

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

Title:
  bluetooth connections are unstable with linux-image-6.5.0-6-generic
  and above (MANTIC)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Seems some random network activity regularly breaks bluetooth connections.. 
headphones connect and reconnect or suffer breaks in sound etc. 
  Started with this kernel version linux-image-6.5.0-7 .. previous kernel 
linux-image-6.5.0-5 works perfectly 
  Booting into the older kernel restores bluetooth stability.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-7-generic 6.5.0-7.7
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  derk   1690 F wireplumber
   /dev/snd/controlC0:  derk   1690 F wireplumber
   /dev/snd/seq:derk   1687 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Oct  5 08:33:01 2023
  InstallationDate: Installed on 2023-10-04 (1 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: L9CN21WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Slim 5 16ABR8
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
  dmi.product.family: IdeaPad Slim 5 16ABR8
  dmi.product.name: 82XG
  dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
  dmi.product.version: IdeaPad Slim 5 16ABR8
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  derk   1691 F wireplumber
   /dev/snd/controlC0:  derk   1691 F wireplumber
   /dev/snd/seq:derk   1688 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-10-04 (12 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=1d40ce67-0e56-4531-a16f-817634fd450a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: L9CN21WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Slim 5 16ABR8
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 

[Kernel-packages] [Bug 2038928] Re: Unable to handle kernel paging request at virtual address ffffff8a012abe1a

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038928

** Tags added: iso-testing

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

Title:
  Unable to handle kernel paging request at virtual address
  ff8a012abe1a

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  I have been running the Mantic preinstalled image on the VisionFive 2 1.3B 
board.
  
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20231010/mantic-preinstalled-server-riscv64+visionfive2.img.xz

  Kernel Ubuntu 6.5.0-9.9.1-generic 6.5.3

  [ 4050.418337] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.426326] Oops [#1]
  [ 4050.428601] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.503975] CPU: 1 PID: 1866 Comm: check-new-relea Not tainted 
6.5.0-9-generic #9.1-Ubuntu
  [ 4050.512235] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.517804] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.521997]  ra : lookup_fast+0x36/0xfc
  [ 4050.525837] epc : 80315146 ra : 803042bc sp : 
ffc800a6bab0
  [ 4050.533056]  gp : 822602d8 tp : ffd8c56ea880 t0 : 
ffc800a6bce8
  [ 4050.540279]  t1 :  t2 : 812002e8 s0 : 
ffc800a6bae0
  [ 4050.547502]  s1 : ffc800a6bc00 a0 : ffd8c9fd8a80 a1 : 
ffc800a6bc10
  m[ 4050.554810]  a2 : ffc800a6bc44 a3 : 0001 a4 : 
00015635
  [ 4050.562033]  a5 : 00015635 a6 : 00035238 a7 : 

  [ 4050.569254]  s2 : 0002 s3 : ffd8c9fd8a80 s4 : 
002e
  [ 4050.576476]  s5 : 0020 s6 : 0070 s7 : 
fff6
  [ 4050.583697]  s8 : 0002 s9 : ffd8ca244025 s10: 
ffc800a6bc00
  [ 4050.590918]  s11: 002f t3 : ffd8c9fd8a80 t4 : 
000335238e2d
  [ 4050.598141]  t5 : ffc800a6bc44 t6 : ffd8ca244021
  [ 4050.603452] status: 00020120 badaddr: ffb4fffc cause: 
000d
  [ 4050.611367] [] __d_lookup_rcu+0x4a/0x100
  [ 4050.616858] [] walk_component+0x26/0x194
  [ 4050.622348] [] 
link_path_walk.part.0.constprop.0+0x1c2/0x2c2
  [ 4050.629575] [] path_parentat+0x48/0x96
  [ 4050.634890] [] __filename_parentat+0x9e/0x188
  [ 4050.640813] [] do_renameat2+0xc8/0x4e2
  [ 4050.646128] [] sys_renameat2+0x5a/0x76
  [ 4050.651441] [] do_trap_ecall_u+0xd6/0x154
  [ 4050.657018] [] ret_from_exception+0x0/0x64
  [ 4050.662691] Code: 4685 8e2a 8f32 7793 ffe7 e563 00e6 a885 639c c7b5 (a703) 
ffc7 
  [ 4050.670148] ---[ end trace  ]---
  [ 4050.670271] Unable to handle kernel paging request at virtual address 
005dfffc
  [ 4050.670360] Unable to handle kernel paging request at virtual address 
ffb4fffc
  [ 4050.670368] Oops [#2]
  [ 4050.670371] Modules linked in: cfg80211 binfmt_misc nls_iso8859_1 cdns3 
cdns_usb_common udc_core jh7110_tdm ofpart cdns3_starfive cmdlinepart 
snd_soc_core spi_nor snd_compress ac97_bus snd_pcm_dmaengine axp20x_pek mtd 
snd_pcm snd_timer dw_axi_dmac_platform pwm_starfive sfctemp snd soundcore 
uio_pdrv_genirq uio dm_multipath drm efi_pstore backlight ip_tables x_tables 
autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
motorcomm dwmac_starfive nvme stmmac_platform axp20x_regulator stmmac nvme_core 
dw_mmc_starfive dw_mmc_pltfm xhci_pci pcs_xpcs axp20x_i2c 
clk_starfive_jh7110_vout phylink xhci_pci_renesas axp20x dw_mmc 
pinctrl_starfive_jh7110_aon clk_starfive_jh7110_isp nvme_common 
clk_starfive_jh7110_aon jh7110_trng phy_jh7110_usb spi_cadence_quadspi
  [ 4050.670556] CPU: 3 PID: 788 Comm: rs:main Q:Reg Tainted: G  D  
  6.5.0-9-generic #9.1-Ubuntu
  [ 4050.670562] Hardware name: StarFive VisionFive 2 v1.3B (DT)
  [ 4050.670565] epc : __d_lookup_rcu+0x4a/0x100
  [ 4050.670574]  ra : lookup_fast+0x36/0xfc
  [ 

[Kernel-packages] [Bug 2038920] Re: Nezahl D1: usb 1-1: device descriptor read/64, error -71

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038920

** Tags added: iso-testing

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

Title:
  Nezahl D1: usb 1-1: device descriptor read/64, error -71

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  On the Nezha D1 board USB does not work correctly.

  I have connected a USB keyboard and get errors like:

  [ 4458.313671] usb 1-1: device descriptor read/64, error -71
  [ 4459.189686] usb 1-1: device descriptor read/64, error -71
  [ 4460.157594] usb 4-1: device descriptor read/64, error -62
  [ 4460.461621] usb 4-1: device descriptor read/64, error -62
  [ 4460.953646] usb 4-1: device descriptor read/64, error -62
  [ 4461.257626] usb 4-1: device descriptor read/64, error -62

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  ProcVersionSignature: Ubuntu 6.5.0-9.9.1-generic 6.5.3
  Uname: Linux 6.5.0-9-generic riscv64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20231010
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue Oct 10 12:20:40 2023
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
  SourcePackage: linux-riscv
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 2038893] Re: probe-bcache[132]: unhandled signal 11 code 0x1 at 0x0038004000000004

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038893

** Tags added: iso-testing

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

Title:
  probe-bcache[132]: unhandled signal 11 code 0x1 at 0x00380044

Status in linux-riscv package in Ubuntu:
  New

Bug description:
  Running http://cdimage.ubuntu.com/ubuntu-server/daily-
  preinstalled/20231010/mantic-preinstalled-server-riscv64.img.xz on
  QEMU with

  qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
  /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel
  /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
  device,netdev=eth0 -netdev user,id=eth0 -device virtio-rng-pci -drive
  file=mantic-preinstalled-server-riscv64.img,format=raw,if=virtio

  a crash was reported:

  Starting systemd-udevd version 253.5-1ubuntu6
  [3.919909] probe-bcache[132]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.920554] CPU: 3 PID: 132 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.921064] Hardware name: riscv-virtio,qemu (DT)
  [3.921382] epc : 00380044 ra : 7fffadf8ac82 sp : 
7fffce174160
  [3.921750]  gp : 5fd56800 tp : 7fffade18780 t0 : 
1000
  [3.922110]  t1 : 5fd53a3c t2 : 0034e6b4 s0 : 
7fffae006ae0
  [3.922422]  s1 : 7fffce174c78 a0 : 7fffce174178 a1 : 
7fffae006ae0
  [3.922751]  a2 : 00022560 a3 : 7fff a4 : 

  [3.923121]  a5 : 00380045 a6 : 0007d436 a7 : 
001d
  [3.923576]  s2 : 0001 s3 : 7fffae005d80 s4 : 
0003
  [3.923913]  s5 : 7d4352a0 s6 :  s7 : 
7fffce174160
  [3.924251]  s8 : 7fffce174a30 s9 : 7fffadfb86f0 s10: 
7fffce174178
  [3.924585]  s11: 7fffce174188 t3 : 7fffadf8abe8 t4 : 

  [3.924897]  t5 : 7fffadfdda40 t6 : 7fffadfde028
  [3.925090] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.933878] probe-bcache[130]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.934386] CPU: 1 PID: 130 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.934742] Hardware name: riscv-virtio,qemu (DT)
  [3.934974] epc : 00380044 ra : 7fff9b9acc82 sp : 
7fffe3a88160
  [3.935316]  gp : 91f30800 tp : 7fff9b83a780 t0 : 
1000
  [3.935869]  t1 : 91f2da3c t2 : 0034e6b4 s0 : 
7fff9ba28ae0
  [3.936224]  s1 : 7fffe3a88c78 a0 : 7fffe3a88178 a1 : 
7fff9ba28ae0
  [3.936606]  a2 : 00022560 a3 : 7fff a4 : 

  [3.937030]  a5 : 00380045 a6 : 000b3fa0 a7 : 
001d
  [3.937443]  s2 : 0001 s3 : 7fff9ba27d80 s4 : 
0003
  [3.937868]  s5 : b3f9f2a0 s6 :  s7 : 
7fffe3a88160
  [3.938261]  s8 : 7fffe3a88a30 s9 : 7fff9b9da6f0 s10: 
7fffe3a88178
  [3.938681]  s11: 7fffe3a88188 t3 : 7fff9b9acbe8 t4 : 

  [3.939113]  t5 : 7fff9b9ffa40 t6 : 7fff9ba00028
  [3.939469] status: 00024020 badaddr: 00380044 cause: 
000c
  [3.951861] probe-bcache[129]: unhandled signal 11 code 0x1 at 
0x00380044
  [3.952290] CPU: 0 PID: 129 Comm: probe-bcache Not tainted 6.5.0-9-generic 
#9.1-Ubuntu
  [3.952680] Hardware name: riscv-virtio,qemu (DT)
  [3.952887] epc : 00380044 ra : 7fff86598c82 sp : 
7fffea625160
  [3.953236]  gp : 74eb1800 tp : 7fff86426780 t0 : 
1000
  [3.953582]  t1 : 74eaea3c t2 : 0034e6b4 s0 : 
7fff86614ae0
  [3.953936]  s1 : 7fffea625c78 a0 : 7fffea625178 a1 : 
7fff86614ae0
  [3.954302]  a2 : 00022560 a3 : 7fff a4 : 

  [3.954700]  a5 : 00380045 a6 : 0009411b a7 : 
001d
  [3.955114]  s2 : 0001 s3 : 7fff86613d80 s4 : 
0003
  [3.955657]  s5 : 9411a2a0 s6 :  s7 : 
7fffea625160
  [3.956018]  s8 : 7fffea625a30 s9 : 7fff865c66f0 s10: 
7fffea625178
  [3.956368]  s11: 7fffea625188 t3 : 7fff86598be8 t4 : 

  [3.956741]  t5 : 7fff865eba40 t6 : 7fff865ec028
  [3.957026] status: 00024020 badaddr: 00380044 cause: 
000c
  Begin: Loading essential drivers ... [6.255484] raid6: int64x8  gen()   
635 MB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9.1
  

[Kernel-packages] [Bug 2038765] Re: df: /sys/firmware/efi/efivars: Invalid argument causes installation crash

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038765

** Tags added: iso-testing

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

Title:
  df: /sys/firmware/efi/efivars: Invalid argument causes installation
  crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  df: /sys/firmware/efi/efivars: Invalid argument appears on first
  display of the  live session - I note subsequently that at the end of
  the installation curtin fails due to an efivars error - looking at
  syslog I saw various efivars errors so I'm filing this with the kernel
  since this is the first instance.

  i.e. running grep efivars /var/log/*

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-7-generic 6.5.0-7.7
  ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
  Uname: Linux 6.5.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu-budgie   2077 F wireplumber
   /dev/snd/seq:ubuntu-budgie   2074 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CasperVersion: 1.486
  CurrentDesktop: Budgie:GNOME
  Date: Sun Oct  8 16:27:29 2023
  LiveMediaBuild: Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 
(20231008.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-7-generic N/A
   linux-backports-modules-6.5.0-7-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D9.B00.1802021100
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D9.B00.1802021100:bd02/02/2018:br0.1:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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


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

[Kernel-packages] [Bug 2038084] Re: There was an error playing video.

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2038084

** Tags added: iso-testing

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

Title:
  There was an error playing video.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  cheese '..' but if i try to open a bug with 'ubuntu-bug cheese' cheese
  takes control and creates a bug for linux package

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: cheese 44.1-1
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.484
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  2 12:09:01 2023
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231002)
  MachineType: ASUS System Product Name
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   cheese44.1-1
   cheese-common 44.1-1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2022
  dmi.bios.release: 14.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1402
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME H610M-E D4
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1402:bd04/01/2022:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610M-ED4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1861419] Re: kworker takes a lot of CPU

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1861419

** Tags added: iso-testing

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

Title:
  kworker takes a lot of CPU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kworker takes a lot of CPU. no other app are active.

  top - 15:52:50 up 8 min,  1 user,  load average: 1,16, 1,24, 0,77
  Tasks: 204 total,   2 running, 202 sleeping,   0 stopped,   0 zombie
  %Cpu(s):  4,9 us, 26,2 sy,  0,0 ni, 62,3 id,  0,0 wa,  0,0 hi,  6,6 si,  0,0 
st
  MiB Mem :   3867,1 total,   1737,2 free,895,9 used,   1234,0 buff/cache
  MiB Swap:   4096,0 total,   4096,0 free,  0,0 used.   2568,5 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
239 root  20   0   0  0  0 R  81,2   0,0   0:31.92 
kworker/0+
   1623 corrado   20   0  304848  53436  38048 S   6,2   1,3   0:13.02 Xorg
   1921 corrado   20   0  323484  10544   8768 S   6,2   0,3   0:00.42 
ibus-daem+
  1 root  20   0  167140  10868   7952 S   0,0   0,3   0:02.04 systemd

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-29-generic 5.3.0-29.31
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1613 F pulseaudio
   /dev/snd/controlC1:  corrado1613 F pulseaudio
  Date: Thu Jan 30 15:49:01 2020
  InstallationDate: Installed on 2019-12-28 (33 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Hewlett-Packard HP 250 G3 Notebook PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=24e2ba6f-1b75-4b3c-835e-63387635551b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.49
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV
  dmi.product.name: HP 250 G3 Notebook PC
  dmi.product.sku: J4R70EA#ABZ
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 2037000] Re: No HDMI output with 6.5.0-2-generic

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2037000

** Tags added: iso-testing

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

Title:
  No HDMI output with 6.5.0-2-generic

Status in linux-meta-riscv package in Ubuntu:
  New

Bug description:
  I am currently testing the mantic preinstalled server image for the
  LicheeRV Dock.

  After upgrading to Linux 6.5 from ppa:esmil/ppa output for HDMI is
  missing. Before we build the final images this needs to be fixed.

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


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

[Kernel-packages] [Bug 2028237] Re: radeon ring issue & box unusuable

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2028237

** Tags added: iso-testing

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

Title:
  radeon ring issue & box unusuable

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  will add details shortly

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.3.0-7-generic 6.3.0-7.7
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guiverc2457 F wireplumber
   /dev/snd/seq:guiverc2451 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Thu Jul 20 17:47:51 2023
  InstallationDate: Installed on 2023-07-20 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230719)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
   XDG_RUNTIME_DIR=
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.3.0-7-generic 
root=UUID=b395b94d-a495-4bad-9d83-25eb344c854a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.3.0-7-generic N/A
   linux-backports-modules-6.3.0-7-generic  N/A
   linux-firmware   20230629.gitee91452d-0ubuntu1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2006
  dmi.bios.release: 1.5
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.05
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7700 Small Form Factor
  dmi.product.sku: ET090AV
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 2027531] Re: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2027531

** Tags added: iso-testing

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

Title:
  ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on
  this box

Status in linux package in Ubuntu:
  New

Bug description:
  On this device, wifi is only usable occasionally on repeated boots
  when using the 6.3 kernel now included on Ubuntu mantic.

  Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not
  with 22.04.2, 20.04 or 23.04 ISOs.  I'm seeing this as a regression on
  the kernel.

  PLEASE NOTE:  This is the 5th time I've booted this thumb-drive since
  it was written yesterday and the FIRST of the 5 boots where it worked;
  thus I've used this "working" boot to file issue (hardware details)
  EVEN though its working now...

  I intend adding more, but at least can use this bug report to track
  when this issue occurs from now on (wifi is the ONLY networking on
  this box; so its a problem to report when I have the issue...

  If specific details would be helpful, please let me know.  Also note I
  have a Ubuntu mantic desktop install currently on this box; and the
  issue occurs on installed images and not just LIVE boots; ie.
  installing Ubuntu Desktop, Lubuntu usually results in a boot that
  won't have wifi on first boot (thus far I've not had wifi first boot
  when installs are with 6.3 kernel!)

  Why it works after boot an older ISO though on thumb-drive seems
  strange to me.. maybe it's just luck & I'm seeing a pattern that isn't
  actually there.  This issue I've been aware there since 6.3 kernel in
  my experience, but on this box/hardware only.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.3.0-7-generic 6.3.0-7.7
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1659 F wireplumber
   /dev/snd/controlC0:  ubuntu 1659 F wireplumber
   /dev/snd/seq:ubuntu 1656 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CasperVersion: 1.481
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 03:16:45 2023
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705)
  MachineType: Sony Corporation SVP11216CGB
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.3.0-7-generic N/A
   linux-backports-modules-6.3.0-7-generic  N/A
   linux-firmware   20230629.gitee91452d-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2013
  dmi.bios.release: 2.70
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0270V7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 2.70
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:sku54585979:
  dmi.product.family: VAIO
  dmi.product.name: SVP11216CGB
  dmi.product.sku: 54585979
  dmi.product.version: C60BZAQW
  dmi.sys.vendor: Sony Corporation

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


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

[Kernel-packages] [Bug 2015670] Re: [r8169] Kernel loop PCIe Bus Error on RTL810xE

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2015670

** Tags added: iso-testing

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

Title:
  [r8169] Kernel loop PCIe Bus Error on RTL810xE

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel loop after login
  This happens with both kernels 6.2.0-18 and 6.2.0-19 on 2 different 
partitions of same PC:
  Partition installed from beta and partition from ISO dated 04/02.
  No problem on same PC different partitions of same disk with Ubuntu Focal, 
Jammy and Kinetic
  Problem does not occur with kernel 5.19.17-051917-generic installed from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/
  Adding journalctl -b related to the problem

  note: I opened another bug for this problem blaming gnome-shell but it's wrong
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015540

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-19-generic 6.2.0-19.19
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  Uname: Linux 6.2.0-19-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1511 F wireplumber
   /dev/snd/seq:corrado1508 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  9 09:33:06 2023
  InstallationDate: Installed on 2023-04-07 (1 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230402)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3793
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic 
root=UUID=78239576-b8af-4c66-bf15-8d5ee9a63d35 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2019
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0C1PF2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:sku097A:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 2017687] Re: GTX 675MX fails with blank screen

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2017687

** Tags added: iso-testing

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

Title:
  GTX 675MX fails with blank screen

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

Bug description:
  Installing with additional drivers or adding nvidia-driver-390 renders
  the system unusable.

  On restart there are few lines of the usual kernal information then a
  brief orange flash follwed by black.  System is unusable.

  Is the GTX 675MX supported?  If not, this option should be removed
  from lunar.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nvidia-driver-390 (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 25 17:51:25 2023
  InstallationDate: Installed on 2023-04-23 (2 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/2017687/+subscriptions


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

[Kernel-packages] [Bug 2007857] Re: 5.19.0-1007-allwinner: screen buffer not completely displayed

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2007857

** Tags added: iso-testing

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

Title:
  5.19.0-1007-allwinner: screen buffer not completely displayed

Status in linux-allwinner package in Ubuntu:
  New

Bug description:
  I have installed the Kinetic preinstalled image on the Nezha board and
  upgraded it.

  With the 5.19 kernel the HDMI console output uses a larger font. Not
  all columns and not all lines of the screen buffer are visible. So
  when reaching the lower end of the HDMI output you start typing in the
  dark. At least 20 lines of output are invisible. At least 80 columns
  on the right side are not displayed.

  This renders the HDMI console unusable.

  $ cat /sys/class/drm/card0-HDMI-A-1/modes
  1024x768
  800x600
  800x600
  848x480
  640x480

  The 1920x1080 mode is not displayed.

  The screen is actually running in 1024x768 mode while the screen
  buffer assumes 1920x1080.

  With the 5.17 allwinner kernel the problem did not exist.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-1007-allwinner 5.19.0-1007.7
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-allwinner 5.19.17
  Uname: Linux 5.19.0-1007-allwinner riscv64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  Date: Mon Feb 20 14:21:12 2023
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-allwinner
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  Package: linux-allwinner 5.19.0.1007.7
  PackageArchitecture: riscv64
  ProcCpuinfoMinimal:
   processor: 0
   hart : 0
   isa  : rv64imafdc
   mmu  : sv39
   uarch: thead,c906
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.19.0-1007.7-allwinner 5.19.17
  Tags:  kinetic uec-images
  Uname: Linux 5.19.0-1007-allwinner riscv64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 2007829] Re: USB keyboard not detected

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2007829

** Tags added: iso-testing

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

Title:
  USB keyboard not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am currently testing the Nezha image according to
  
http://iso.qa.ubuntu.com/qatracker/milestones/442/builds/271832/testcases/1755/results

  When I plugin a USB keyboard after the system is up it is correctly
  discovered.

  When I power up the device with a plugged in USB keyboard it is not
  detected. See the relevant kernel messages below.

  
  [  +0.000651] usbcore: registered new interface driver usbfs
  [  +0.000162] usbcore: registered new interface driver hub
  [  +0.000128] usbcore: registered new device driver usb
  [  +0.001479] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
  [  +0.000489] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
  [  +0.000532] uhci_hcd: USB Universal Host Controller Interface driver
  [  +0.000787] usbcore: registered new interface driver uas
  [  +0.000157] usbcore: registered new interface driver usb-storage
  [  +0.000300] usbcore: registered new interface driver usbserial_generic
  [  +0.000104] usbserial: USB Serial support registered for generic
  [  +0.000118] usbcore: registered new interface driver ch341
  [  +0.94] usbserial: USB Serial support registered for ch341-uart
  [  +0.007873] ehci-platform 4101000.usb: EHCI Host Controller
  [  +0.005820] ehci-platform 4101000.usb: new USB bus registered, assigned bus 
number 1
  [  +0.008338] ehci-platform 4101000.usb: irq 107, io mem 0x04101000
  [  +0.014689] ehci-platform 4101000.usb: USB 2.0 started, EHCI 1.00
  [  +0.006889] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 5.17
  [  +0.008389] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [  +0.007304] usb usb1: Product: EHCI Host Controller
  [  +0.004955] usb usb1: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd
  [  +0.006776] usb usb1: SerialNumber: 4101000.usb
  [  +0.006016] hub 1-0:1.0: USB hub found
  [  +0.006124] ehci-platform 420.usb: EHCI Host Controller
  [  +0.005820] ehci-platform 420.usb: new USB bus registered, assigned bus 
number 2
  [  +0.008177] ehci-platform 420.usb: irq 109, io mem 0x0420
  [  +0.019500] ehci-platform 420.usb: USB 2.0 started, EHCI 1.00
  [  +0.006924] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, 
bcdDevice= 5.17
  [  +0.008406] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [  +0.007308] usb usb2: Product: EHCI Host Controller
  [  +0.004956] usb usb2: Manufacturer: Linux 5.17.0-1010-allwinner ehci_hcd
  [  +0.006773] usb usb2: SerialNumber: 420.usb
  [  +0.006015] hub 2-0:1.0: USB hub found
  [  +0.030690] ohci-platform 4101400.usb: Generic Platform OHCI controller
  [  +0.006797] ohci-platform 4101400.usb: new USB bus registered, assigned bus 
number 3
  [  +0.008115] ohci-platform 4101400.usb: irq 108, io mem 0x04101400
  [  +0.069475] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 5.17
  [  +0.008365] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [  +0.007300] usb usb3: Product: Generic Platform OHCI controller
  [  +0.006002] usb usb3: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd
  [  +0.006775] usb usb3: SerialNumber: 4101400.usb
  [  +0.005758] hub 3-0:1.0: USB hub found
  [  +0.006081] ohci-platform 4200400.usb: Generic Platform OHCI controller
  [  +0.006750] ohci-platform 4200400.usb: new USB bus registered, assigned bus 
number 4
  [  +0.008506] ohci-platform 4200400.usb: irq 110, io mem 0x04200400
  [  +0.068747] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, 
bcdDevice= 5.17
  [  +0.008395] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
  [  +0.007335] usb usb4: Product: Generic Platform OHCI controller
  [  +0.006003] usb usb4: Manufacturer: Linux 5.17.0-1010-allwinner ohci_hcd
  [  +0.006778] usb usb4: SerialNumber: 4200400.usb
  [  +0.006154] hub 4-0:1.0: USB hub found
  [  +0.016572] usb 2-1: new high-speed USB device number 2 using ehci-platform
  [  +0.613864] usb 4-1: new low-speed USB device number 2 using ohci-platform
  [  +0.207989] usb 4-1: device descriptor read/64, error -62
  [  +0.304014] usb 4-1: device descriptor read/64, error -62
  [  +0.29] usb 4-1: new low-speed USB device number 3 using ohci-platform
  [  +0.208012] usb 4-1: device descriptor read/64, error -62
  [  +0.303984] usb 4-1: device descriptor read/64, error -62
  [  +0.112175] usb usb4-port1: attempt power cycle
  [  +0.511829] usb 4-1: new low-speed USB device number 4 using ohci-platform
  [  +0.431956] usb 

[Kernel-packages] [Bug 1993645] Re: Kernel crash when inserting USB Ethernet NIC

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1993645

** Tags added: iso-testing

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

Title:
  Kernel crash when inserting USB Ethernet NIC

Status in linux-allwinner package in Ubuntu:
  New

Bug description:
  When attaching a USB Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter a crash occured.

  System: LicheeRV
  Kernel: 5.17.0-1003-allwinner #3-Ubuntu SMP Fri Jul 15 15:28:33 UTC 2022

  Oct 20 10:56:08 ubuntu kernel: [  547.169633] usb 2-1: new high-speed USB 
device number 4 using ehci-platform
  Oct 20 10:56:08 ubuntu kernel: [  547.328329] usb 2-1: New USB device found, 
idVendor=0bda, idProduct=8153, bcdDevice=30.00
  Oct 20 10:56:08 ubuntu kernel: [  547.328365] usb 2-1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Oct 20 10:56:08 ubuntu kernel: [  547.328382] usb 2-1: Product: USB 
10/100/1000 LAN
  Oct 20 10:56:08 ubuntu kernel: [  547.328396] usb 2-1: Manufacturer: Realtek
  Oct 20 10:56:08 ubuntu kernel: [  547.328411] usb 2-1: SerialNumber: 
00E04D680306
  Oct 20 10:56:08 ubuntu kernel: [  547.477744] usb 2-1: reset high-speed USB 
device number 4 using ehci-platform
  Oct 20 10:56:09 ubuntu kernel: [  547.651531] Unable to handle kernel paging 
request at virtual address 0072cde39b4a
  Oct 20 10:56:09 ubuntu kernel: [  547.659996] Oops [#1]
  Oct 20 10:56:09 ubuntu kernel: [  547.662424] Modules linked in: r8153_ecm 
cdc_ether usbnet r8152 input_leds joydev 8723ds(OE) snd_soc_hdmi_codec 
hid_generic cfg80211 dw_hdmi_i2s_audio dw_hdmi_cec usbhid pwrseq_simple 
sunxi_cir hid rc_core sun8i_drm_hdmi dw_hdmi sun8i_mixer sunxi phy_generic 
sunxi_cedrus(C) snd_soc_simple_card v4l2_mem2mem snd_soc_simple_card_utils 
sun20i_codec snd_soc_dmic videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 
videobuf2_common sun4i_drm sun4i_frontend sun4i_tcon sun8i_tcon_top 
snd_soc_core drm_cma_helper display_connector videodev snd_compress ac97_bus 
snd_pcm_dmaengine drm_kms_helper snd_pcm leds_sun50i_r329 mc 
led_class_multicolor snd_timer snd fb_sys_fops syscopyarea sysfillrect 
sysimgblt binfmt_misc soundcore leds_gpio backlight nls_iso8859_1 
uio_pdrv_genirq uio ramoops pstore_blk reed_solomon pstore_zone efi_pstore 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ip_tables x_tables autofs4 
efivarfs raid10 raid456 libcrc32c async_raid6_recov a
 sync_memcpy async_pq async_xor xor
  Oct 20 10:56:09 ubuntu kernel: [  547.662953]  async_tx raid6_pq raid1 raid0 
multipath linear
  Oct 20 10:56:09 ubuntu kernel: [  547.760181] CPU: 0 PID: 48 Comm: 
kworker/0:2 Tainted: G C OE 5.17.0-1003-allwinner #3-Ubuntu
  Oct 20 10:56:09 ubuntu kernel: [  547.770172] Hardware name: Sipeed Lichee RV 
Dock (DT)
  Oct 20 10:56:09 ubuntu kernel: [  547.775506] Workqueue: events_long 
rtl_hw_phy_work_func_t [r8152]
  Oct 20 10:56:09 ubuntu kernel: [  547.782118] epc : __kmalloc+0x9a/0x30e
  Oct 20 10:56:09 ubuntu kernel: [  547.786104]  ra : __kmalloc+0x60/0x30e
  Oct 20 10:56:09 ubuntu kernel: [  547.790079] epc : 80239bde ra : 
80239ba4 sp : ffd802c8fbf0
  Oct 20 10:56:09 ubuntu kernel: [  547.797692]  gp : 81e93b80 tp : 
ffd802b17080 t0 : ffd81ecc50e8
  Oct 20 10:56:09 ubuntu kernel: [  547.805304]  t1 : 4ed8 t2 : 
ffd804b90fc0 s0 : ffd802c8fc60
  Oct 20 10:56:09 ubuntu kernel: [  547.812916]  s1 : ffd802201200 a0 : 
ffd802201200 a1 : 81f01dd0
  Oct 20 10:56:09 ubuntu kernel: [  547.820529]  a2 : 0001 a3 : 
485a6672cde39b4a a4 : 
  Oct 20 10:56:09 ubuntu kernel: [  547.828143]  a5 : 485a6672cde39b4a a6 : 
0133 a7 : b434
  Oct 20 10:56:09 ubuntu kernel: [  547.835752]  s2 : 0004 s3 : 
ffd804495980 s4 : 0cc0
  Oct 20 10:56:09 ubuntu kernel: [  547.843363]  s5 : 0004 s6 : 
ffd802201200 s7 : 02402f2c
  Oct 20 10:56:09 ubuntu kernel: [  547.850974]  s8 : 81f01dd0 s9 : 
80e7d600 s10: 80e7d600
  Oct 20 10:56:09 ubuntu kernel: [  547.858585]  s11: ffd802c8b300 t3 : 
884ae8472f2d4987 t4 : 558b
  Oct 20 10:56:09 ubuntu kernel: [  547.866197]  t5 : ffd804b90fc0 t6 : 
0002
  Oct 20 10:56:09 ubuntu kernel: [  547.871798] status: 00020120 
badaddr: 0072cde39b4a cause: 000d
  Oct 20 10:56:09 ubuntu kernel: [  547.880144] [] 
get_registers+0x3e/0xae [r8152]
  Oct 20 10:56:09 ubuntu kernel: [  547.886657] [] 
generic_ocp_read+0x44/0x82 [r8152]
  Oct 20 10:56:09 ubuntu kernel: [  547.893441] [] 
ocp_reg_read+0x92/0xc8 [r8152]
  Oct 20 10:56:09 ubuntu kernel: [  547.899858] [] 
r8153_aldps_en+0x3e/0x108 [r8152]
  Oct 20 10:56:09 ubuntu kernel: [  

[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1991725

** Tags added: iso-testing

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

Title:
  fails to sign kernel modules

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  Expected on kinetic:  dkms will sign built modules with MOK key if
  requested.

  What happens:
  dkms outputs "Binary kmod-sign not found, modules won't be signed"

  Fix:
  update dkms to 3.0.7:  https://github.com/dell/dkms/pull/242

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


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

[Kernel-packages] [Bug 1988209] Re: application does not display anything

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1988209

** Tags added: iso-testing

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

Title:
  application does not display anything

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  I just did a fresh install of Ubuntu 20.04.5 and the when launching
  nvidia-settings the GUI does not display anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nvidia-settings 470.57.01-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 30 11:06:06 2022
  InstallationDate: Installed on 2022-08-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 
(20220829.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1988209/+subscriptions


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

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967562

** Tags added: iso-testing

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

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in grub2-unsigned package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

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


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

[Kernel-packages] [Bug 1960083] Re: dirname applet missing from initramfs

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1960083

** Tags added: iso-testing

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

Title:
  dirname applet missing from initramfs

Status in busybox package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  The initramfs is currently being built without the dirname applet.
  This is causing issues with zfs encrypted devices, as cryptsetup is
  attempting to use dirname to determine the location of the system key.
  This results in the following error:

  /init: line 971: dirname: not found

  followed by a prompt that is missing the zpool name. For example

  "Please unlock disk keystore-" rather than "Please unlock disk
  keystore-rpool".

  After entering the password, the user is dropped to an initramfs
  shell.

  It appears that this was caused by a change in cryptsetup to suddenly
  need dirname to function properly.

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


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

[Kernel-packages] [Bug 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1810416

** Tags added: iso-testing

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

Title:
  SD card error mmc0: error -110 whilst initialising SD card

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When inserting card to internal card reader:

  laurynas@laurynas-ThinkPad-T450:~$ dmesg
  [342809.333716] mmc0: error -110 whilst initialising SD card

  laurynas@laurynas-ThinkPad-T450:~$ uname -a
  Linux laurynas-ThinkPad-T450 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 
14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  
  SanDisk Extreme 64GB UHS 3. Working fine on windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  laurynas   3963 F pulseaudio
   /dev/snd/controlC0:  laurynas   3963 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  3 16:09:26 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6d87ff4e-c0ef-4f84-a96e-19a22e4acce4
  InstallationDate: Installed on 2017-02-18 (683 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20BUS3GN07
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=a0b409bc-4664-443b-b5be-7941f78d50a8 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-10-04 (90 days ago)
  dmi.bios.date: 02/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET68WW (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BUS3GN07
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET68WW(1.32):bd02/27/2018:svnLENOVO:pn20BUS3GN07:pvrThinkPadT450:rvnLENOVO:rn20BUS3GN07:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BUS3GN07
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1946828] Re: ntfsresize hang and call traces in syslog

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1946828

** Tags added: iso-testing

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

Title:
  ntfsresize hang and call traces in syslog

Status in linux package in Ubuntu:
  Confirmed
Status in ntfs-3g package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Attempting to boot the impish final iso on my kvm VM setup with a
  windows 10 install on the virtual disk.  The install process hangs at
  the "updates and other software" screen, apparently on a ntfsresize
  call.  Mind you, this is before I have chosen disks to partition - I'm
  at the step where I can choose a Normal or Minimal installation.

  While this is not a 100% reproduction rate issue, the rate seems high
  - above 50% I would guess.  If I try to quickly click thru the
  installer on boot it might be a little more likely.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-19-generic 5.13.0-19.19
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4609 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 13 02:40:56 2021
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.2
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 1943752] Re: cheese does not display image when first opened

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1943752

** Tags added: iso-testing

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

Title:
  cheese does not display image when first opened

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 21.10 from live usb on a HP 840 G3 laptop
  1.Ubuntu Impish Indri (development branch)
  2.cheese version installed: 3.38.0-4, candidate: 3.38.0-4
  version table:***3.38.0-4 500
  3.cheese should display an image from laptop camera after being opened.
  4.The error has reproduced by me on this hardware at least 4 times.
  When opening the cheese app no image is displayed until closing and reopening 
the app at least 2 to 3 times. The cheese app works as expected in both Ubuntu 
18.04 and Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-4
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 15 17:10:23 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915)
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.38.0-4
   cheese-common 3.38.0-4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: 2FZ00UP#ABA
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 002: ID 154b:0054 PNY USB 2.0 FD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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


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

[Kernel-packages] [Bug 1943662] Re: on booting 18.04.6 ISO (RC QA-test) the CD/DVD tray ejects

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1943662

** Tags added: iso-testing

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

Title:
  on booting 18.04.6 ISO (RC QA-test) the CD/DVD tray ejects

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

Bug description:
  Ubuntu 18.04.6 (desktop) RC QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  
  The media is on USB-thumb-drive so consequence in this case is only minor 
annoyance.

  But during boot; the CD/DVD tray ejects?   What if the ISO media was
  on a DVD?

  This has been noticed before; first on impish, also focal so this
  isn't new; except now on bionic.

  Related
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942299 (impish)
  - https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1943379 (focal)
  - https://bugs.launchpad.net/ubuntu/+bug/1943616 (focal)
  Likely related
  - https://bugzilla.kernel.org/show_bug.cgi?id=213795

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.4.0-84-generic 5.4.0-84.94~18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: amd64
  CasperVersion: 1.394.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 15 02:44:12 2021
  LiveMediaBuild: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210913.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1942299] Re: On booting Lubuntu impish daily - cd/dvd tray ejects

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1942299

** Tags added: iso-testing

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

Title:
  On booting Lubuntu impish daily - cd/dvd tray ejects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu impish daily boot on 
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  This daily was booted more than once, on each boot, just prior to
  plymouth screen appearing the cd/dvd tray would be ejected.

  If my installation media was on the cd/dvd - would that have crashed
  install?

  I've been noting this behavior on my primary box
  - dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)
  each day (Ubuntu impish, ubuntu, xubuntu & lubuntu desktops installed; occurs 
when Xfce or LXQt is running.. I don't think I've tried suspend with GNOME with 
5.13 kernel) when I resume it in the morning (I suspend each night), likely the 
11 days since `uptime` says  I last rebooted (I tend to reboot only about once 
per fortnight)

  ** actual results

  On booting daily; the CD/DVD tray ejects

  ** expected results

  The CD/DVD is not being used on this boot; I'd expect the tray to
  remain as it was

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-14-generic 5.13.0-14.14
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1602 F pulseaudio
   /dev/snd/controlC1:  lubuntu1602 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: LXQt
  Date: Wed Sep  1 07:03:31 2021
  IwConfig:
   lono wireless extensions.

   enp0s25   no wireless extensions.
  LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Alpha amd64 (20210831)
  MachineType: Dell Inc. OptiPlex 780
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-14-generic N/A
   linux-backports-modules-5.13.0-14-generic  N/A
   linux-firmware 1.199
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2010
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0200DY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:br3.0:svnDellInc.:pnOptiPlex780:pvr:sku:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1937897

** Tags added: iso-testing

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

Title:
  GPIO error logs in start and dmesg after update of kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]
  After upgrade kernel to 5.11.0-25, user encounters below errors
  [   5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  [Fix]
  AAEON provides a patch to check the BFPI version before loading the driver.

  [Test]
  Verified by AAEON.

  [Where problems could occur]
  It adds a check while probing the driver, should have no impact to normal 
user.

  =

  After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error
  to gpio:

     5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  On pc:

  description: Desktop Computer
  product: System Product Name (SKU)
  vendor: ASUS
  version: System Version
  serial: System Serial Number
  width: 64 bits
  capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
  configuration: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4
    *-core
     description: Motherboard
     product: TUF GAMING B550M-PLUS (WI-FI)
     vendor: ASUSTeK COMPUTER INC.
     physical id: 0
     version: Rev X.0x
     serial: 201176738701636
     slot: Default string
   *-firmware
    description: BIOS
    vendor: American Megatrends Inc.
    physical id: 0
    version: 2403
    date: 06/16/2021
    size: 64KiB
    capacity: 16MiB
    capabilities: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory

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


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

[Kernel-packages] [Bug 1933788] Re: post qa-test install, adjusting displays to match setup & display becomes blocky mess

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1933788

** Tags added: iso-testing

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

Title:
  post qa-test install, adjusting displays to match setup & display
  becomes blocky mess

Status in linux package in Ubuntu:
  New

Bug description:
  kubuntu impish install (QA) on
  -

  New impish (daily) looks good on login.  As part of testing the new
  system, I adjust displays to my configuration; which required changing
  right-display to portrait-left tilt.  On performing that function I
  get

  ** Expected results

  I expected the right-display to portrait-left tilt, and left-display
  to remain unchanged.

  ** Actual results

  Right display did portrait-left tilt & is perfectly usable (what I'm
  using now).  The left display however is now just a blocky mess that
  changes as I type, and slowly flashes (at the bottom of display).

  https://photos.app.goo.gl/BvUTkDczbqU78q8G6

  ** Package

  Package is likely wrongly marked; likely radeon related (or whatever
  graphics exists in this box)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.11.0-20-generic 5.11.0-20.21+21.10.1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guiverc 780 F pulseaudio
   /dev/snd/pcmC0D0p:   guiverc 780 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Mon Jun 28 14:47:15 2021
  InstallationDate: Installed on 2021-06-28 (0 days ago)
  InstallationMedia: Kubuntu 21.10 "Impish Indri" - Alpha amd64 (20210627)
  IwConfig:
   lono wireless extensions.

   enp0s25   no wireless extensions.
  MachineType: Dell Inc. OptiPlex 755
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-20-generic 
root=UUID=2dc50c61-35cd-4c21-a9ba-819a5aeedc7f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-20-generic N/A
   linux-backports-modules-5.11.0-20-generic  N/A
   linux-firmware 1.198
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.release: 11.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0DR845
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:br11.0:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1926062

** Tags added: iso-testing

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:744804 acl:76 sco:0 events:105989 errors:0
TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

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

[Kernel-packages] [Bug 1930447] Re: Unable to turn on bluetooth

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1930447

** Tags added: iso-testing

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

Title:
  Unable to turn on bluetooth

Status in bluez package in Ubuntu:
  New

Bug description:
  Testing Ubuntu Impish daily ISO 01-06-2021 0n QA tracking site -

  After successful install go to settings "Bluetooth" and select the on
  tab in upper right hand corner and nothing happens.

  This maybe related to bug # 1928924
  https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/1928924

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: bluez 5.58-0ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  1 16:30:07 2021
  InstallationDate: Installed on 2021-06-01 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210601)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 82C4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=efd131f1-9709-400b-9f5d-d72be1df3885 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 28:39:26:D5:7D:8E  ACL MTU: 1021:6  SCO MTU: 255:12
DOWN 
RX bytes:1682 acl:0 sco:0 events:183 errors:0
TX bytes:36490 acl:0 sco:0 commands:183 errors:0

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

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

[Kernel-packages] [Bug 1925344] Re: Session not started after reboot (black screen) - requires switching tty back and forth

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925344

** Tags added: iso-testing

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

Title:
  Session not started after reboot (black screen) - requires switching
  tty back and forth

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New
Status in nvidia-prime package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  After installation, the first boot works as expected - the system
  boots into a graphical shell login screen. However all subsequent
  reboots end up with a black screen with a blinking cursor in the top-
  left corner of the screen. To get to the login screen, one has to
  switch to a different tty (like tty2 with ctrl+alt+f2) and then to
  tty1.

  Running `prime-select query` shows `nvidia`.

  Interesting enough, when I change the nvidia-prime settings at least
  once, like to on-demand via `prime-select on-demand` - then everything
  starts working as expected. Even when I switch back to `nvidia`.

  Not sure which package I should fill this under.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xserver-xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 
UTC 2021
   GCC version:
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 21 15:20:15 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Dell UHD Graphics [1028:09e1]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1]
  InstallationDate: Installed on 2021-04-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. G3 3500
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 06ND9G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3500
  dmi.product.sku: 09E1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1925221] Re: Not possible to select language on Ubuntu Studio Live Session

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925221

** Tags added: iso-testing

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

Title:
  Not possible to select language on Ubuntu Studio Live Session

Status in Ubuntu Manual Tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I just tried running the Hirsute Final image for Ubuntu Studio in a
  Virtual Box machine and it is not possible to select a language as
  stated in the Live Session Test Case.

  Expected behaviour (as stated in the test case):
  1. Boot Screen
  2. Ubiquity - select language
  3. Click Try Ubuntu

  Actual behaviour:
  1. Grub menu - I chose Ubuntu Studio (not clear it was for the live session - 
but the other options were definitely not).
  2. Boots successfully into the Live Session, but everything is in English.

  This is probably not the best experience for a non-English speaker to
  "try Ubuntu Studio".

  Regards,

  Ross

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1925221/+subscriptions

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

[Kernel-packages] [Bug 1925075] Re: Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925075

** Tags added: iso-testing

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

Title:
  Gigabyte R120-T33 (ARM ThunderX SoC) fails to boot in ACPI mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The Gigabyte R120-T33 platform provides both device-tree and ACPI
  hardware descriptions. By default, the Linux kernel will boot in
  device-tree mode. A user can override this and choose ACPI mode by
  passing acpi=force. This system boots fine in DTB mode, but fails when
  booted in ACPI mode with acpi=force.

  [7.936228] ACPI: Power Button [PWRB]
  [7.941359] ACPI GTDT: [Firmware Bug]: failed to get the Watchdog base 
address.
  [7.948807] Unable to handle kernel read from unreadable memory at virtual 
address 0028
  [7.957843] Mem abort info:
  [7.960625]   ESR = 0x9604
  [7.963667]   EC = 0x25: DABT (current EL), IL = 32 bits
  [7.968968]   SET = 0, FnV = 0
  [7.972010]   EA = 0, S1PTW = 0
  [7.975140] Data abort info:
  [7.978008]   ISV = 0, ISS = 0x0004
  [7.981832]   CM = 0, WnR = 0
  [7.984788] [0028] user address but active_mm is swapper
  [7.991131] Internal error: Oops: 9604 [#1] SMP
  [7.996000] Modules linked in:
  [7.999047] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.11.0-16-generic 
#17-Ubuntu
  [8.006606] Hardware name: GIGABYTE R120-T33/MT30-GS1, BIOS F02 08/06/2019
  [8.013469] pstate: 40400085 (nZcv daIf +PAN -UAO -TCO BTYPE=--)
  [8.019465] pc : __ipi_send_mask+0x60/0x114
  [8.023645] lr : smp_cross_call+0x3c/0xdc
  [8.027648] sp : 8000127a3c90
  [8.030951] x29: 8000127a3c90 x28: 000a
  [8.036256] x27: 800011b60510 x26: 8000122e5108
  [8.041560] x25: 0001 x24: 
  [8.046864] x23: 8000122ee000 x22: 8000123f8448
  [8.052168] x21: 800010fd9a28 x20: 800010fd9a28
  [8.056864] Unable to handle kernel read from unreadable memory at virtual 
address 0028
  [8.057472] x19: 000100157c60 x18: 0020
  [8.067011] Mem abort info:
  [8.067013]   ESR = 0x9604
  [8.072308]
  [8.072310] x17: c2da3fd1
  [8.075089]   EC = 0x25: DABT (current EL), IL = 32 bits
  [8.078131] x16: 1b5980d2
  [8.079609]   SET = 0, FnV = 0
  [8.082998]
  [8.082999] x15: 
  [8.088295]   EA = 0, S1PTW = 0
  [8.091684] x14: 
  [8.094725] Data abort info:
  [8.096203]
  [8.096204] x13: 003d0900
  [8.099591]   ISV = 0, ISS = 0x0004
  [8.102719] x12: 3d09
  [8.106108]   CM = 0, WnR = 0
  [8.108975]
  [8.108977] x11: 
  [8.110453] [0028] user address but active_mm is swapper
  [8.113841] x10: 3d09
  [8.138598] x9 : 800010028c80 x8 : 0001
  [8.143902] x7 :  x6 : 000ff61d7318
  [8.149206] x5 : 800011620080 x4 : 800011620150
  [8.154510] x3 : 800010fd99e8 x2 : 
  [8.159815] x1 : 800010fd9a28 x0 : 
  [8.165120] Call trace:
  [8.167556]  __ipi_send_mask+0x60/0x114
  [8.171383]  smp_cross_call+0x3c/0xdc
  [8.175036]  smp_send_reschedule+0x3c/0x50
  [8.179123]  resched_curr+0x5c/0xb0
  [8.182603]  check_preempt_curr+0x58/0x90
  [8.186604]  ttwu_do_wakeup+0x2c/0x1a0
  [8.190343]  ttwu_do_activate+0x7c/0x114
  [8.194256]  try_to_wake_up+0x2cc/0x5b0
  [8.198082]  wake_up_process+0x24/0x30
  [8.201821]  swake_up_one+0x48/0x9c
  [8.205300]  rcu_gp_kthread_wake+0x68/0x8c
  [8.209388]  rcu_accelerate_cbs_unlocked+0xb4/0xf0
  [8.214168]  rcu_core+0x208/0x230
  [8.217473]  rcu_core_si+0x1c/0x30
  [8.220865]  __do_softirq+0x128/0x3a4
  [8.224517]  irq_exit+0xc4/0xec
  [8.227649]  __handle_domain_irq+0x8c/0xec
  [8.231737]  gic_handle_irq+0x84/0xfc
  [8.235389]  el1_irq+0xc0/0x180
  [8.238520]  klist_next+0xc0/0x180
  [8.241913]  bus_for_each_dev+0x68/0xe0
  [8.245740]  driver_attach+0x30/0x3c
  [8.249306]  bus_add_driver+0x154/0x250
  [8.253131]  driver_register+0x84/0x140
  [8.256958]  __platform_driver_register+0x34/0x40
  [8.261653]  of_fixed_clk_driver_init+0x28/0x34
  [8.266176]  do_one_initcall+0x50/0x290
  [8.270001]  do_initcalls+0x104/0x144
  [8.273659]  kernel_init_freeable+0x174/0x1c0
  [8.278005]  kernel_init+0x20/0x134
  [8.281486]  ret_from_fork+0x10/0x18
  [8.285056] Code: a90363f7 aa0103f5 b0010db7 f9401260 (b9402800)
  [8.291168] ---[ end trace 

[Kernel-packages] [Bug 1910817] Re: Focal update: v5.4.85 upstream stable release

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1910817

** Tags added: iso-testing

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

Title:
  Focal update: v5.4.85 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     v5.4.85 upstream stable release
     from git://git.kernel.org/

  ptrace: Prevent kernel-infoleak in ptrace_get_syscall_info()
  ipv4: fix error return code in rtm_to_fib_config()
  mac80211: mesh: fix mesh_pathtbl_init() error path
  net: bridge: vlan: fix error return code in __vlan_add()
  vrf: packets with lladdr src needs dst at input with orig_iif when needs 
strict
  net: hns3: remove a misused pragma packed
  udp: fix the proto value passed to ip_protocol_deliver_rcu for the segments
  enetc: Fix reporting of h/w packet counters
  bridge: Fix a deadlock when enabling multicast snooping
  net: stmmac: free tx skb buffer in stmmac_resume()
  tcp: select sane initial rcvq_space.space for big MSS
  tcp: fix cwnd-limited bug for TSO deferral where we send nothing
  net/mlx4_en: Avoid scheduling restart task if it is already running
  lan743x: fix for potential NULL pointer dereference with bare card
  net/mlx4_en: Handle TX error CQE
  net: ll_temac: Fix potential NULL dereference in temac_probe()
  net: stmmac: dwmac-meson8b: fix mask definition of the m250_sel mux
  net: stmmac: delete the eee_ctrl_timer after napi disabled
  ktest.pl: If size of log is too big to email, email error message
  USB: dummy-hcd: Fix uninitialized array use in init()
  USB: add RESET_RESUME quirk for Snapscan 1212
  ALSA: usb-audio: Fix potential out-of-bounds shift
  ALSA: usb-audio: Fix control 'access overflow' errors from chmap
  xhci: Give USB2 ports time to enter U3 in bus suspend
  xhci-pci: Allow host runtime PM as default for Intel Alpine Ridge LP
  USB: UAS: introduce a quirk to set no_write_same
  USB: sisusbvga: Make console support depend on BROKEN
  UBUNTU: [Config] updateconfigs for USB_SISUSBVGA_CON
  ALSA: pcm: oss: Fix potential out-of-bounds shift
  serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access
  KVM: mmu: Fix SPTE encoding of MMIO generation upper half
  membarrier: Explicitly sync remote cores when SYNC_CORE is requested
  x86/resctrl: Remove unused struct mbm_state::chunks_bw
  x86/resctrl: Fix incorrect local bandwidth when mba_sc is enabled
  Linux 5.4.85
  UBUNTU: upstream stable to v5.4.85

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

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

[Kernel-packages] [Bug 1903964] Re: The installer encountered an unrecoverable error

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1903964

** Tags added: iso-testing

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

Title:
  The installer encountered an unrecoverable error

Status in linux-meta package in Ubuntu:
  New

Bug description:
  
  Attempting to install Kubuntu Hirsute daily ISO 
http://cdimage.ubuntu.com/kubuntu/daily-live/20201112/hirsute-desktop-amd64.iso 
the installer failed with the following error message:

  The installer encountered an unrecoverable error.A desktop session
  will now be run so that you may investgate the problem or try
  installing again.

  This error occurred immediately after booting and the running of the
  file checks before entering the installer.

  The machine invlved were :

  1. Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel
  HM76 chipset 10/100 Mbps ethernet controller integrated on system
  board, WiFi 802.11 b/g/N, Bluetooth 4.0, 500 GB hd) This machine was
  in UEFI+secure boot mode.

  2. InWin BL641 i5-10400,32GB,Intel UHD Graphics 630,Ethernet,Intel
  660p 512GB M.2 NVMe hd - this install was in a VIrtualBox machine in
  BIOS mode.

  Attached is the dmesg log file from the USB media that booted the Dell
  Inspirion machine (#1 above )

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

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

[Kernel-packages] [Bug 1900865] Re: NVIDIA drivers aren't running after fresh groovy install with Secure Boot enabled

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1900865

** Tags added: iso-testing

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

Title:
  NVIDIA drivers aren't running after fresh groovy install with Secure
  Boot enabled

Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  Ran an installation enabling nvidia drivers setup, at reboot I used my
  key to sign it...

  However the module can't be loaded on reboot:

  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.969187] Lockdown: swapper/0: hibernation is restricted; see man 
kernel_lockdown.7
  [2.445463] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man 
kernel_lockdown.7
  [3.197078] Lockdown: systemd-udevd: unsigned module loading is 
restricted; see man kernel_lockdown.7
  [3.555760] Lockdown: systemd-udevd: unsigned module loading is 
restricted; see man kernel_lockdown.7
  [7.522144] Lockdown: modprobe: unsigned module loading is restricted; see 
man kernel_lockdown.7
  [   11.260801] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   22.069746] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   23.863146] Lockdown: modprobe: unsigned module loading is restricted; see 
man kernel_lockdown.7
  [   24.152678] Lockdown: modprobe: unsigned module loading is restricted; see 
man kernel_lockdown.7
  [  198.092912] Lockdown: modprobe: unsigned module loading is restricted; see 
man kernel_lockdown.7
  [ 4870.953205] Lockdown: modprobe: unsigned module loading is restricted; see 
man kernel_lockdown.7

  Module should be signed though:

  marco@marco-HP-Pavilion-Notebook-15-bc5xxx:~$ modinfo nvidia
  filename:   /lib/modules/5.8.0-25-generic/updates/dkms/nvidia.ko
  alias:  char-major-195-*
  version:455.28
  supported:  external
  license:NVIDIA
  srcversion: 9C3C7EC5A6962563520EEFD
  alias:  pci:v10DEd*sv*sd*bc03sc02i00*
  alias:  pci:v10DEd*sv*sd*bc03sc00i00*
  depends:
  retpoline:  Y
  name:   nvidia
  vermagic:   5.8.0-25-generic SMP mod_unload 
  sig_id: PKCS#7
  signer: ubuntu Secure Boot Module Signature key
  sig_key:10:CE:AB:F5:60:0E:86:AA:FB:81:9B:80:D5:9E:11:32:B3:BF:86:B1
  sig_hashalgo:   sha512
  signature:  57:C9:02:C9:D6:46:8A:F5:A5:B8:14:EF:2F:00:54:37:25:B3:24:0C:
FF:12:6A:50:FC:91:E4:5F:16:7B:5E:95:9E:E1:5E:A2:F1:FC:8A:17:
E3:36:86:00:CC:04:5A:9E:71:28:CC:A1:18:FE:27:FE:FF:9D:BE:D7:
7E:7E:0F:0D:EF:EE:BC:AE:8B:0C:77:53:50:7C:C0:70:90:D1:B9:7B:
6D:C4:FE:C0:62:88:A7:01:30:07:95:92:87:9C:E7:E5:37:74:1E:22:
EB:17:E7:35:49:26:64:E5:92:22:5F:FA:DB:84:7A:DA:1D:D2:0C:F1:
05:55:89:92:10:7F:9B:F1:A6:04:B4:CD:16:98:92:56:3A:35:3B:E9:
BB:26:03:02:F9:80:23:AA:24:2B:30:E8:BE:40:87:B9:7A:DB:BF:E2:
A2:EB:3D:EB:13:55:A3:B9:0A:18:EA:3B:67:A8:A5:85:79:01:D6:A3:
47:8F:50:C3:18:DF:BD:AF:B4:2A:04:88:AE:A5:61:7E:86:B7:E2:D9:
9B:CF:DE:BE:33:27:A3:0A:E2:A2:F0:9F:E9:16:58:04:68:82:F5:3C:
31:42:50:6F:FC:51:09:E7:BE:16:52:41:00:C8:9E:42:D0:25:F8:CD:
4E:90:89:B8:44:64:A7:8E:D6:07:C2:29:4D:F0:43:DF
  parm:   NvSwitchRegDwords:NvSwitch regkey (charp)
  parm:   NvSwitchBlacklist:NvSwitchBlacklist=uuid[,uuid...] (charp)
  parm:   nv_cap_enable_devfs:Enable (1) or disable (0) nv-caps devfs 
support. Default: 1 (int)
  parm:   NVreg_ResmanDebugLevel:int
  parm:   NVreg_RmLogonRC:int
  parm:   NVreg_ModifyDeviceFiles:int
  parm:   NVreg_DeviceFileUID:int
  parm:   NVreg_DeviceFileGID:int
  parm:   NVreg_DeviceFileMode:int
  parm:   NVreg_InitializeSystemMemoryAllocations:int
  parm:   NVreg_UsePageAttributeTable:int
  parm:   NVreg_RegisterForACPIEvents:int
  parm:   NVreg_EnablePCIeGen3:int
  parm:   NVreg_EnableMSI:int
  parm:   NVreg_TCEBypassMode:int
  parm:   NVreg_EnableStreamMemOPs:int
  parm:   NVreg_EnableBacklightHandler:int
  parm:   NVreg_RestrictProfilingToAdminUsers:int
  parm:   NVreg_PreserveVideoMemoryAllocations:int
  parm:   NVreg_DynamicPowerManagement:int
  parm:   NVreg_DynamicPowerManagementVideoMemoryThreshold:int
  parm:   NVreg_EnableUserNUMAManagement:int
  parm:   NVreg_MemoryPoolSize:int
  parm:   

[Kernel-packages] [Bug 1899719] Re: Groovy live boots have sound muted by default

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1899719

** Tags added: iso-testing

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

Title:
  Groovy live boots have sound muted by default

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Lubuntu groovy QA-test (LIVE) on
  - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)

  ** Background

  I've been noticing this for awhile (was noticed first on Xubuntu), eg.
  https://irclogs.ubuntu.com/2020/09/25/%23xubuntu-devel.html

  "xubuntu groovy daily; I've had a number (3) of boxes boot with sound
  muted; this isn't intentional is it?"

  ** What occurred this boot

  Note this is not the initial boot of this box, it was booted twice
  with same results.

  Sound is muted, I can't get sound working using the PANEL volume
  control.

  I have to start `pavucontrol-qt` using the menu, go to the OUTPUT
  DEVICES tab, and click the 'speaker' button to enable sound.

  ** What I expect to occur

  I'd expect sound to be enabled by default.

  ** Further comments

  - this is minor, once fixed it's gone, also not all users will need sound & 
can be easily fixed as outlined.  Most QA installs I don't re-use, but I do on 
occasion in support, I can't recall muted-sound reappearing (though most times 
I'd not use audio) 
  - it appears to be box specific, and occurring only on some older boxes
  - this was filed with Lubuntu, but as initially noticed on Xubuntu  (I've 
explored it before, but comments only made on IRC)
  - filed on kernel but could be pulseaudio, alsa or other?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-22-generic 5.8.0-22.23
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1754 F pulseaudio
    lubuntu1775 F pipewire-media-
   /dev/snd/pcmC0D0p:   lubuntu1754 F...m pulseaudio
   /dev/snd/seq:lubuntu1753 F pipewire
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  Date: Wed Oct 14 01:23:28 2020
  IwConfig:
   lono wireless extensions.

   enp0s25   no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013)
  MachineType: Dell Inc. OptiPlex 755
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-22-generic N/A
   linux-backports-modules-5.8.0-22-generic  N/A
   linux-firmware1.190
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.release: 0.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0DR845
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd10/02/2007:br0.0:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1899678] Re: No wifi after installation: could not insert 'wl': operation not permitted

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1899678

** Tags added: iso-testing

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

Title:
  No wifi after installation: could not insert 'wl': operation not
  permitted

Status in bcmwl package in Ubuntu:
  New

Bug description:
  After installation I noted that my broadcom wifi was not available.
  This is a regression from 20.04 where installation automatically
  installed the broadcom driver.

  So I tried to force the installation again - see trace below.

  The dialog message to enter the secure password appeared - however on
  reboot a confirmation to change the MOK state was not seen - the
  distro booted straight in.

  sudo apt install --reinstall bcmwl-kernel-source 
  [sudo] password for dad: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to 
upgrade.
  Need to get 1,546 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 
bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB]
  Fetched 1,546 kB in 0s (5,232 kB/s)   
  (Reading database ... 202371 files and directories currently installed.)
  Preparing to unpack 
.../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ...
  Removing all DKMS Modules
  Done.
  Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over 
(6.30.223.271+bdcom-0ubuntu7) ...
  Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ...
  Loading new bcmwl-6.30.223.271+bdcom DKMS files...
  Building for 5.8.0-22-generic
  Building for architecture x86_64
  Building initial module for 5.8.0-22-generic
  Done.

  wl.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/

  depmod

  DKMS: install completed.
  modprobe: ERROR: could not insert 'wl': Operation not permitted
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.137ubuntu12) ...
  update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14
  Uname: Linux 5.8.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Oct 13 18:32:47 2020
  InstallationDate: Installed on 2020-10-13 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 
(20201013)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1898041] Re: Xubuntu groovy QA-test install, strange behavior first boot

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1898041

** Tags added: iso-testing

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

Title:
  Xubuntu groovy QA-test install, strange behavior first boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu groovy QA-test install on
  sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
  (no internet connected)

  this contains two issues.

  (1) Bootloader error post-install

  "System Bootloader not found. Initializing defaults"
  "Creating Boot Entry BOOT..."

  (2) Strange behavior with Xubuntu's greeter/DM login


  ** edited ISO.qa.ubuntu report

  On first reboot, bootup is not as expected.
  First message is at least two lines, first being

  "System Bootloader not found. Initializing defaults"
  "Creating Boot Entry BOOT..."

  Second line relates to the reconstruction of bootloader but it's too
  quick for me to recall/type..

  This is followed by of flashing between FSCK like screen & VAIO logo,
  many times and looks like it's having issues, or a 'fight'?

  once DM/greeter appears, the session is as expected. ctrl+alt+T and
  terminal & all disk space utilized and system looks as expected,
  install appears good now.

  On second boot, the "System Bootloader not found... (error continues
  again I'm not quick enough)" but it's NOT followed by he flashing
  FSCK/VAIO screen this time..

  DM/greeter has appeared, HOWEVER no background logo, characters at top
  are just BOXES. Once I'm logged in all looks good though again??!!

  Third boot and different behavior again, more normal than 2nd time...
  but 3 boots have resulted in 3 different behaviors at the greeter/DM &
  not what I except from a Xubuntu install.

  Fourth boot, and back to black screen at greeter/DM, BOXES instead of
  charaters again in the top panel... This issue has to be related to
  Xubuntu software and not installer is my feeling

  ** Expected Results

  (1) No boot loader error messages are expected

  (2) Consistent greeter, with background, and letters in the top panel
  (not boxes). Once logged in session is good, this is a Xubuntu issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-20-generic 5.8.0-20.21
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guiverc 834 F pulseaudio
   /dev/snd/controlC1:  guiverc 834 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Oct  1 22:37:33 2020
  InstallationDate: Installed on 2020-10-01 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
  MachineType: Sony Corporation SVP11216CGB
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic 
root=UUID=c10da064-d98b-4678-94af-c267fe1c3b8c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-20-generic N/A
   linux-backports-modules-5.8.0-20-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2013
  dmi.bios.release: 2.70
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0270V7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 2.70
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVP11216CGB
  dmi.product.sku: 54585979
  dmi.product.version: C60BZAQW
  dmi.sys.vendor: Sony Corporation

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

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

[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1878045

** Tags added: iso-testing

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

Title:
  doing dist-upgrade got error related do Broadcom

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  I had a working 20.04 installation running, including the Broadcom Wifi. 
After upgrade to 20.10 the Broadcom Wifi is not working. I tried several 
suggestions and always end to an error similiar to this one: 
  ...
  Building initial module for 5.4.0-30-generic
  ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not 
supported
  Error! Application of patch 0028-add-support-for-linux-5.6.patch failed.
  Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information.
  dpkg: error processing package bcmwl-kernel-source (--configure):
   installed bcmwl-kernel-source package post-installation script subprocess 
returned error exit status 6
  Errors were encountered while processing:
   bcmwl-kernel-source
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.1
  ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34
  Uname: Linux 5.4.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu33
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  Date: Mon May 11 17:16:43 2020
  InstallationDate: Installed on 2020-02-22 (78 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  mtime.conffile..etc.update-manager.release-upgrades: 
2020-05-07T09:26:37.178586

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

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

[Kernel-packages] [Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1895905

** Tags added: iso-testing

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

Title:
  lubuntu groovy; flashing of sddm greeter

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu groovy QA-test install.

  On reboot, the login greeter (sddm) screen isn't nice, with areas of
  the screen flashing white/black/white/black (maybe white & black each
  second like a ":" might flash on the clock, only the ":" on the clock
  is static)

  likely package at fault should be xserver-xorg-video-nouveau

  Photo can be seen at

  https://photos.app.goo.gl/SYPytVxtkKBEj9NY8

  The
  - drop down for session (not selected Lubuntu)
  - language drop down (not US flag)
  - white/black on login picture (not grey name)

  flashes black & white on a cycle...

  The top panel items will eventually stop flashing (ie. session &
  layout) but time or certain actions cause the flashing white then
  black in cycle to occur again.

  ** Expected Result

  No flashing, its irritating & potentially a problem for some with
  certain health conditions.

  
  ** Not new issue, it's occurred in the past

  hp dx6120mt (pentium 4, 3gb, winfast clone of nvidia 7600gt)

  I've had this issue before on eoan on hp dx6120 i believe but cannot
  find bug report. The bug was likely not filed as that box was i386 &
  support was being dropped when I noticed it so I didn't see any point.

  It's not new, and no doubt relates to Nvidia cards, and I'm convinced
  I've filed this before on dx6120 so if not eoan, disco, but I've not
  yet found it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  guiverc1095 F pulseaudio
   /dev/snd/controlC0:  guiverc1095 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep 17 11:13:50 2020
  InstallationDate: Installed on 2021-09-17 (-365 days ago)
  InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200916)
  IwConfig:
   lono wireless extensions.

   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 990
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=c29a66dc-4cfc-4dc1-9fe7-3c9d8a8ab4a1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A20
  dmi.board.name: 06D7TR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA20:bd05/05/2017:br4.6:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn06D7TR:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1894064] Re: lubuntu groovy QA-test live session locked up

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1894064

** Tags added: iso-testing

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

Title:
  lubuntu groovy QA-test live session locked up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu groovy 'live' QA-test on 
  hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

  Test went for some time, then on waking xscreensaver (testing for a
  bug), the session froze (news being streamed was still audible)

  I attempted to fix (see below), but was unable. On switching to text
  term (ctrl+alt+F4) audio ended (I was streaming news in firefox) &
  nothing responded (numlock & capslock had already stopped responding
  on GUI lock up).

  This report will be of little value I suspect, as the logs are of a
  new session given I was unable to recover the first session (which had
  the useful logs).

  Refer to iso.qa.ubuntu.com for test details.. 
  Key paste from the link will be as follows

  ---
  ...
  this session went for some time, I had screensaver kick in, plus stated it 
looking for http://launchpad.net/bugs/1855220 (choppy issues) and didn't notice 
anything choppy (maybe these screens but a different box)... However after 
waking screensaver for a "preview" the session was not recoverable... news kept 
streaming so session was running.. but session appeared unrecoverable..

  using ctrl+alt+F4 shut news up.. but screen did not change. black
  upper display still (it went black when I stopped xscreensaver
  preview, pointer visible on top display but won't move.. and bottom
  display shows a stuck flurry screen still).

  I was unable to recover session, could not use a text terminal either
  and strangely he numlock/capslock keys weren't even changing the LEDs
  on the keyboard..

  No mouse movement after I tried to end xscreensaver preview.
  - the upper display had returned to black (flurry xscreensaver image gone 
where I was expecting the streaming firefox/news to return but no
  - mouse pointer was drawn on upper display
  - lower display stayed locked on a frozen flurry (xscreensaver) screen

  I've machine (with SysRq REISUB) and will file bug from there, alas as
  session is lost the bug report will be near meaningless, but filed for
  this QA anyway.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-16-generic 5.8.0-16.17
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1552 F pulseaudio
   /dev/snd/controlC1:  lubuntu1552 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: LXQt
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Thu Sep  3 08:32:43 2020
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200902)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-16-generic N/A
   linux-backports-modules-5.8.0-16-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2011
  dmi.bios.release: 2.6
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.06
  dmi.board.asset.tag: AUD14001GG
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: AUD14001GG
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.06:bd06/09/2011:br2.6:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.product.sku: XL510AV
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1893493] Re: ubuntu groovy desktop, change screen position and lost background, then background went low-signal blotchy tv like

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1893493

** Tags added: iso-testing

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

Title:
  ubuntu groovy desktop, change screen position and lost background,
  then background went low-signal blotchy tv like

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu groovy QA-test (live)

  I changed screen setup to match my setup (2x 1920x1080 displays one
  above the other, the default-right got moved to above my other
  monitor).  On doing this screen background disappeared and became
  black.

  On using system, background changes from all BLACK to blocky-low-
  signal digital-tv like blocks that is unusable for reading detail on
  screen, but it seems to return to all black in time (or with use)

  I can change wallpapers and that appears to work correctly at least
  for a time, the new wallpaper will disappear (again with time or use)
  and wallpaper goes dead-black again (though primary screen may also
  have mimimized windows appearing in blocky-low-signal-tv like; not
  neat and readable but messy & changing..  nice easy black on second
  monitor)

  I've been unable to take screen dumps, not sure why.

  /var/crash/ is empty

  Minimized windows do not disappear from screen, hitting minimize on a
  window does nothing (visually). It's these images that appear to
  become the blocky-blotchety-low-signal background that eventually
  becomes all black. Once a window was made to minimize, even though
  image is fully on screen, clicking mouse on visible-window works now
  like you're clicking background (though minimized window is
  displayed). If i could get screendumps this effect could be lost.

  Currently this report is low quality (can't get screencaptures, no
  photo), but the behavior differs between my screens. My upper screen
  is a lot less problematic than my-lower (primary) display.

  Opening the menu blackens (completely) the background on lower display
  (yeah, the older windows that were minimized can be distracting..) and
  improves usability.

  /var/crash now has contents

  ubuntu@ubuntu:~$ ls -la /var/crash
  total 168
  drwxrwsrwt 1 root whoopsie100 Aug 29 01:18 .
  drwxr-xr-x 1 root root160 Aug 28 08:15 ..
  -rw-r- 1 ubuntu   whoopsie 164662 Aug 29 01:18 
_usr_share_apport_dump_acpi_tables.py.999.crash
  -rw-rw-r-- 1 ubuntu   whoopsie  0 Aug 29 01:18 
_usr_share_apport_dump_acpi_tables.py.999.upload
  -rw--- 1 whoopsie whoopsie 37 Aug 29 01:18 
_usr_share_apport_dump_acpi_tables.py.999.uploaded

  I haven't worked out a pattern on what causes the strange behavior,
  it's not all the time  -- however I can create the worst of it by just
  changing the screen orientation (even just a little).  Do that and any
  chosen wallpaper is gone, and my background appears to be filled with
  detail from possibly prior? pages!??  eg. rather than my two screens
  directly one above the other, I move to top to be slight left/right a
  little..

  As I type this into firefox window (on lp), I'm getting glitches on
  the background that is somewhat distracting/annoying. I wouldn't use
  this system as it is.

  The issue is likely graphics driver related.. though I've tagged
  kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4611 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 29 01:17:01 2020
  IwConfig:
   lono wireless extensions.

   enp0s25   no wireless extensions.
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200828)
  MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-42-generic N/A
   linux-backports-modules-5.4.0-42-generic  N/A
   linux-firmware1.190
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.05
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  

[Kernel-packages] [Bug 1890487] Re: rpi3b+ wifi doesn't get used if ethernet disconnected

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1890487

** Tags added: iso-testing

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

Title:
  rpi3b+ wifi doesn't get used if ethernet disconnected

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  When testing 20.04.1, I noticed some different behavior on rpi3b+ that
  I didn't see on rpi3b or rpi4.  I have configured the device with
  ethernet, added netplan yaml for my wifi network, and rebooted. So
  both eth0 and wlan0 have an ip address.

  On all other devices (rpi3b, rpi4, etc), if I unplug eth0 wile pinging
  something, I'll miss maybe 1 ping and then it will continue to work
  and just switch over to wlan0.  However, on rpi3b+ it just stops being
  able to access the network completely.  If I re-run netplan apply, it
  will start using wifi again, but if I plug eth0 back in, then unplug
  it, it stops just like before.

  I am seeing this with the current 20.04.1 release:
  Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

  I also went back and tested the original 20.04 release and it happens there 
too, so this is not a regression:
  Linux ubuntu 5.4.0-1008-raspi #8-Ubuntu SMP Wed Apr 8 11:13:06 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

  I see this happen on both armhf and arm64. One difference I did note, is that 
I get a link down message in dmesg on rpi3b, but not rpi3b+.  When I disconnect 
eth0 on rpi3b I see this:
  [   82.203702] smsc95xx 1-1.1:1.0 eth0: link down

  ...but nothing on the 3b+.

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

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

[Kernel-packages] [Bug 1889468] Re: 20.04.1 selecting audio output device does not work on rpi

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1889468

** Tags added: iso-testing

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

Title:
  20.04.1 selecting audio output device does not work on rpi

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  Testing the 20.04.1 candidate images on rpi (currently rpi4-2GB) I'm noticing 
that I can no longer select the audio output device with amixer. This used to 
be possible by using:
  amixer cset numid=3 2 for HDMI0
  amixer cset numid=3 3 for HDMI1
  amixer cset numid=3 1 for 3.5mm headphone jack

  However, now trying to set this gets the following error:
  amixer: Cannot find the given element from control default

  It seems that by default, it will now use the hdmi output for
  whichever one is connected, and will only output through the
  headphones if no hdmi device is connected.

  Kernel is:
  Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 
aarch64 aarch64 aarch64 GNU/Linux

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

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

[Kernel-packages] [Bug 1054458] Re: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304'

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1054458

** Tags added: iso-testing

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

Title:
  nvidia-detector crashed with ValueError in __get_value_from_name():
  invalid literal for int() with base 10: 'experimental-304'

Status in nvidia-common package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in nvidia-common source package in Precise:
  Fix Released
Status in ubuntu-drivers-common source package in Precise:
  Invalid
Status in nvidia-common source package in Quantal:
  Invalid
Status in ubuntu-drivers-common source package in Quantal:
  Fix Released
Status in nvidia-common source package in Bionic:
  Invalid
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  If other people report this at the current level with xorg/nvidia it
  might be a bug. It is also possible the error stems from a bad
  combination of free and proprietary material. Further details will be
  provided as necessary/available.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: ubuntu-drivers-common 1:0.2.69
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic i686
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: i386
  Date: Fri Sep 21 22:48:18 2012
  ExecutablePath: /usr/bin/nvidia-detector
  InterpreterPath: /usr/bin/python3.2mu
  ProcCmdline: /usr/bin/python3.2 /usr/bin/nvidia-detector
  ProcEnviron:
   SHELL=/bin/bash
   TERM=linux
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   LANGUAGE=de_CH:de
  PythonArgs: ['/usr/bin/nvidia-detector']
  SourcePackage: ubuntu-drivers-common
  Title: nvidia-detector crashed with ValueError in __get_value_from_name(): 
invalid literal for int() with base 10: 'experimental-304'
  UpgradeStatus: Upgraded to quantal on 2012-07-31 (52 days ago)
  UserGroups: audio pulse pulse-access video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/1054458/+subscriptions

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

[Kernel-packages] [Bug 1862831] Re: hciattach on rpi4 times out on first attempt

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1862831

** Tags added: iso-testing

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

Title:
  hciattach on rpi4 times out on first attempt

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Eoan:
  New

Bug description:
  I've observed this in both armhf and arm64 on:
  19.10.1-server
  18.04.4-server
  core18

  It does not seem to happen on rpi3, only on rpi4.
  If you want to use Bluetooth on rpi, one must first run:
  $ sudo hciattach /dev/ttyAMA0 bcm43xx 921600 noflow

  On RPI4, this results in a timeout on the first attempt. Reattempting
  it right after will work though, 100% of the times I've tried it.

  In the failed attempt, the output is:
bcm43xx_init
Initialization timed out.

  And the following is the only new message to show up in dmesg when this fails:
[  270.303691] uart-pl011 fe201000.serial: no DMA platform data

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

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

[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1871182

** Tags added: iso-testing

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

Title:
  [RTL810xE] No ethernet connection

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu doesn't show cable plugged-in. Wifi is also intermittent.
  Errors in log with realtek. long boot up. No problems with live-USB or
  fresh install, only after update.

  sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.4.0-22-generic 5.4.0-22.26
  ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
  Uname: Linux 5.4.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  finisdiem   1332 F pulseaudio
   /dev/snd/controlC0:  finisdiem   1332 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 10:49:03 2020
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic 
root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-22-generic N/A
   linux-backports-modules-5.4.0-22-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1849
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.2F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: C2N51UA#ABA
  dmi.product.version: 088B1130591620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1873360] Re: Ethernet driver not loaded at boot

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1873360

** Tags added: iso-testing

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

Title:
  Ethernet driver not loaded at boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running a test on Focal Daily build 16.04.2020

  the ethernet driver was not loaded at boot - attached is the dmesg.log

  - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD
  Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller
  integrated on system board, WiFi 802.11 b/g/N,

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

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

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

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845801

** Tags added: iso-testing

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1835660

** Tags added: iso-testing

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

Title:
  initramfs unpacking failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

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

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

[Kernel-packages] [Bug 1867534] Re: Wifi requires interruption before timing out (and immediate reconnect attempt succeeds)

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1867534

** Tags added: iso-testing

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

Title:
  Wifi requires interruption before timing out (and immediate reconnect
  attempt succeeds)

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  ISO testing 20.04 Lubuntu daily (20200315). From the Live desktop, I
  click my nm-tray access point, supply the password. nm-tray will
  timeout. Trying again will timeout. What works is clicking the same
  access point a couple times before it times out. This causes an
  immediate failure and successful connection (two balloon msgs).

  This problem is not specific to Lubuntu. It happens with Kubuntu,
  Budgie, Mate, Xubuntu. The common theme is: it appears to be out of
  sync in some manner. The wifi connection needs to be interrupted
  before timing out. Then an immediate attempt (within 2-3 seconds? I
  haven't tested how long it can wait) succeeds.

  This problem also happens after install and reboot. For example, with
  yesterday's daily image (20200314), I had to reboot Lubuntu twice
  after install before the wifi worked. (I haven't reached that point
  yet today. I'm creating this bug report from the Live desktop. I will
  update with more info about post-install.).

  Note: I don't know if this is acceptable wifi behavior. Good enough? I
  figured I should report it and let someone decide. It seems to be
  specific to this laptop (Lenovo Thinkpad E440 20C5) or it's Intel 7260
  wifi card.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lubuntu1857 F pulseaudio
   /dev/snd/controlC0:  lubuntu1857 F pulseaudio
  CasperVersion: 1.441
  Date: Sun Mar 15 17:17:43 2020
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  MachineType: LENOVO 20C5004YUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  SourcePackage: linux-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ETA2WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C5004YUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C5004YUS:pvrThinkPadEdgeE440:rvnLENOVO:rn20C5004YUS:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E440
  dmi.product.name: 20C5004YUS
  dmi.product.sku: LENOVO_MT_20C5_BU_Think_FM_ThinkPad Edge E440
  dmi.product.version: ThinkPad Edge E440
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1866172] Re: xubuntu 20.04 'live' qa-test; suspend, resume but system froze on waking

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1866172

** Tags added: iso-testing

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

Title:
  xubuntu 20.04 'live' qa-test; suspend, resume but system froze on
  waking

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  Xubuntu daily test (20.04) on
  dell vostro 430 (i7-870, 8gb, nvidia geforce gt 6600 gt)
  test went well, then I suspended system, waited, on resume (keystroke) system 
appeared to stop with mucked-up but mostly-recognizable display 
(https://photos.app.goo.gl/2kSU5SubdbkdpFUcA)

  I was unable to use any keyboard input to switch to terminal, or gain
  any clues (sorry keyboard didn't have sysrq key to see if kernel was
  up).

  I rebooted the system which is when `ubuntu-bug linux` was ran. After
  this bug was submitted I suspended system, waited & it resumed
  correctly.  I suspended it again, waited & it resumed normally; so the
  issue doesn't occur all the time.

  Because CTRL+ALT+T wasn't working (different issue;
  https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1827459),
  nor menu items having icons etc, I `xfsettingsd --replace` to fix that
  issue & suspended again.. This time the system didn't resume reliably.
  This time however it was not as I'm describing above, as the screen
  was correctly drawn.  The mouse-pointer was visible but static, then
  appeared to move (following my movements) before disappearing, redrawn
  but static again .. IF the system was 'up', it'd become super slow;
  and I eventually turned box off.  I'll retest on requests (too tried
  now)

  photo of screen on resume :
  https://photos.app.goo.gl/2kSU5SubdbkdpFUcA

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu4057 F pulseaudio
  CasperVersion: 1.441
  CurrentDesktop: XFCE
  Date: Thu Mar  5 10:35:57 2020
  IwConfig:
   enp2s0no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200305)
  MachineType: Dell Inc. Vostro 430
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill:

  SourcePackage: linux-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 054KM3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/13/2011:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: 0
  dmi.product.name: Vostro 430
  dmi.product.sku: 0
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1861470] Re: BIOS logo reappears mid-boot after the purple screen

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1861470

** Tags added: iso-testing

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

Title:
  BIOS logo reappears mid-boot after the purple screen

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-5.4 package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  New

Bug description:
  BIOS logo (the ACPI BGRT graphic) reappears mid-boot after the purple
  screen.

  This seems to be happening reliably on multiple focal machines:

  0. Turn on or reboot the machine.
  1. See the BIOS logo.
  2. See a blank purple screen (grub)
  3. See the BIOS logo again (this bug)
  4. See the purple screen with Ubuntu logo (plymouth)
  5. See the login screen

  I believe this is related to ACPI BGRT changes in the kernel. And I
  guess it wouldn't even need fixing if we just eliminated the blank
  purple grub screen (step 2)...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Fri Jan 31 11:31:44 2020
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1316 F pulseaudio
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-01-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  MachineType: LENOVO 20KFCTO1WW
  Package: linux-signed-5.4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=50f3b272-d351-4a2a-9661-d39e9fcf2195 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.185
  Tags:  focal
  Uname: Linux 5.4.0-12-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: 01/10/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N20ET51W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN20ET51W(1.36):bd01/10/2020:svnLENOVO:pn20KFCTO1WW:pvrThinkPadX280:rvnLENOVO:rn20KFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X280
  dmi.product.name: 20KFCTO1WW
  dmi.product.sku: LENOVO_MT_20KF_BU_Think_FM_ThinkPad X280
  dmi.product.version: ThinkPad X280
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1848333] Re: wifi problem delays boot in live mode

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1848333

** Tags added: iso-testing

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

Title:
  wifi problem delays boot in live mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
  days ago (Oct 6).

  Now there is a delay of 1 min 30 sec during booting, and I think there
  is something wrong with the recognition of the wifi hardware or maybe
  matching of driver and hardware. It happens in 'this' computer, a
  middle-aged Toshiba laptop with a generation 3 Intel i5 cpu and also
  in a Dell Latitude E7240 with a generation 4 Intel i5 cpu and I guess
  another wifi chip.

  In both cases both ethernet and wifi works. I see available wifi
  routers and can connect (when I have the password).

  I tested also with the Xubuntu eoan iso file, and the same delay
  happened there.

  I think the drivers are OK, but something in the logic for recognition
  of them might be bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu2316 F pulseaudio
  CasperVersion: 1.426
  CurrentDesktop: LXQt
  Date: Wed Oct 16 11:36:22 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
  MachineType: TOSHIBA SATELLITE PRO C850-19W
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed persistent ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-19W
  dmi.product.sku: PSCBXE
  dmi.product.version: PSCBXE-00C00VN5
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1848075] Re: eoan server image does not boot on RPI3-A+

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1848075

** Tags added: iso-testing

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

Title:
  eoan server image does not boot on RPI3-A+

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  I've tried with both the  20191010.1 and  20191012 image, and it boots
  on all other pi devices I have, but not on the rpi3-a+.  On the serial
  console, it only gets as far as "Starting kernel..." but over hdmi,
  there are some more details reported. I'll try to attach a screenshot
  in a moment.

  After talking to Dave Jones about this, it sounds like some dtb files
  are missing to make this work on a+

  From the 20191012 image:
  ii  linux-raspi25.3.0.1007.3arm64
Complete Linux kernel for the BCM2709 architecture.
  ii  linux-firmware-raspi2   1.20190819-0ubuntu2 arm64
Raspberry Pi 2/3/4 GPU firmware and bootloaders

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

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

[Kernel-packages] [Bug 1847927] Re: Upgrading of 20191010 installed on ZFS will lead to "device-mapper: reload ioctl on osprober-linux-sda6 failed: Device or resource busy" and then to auto-removal of

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1847927

** Tags added: iso-testing

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

Title:
  Upgrading of 20191010 installed on ZFS will lead to "device-mapper:
  reload ioctl on osprober-linux-sda6  failed: Device or resource busy"
  and then to auto-removal of all zfs packages

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 19.10 from 20191010 ISO
  2. Run `sudo apt-get update` and `sudo apt-get upgrade`
  3. Note the following lines in the APT output:

  ...
  Warning: Couldn't find any valid initrd for dataset rpool/ROOT/ubuntu_69xc2t.
  Found memtest86+ image: /BOOT/ubuntu_69xc2t@/memtest86+.elf
  Found memtest86+ image: /BOOT/ubuntu_69xc2t@/memtest86+.bin
  device-mapper: reload ioctl on osprober-linux-sda6  failed: Device or 
resource busy
  Command failed.
  done
  ...
  device-mapper: reload ioctl on osprober-linux-sda6  failed: Device or 
resource busy
  Command failed.
  done

  4. Run `sudo apt-get autoremove --purge`

  $ sudo apt-get autoremove --purge
  [sudo] password for zfs: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
libnvpair1linux* libuutil1linux* libzfs2linux* libzpool2linux* 
zfs-initramfs* zfs-zed* zfsutils-linux*
  0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded.
  After this operation, 5 243 kB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  
  Expected results:
  * upgrading of packages run without errors

  Actual results:
  * system will not boot if user will proceed with package autoremoval

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libzfs2linux 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 13 22:51:39 2019
  InstallationDate: Installed on 2019-10-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1847596] Re: rpi3b+: corrupted screen on hdmi

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1847596

** Tags added: iso-testing

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

Title:
  rpi3b+: corrupted screen on hdmi

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  Eoan daily: 20191010
  Ubuntu Server arm64+raspi3
  HW: Raspberrypi 3 B+

  Initial boot ok but as soon as changing to the high resolution
  framebuffer, the whole screen consists mostly of bright yellow and
  darker yellow vertical stipes. Further boot messages are visible but
  barely readable. Device is accessible via ssh. The dmesg there shows
  some kernel warnings:

  [1.450650] bcm2708_fb soc:fb: FB found 1 display(s)
  [1.452916] WARNING: CPU: 2 PID: 1 at mm/page_alloc.c:4696 
__alloc_pages_nodemask+0x284/0x2c8
  [1.460096] Modules linked in:
  [1.467227] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.3.0-1005-raspi2 
#6-Ubuntu
  [1.474549] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT)
  [1.481908] pstate: 2045 (nzCv daif +PAN -UAO)
  [1.489237] pc : __alloc_pages_nodemask+0x284/0x2c8
  [1.496499] lr : __dma_direct_alloc_pages+0x100/0x1e8
  ...
  [1.761649] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 
1824x984
  [1.850950] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
  [1.859009] bcm2835-rng 3f104000.rng: hwrng registered
  [1.865102] vc-mem: phys_addr:0x mem_base=0x3ec0 
mem_size:0x4000(1024 MiB)
  ...
  [2.909823] WARN::dwc_otg_hcd_init:1043: FIQ DMA bounce buffers: virt = 
10616000 dma = 0xfad1 len=9024
  ...
  [2.946722] WARN::hcd_init_fiq:496: MPHI regs_base at 10075000

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

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

[Kernel-packages] [Bug 1845572] Re: udevadm trigger will fail when trying to add /sys/devices/vio/

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845572

** Tags added: iso-testing

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

Title:
  udevadm trigger will fail when trying to add /sys/devices/vio/

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  This will cause the installer to exit early, causing a kernel panic before 
any prompt to the user. This is restricted to some Power systems.

  [Test case]
  A build vmlinux was used to boot the installer, and a prompt was available.
  'add' was written to /sys/devices/vio/uevent was written to, and no error was 
found.
  'add' was written to /sys/devices/vio/*/uevent, and modalias information was 
found when 'udevadm monitor -p' was run in the background.

  [Regression potential]
  Events may be missing and coldplug/hotplug of vio devices may fail. That was 
tested in the test case and not found to be the case.

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

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

[Kernel-packages] [Bug 1843960] Re: cherrypick has_sipl fix

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1843960

** Tags added: iso-testing

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

Title:
  cherrypick has_sipl fix

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  cherrypick has_sipl fix from the s390 maintainer tree

  
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/patch/?id=4df9a82549cfed5b52da21e7d007b79b2ea1769a

  Otherwise, has_secure sysfs attribute is never correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1843960/+subscriptions

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

[Kernel-packages] [Bug 1845454] Re: Dell XPS 13 7390 - Kernel panic with 19.10 beta image

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845454

** Tags added: iso-testing

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

Title:
  Dell XPS 13 7390 - Kernel panic with 19.10 beta image

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  When trying to start the live session ("try Ubuntu") or trying to
  install the ISO ("install Ubuntu"), the boot process stops within 1
  second with a kernel panic (see attached screenshot).

  The system could boot with a previous version of Eoan image:
  2019-09-09 09:11 (kernel 5.3.0-10)

  Workaround: disable TPM2 in the BIOS.

  /!\ Please note: the information below (and the attached file  
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot 
anything with 19.10 beta image.
  ==
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: syslinux 3:6.03+dfsg1-2
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 26 07:41:16 2019
  Dependencies:
   gcc-8-base 8.3.0-6ubuntu1~18.04.1
   libc6 2.27-3ubuntu1
   libgcc1 1:8.3.0-6ubuntu1~18.04.1
   mtools 4.0.18-2ubuntu1
   syslinux-common 3:6.03+dfsg1-2
  LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1827228] Re: nVidia-340 driver install failed, black screen upon boot and hanging

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1827228

** Tags added: iso-testing

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

Title:
  nVidia-340 driver install failed, black screen upon boot and hanging

Status in nvidia-settings package in Ubuntu:
  New

Bug description:
  Hello all,
  I was trying to install nVidia driver 340 onto Kbuntu 19.04 (also tried 
Ubuntu 18.04 and Linux mint 19.04)
  ;
   ALL installs failed.  Cannot boot and/or upon booting (Linux Mint 19.04), it 
will hanged hard.

  
  I am a newbie in Linux, please offer help.
  I am using a HP G60 (old laptop) w/ a Nvidia GF8200M G graphics chip.

  Also tried download the specific driver from nVidia's web site, file:
  340.1070 and 340.1060; and installed them, ALL not working and system
  hung.  Using the X-org driver is fine, but no 3D acceleration.

  Any idea??  Please help.

  
  Andrew Cheng - x Windows system engineer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1827228/+subscriptions

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

[Kernel-packages] [Bug 1829494] Re: 19.10 lubuntu suspend test; on wake no sound

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1829494

** Tags added: iso-testing

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

Title:
  19.10 lubuntu suspend test; on wake no sound

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i was attempting to add this as additional info to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816394
  this has occurred on various model dells (755x2, 780, 960..) but they are all 
similar) and occurs on occasion on installed systems (18.10, 19.04 & 19.10)

  19.10 live QA-Test, I suspended system, waited.   On hitting power
  button to resume the machine resumed as expected, but firefox (when
  unpaused) was silent with only video showing.   Like aforementioned
  bug, to fix I go to pavucontrol & go to last tab, click the profile
  off, then back on and instantly firefox sound resumed (it'd been
  silent.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu1808 F pulseaudio
   /dev/snd/controlC1:  lubuntu1808 F pulseaudio
  CasperVersion: 1.407
  CurrentDesktop: LXQt
  Date: Fri May 17 09:52:16 2019
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190516)
  MachineType: Dell Inc. OptiPlex 780
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.179
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0200DY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 780
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1825235

** Tags added: iso-testing

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

Title:
  Load average inexplicably high with 5.0 kernel on rpi

Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC
  2019 aarch64 aarch64 aarch64 GNU/Linux

  I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the 
disco release candidate.
  After booting, the load average stays quite high, typically over 4.0. This 
persists, even if I leave it idle for several hours:
  ubuntu@ubuntu:~$ w
   19:44:05 up  2:22,  1 user,  load average: 4.16, 4.03, 4.01

  /proc/loadavg is consistent with these numbers. But when I check top,
  there are no obvious culprits hogging the cpu or anything. Typically
  everything looks to be <1% cpu usage, with top being the biggest cpu
  hog at about 2%. The system doesn't seem too slow (for a pi), but it's
  unusual to see such high numbers.

  Nothing seems to be swapping:

  ubuntu@ubuntu:~$ free -m
totalusedfree  shared  buff/cache   
available
  Mem:908 173 422   6 312 
707
  Swap: 0   0   0

  
  ubuntu@ubuntu:~$ iostat
  Linux 5.0.0-1006-raspi2 (ubuntu)  04/17/19_aarch64_   (4 CPU)

  avg-cpu:  %user   %nice %system %iowait  %steal   %idle
 1.640.151.572.060.00   94.57

  Device tpskB_read/skB_wrtn/skB_readkB_wrtn
  loop0 0.08 0.50 0.00354  0
  loop1 2.56 3.98 0.00   2805  0
  loop2 0.01 0.01 0.00  4  0
  mmcblk0  12.70   367.40   705.16 258830 496785

  ubuntu@ubuntu:~$ vmstat 1
  procs ---memory-- ---swap-- -io -system-- 
--cpu-
   r  b   swpd   free   buff  cache   si   sobibo   in   cs us sy id wa 
st
   0  0  0 514540  18004 2240720097   182 2564   76  2  2 94  2 
 0
   0  0  0 514512  18004 22413600 0  2012 10136  142  0  0 94  
5  0
   0  0  0 514512  18004 22413600 0 0 10117  106  0  0 100  
0  0
   0  0  0 514512  18004 22413600 0 0 10121   98  0  0 100  
0  0
   0  0  0 514512  18012 22412800 0  2028 10129  141  0  0 93  
7  0
   0  0  0 514512  18012 22413600 0 0 10149  135  0  0 100  
0  0
   0  0  0 514512  18012 22413600 0 0 10108   97  0  0 100  
0  0
   0  0  0 514512  18012 22413600 0  2012 10125  126  0  0 95  
5  0
   0  0  0 514512  18012 22413600 0 0 10117  101  0  0 100  
0  0
   0  1  0 514512  18012 22413600 0  2012 10109  104  0  0 98  
2  0
   0  0  0 514512  18020 22412800 012 10139  150  0  0 96  
4  0
   0  0  0 514512  18020 22412800 0 0 10108   90  0  0 100  
0  0

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

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

[Kernel-packages] [Bug 1823819] Re: Upgrade to 19.04 fails with linux-image-5.0.0-8

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1823819

** Tags added: iso-testing

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

Title:
  Upgrade to 19.04 fails with linux-image-5.0.0-8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrade to 19.04 Ubuntu MATE fails with following:

  Could not install 'linux-image-5.0.0-8-generic
  triggers looping, abandoned

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  Same error as Bug #1823116

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-8-generic 5.0.0-8.9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testdev1634 F pulseaudio
  CurrentDesktop: MATE
  Date: Mon Apr  8 18:22:14 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=f20f596d-9e53-4bb6-bf4a-df5764d8ddb2 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-09 (0 days ago)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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/1823819/+subscriptions

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

[Kernel-packages] [Bug 1823116] Re: Upgrade to 19.04 fails with linux-image-5.0.0-8

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1823116

** Tags added: iso-testing

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

Title:
  Upgrade to 19.04 fails with linux-image-5.0.0-8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrade to 19.04 Ubuntu MATE fails with following:

  Could not install 'linux-image-5.0.0-8-generic
  triggers looping, abandoned

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  Crash file attached

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-8-generic 5.0.0-8.9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testdev1693 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr  3 22:17:28 2019
  InstallationDate: Installed on 2019-04-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=c2660f0c-ec7a-463d-9e93-56ddd8833be3 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-04 (0 days ago)
  dmi.bios.date: 04/13/2018
  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:bd04/13/2018: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/1823116/+subscriptions

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

[Kernel-packages] [Bug 1822987] Re: nouveau timeout on Disco with nvidia GTX 1060

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1822987

** Tags added: iso-testing

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

Title:
  nouveau timeout on Disco with nvidia GTX 1060

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following error message could be found while booting this Dell G7
  with Disco LiveUSB (20190403)

  Despite there is a such error message, the graphic looks OK.

  [   15.714767] [ cut here ]
  [   15.714768] nouveau :01:00.0: timeout
  [   15.714818] WARNING: CPU: 7 PID: 2038 at 
drivers/gpu/drm/nouveau/nvkm/subdev/secboot/ls_ucode_msgqueue.c:183 
acr_ls_sec2_post_run+0x192/0x240 [nouveau]
  [   15.714819] Modules linked in: arc4 cmac bnep intel_rapl snd_soc_skl 
x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp snd_soc_hdac_hda 
coretemp snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp 
kvm_intel snd_soc_acpi_intel_match snd_soc_acpi ath10k_pci snd_soc_core 
snd_hda_codec_realtek ath10k_core snd_hda_codec_generic snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel snd_hda_codec crct10dif_pclmul joydev 
crc32_pclmul ghash_clmulni_intel snd_hda_core ath uvcvideo btusb aesni_intel 
mac80211 snd_hwdep btrtl snd_pcm videobuf2_vmalloc btbcm videobuf2_memops 
snd_seq_midi videobuf2_v4l2 snd_seq_midi_event btintel aes_x86_64 
videobuf2_common bluetooth crypto_simd snd_rawmidi cryptd videodev glue_helper 
intel_cstate snd_seq mei_me media cdc_acm dell_laptop processor_thermal_device 
snd_seq_device cfg80211 snd_timer input_leds ucsi_acpi idma64 ecdh_generic 
ledtrig_audio mei serio_raw hid_multitouch intel_rapl_perf typec_ucsi snd 
intel_soc_dts_iosf dell_wmi int3403_thermal
  [   15.714833]  virt_dma intel_hid wmi_bmof sparse_keymap 
intel_wmi_thunderbolt dell_smbios soundcore dcdbas int3400_thermal 
intel_pch_thermal int340x_thermal_zone acpi_thermal_rel dell_wmi_descriptor 
typec mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables 
x_tables autofs4 overlay nls_utf8 isofs nls_iso8859_1 jfs xfs libcrc32c 
reiserfs dm_mirror dm_region_hash dm_log uas usb_storage hid_generic usbhid 
i915 nouveau kvmgt vfio_mdev mdev vfio_iommu_type1 vfio kvm irqbypass ttm 
i2c_algo_bit drm_kms_helper syscopyarea nvme sysfillrect sysimgblt fb_sys_fops 
mxm_wmi drm psmouse alx ahci nvme_core intel_lpss_pci mdio libahci i2c_hid 
intel_lpss hid pinctrl_cannonlake wmi video pinctrl_intel
  [   15.714848] CPU: 7 PID: 2038 Comm: Xorg Not tainted 5.0.0-8-generic 
#9-Ubuntu
  [   15.714849] Hardware name: Dell Inc. G7 7588/, BIOS 1.0.1 03/14/2018
  [   15.714867] RIP: 0010:acr_ls_sec2_post_run+0x192/0x240 [nouveau]
  [   15.714868] Code: 45 a8 48 8b 40 10 48 8b 78 10 4c 8b 7f 50 4d 85 ff 74 1e 
e8 40 ac 37 f7 4c 89 fa 48 c7 c7 15 56 62 c0 48 89 c6 e8 80 98 d7 f6 <0f> 0b e9 
25 ff ff ff 4c 8b 7f 10 eb dc 8b 43 20 48 c7 c6 08 c7 61
  [   15.714869] RSP: 0018:ac7305a079b8 EFLAGS: 00010286
  [   15.714869] RAX:  RBX: 9b950cdde300 RCX: 
0006
  [   15.714870] RDX: 0007 RSI: 0096 RDI: 
9b951f3d6440
  [   15.714870] RBP: ac7305a07a10 R08: 0001 R09: 
03e2
  [   15.714870] R10: 0004 R11:  R12: 

  [   15.714871] R13: 9b951921a800 R14: 0040 R15: 
9b951ab96940
  [   15.714872] FS:  7f14f3629a80() GS:9b951f3c() 
knlGS:
  [   15.714872] CS:  0010 DS:  ES:  CR0: 80050033
  [   15.714873] CR2: 7f14f00ef000 CR3: 000856790003 CR4: 
003606e0
  [   15.714873] DR0:  DR1:  DR2: 

  [   15.714874] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   15.714874] Call Trace:
  [   15.714893]  acr_r352_bootstrap+0x1a9/0x2b0 [nouveau]
  [   15.714910]  acr_r352_reset+0x39/0x230 [nouveau]
  [   15.714926]  nvkm_secboot_reset+0x35/0x70 [nouveau]
  [   15.714944]  gf100_gr_init_ctxctl_ext+0x72/0x7e0 [nouveau]
  [   15.714962]  ? gf100_gr_zbc_init+0x15f/0x2a0 [nouveau]
  [   15.714979]  gf100_gr_init_ctxctl+0x32/0x2b0 [nouveau]
  [   15.714997]  gf100_gr_init+0x563/0x590 [nouveau]
  [   15.715015]  gf100_gr_init_+0x5b/0x60 [nouveau]
  [   15.715032]  nvkm_gr_init+0x1d/0x20 [nouveau]
  [   15.715041]  nvkm_engine_init+0xb9/0x1f0 [nouveau]
  [   15.715052]  nvkm_subdev_init+0xbc/0x210 [nouveau]
  [   15.715061]  nvkm_engine_ref.part.0+0x4a/0x70 [nouveau]
  [   15.715071]  nvkm_engine_ref+0x13/0x20 [nouveau]
  [   15.715081]  nvkm_ioctl_new+0x129/0x220 [nouveau]
  [   15.715098]  ? nvkm_fifo_chan_child_del+0xa0/0xa0 [nouveau]
  [   15.715115]  ? gf100_gr_dtor+0xd0/0xd0 [nouveau]
  [   15.715125]  nvkm_ioctl+0xe2/0x180 

[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1821823

** Tags added: iso-testing

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

Title:
  No wireless networks displayed for broadcom BCM43142

Status in linux package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  New

Bug description:
  For 19.04 UB did a minimal install.  I selected the ubiquity
  proprietary option and expected the broadcom driver to be found and
  installed.

  On reboot I could not see and wireless networks.  I went to the
  Additional Drivers window and it stated that the computer was indeed
  using Broadcom 802.11 Linux STA wireless driver and was in use.

  This is a regression - in both 18.04 and 18.10, the same steps also
  installed the driver, and wireless networks were found and could be
  connected to.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dad1060 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Wed Mar 27 00:25:09 2019
  InstallationDate: Installed on 2019-03-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1815579

** Tags added: iso-testing

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

Title:
  Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04
  in bionic

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed

Bug description:
  I am trying to test new HWE stack from 18.10 in my destkop Ubuntu
  18.04.1 (expected release 18.04.2 this week) and I have broken
  dependencies when installing `xserver-xorg-hwe-18.04` package with
  NVidia drivers:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
xserver-xorg-video-nvidia-390 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-nvidia-390 is already the newest version 
(390.77-0ubuntu0.18.04.1).
  xserver-xorg-video-nvidia-390 set to manually installed.
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 
2:1.17.2-2) but it is not going to be installed
Conflicts: xserver-xorg-core (>= 0~)
Recommends: xserver-xorg-video-all-hwe-18.04 but it 
is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` 
this happens:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 
libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 
libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 
libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 
libnvidia-compute-390:i386 libnvidia-decode-390
libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 
libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 
libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386
libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 
libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 
libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 
libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers
nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 
nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 
pkg-config screen-resolution-extra vdpau-driver-all
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 
xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 
xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 
xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 
xserver-xorg-video-radeon-hwe-18.04
xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04
  Suggested packages:
xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 
xserver-xorg-video-mach64 firmware-misc-nonfree
  Recommended packages:
xserver-xorg-input-wacom-hwe-18.04
  The following packages will be REMOVED:
nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all 
xserver-xorg-input-libinput xserver-xorg-video-nvidia-390
  The following NEW packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 
xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 
xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04
xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 
xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 
xserver-xorg-video-qxl-hwe-18.04

[Kernel-packages] [Bug 1810108] Re: Failure to boot as QEMU guest when using -device virtio-vga, virgl=true

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1810108

** Tags added: iso-testing

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

Title:
  Failure to boot as QEMU guest when using -device virtio-vga,virgl=true

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Xubuntu 18.04 in a QEMU virtual machine using -device
  virtio-vga,virgl=true fails to boot. Even setting to output boot
  messages to a serial console no messages appear as if it never tried
  to boot at all.

  What makes this strange is that the live media works correctly using
  -device virtio-vga,virgl=true, but then, on reboot, the installed
  system fails to boot.

  To make the guest work it's required to remove the option ,virgl=true
  from the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sun Dec 30 17:33:21 2018
  InstallationDate: Installed on 2018-12-30 (0 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230)
  IwConfig:
   ens2  no wireless extensions.
   
   lono wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcFB: 0 virtiodrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=15c2a9cf-1159-4e4a-a06c-68ad2ad82d12 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1795857

** Tags added: iso-testing

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

Title:
  enable CONFIG_DRM_BOCHS

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

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

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

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

[Kernel-packages] [Bug 178405] Re: Two oops an panic in xen DomU

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/178405

** Tags added: iso-testing

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

Title:
  Two oops an panic in xen DomU

Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix

Bug description:
  While using rsync to copy data from another machine on the lan I got
  two Oops followed by a panic on a Xen DomU.

  The Dom0 is running Gutsy, the DomU us running Dapper. Both are
  running a 2.6.22-14-xen kernel. The machine is a Core2 Quad. The DomU
  had 2 vcpu's and 2 vif's assigned to it. All the DomU's file systems
  are on LVM partitions with each partition exported as a separate
  device to the DomU.

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

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

[Kernel-packages] [Bug 1676918] Re: Kernel 4.10+ regression: blackscreen when trying to resume from suspend

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1676918

** Tags added: iso-testing

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

Title:
  Kernel 4.10+ regression: blackscreen when trying to resume from
  suspend

Status in gnome-power-manager package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  Update: So far I did not encounter any issues with suspend/resume with
  Kernel 4.8 and 4.9. This seems to be a regression in 4.10.

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions

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

[Kernel-packages] [Bug 1740289] Re: print_req_error: critical target error, dev sr0, sector 2097136

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1740289

** Tags added: iso-testing

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

Title:
  print_req_error: critical target error, dev sr0, sector 2097136

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  dmesg:
  [ 1816.482664] print_req_error: critical target error, dev sr0, sector 2097136

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1655 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1655 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 27 15:28:36 2017
  InstallationDate: Installed on 2017-10-13 (75 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1504909] Re: blk_update_request: I/O error when accessing a disk that is spun down

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1504909

** Tags added: iso-testing

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

Title:
  blk_update_request: I/O error when accessing a disk that is spun down

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 6 3TB SATA disks that are attached via a IBM M1015 in IT mode
  and the mpt2sas driver. The filesystem is zfsonlinux.

  I can't name the exact 3.19 kernel version when this error began, but
  it was not the inital 3.19 Vivid LTS Kernel because after initally
  upgrading to 3.19 everything still worked.

  After a recent update I have the following problem:

  When disks are spun down and then accessed an error occurs which corrupts 
data.
  When the disks are finally spun up everything works as expected, also 
preventing them from spinning down works as a workaround.

  Could this be a NCQ bug?

  Drives are 5x Seagate ST3000DM001 and 1x HGST HDN724030ALE640.

  [59526.359997] sd 0:0:1:0: [sdc] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59526.360003] sd 0:0:1:0: [sdc] CDB:
  [59526.360006] Read(16): 88 00 00 00 00 00 31 28 fd 58 00 00 00 08 00 00
  [59526.360022] blk_update_request: I/O error, dev sdc, sector 824769880
  [59544.111090] sd 0:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59544.111097] sd 0:0:0:0: [sdb] CDB:
  [59544.00] Read(16): 88 00 00 00 00 00 31 28 fd 50 00 00 00 08 00 00
  [59544.15] blk_update_request: I/O error, dev sdb, sector 824769872
  [59544.114465] sd 0:0:4:0: [sdf] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59544.114468] sd 0:0:4:0: [sdf] CDB:
  [59544.114469] Read(16): 88 00 00 00 00 00 31 28 fd 58 00 00 00 08 00 00
  [59544.114483] blk_update_request: I/O error, dev sdf, sector 824769880
  [59552.117436] sd 0:0:3:0: [sde] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59552.117443] sd 0:0:3:0: [sde] CDB:
  [59552.117446] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59552.117462] blk_update_request: I/O error, dev sde, sector 824769968
  [59572.951158] sd 0:0:2:0: [sdd] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59572.951167] sd 0:0:2:0: [sdd] CDB:
  [59572.951170] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59572.951192] blk_update_request: I/O error, dev sdd, sector 824769968
  [59572.955679] sd 0:0:5:0: [sdg] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [59572.955695] sd 0:0:5:0: [sdg] CDB:
  [59572.955701] Read(16): 88 00 00 00 00 00 31 28 fd b0 00 00 00 08 00 00
  [59572.955720] blk_update_request: I/O error, dev sdg, sector 824769968
  [70357.782677] sd 0:0:4:0: [sdf] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [70357.782686] sd 0:0:4:0: [sdf] CDB:
  [70357.782690] Read(16): 88 00 00 00 00 00 85 c1 c9 08 00 00 00 08 00 00
  [70357.782712] blk_update_request: I/O error, dev sdf, sector 2244069640
  [70368.087947] sd 0:0:0:0: [sdb] FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_OK
  [70368.087953] sd 0:0:0:0: [sdb] CDB:
  [70368.087955] Read(16): 88 00 00 00 00 00 85 c1 c9 00 00 00 00 08 00 00
  [70368.087969] blk_update_request: I/O error, dev sdb, sector 2244069632

  lsb_release -rd:
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Kernel Version: 3.19.0-30-generic
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Okt  8 18:46 seq
   crw-rw 1 root audio 116, 33 Okt  8 18:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.15
  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
  HibernationDevice: RESUME=/dev/mapper/eternity--vg-swap_1
  InstallationDate: Installed on 2014-09-25 (380 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   lono wireless extensions.
   
   em1   no wireless extensions.
  MachineType: Dell Inc. PowerEdge T20
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-30-generic 
root=/dev/mapper/hostname--vg-root ro console=tty0 console=ttyS4,115200 
intel_pstate=enable cgroup_enable=memory swapaccount=1 intel_iommu=on 
enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=16M mtrr_chunk_size=64M 
i915.enable_rc6=0 nmi_watchdog=0
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 

[Kernel-packages] [Bug 1566468] Re: systemd-modules-load.service: Failing due to missing module 'ib_iser'

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1566468

** Tags added: iso-testing

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

Title:
  systemd-modules-load.service: Failing due to missing module 'ib_iser'

Status in linux package in Ubuntu:
  Fix Released
Status in linux-kvm package in Ubuntu:
  New
Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-kvm source package in Xenial:
  New
Status in linux-raspi2 source package in Xenial:
  Confirmed
Status in open-iscsi source package in Xenial:
  Invalid

Bug description:
  On a number of VMs using Xenial daily builds 20160330 and 20160403,
  out of the box (just after booting for the first time), the following
  appears in dmesg at boot time:

  systemd[1]: systemd-modules-load.service: Main process exited, code=exited, 
status=1/FAILURE
  systemd[1]: Failed to start Load Kernel Modules.
  systemd[1]: systemd-modules-load.service: Unit entered failed state.
  systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

  The following related complaint appears in /var/log/syslog:

  ubuntu systemd-modules-load[352]: Inserted module 'iscsi_tcp'
  ubuntu systemd-modules-load[352]: Failed to find module 'ib_iser'

  It looks like 'ib_iser' is some Mellanox-related module, which I don't
  *think* is something that a stock cloudimg install should attempt to
  load but I may be wrong; in any case, it's not present (nor is there
  any similar whingeing) on similar VMs running off 14.04 cloudimg.

  More info: http://askubuntu.com/questions/753672/xenial-beta2-systemd-
  modules-load-service-failed-due-to-missing-module-ib-i

  ---
  root@testvm4:~# lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  root@testvm4:~# apt policy systemd
  systemd:
Installed: 229-3ubuntu2
Candidate: 229-3ubuntu2

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

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

[Kernel-packages] [Bug 1710517] Re: Enable EFI stub for raspi2 kernels

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1710517

** Tags added: iso-testing

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

Title:
  Enable EFI stub for raspi2 kernels

Status in linux package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  New

Bug description:
  U-boot is now able to emulate UEFI and this is used by openSUSE to
  boot the raspberry pi [1].

  I would like to use this technique to load grub2.  However, according
  to [2] new versions of grub2 require a 32 bit kernel to be built with
  EFI stub enabled.

  I have successfully used this U-boot/grub2 combination to boot a
  generic aarch64 Ubuntu kernel on my pi3 [3].  It works well and would
  be a huge improvement if this could be brought to arm 32 bit.


  [1]
  https://www.suse.com/docrep/documents/a1f0ledpbe/UEFI%20on%20Top%20of
  %20U-Boot.pdf

  [2] https://wiki.linaro.org/LEG/Engineering/Kernel/GRUB

  [3] https://lists.ubuntu.com/archives/lubuntu-
  users/2017-August/011613.html

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

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

[Kernel-packages] [Bug 1729128] Re: Raspberry Pi 3 microSD support missing from the installer

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1729128

** Tags added: iso-testing

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

Title:
  Raspberry Pi 3 microSD support missing from the installer

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  Without this module in block-modules.udeb, the default generic arm64
  image cannot install on a raspberrypi3 board.

  [Test case]

  Build the block-modules.udeb with and without the attached patch and
  check for the presence of the drivers/mmc/host/bcm2835.ko.

  [Regression Potential]

  None, we are adding a ko to a udeb, not removing it.

  ---

  
  Please add bcm2835 to block-modules on arm64 (and armhf?).

  artful's arm64 d-i mini.iso works fine on Raspberry Pi 3 when booting
  with a UEFI-capable u-boot, except for one detail: mmc/host/bcm2835.ko
  is missing from block-modules, so you can't install to microSD without
  manually grabbing and loading the module.

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

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

[Kernel-packages] [Bug 1761468] Re: Debian-installer missing mmc bcm2835 module

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1761468

** Tags added: iso-testing

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

Title:
  Debian-installer missing mmc bcm2835 module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Testing the latest arm64 18.04 mini ISO on a raspberry pi 3, I found
  the internal sd card reader was not recognised.  This is the main
  storage on a pi.  Manually extracting the mmc/host/bcm2835 module from
  the extras package and insmod'ing it got it working on the d-i
  installer.

  It would be great if the sd card could be recognised out of the box.
  I think all that is needed is to include the module in the block
  storage udeb.

  Note the pi has two SD controllers.  A second is used for the WiFi
  (but can also be used for the sd card reader).  That is also missing
  from the debian installer as far as I can tell.

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

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

[Kernel-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1754836

** Tags added: iso-testing

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

Title:
  Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut:
  Failed to activate service 'org.bluez': timed out
  (service_start_timeout=25000ms)

Status in blueman package in Ubuntu:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu seeing long first time boot to desktop from login.

  Possibly also causing the long time to desktop from try/install
  livesession dialogue.

  Including xsession-errors from the first time boot on installed
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 11:32:59 2018
  InstallationDate: Installed on 2018-03-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: bluetooth
  MachineType: NOVATECH LTD MBB-44608
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: 7383241-001
  dmi.chassis.type: 3
  dmi.chassis.vendor: NOVATECH LTD
  dmi.chassis.version: V1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0:
  dmi.product.family: AMI PLATFORM
  dmi.product.name: MBB-44608
  dmi.product.version: V1.0
  dmi.sys.vendor: NOVATECH LTD
  hciconfig:
   
  rfkill:
   
  syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]:   
[1520681416.8951] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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

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

[Kernel-packages] [Bug 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1743638

** Tags added: iso-testing

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

Title:
  Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-hwe source package in Xenial:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  Fix Committed
Status in debian-installer source package in Artful:
  Fix Committed
Status in linux source package in Artful:
  Fix Released
Status in linux-firmware source package in Artful:
  Fix Committed
Status in linux-hwe source package in Artful:
  Invalid
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in debian-installer source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work.

  [Test Case]
  Attempt to use the netinst installer to install a system over this NIC.

  [Regression Risk]
  The fix is just add to add additional kernel modules and firmware to the 
installer to support this NIC. The biggest risk I see there is that it 
increases the size of the installer, which could potentially grow to bit for 
some smaller systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743638/+subscriptions

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

[Kernel-packages] [Bug 1745118] Re: Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on Xenial / Artful

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1745118

** Tags added: iso-testing

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

Title:
  Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on
  Xenial / Artful

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Some SRU testing node cannot boot with the latest 32bit 4.13 linux-hwe
  kernel.

  Take node "fozzie"(Dell PowerEdge R320) for example, it works with
  4.13.0-21.24~16.04.1 but not 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel
  on Xenial.

  From the BMC console, I can see the grub menu on boot and after that
  it will drop into a boot loop.

  This can be reproduced on Artful 4.13 as well.

  Note that this kernel works for some of the node in our test pool
  (Intel SDP - Denlow)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24~16.04.1
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Wed Jan 24 08:49:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 09:17 seq
   crw-rw 1 root audio 116, 33 Jan 24 09:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  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:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-21-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1731971] Re: Artful update to 4.13.12 stable release

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1731971

** Tags added: iso-testing

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

Title:
  Artful update to 4.13.12 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.13.12 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.13.12 stable release shall be applied:
  * ALSA: timer: Add missing mutex lock for compat ioctls
  * ALSA: seq: Fix nested rwsem annotation for lockdep splat
  * cifs: check MaxPathNameComponentLength != 0 before using it
  * KEYS: return full count in keyring_read() if buffer is too small
  * KEYS: trusted: fix writing past end of buffer in trusted_read()
  * KEYS: fix out-of-bounds read during ASN.1 parsing
  * ASoC: adau17x1: Workaround for noise bug in ADC
  * virtio_blk: Fix an SG_IO regression
  * arm64: ensure __dump_instr() checks addr_limit
  * KVM: arm64: its: Fix missing dynamic allocation check in scan_its_table
  * arm/arm64: KVM: set right LR register value for 32 bit guest when inject
abort
  * arm/arm64: kvm: Disable branch profiling in HYP code
  * ARM: dts: mvebu: pl310-cache disable double-linefill
  * ARM: 8715/1: add a private asm/unaligned.h
  * drm/amdgpu: return -ENOENT from uvd 6.0 early init for harvesting
  * drm/amdgpu: allow harvesting check for Polaris VCE
  * userfaultfd: hugetlbfs: prevent UFFDIO_COPY to fill beyond the end of
i_size
  * ocfs2: fstrim: Fix start offset of first cluster group during fstrim
  * fs/hugetlbfs/inode.c: fix hwpoison reserve accounting
  * mm, swap: fix race between swap count continuation operations
  * drm/i915: Do not rely on wm preservation for ILK watermarks
  * drm/i915/edp: read edp display control registers unconditionally
  * Revert "powerpc64/elfv1: Only dereference function descriptor for non-text
symbols"
  * MIPS: bpf: Fix a typo in build_one_insn()
  * MIPS: smp-cmp: Use right include for task_struct
  * MIPS: microMIPS: Fix incorrect mask in insn_table_MM
  * MIPS: SMP: Fix deadlock & online race
  * Revert "x86: do not use cpufreq_quick_get() for /proc/cpuinfo "cpu MHz""
  * x86: CPU: Fix up "cpu MHz" in /proc/cpuinfo
  * powerpc/kprobes: Dereference function pointers only if the address does not
belong to kernel text
  * futex: Fix more put_pi_state() vs. exit_pi_state_list() races
  * perf/cgroup: Fix perf cgroup hierarchy support
  * x86/mcelog: Get rid of RCU remnants
  * irqchip/irq-mvebu-gicp: Add missing spin_lock init
  * Linux 4.13.12

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

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

[Kernel-packages] [Bug 1724639] Re: Graphics problem - 80% of the Left hand side of screen solid black

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1724639

** Tags added: iso-testing

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

Title:
  Graphics problem -  80% of the Left hand side of screen solid black

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1723619

** Tags added: iso-testing

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

Title:
  Ubuntu Desktop ISO fails to boot with nouveau

Status in Release Notes for Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On the latest daily artful image (/current as of 2017-01-14), the
  following occurs on a system with nVidia graphics (on my system, a
  GTX970): https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2

  Steps to reproduce:
  - Download latest daily image, check checksums, burn to USB
  - Boot from USB.
  - Choose "Install Ubuntu" or "try ubuntu" at the menu.

  This happens on the livecd, but also upon ugrading the system from a
  previous daily with a different kernel: my "old" daily booted and
  installed fine with kernel 4.12.0-12, then failed with same error once
  dist-upgraded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions

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

[Kernel-packages] [Bug 1720229] Re: arm64: usercopy: kernel memory overwrite attempt detected to (null) () (6 bytes)

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1720229

** Tags added: iso-testing

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

Title:
  arm64: usercopy: kernel memory overwrite attempt detected to
  (null) () (6 bytes)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I observed this stack trace when attempting to install the 2017.09.26
  daily arm64/artful server ISO:

  [  107.816592] usercopy: kernel memory overwrite attempt detected to  
 (null) () (6 bytes)
  [  107.818389] Internal error: Oops - BUG: 0 [#1] SMP
  [  107.819170] Modules linked in: raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac virtio_blk 
virtio_net nls_utf8 isofs usb_storage virtio_scsi
  [  107.823033] CPU: 0 PID: 8105 Comm: dmraid Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [  107.824318] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
  [  107.825490] task: 80007cfbe900 task.stack: 80007792c000
  [  107.826498] PC is at __check_object_size+0x114/0x200
  [  107.827349] LR is at __check_object_size+0x114/0x200
  [  107.828192] pc : [] lr : [] pstate: 
00400145
  [  107.829458] sp : 80007792fb00
  [  107.830026] x29: 80007792fb00 x28:  
  [  107.830934] x27: fa066520 x26: 80007ce6c000 
  [  107.831840] x25: 0002001d x24: 80007ce6 
  [  107.832743] x23: 0006 x22: 0006 
  [  107.833657] x21:  x20: 0006 
  [  107.834564] x19:  x18:  
  [  107.835467] x17:  x16:  
  [  107.836371] x15: 093b8c08 x14: 2820296c6c756e28 
  [  107.837273] x13: 2020202020202020 x12: 2020206f74206465 
  [  107.838175] x11: 093b9658 x10: 086a7e40 
  [  107.839072] x9 : 746972777265766f x8 : 0017 
  [  107.839972] x7 : 20293e6c6c756e3c x6 : 80007ffb5dc0 
  [  107.840867] x5 : 80007ffb5dc0 x4 :  
  [  107.841771] x3 : 80007ffbe038 x2 : 00040d00 
  [  107.842668] x1 :  x0 : 0059 
  [  107.843566] Process dmraid (pid: 8105, stack limit = 0x80007792c000)
  [  107.844698] Stack: (0x80007792fb00 to 0x80007793)
  [  107.845680] fb00: 80007792fb40 084e22c0 80007792fc40 
80007735ca08
  [  107.846998] fb20: 80007735c8c0 093b8000 0006 
082cd088
  [  107.848319] fb40: 80007792fbf0 084e2da4 093b8000 
2285
  [  107.849649] fb60: 80007ce6 fa0664c8 80007ce6c000 
0002001d
  [  107.850974] fb80: 80007792fc40 80007cfbe900 08a91000 
80007cfbe900
  [  107.852295] fba0: 80007792fc10  093b8000 

  [  107.853626] fbc0: 80007792fbf0 082d022c 80007cfe9000 

  [  107.854944] fbe0: 80007cfe9000 00040d00 80007792fce0 
084e2f88
  [  107.856264] fc00: 2285 80007a8d7a80 0002001d 
fa0664c8
  [  107.857592] fc20: fa0664c8 0009 0124 
001d
  [  107.858917] fc40: fffd0053 00040006 0ed36f10 
fa066520
  [  107.860240] fc60:  1770  

  [  107.861568] fc80:    
0200
  [  107.862890] fca0: 0ed2ee10 80007792fe30 07ff 
0fe4
  [  107.864214] fcc0: 80007792fce0 084e2f6c 2285 
00040d00
  [  107.865539] fce0: 80007792fd10 00ae6798 80007c873418 
80007a8d7a80
  [  107.866861] fd00: 0002001d 2285 80007792fd50 
084d4294
  [  107.868184] fd20: 2285 093b8000 fa0664c8 
80007a8d7a80
  [  107.869513] fd40: 0002001d ff9c 80007792fdc0 
083057f8
  [  107.870837] fd60: 80007ccac600 2285 fa0664c8 
80007ccac600
  [  107.872154] fd80: 80007cea0328 fc00  

  [  107.873479] fda0: 1000  59cd5389 
00040d00
  [  107.874798] fdc0: 80007792fdf0 082d4b4c 093b8000 
2285
  [  107.876115] fde0: fa0664c8 00040d00 80007792fe80 
082d530c
  [  107.877432] fe00:  80007ccac600 80007ccac600 
0009
  [  107.878757] fe20: 2285 fa0664c8 618007ff 
1001
  [  

[Kernel-packages] [Bug 1711358] Re: 20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1711358

** Tags added: iso-testing

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

Title:
  20170817 - ISO hangs on boot on qemu with splash screen enabled and
  qxl graphics driver

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  1. Boot artful desktop 20170817 under qemu with qxl
  2. Wait until ubiquity-dm is displayed

  Expected result
  It boots

  Actual result
  It hangs on the splash screen and the dots below the Ubuntu logo are not 
blinking. If the option 'splash' is removed from the boot command line it boots 
successfully.

  It also boots successfully with -vga std but in this case the splash
  screen is in text mode not graphical unlike with the qxl driver.

  - It started with kernel 4.12.
  - It is still happening with kernel 4.13.
  - It only happens when booting from an ISO and not on an installed system.
  - It works with cirrus/vga, but not qxl
  - It works if nosplash is set (or splash removed from the boot command line)
  - It works on Xenial but not on Artful

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

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

[Kernel-packages] [Bug 367688] Re: [424469.038129] ------------[ cut here ]------------

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/367688

** Tags added: iso-testing

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

Title:
  [424469.038129] [ cut here ]

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I'm not entirely sure what the oops did, as I'm by no means familiar
  with the kernel. First time this has happened, but since apport
  prompted me for a report I sent it through. If any further info is
  needed, I'll be glad to help and I will be keeping any eye out for any
  more problems along these lines.

  ProblemType: KernelOops
  Annotation: Your system might become unstable now and might need to be 
restarted.
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Failure: oops
  HibernationDevice: RESUME=UUID=9411d919-3750-47e2-bacd-fcffd1cb3273
  MachineType: EMACHINES T3604
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.28-11-generic 2.6.28-11.42
  ProcCmdLine: root=UUID=fe6b2c3e-6365-4730-a43c-673fe64457d6 ro quiet splash
  ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
  SourcePackage: linux
  Tags: kernel-oops
  Title: [424469.038129] [ cut here ]

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

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

[Kernel-packages] [Bug 1718679] Re: Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1718679

** Tags added: iso-testing

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

Title:
  Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I have a virtualbox VM running artful which I upgrade every day. Today
  when upgrading from kernel  4.12.0-12.13 to 4.13.0-11.12, after a
  reboot gdm3 failed to display the login screen. All I got was a black
  screen, but I could access a virtual terminal.

  Downgrading the kernel back to 4.12.0-12.13 fixed the issue.

  jibel suggested to trying disabling wayland in gdm (by uncommenting
  #WaylandEnable=false in /etc/gdm3/custom.conf), and that did the trick
  too, but only X11 sessions were available of course.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1726 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 1726 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1726 F pulseaudio
   /dev/snd/timer:  ubuntu 1726 f pulseaudio
  Date: Thu Sep 21 15:40:40 2017
  InstallationDate: Installed on 2017-06-07 (106 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=e23963bd-97af-4402-b681-376a6fcaae62 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1686061] Re: Precision Rack failed to resume from S4

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1686061

** Tags added: iso-testing

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

Title:
  Precision Rack failed to resume from S4

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On a Precision Rack with two CPUs, it failed to resume from S4 at ~70%
  rate.

  These two commits can fix the issue:

  commit 406f992e4a372dafbe3c2cff7efbb2002a5c8ebd
  Author: Rafael J. Wysocki 
  Date:   Thu Jul 14 03:55:23 2016 +0200

  x86 / hibernate: Use hlt_play_dead() when resuming from
  hibernation

  
  commit e4630fdd47637168927905983205d7b7c5c08c09
  Author: Rafael J. Wysocki 
  Date:   Mon Aug 8 15:31:31 2016 +0200

  x86/power/64: Always create temporary identity mapping correctly

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

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

[Kernel-packages] [Bug 1675522] Re: arm64: Synchronous Exception at 0x00000000BBC129BC

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1675522

** Tags added: iso-testing

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

Title:
  arm64: Synchronous Exception at 0xBBC129BC

Status in edk2 package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  New

Bug description:
  I installed a KVM VM with the zesty beta server ISO. The install went
  well but, upon reboot, GRUB entered a Synchronous Exception loop after
  selecting the Ubuntu boot option.

  After killing qemu-system-aarch64 and restarting the VM, the system
  booted to a prompt w/o issue.

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

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

[Kernel-packages] [Bug 1633019] Re: BT driver in dell xps 9343 not functioning

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1633019

** Tags added: iso-testing

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

Title:
  BT driver in dell xps 9343 not functioning

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Scanning reveals no mice, keyboards or computers.

  Everything looks to be fine but the Bluetooth seemingly does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24 [modified: 
boot/vmlinuz-4.8.0-22-generic]
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2157 F pulseaudio
   /dev/snd/controlC1:  dave   2157 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 13 11:08:00 2016
  HibernationDevice: RESUME=UUID=7a85aeaa-7621-4d4f-8dd3-f28c0426f22a
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=ed0a9de6-b9f4-4471-843b-2d8d2135c189 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1628284] Re: yakkety: daily powerpc server ISO fails to find cdrom during install in a VM

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1628284

** Tags added: iso-testing

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

Title:
  yakkety: daily powerpc server ISO fails to find cdrom during install
  in a VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  xenial daily ISO successfully installs using the same method on the
  same system, but yakkety reports:

  Sep 27 21:13:14 cdrom-detect: Searching for Ubuntu installation media...
  Sep 27 21:13:18 cdrom-detect: Devices: ''
  Sep 27 21:13:23 cdrom-detect: Devices: ''
  Sep 27 21:13:24 kernel: [  154.649279] random: crng init done
  Sep 27 21:13:28 cdrom-detect: Devices: ''
  Sep 27 21:13:33 cdrom-detect: Devices: ''
  Sep 27 21:13:38 cdrom-detect: Devices: ''
  Sep 27 21:13:43 cdrom-detect: Devices: ''
  Sep 27 21:13:48 cdrom-detect: Devices: ''
  Sep 27 21:13:53 cdrom-detect: Devices: ''
  Sep 27 21:13:58 cdrom-detect: Devices: ''
  Sep 27 21:14:06 cdrom-detect: CDROM-detect failed; unmounting CD just to be 
sure
  Sep 27 21:14:06 main-menu[267]: WARNING **: Configuring 'cdrom-detect' failed 
with error code 1
  Sep 27 21:14:06 main-menu[267]: WARNING **: Menu item 'cdrom-detect' failed.

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

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

[Kernel-packages] [Bug 1626332] Re: Ubuntu MATE 16.10 fails to boot with linux-image-4.8.0-11-generic kernel on PowerMac G5 7, 3

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1626332

** Tags added: iso-testing

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

Title:
  Ubuntu MATE 16.10 fails to boot with linux-image-4.8.0-11-generic
  kernel on PowerMac G5 7,3

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Tried to boot todays daily Yakkety iso on my PowerMac G5 7,3 which failed:
  "Unable to find a medium containing a live file system" (see photo). Same 
problem also for Lubuntu's daily Yakkety iso.

  The same iso boots however on my PowerBook G4 5,6 + 5,8.

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

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

[Kernel-packages] [Bug 813048] Re: Oneiric ALPHA 2 does not detect external card reader

[Ubuntu QA Website]

This bug has been reported on the Ubuntu laptop testing tracker.

A list of all reports related to this bug can be found here:
http://laptop.qa.ubuntu.com/qatracker/reports/bugs/813048

** Tags added: laptop-testing

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

Title:
  Oneiric ALPHA 2 does not detect external card reader

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ACER Aspire One 532h

   ubuntu-bug linux
  Problem in linux-image-3.0-3-generic
  The problem cannot be reported:
  This is not a genuine Ubuntu package

  cat /proc/version_signature > version.log
  sudo lspci -vnvn > lspci-vnvn.log
  [sudo] password for mark: 
  pcilib: sysfs_read_vpd: read failed: Connection timed out

  lsb_release -rd
  Description:  Ubuntu oneiric (development branch)
  Release:  11.10

  I don't know what package detects an external card reader

  I expected it to be detected

  It wasn't detected. It almost crashed the system. It slowed all the processes 
so much I had to manually shutoff the laptop.
  I do have a Nautilus bug #813004 on file for crashes that might be related.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mark   1359 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x5820 irq 45'
 Mixer name : 'Realtek ALC272X'
 Components : 'HDA:10ec0272,10250349,0011'
 Controls  : 17
 Simple ctrls  : 10
  DistroRelease: Ubuntu 11.10
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
  MachineType: Acer AO532h
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-5-generic 
root=UUID=769c17aa-2ba6-4d81-ba73-82b6f39283d2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-5-generic N/A
   linux-backports-modules-3.0.0-5-generic  N/A
   linux-firmware   1.56
  Tags:  oneiric running-unity unity-2d
  Uname: Linux 3.0.0-5-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 03/11/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AO532h
  dmi.board.vendor: Acer
  dmi.board.version: V1.20
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.20
  dmi.modalias: 
dmi:bvnAcer:bvrV1.20:bd03/11/2010:svnAcer:pnAO532h:pvrV1.20:rvnAcer:rnAO532h:rvrV1.20:cvnAcer:ct10:cvrV1.20:
  dmi.product.name: AO532h
  dmi.product.version: V1.20
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 753857] Re: 14e4:4727 [brcmsmac] Wireless LED does not give appropriate feedback on hardware status

[Ubuntu QA Website]

This bug has been reported on the Ubuntu laptop testing tracker.

A list of all reports related to this bug can be found here:
http://laptop.qa.ubuntu.com/qatracker/reports/bugs/753857

** Tags added: laptop-testing

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

Title:
  14e4:4727 [brcmsmac] Wireless LED does not give appropriate feedback
  on hardware status

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Noticed in Natty-Beta1 that the LED light of my wireless adapter doesn't turn 
on. Is not dead since it works in Maverick with proprietary drivers (Broadcom 
STA).
  In Natty, don't even blinks. Installed Broadcom STA proprietary drivers and 
nothing changed.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.41
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joaquin1472 F pulseaudio
  CRDA: Error: [Errno 2] No existe el fichero o el directorio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfb40 irq 48'
     Mixer name : 'IDT 92HD81B1X5'
     Components : 'HDA:111d7605,10280441,00100105'
     Controls  : 14
     Simple ctrls  : 9
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfa08 irq 17'
     Mixer name : 'Nvidia GPU 0b HDMI/DP'
     Components : 'HDA:10de000b,10de0101,00100200'
     Controls  : 16
     Simple ctrls  : 4
  Date: Thu Apr  7 14:38:55 2011
  HibernationDevice: RESUME=UUID=d5351580-0833-43fe-ae8c-5434a1a56944
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  MachineType: Dell Inc. Vostro 3500
  ProcEnviron:
   LANGUAGE=es:en
   LANG=es_AR.UTF-8
   LC_MESSAGES=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic 
root=UUID=296a7f95-929d-4efb-a166-2da5eee4ed68 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-2.6.38-8-generic N/A
   linux-backports-modules-2.6.38-8-generic  N/A
   linux-firmware1.50
  SourcePackage: linux
  StagingDrivers: brcm80211
  Title: [STAGING]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0NVXFV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/10/2010:svnDellInc.:pnVostro3500:pvrNotSpecified:rvnDellInc.:rn0NVXFV:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3500
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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