[Kernel-packages] [Bug 2026605] [NEW] Error while apt upgrade this package
Public bug reported:
sudo apt upgrade
...
nvidia-dkms-535 (535.54.03-0ubuntu0.22.04.1) wird eingerichtet ...
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
Removing old nvidia-535.54.03 DKMS files...
Deleting module nvidia-535.54.03 completely from the DKMS tree.
Loading new nvidia-535.54.03 DKMS files...
Building for 6.1.0-1015-oem
Building for architecture x86_64
Building initial module for 6.1.0-1015-oem
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/nvidia-kernel-source-535.0.crash'
Error! Bad return status for module build on kernel: 6.1.0-1015-oem (x86_64)
Consult /var/lib/dkms/nvidia/535.54.03/build/make.log for more information.
dpkg: Fehler beim Bearbeiten des Paketes nvidia-dkms-535 (--configure):
»installiertes nvidia-dkms-535-Skript des Paketes
post-installation«-Unterprozess gab den Fehlerwert 10 zurück
Trigger für initramfs-tools (0.140ubuntu13.1) werden verarbeitet ...
update-initramfs: Generating /boot/initrd.img-6.1.0-1015-oem
Fehler traten auf beim Bearbeiten von:
nvidia-dkms-535
E: Sub-process /usr/bin/dpkg returned an error code (1)
###
Content of make.log
###
DKMS make.log for nvidia-535.54.03 for kernel 6.1.0-1015-oem (x86_64)
Fr 7. Jul 21:04:29 CEST 2023
make[1]: Verzeichnis „/usr/src/linux-headers-6.1.0-1015-oem“ wird betreten
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu
12.1.0-2ubuntu1~22.04) 12.1.0
You are using: cc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0
make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia/535.54.03/build
need-builtin=1 need-modorder=1
printf '%s
' nvidia/nv.o nvidia/nv-pci.o nvidia/nv-dmabuf.o nvidia/nv-nano-timer.o
nvidia/nv-acpi.o nvidia/nv-cray.o nvidia/nv-dma.o nvidia/nv-i2c.o
nvidia/nv-mmap.o nvidia/nv-p2p.o nvidia/nv-pat.o nvidia/nv-procfs.o
nvidia/nv-usermap.o nvidia/nv-vm.o nvidia/nv-vtophys.o nvidia/os-interface.o
nvidia/os-mlock.o nvidia/os-pci.o nvidia/os-registry.o nvidia/os-usermap.o
nvidia/nv-modeset-interface.o nvidia/nv-pci-table.o nvidia/nv-kthread-q.o
nvidia/nv-memdbg.o nvidia/nv-ibmnpu.o nvidia/nv-report-err.o nvidia/nv-rsync.o
nvidia/nv-msi.o nvidia/nv-caps.o nvidia/nv-frontend.o nvidia/nv_uvm_interface.o
nvidia/nvlink_linux.o nvidia/nvlink_caps.o nvidia/linux_nvswitch.o
nvidia/procfs_nvswitch.o nvidia/i2c_nvswitch.o nvidia/nv-kernel.o | awk
'!x[$0]++ { print("/var/lib/dkms/nvidia/535.54.03/build/"$0) }' >
/var/lib/dkms/nvidia/535.54.03/build/nvidia.mod
ln -sf /var/lib/dkms/nvidia/535.54.03/build/nvidia/nv-kernel.o_binary
/var/lib/dkms/nvidia/535.54.03/build/nvidia/nv-kernel.o
printf '%s
' nvidia-uvm/uvm_ats_sva.o nvidia-uvm/uvm_conf_computing.o
nvidia-uvm/uvm_sec2_test.o nvidia-uvm/uvm_maxwell_sec2.o
nvidia-uvm/uvm_hopper_sec2.o nvidia-uvm/uvm_common.o nvidia-uvm/uvm_linux.o
nvidia-uvm/nvstatus.o nvidia-uvm/nvCpuUuid.o nvidia-uvm/nv-kthread-q.o
nvidia-uvm/nv-kthread-q-selftest.o nvidia-uvm/uvm.o nvidia-uvm/uvm_tools.o
nvidia-uvm/uvm_global.o nvidia-uvm/uvm_gpu.o nvidia-uvm/uvm_gpu_isr.o
nvidia-uvm/uvm_procfs.o nvidia-uvm/uvm_va_space.o nvidia-uvm/uvm_va_space_mm.o
nvidia-uvm/uvm_gpu_semaphore.o nvidia-uvm/uvm_mem.o nvidia-uvm/uvm_rm_mem.o
nvidia-uvm/uvm_channel.o nvidia-uvm/uvm_lock.o nvidia-uvm/uvm_hal.o
nvidia-uvm/uvm_range_tree.o nvidia-uvm/uvm_rb_tree.o
nvidia-uvm/uvm_range_allocator.o nvidia-uvm/uvm_va_range.o
nvidia-uvm/uvm_va_policy.o nvidia-uvm/uvm_va_block.o
nvidia-uvm/uvm_range_group.o nvidia-uvm/uvm_gpu_replayable_faults.o
nvidia-uvm/uvm_gpu_non_replayable_faults.o nvidia-uvm/uvm_gpu_access_counters.o
nvidia-uvm/uvm_perf_events.o nvidia-uvm/uvm_perf_module.o nvidia-uvm/uvm_mmu.o
nvidia-uvm/uvm_pte_batch.o nvidia-uvm/uvm_tlb_batch.o nvidia-uvm/uvm_push.o
nvidia-uvm/uvm_pushbuffer.o nvidia-uvm/uvm_thread_context.o
nvidia-uvm/uvm_tracker.o nvidia-uvm/uvm_maxwell.o nvidia-uvm/uvm_maxwell_host.o
nvidia-uvm/uvm_maxwell_ce.o nvidia-uvm/uvm_maxwell_mmu.o
nvidia-uvm/uvm_maxwell_fault_buffer.o
nvidia-uvm/uvm_maxwell_access_counter_buffer.o nvidia-uvm/uvm_pascal.o
nvidia-uvm/uvm_pascal_ce.o nvidia-uvm/uvm_pascal_host.o
nvidia-uvm/uvm_pascal_mmu.o nvidia-uvm/uvm_pascal_fault_buffer.o
nvidia-uvm/uvm_volta_ce.o nvidia-uvm/uvm_volta_host.o
nvidia-uvm/uvm_volta_mmu.o nvidia-uvm/uvm_volta.o
nvidia-uvm/uvm_volta_fault_buffer.o
nvidia-uvm/uvm_volta_access_counter_buffer.o nvidia-uvm/uvm_turing.o
nvidia-uvm/uvm_turing_access_counter_buffer.o
nvidia-uvm/uvm_turing_fault_buffer.o nvidia-uvm/uvm_turing_mmu.o
nvidia-uvm/uvm_turing_host.o nvidia-uvm/uvm_ampere.o nvidia-uvm/uvm_ampere_ce.o
nvidia-uvm/uvm_ampere_host.o nvidia-uvm/uvm_ampere_mmu.o
nvidia-uvm/uvm_hopper.o nvidia-uvm/
[Kernel-packages] [Bug 195982] Re: Shift key (and caps lock) stop working when using VMWare
Wow, I did not expect this bug from 2008 to resurface in 2021! To quote myself in 2008: > As I'm using the free version of vmware, I can live with it until: > 1. They fix it > 2. VirtualBox becomes stable enough to use #2 happened many *many* years ago, so I can no longer test this issue, that was never really resolved beyond the sort-of-workaround with setxkbmap in over 12 years... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/195982 Title: Shift key (and caps lock) stop working when using VMWare Status in Linux: Invalid Status in linux package in Ubuntu: Won't Fix Status in xkeyboard-config package in Ubuntu: Invalid Status in Gentoo Linux: New Bug description: [Problem] VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys stopping functionality when running under VMWare, requiring the user to setup their configuration settings manually in VMWare. For a detailed explanation see the following article: http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html [Original Report] After a day or so of running the shift key mysteriously stops working as does the cap lock. In other words I cannot enter shifted characters of any kind. The keyboard is connected to a KVM and all other systems respond to it properly. In additional any VMWare sessions I have open respond correctly. So I have the condition where all non-vmware applications in Ubuntu Hardy (all updates applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT applications within an active (a paused/restarted session also works) VMWare sessions running DO recognize the key. When this condition occurs ALL applications (except those within a VMWare session) are also unstable and will usually crash within a few keystrokes.If I continue to operate in this mode. I cannot pinpoint what, if any, application triggers this. It has always happened while working within terminal/browser/vmware sessions and NOT when opening a new application. It could be related to the KVM switch, but none of my other systems (2 Mandriva, 1 Windows) are affected by this. This bug has been present on my system for a number of days across daily updates and reboots (if the update requested it) and I think since I installed Hardy Alpha 1. A work around: log off and back on. A reboot/restart does not appear to be needed. Error logs show some unusual activity. --- MARK ... ... kernel ... rtc lost 7 interrupts ... --- MARK --- Plus some segfaults indicating which application crashed as I tried to type into it (mouse works fine). System: HP dv9743cl (which otherwise works lovely) Ubuntu: Hardy 8.04 (from lsb-release) TEST CASE: 1. Click inside the VM and 2. Hold any of the Ctrl, Alt and/or shift keys while releasing the keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt to revert back to windowed mode, as the cursor is then released from the VM). WORKAROUND: After this happens to recover your keyboard execute 'setxkbmap' in a terminal To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/195982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907499] [NEW] Cheese says gives errors, cant use the webcam
Public bug reported: webcam Creative NX pro is detected in lsusb but does not work. has worked in Ubuntu linux many years back. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 9 21:46:43 2020 InstallationDate: Installed on 2020-11-11 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUS All Series RelatedPackageVersions: cheese3.34.0-1ubuntu1 cheese-common 3.34.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2907 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2907:bd03/11/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-P:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal gstreamer-error -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1907499 Title: Cheese says gives errors, cant use the webcam Status in linux package in Ubuntu: Incomplete Bug description: webcam Creative NX pro is detected in lsusb but does not work. has worked in Ubuntu linux many years back. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 9 21:46:43 2020 InstallationDate: Installed on 2020-11-11 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUS All Series RelatedPackageVersions: cheese3.34.0-1ubuntu1 cheese-common 3.34.0-1ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2907 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2907:bd03/11/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-P:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All 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/1907499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864258] [NEW] no sound since the last update
Public bug reported: no sound since the last update. quick fix to load the previous kernel solved the problem temporarily. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-41-generic 5.3.0-41.33 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Budgie:GNOME Date: Fri Feb 21 23:33:29 2020 InstallationDate: Installed on 2019-10-02 (142 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 840 G6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-41-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-41-generic N/A linux-backports-modules-5.3.0-41-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2019 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.02.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.4C.00 dmi.chassis.asset.tag: 5CG9363LM6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR70Ver.01.02.00:bd06/18/2019:svnHP:pnHPEliteBook840G6:pvr:rvnHP:rn8549:rvrKBCVersion52.4C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G6 dmi.product.sku: 7YM32ES#ABD dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan package-from-proposed ** Description changed: + no sound since the last update. quick fix to load the previous kernel solved the problem temporarily. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-41-generic 5.3.0-41.33 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Budgie:GNOME Date: Fri Feb 21 23:33:29 2020 InstallationDate: Installed on 2019-10-02 (142 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera - Bus 001 Device 003: ID 8087:0aaa Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera + Bus 001 Device 003: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 840 G6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-41-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.3.0-41-generic N/A - linux-backports-modules-5.3.0-41-generic N/A - linux-firmware1.183.4 + linux-restricted-modules-5.3.0-41-generic N/A + linux-backports-modules-5.3.0-41-generic N/A + linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2019 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.02.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.4C.00 dmi.chassis.asset.tag: 5CG9363LM6 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR70Ver.01.02.00:bd06/18/2019:svnHP:pnHPEliteBook840G6:pvr:rvnHP:rn8549:rvrKBCVersion52.4C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G6 dmi.product.sku: 7YM32ES#ABD dmi.sys.vendor: HP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864258 Title: no sound since the last update Status in linux package in Ubuntu: New Bug description: no sound since the last update. quick fix to load the previous kernel solved the problem temporarily. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-41-generic 5.3.0-41.33 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu
[Kernel-packages] [Bug 1594974] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build
same failure, please help. what can i do -- 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/1594974 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: just happened...no idea why ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-89.136-generic 3.13.11-ckt39 Uname: Linux 3.13.0-89-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 DKMSKernelVersion: 4.4.0-26-generic Date: Tue Jun 21 23:28:52 2016 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/shared/linux_osl.c:935:2: error: implicit declaration of function ‘rdtscl’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2015-10-16 (249 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS i386 (20150323) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.2 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1594974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1478623] Re: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test
This is an upstream Linux kernel bug, see here: https://bugzilla.kernel.org/show_bug.cgi?id=101011 ** Bug watch added: Linux Kernel Bug Tracker #101011 http://bugzilla.kernel.org/show_bug.cgi?id=101011 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1478623 Title: [4.1.0 regression] Kernel oops - blk_update_request: I/O error when running udisks2 force_test_removal test Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: We noticed that the udisks2 autopkgtest is failing on i386 in the "forced removal" test, for example https://jenkins.qa.ubuntu.com/job/wily-adt- udisks2/ARCH=i386,label=adt/55/console I reproduced this locally, on this kernel ubuntu@autopkgtest:~$ uname -a Linux autopkgtest 4.1.0-2-generic #2-Ubuntu SMP Wed Jul 22 18:17:34 UTC 2015 i686 i686 i686 GNU/Linux and got the following spewed to console fs: forced removal ... [ 303.782426] blk_update_request: I/O error, dev sdb, sector 0 [ 303.807400] BUG: unable to handle kernel paging request at 1afde000 [ 303.808010] IP: [] __percpu_counter_add+0x16/0x90 [ 303.808010] *pdpt = 0ee9b001 *pde = [ 303.808010] Oops: [#1] SMP [ 303.808010] Modules linked in: scsi_debug btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c ppdev kvm_intel kvm joydev serio_raw 8250_fintek parport_pc parport i2c_piix4 mac_hid autofs4 psmouse pata_acpi floppy [ 303.808010] CPU: 0 PID: 22573 Comm: umount Not tainted 4.1.0-2-generic #2-Ubuntu [ 303.808010] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.8.1-20150604_211837-tipua 04/01/2014 [ 303.808010] task: dc75e5e0 ti: ce85a000 task.ti: ce85a000 [ 303.808010] EIP: 0060:[] EFLAGS: 00010092 CPU: 0 [ 303.808010] EIP is at __percpu_counter_add+0x16/0x90 [ 303.808010] EAX: 0001 EBX: dbba9c08 ECX: EDX: 0001 [ 303.808010] ESI: EDI: EBP: ce85be6c ESP: ce85be54 [ 303.808010] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 303.808010] CR0: 8005003b CR2: 1afde000 CR3: 1e9c88c0 CR4: 07f0 [ 303.808010] Stack: [ 303.808010] c1aa7b40 0001 dbba9be8 decbfd60 ce85be88 c115bca4 [ 303.808010] 0008 ddce5228 ddce5228 decbfd60 decbfd70 ce85bea4 c11e47f9 [ 303.808010] 0286 ddce5228 d559cbd0 cdd41400 ce85beb4 c11e496f d3cc2000 [ 303.808010] Call Trace: [ 303.808010] [] account_page_dirtied+0x74/0xf0 [ 303.808010] [] __set_page_dirty+0x39/0xc0 [ 303.808010] [] mark_buffer_dirty+0x4f/0xb0 [ 303.808010] [] ext4_commit_super+0x168/0x220 [ 303.808010] [] ext4_put_super+0xc1/0x310 [ 303.808010] [] ? dispose_list+0x32/0x40 [ 303.808010] [] ? evict_inodes+0xda/0xf0 [ 303.808010] [] generic_shutdown_super+0x64/0xe0 [ 303.808010] [] ? unregister_shrinker+0x40/0x50 [ 303.808010] [] kill_block_super+0x1f/0x70 [ 303.808010] [] deactivate_locked_super+0x3d/0x70 [ 303.808010] [] deactivate_super+0x57/0x60 [ 303.808010] [] cleanup_mnt+0x39/0x90 [ 303.808010] [] __cleanup_mnt+0x10/0x20 [ 303.808010] [] task_work_run+0xb1/0xd0 [ 303.808010] [] do_notify_resume+0x53/0x70 [ 303.808010] [] work_notifysig+0x26/0x2b [ 303.808010] Code: 24 8b 54 24 04 83 c4 08 5b 5e 5f 5d c3 90 8d b4 26 00 00 00 00 55 89 e5 57 56 53 89 c3 89 d0 83 ec 0c 89 45 ec 89 4d f0 8b 7b 14 <64> 8b 37 89 7d e8 89 f7 c1 ff 1f 01 c6 11 cf 8b 4d 08 c1 f9 1f [ 303.808010] EIP: [] __percpu_counter_add+0x16/0x90 SS:ESP 0068:ce85be54 [ 303.808010] CR2: 1afde000 [ 303.808010] ---[ end trace bd84bb1a9fa3ebd4 ]--- [ 304.463429] scsi 2:0:0:0: Direct-Access Linuxscsi_debug 0184 PQ: 0 ANSI: 6 [ 304.468098] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 304.472038] sd 2:0:0:0: [sdc] 585728 512-byte logical blocks: (299 MB/286 MiB) [ 304.476079] sd 2:0:0:0: [sdc] Write Protect is off [ 304.476661] sd 2:0:0:0: [sdc] Mode Sense: 73 00 10 08 [ 304.484045] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 304.572090] sd 2:0:0:0: [sdc] Attached SCSI disk To reproduce, do something like this: $ adt-buildvm-ubuntu-cloud -r wily -a i386 # download a cloud image, fettle it a bit to be more useful $ qemu-system-i386 -m 2048 -net user -net nic,model=virtio -enable-kvm -nographic adt-wily* # login with ubuntu/ubuntu # apt-get update # apt-get dist-upgrade $ apt-get source udisks2 $ cd udisks2-* $ cat debian/tests/control # install the test-deps # debian/tests/upstream-system # runs the testsuite, when it gets to test_force_removal you should see this bug. the testsuite hangs too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478623/+subscriptions -- M
