Bug#941712: hfs partitions corrupted when removing lots of files over network
Hi Salvatore,
Thank you for following up on this. Unfortunately I can no longer test
this out. The hardware is no longer unavailable and since "upgrading" to
Catalina I can't get virtualbox running on my mac :(.
Given I can't test this out, would you like me to close the bug report?
Apologies, Graham.
On Sun, 6 Sep 2020 at 19:30, Salvatore Bonaccorso wrote:
> Hi
>
> I assume the issue might be fixed with 25efb2ffdf99 ("hfsplus: fix
> crash and filesystem corruption when deleting files") which was
> included upstream in 5.7-rc1 and was backported to 4.19.116 as well.
>
> Can you please do check if the issue is still prsent in up to date
> buster?
>
> Regards,
> Salvatore
>
Processed: reassign 962509 to zfs-initramfs
Processing commands for cont...@bugs.debian.org: > reassign 962509 zfs-initramfs Bug #962509 [initramfs-tools] Not always boot arguments must include a root= parameter Bug reassigned from package 'initramfs-tools' to 'zfs-initramfs'. No longer marked as found in versions initramfs-tools/0.133+deb10u1. Ignoring request to alter fixed versions of bug #962509 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 962509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition
Hi Nicolas, Not a direct help, but some comments: On Mon, Aug 17, 2020 at 07:12:32PM +0200, Nicolas Courtel wrote: > Package: src:linux > Version: 4.19.132-1 > Severity: normal > > Dear maintainer, > > After upgrading to kernel 4.19.0-10, writing to a GFS2 volume makes the kernel > output a series of messages, and the server quickly becomes unusable. Before > trying to write, mounting the volume and reading its content works as > expected. > > The problem is reproductible on 2 different servers, using FC and iSCSI. They > both work well otherwise, the normal behavior is restored after switching to > previous kernel 4.19.0-9 > > The kernel messages are the following: > > Aug 12 16:31:26 ertok kernel: [ 90.951413] BUG: unable to handle kernel > NULL pointer dereference at 0008 > Aug 12 16:31:26 ertok kernel: [ 90.951415] PGD 0 P4D 0 > Aug 12 16:31:26 ertok kernel: [ 90.951418] Oops: 0002 [#1] SMP PTI > Aug 12 16:31:26 ertok kernel: [ 90.951420] CPU: 2 PID: 2140 Comm: libvirtd > Not tainted 4.19.0-10-amd64 #1 Debian 4.19.132-1 > Aug 12 16:31:26 ertok kernel: [ 90.951420] Hardware name: HP ProLiant > DL360p Gen8, BIOS P71 02/25/2012 > Aug 12 16:31:26 ertok kernel: [ 90.951433] RIP: > 0010:gfs2_log_commit+0x104/0x400 [gfs2] > Aug 12 16:31:26 ertok kernel: [ 90.951435] Code: 60 4c 8d b3 dc 08 00 00 4c > 89 f7 e8 f6 90 d2 dd 48 8b 55 70 48 8d 45 70 48 39 d0 74 29 49 8b 4c 24 78 48 > 8b 75 70 48 8b 55 78 <48> 89 4e 08 48 89 31 49 8d 4c 24 70 48 89 0a 49 89 54 > 24 78 48 89 > Aug 12 16:31:26 ertok kernel: [ 90.951435] RSP: 0018:ad46c24dfba8 > EFLAGS: 00010282 > Aug 12 16:31:26 ertok kernel: [ 90.951437] RAX: 9caba6487b70 RBX: > 9cab8bc32000 RCX: > Aug 12 16:31:26 ertok kernel: [ 90.951437] RDX: RSI: > RDI: 9cab8bc328dc > Aug 12 16:31:26 ertok kernel: [ 90.951438] RBP: 9caba6487b00 R08: > 9caba6487b58 R09: 9caba33fe4d0 > Aug 12 16:31:26 ertok kernel: [ 90.951439] R10: 9cab54d8b000 R11: > R12: 9caba94f9200 > Aug 12 16:31:26 ertok kernel: [ 90.951440] R13: 9cab8bc327c8 R14: > 9cab8bc328dc R15: d40b0f4b1740 > Aug 12 16:31:26 ertok kernel: [ 90.951441] FS: 7f6a7cff9700() > GS:9cabaea8() knlGS: > Aug 12 16:31:26 ertok kernel: [ 90.951442] CS: 0010 DS: ES: CR0: > 80050033 > Aug 12 16:31:26 ertok kernel: [ 90.951443] CR2: 0008 CR3: > 0003ebfd6005 CR4: 000606e0 > Aug 12 16:31:26 ertok kernel: [ 90.951443] Call Trace: > Aug 12 16:31:26 ertok kernel: [ 90.951481] gfs2_trans_end+0x7d/0x160 [gfs2] > Aug 12 16:31:26 ertok kernel: [ 90.951492] gfs2_dirty_inode+0x1bc/0x240 > [gfs2] > Aug 12 16:31:26 ertok kernel: [ 90.951497] ? iomap_readpage+0x85/0x110 > Aug 12 16:31:26 ertok kernel: [ 90.951506] ? gfs2_dirty_inode+0x144/0x240 > [gfs2] > Aug 12 16:31:26 ertok kernel: [ 90.951511] __mark_inode_dirty+0x1ba/0x380 > Aug 12 16:31:26 ertok kernel: [ 90.951515] generic_update_time+0xb6/0xd0 > Aug 12 16:31:26 ertok kernel: [ 90.951518] touch_atime+0xbe/0xe0 > Aug 12 16:31:26 ertok kernel: [ 90.951522] > generic_file_read_iter+0x8ca/0xbc0 > Aug 12 16:31:26 ertok kernel: [ 90.951531] ? > gfs2_glock_add_to_lru.part.41+0x7c/0xd0 [gfs2] > Aug 12 16:31:26 ertok kernel: [ 90.951540] gfs2_file_read_iter+0xe3/0xf0 > [gfs2] > Aug 12 16:31:26 ertok kernel: [ 90.951544] new_sync_read+0xf8/0x160 > Aug 12 16:31:26 ertok kernel: [ 90.951547] vfs_read+0x91/0x140 > Aug 12 16:31:26 ertok kernel: [ 90.951549] ksys_read+0x57/0xd0 > Aug 12 16:31:26 ertok kernel: [ 90.951552] do_syscall_64+0x53/0x110 > Aug 12 16:31:26 ertok kernel: [ 90.951556] > entry_SYSCALL_64_after_hwframe+0x44/0xa9 > Aug 12 16:31:26 ertok kernel: [ 90.951558] RIP: 0033:0x7f6a91a43544 > Aug 12 16:31:26 ertok kernel: [ 90.951560] Code: 84 00 00 00 00 00 41 54 49 > 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 5b fc ff ff 4c 89 e2 48 89 ee 89 df > 41 89 c0 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 38 44 89 c7 48 89 44 24 08 e8 97 > fc ff ff 48 > Aug 12 16:31:26 ertok kernel: [ 90.951561] RSP: 002b:7f6a7cff84e0 > EFLAGS: 0246 ORIG_RAX: > Aug 12 16:31:26 ertok kernel: [ 90.951562] RAX: ffda RBX: > 0016 RCX: 7f6a91a43544 > Aug 12 16:31:26 ertok kernel: [ 90.951564] RDX: 2000 RSI: > 7f6a40104ed0 RDI: 0016 > Aug 12 16:31:26 ertok kernel: [ 90.951564] RBP: 7f6a40104ed0 R08: > R09: 7f6a4560 > Aug 12 16:31:26 ertok kernel: [ 90.951565] R10: 7f6a48d0 R11: > 0246 R12: 2000 > Aug 12 16:31:26 ertok kernel: [ 90.951566] R13: R14: > 0016 R15: 2001 > Aug 12 16:31:26 ertok kernel: [ 90.951568] Modules linked in: gfs2 dlm ses > enclosure sctp ip_gre ip_tunnel gre openvswitch nsh nf_nat_ipv6
Bug#964812: closed by Debian FTP Masters (reply to Ben Hutchings ) (Bug#964812: fixed in linux 5.8.3-1~exp1)
On Tue, 2020-09-01 at 11:19 -0700, David Awogbemila wrote: [...] > Thank you for the update! Just to confirm, does this mean the driver > will be available to future versions on Debian > (i.e. have the config options set so that the driver is available in > Debian Images)? > If so, what versions of Debian will this affect? (I'm guessing the > ones starting with linux 5.8?) Right, any change in stable will need to be done separately. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Bug#779159: marked as done (linux-image-3.16.0-4-686-pae: system hangs after login into graphic desktop)
Your message dated Sun, 6 Sep 2020 18:12:44 +0200
with message-id
and subject line Re: Bug#779159: linux-image-3.16.0-4-686-pae: system hangs
after login into graphic desktop
has caused the Debian Bug report #779159,
regarding linux-image-3.16.0-4-686-pae: system hangs after login into graphic
desktop
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
779159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt4-3
Severity: normal
Dear Maintainer,
I upgraded a Wheezy installation to Testing/Jessie. All in all it was without
big surprises.
Except that most of the time after some time (e.g. 15 seconds) after the login
via kdm into
the kde desktop the system hangs.
Staying at the login screen did not trigger these hangs.
I connected via ssh and inspected the dmesg output before logging in to kde.
When later the hang happened there was before always such an entry:
[ 12.423002] [ cut here ]
[ 12.423023] WARNING: CPU: 0 PID: 38 at
/build/linux-AmBmwr/linux-3.16.7-ckt4/include/linux/kref.h:47
kobject_get+0x35/0x40()
[ 12.423027] Modules linked in: acpi_cpufreq(+) processor loop fuse
parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 sg sd_mod
crc_t10dif crct10dif_generic crct10dif_common rtsx_pci_sdmmc mmc_core ahci
libahci rtsx_pci libata uhci_hcd ehci_pci mfd_core ehci_hcd scsi_mod usbcore
usb_common r8169 mii thermal thermal_sys
[ 12.423085] CPU: 0 PID: 38 Comm: kworker/0:1 Not tainted 3.16.0-4-686-pae #1
Debian 3.16.7-ckt4-3
[ 12.423090] Hardware name: Acer AOD270/JE01_CT , BIOS V1.03 01/03/2012
[ 12.423098] Workqueue: kacpi_notify acpi_os_execute_deferred
[ 12.423103] c154e9ac f57e1cf0 c1475f58 c1056ae4 c154eae4
0026
[ 12.423114] c154e9ac 002f c12511d5 c12511d5 0009 f4c4e974 0202
[ 12.423125] f57e1d00 c1056ba2 0009 f57e1d18 c12511d5 f4c4e900
c136e7dc
[ 12.423135] Call Trace:
[ 12.423146] [] ? dump_stack+0x3e/0x4e
[ 12.423155] [] ? warn_slowpath_common+0x84/0xa0
[ 12.423163] [] ? kobject_get+0x35/0x40
[ 12.423169] [] ? kobject_get+0x35/0x40
[ 12.423177] [] ? warn_slowpath_null+0x22/0x30
[ 12.423184] [] ? kobject_get+0x35/0x40
[ 12.423192] [] ? cpufreq_cpu_get+0x5c/0xa0
[ 12.423199] [] ? cpufreq_update_policy+0x1d/0x180
[ 12.423207] [] ? cpufreq_update_policy+0x180/0x180
[ 12.423220] [] ? cpufreq_set_cur_state.part.3+0x6e/0x75
[processor]
[ 12.423229] [] ? processor_set_cur_state+0x8a/0xc3 [processor]
[ 12.423242] [] ? thermal_cdev_update+0x96/0x120 [thermal_sys]
[ 12.423254] [] ? step_wise_throttle+0x40/0x70 [thermal_sys]
[ 12.423265] [] ? handle_thermal_trip+0x45/0x150 [thermal_sys]
[ 12.423275] [] ? thermal_get_temp+0x1d/0x3a [thermal]
[ 12.423285] [] ? thermal_zone_device_update+0x79/0xe0
[thermal_sys]
[ 12.423294] [] ? acpi_device_notify+0x16/0x18
[ 12.423301] [] ? acpi_ev_notify_dispatch+0x35/0x49
[ 12.423307] [] ? acpi_os_execute_deferred+0x11/0x1b
[ 12.423315] [] ? process_one_work+0x115/0x380
[ 12.423322] [] ? mod_timer+0x103/0x190
[ 12.423329] [] ? worker_thread+0xf3/0x470
[ 12.423336] [] ? __wake_up_locked+0x1f/0x30
[ 12.423343] [] ? create_and_start_worker+0x50/0x50
[ 12.423350] [] ? kthread+0x9b/0xb0
[ 12.423359] [] ? ret_from_kernel_thread+0x21/0x30
[ 12.423365] [] ? kthread_create_on_node+0x110/0x110
[ 12.423371] ---[ end trace 863dcb3f68f118cb ]---
On some tries there was such a message missing and then the hang did not
happen, so
I think this could be related.
I was able to collect one dmesg output right before the hang with some more
stack traces introduced by:
[ 179.269865] Watchdog detected hard LOCKUP on cpu 1
[ 184.271061] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by
3, t=5254 jiffies, g=6837, c=6836, q=171573)
Hangs happened also for some newer kernels (from experimantal, snapshot or
Jessie):
linux-image-3.19.0-trunk-686-pae_3.19-1~exp1_i386.deb
linux-image-3.18.0-trunk-686-pae_3.18.6-1%7Eexp1_i386.deb
linux-image-3.16.0-4-686-pae_3.16.7-ckt4-3_i386.deb
But on older kernels it seems not to happen (also from snapshot or Wheezy):
linux-image-3.14-2-686-pae_3.14.15-2_i386.deb
linux-image-3.10-3-686-pae_3.10.11-1_i386.deb
linux-image-3.2.0-4-686-pae_3.2.65-1_i386.deb
Also I assume this is probably specific to this computer:
Acer ASPIRE ONE D270-Dws
I am not confident if severity and the package I opened the ticket is
Processed: reassign 943370 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 943370 src:linux Bug #943370 [linux-image-amd64] linux-image-amd64: Elantech touchpad not working (elan_i2c) Bug reassigned from package 'linux-image-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #943370 to the same values previously set Ignoring request to alter fixed versions of bug #943370 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 943370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 939606
Processing commands for cont...@bugs.debian.org: > tags 939606 - moreinfo Bug #939606 [src:linux] linux-image-5.2.0-2-amd64: Fails to shutdown/reboot/suspend Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 939606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 944428 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 944428 src:linux 5.3.7-1 Bug #944428 [linux-image-amd64] linux-image-amd64: Laptop shutdown and restart function freezing. Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/5.3.7+1. Ignoring request to alter fixed versions of bug #944428 to the same values previously set Bug #944428 [src:linux] linux-image-amd64: Laptop shutdown and restart function freezing. Marked as found in versions linux/5.3.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 944428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 954821
Processing commands for cont...@bugs.debian.org: > close 954821 5.6.14-1 Bug #954821 [src:linux] Regression: cannot use external drive using a JMicron JMS566 chipset Marked as fixed in versions linux/5.6.14-1. Bug #954821 [src:linux] Regression: cannot use external drive using a JMicron JMS566 chipset Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 954821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 949505 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 949505 src:linux Bug #949505 [linux-image-amd64] NFS client nfs4_reclaim_open_state: unhandled error -521 Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/105. Ignoring request to alter fixed versions of bug #949505 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 949505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 954821 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 954821 src:linux 5.4.19-1 Bug #954821 [linux-image-amd64] Regression: cannot use external drive using a JMicron JMS566 chipset Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/5.4.19+1. Ignoring request to alter fixed versions of bug #954821 to the same values previously set Bug #954821 [src:linux] Regression: cannot use external drive using a JMicron JMS566 chipset Marked as found in versions linux/5.4.19-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 954821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954821 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 961566 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=207669
Processing commands for cont...@bugs.debian.org: > forwarded 961566 https://bugzilla.kernel.org/show_bug.cgi?id=207669 Bug #961566 [src:linux] Cannot boot an intel upboard device after kernel upgrade Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=207669'. > thanks Stopping processing here. Please contact me if you need assistance. -- 961566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 961566 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 961566 src:linux Bug #961566 [linux-image-amd64] Cannot boot an intel upboard device after kernel upgrade Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-image-4.19.0-9-amd64. Ignoring request to alter fixed versions of bug #961566 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 961566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 962708 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 962708 src:linux Bug #962708 [linux-image-amd64] Please build dummy_hcd and g_mass_storage modules Bug reassigned from package 'linux-image-amd64' to 'src:linux'. Ignoring request to alter found versions of bug #962708 to the same values previously set Ignoring request to alter fixed versions of bug #962708 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 962708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 964845 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 964845 src:linux Bug #964845 [linux-image-cloud-amd64] Please enable CONFIG_SUSPEND in the cloud image kernel Bug reassigned from package 'linux-image-cloud-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/105+deb10u4. Ignoring request to alter fixed versions of bug #964845 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 964845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 962003
Processing commands for cont...@bugs.debian.org: > notfound 962003 linux/5.4.19-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Ignoring request to alter found versions of bug #962003 to the same values previously set > found 962003 linux/5.5.13-2 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Marked as found in versions linux/5.5.13-2. > found 962003 linux/5.5.17-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Marked as found in versions linux/5.5.17-1. > found 962003 linux/5.6.7-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Marked as found in versions linux/5.6.7-1. > notfound 962003 linux-image-amd64/5.4.19-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-image-amd64 and version 5.4.19-1 do not appear to match any binary packages Ignoring request to alter found versions of bug #962003 to the same values previously set > found 962003 linux-image-amd64/5.5.13-2 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-image-amd64 and version 5.5.13-2 do not appear to match any binary packages Marked as found in versions linux-image-amd64/5.5.13-2. > found 962003 linux-image-amd64/5.5.17-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-image-amd64 and version 5.5.17-1 do not appear to match any binary packages Marked as found in versions linux-image-amd64/5.5.17-1. > found 962003 linux-image-amd64/5.6.7-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-image-amd64 and version 5.6.7-1 do not appear to match any binary packages Marked as found in versions linux-image-amd64/5.6.7-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 962003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959232: linux-image-5.5.0-2-amd64: system freeze after suspend-to-ram: potentially IRQ-related issue
Hi Maximilian, On Fri, May 01, 2020 at 11:56:00AM +0200, Maximilian Stein wrote: > Package: src:linux > Version: 5.5.17-1 > Severity: normal > > Dear maintainer, > > Occasionally my system freezes after waking up from suspend-to-ram. > More precisely, the KDE lock screen appears, I can type my passphrase, > but then the screen just stays black leaving me movable mouse. I > neither can switch to a virtual terminal (Strg+Alt+F1 etc.) nor kill > the session with SysRq+K. Rebooting with SysRqs still works though. > > Investigating the issues in the kernel logs reveals a message > indicating a NULL ptr derefererence in the kernel that is related to > IRQ (see below). > > My device was in suspend-to-ram since yesterday so the attached log > includes all messages since I opened the laptop lid. It was generated > using: > > journalctl -b-1 --dmesg --since today --quiet --no-hostname --grep > '^(?!iptables:)' > > Such freezes happen about once a week and since I got the device (so > it also happened with older kernels). > > The device is a Lenovo X1 Carbon 6th Generation with an Intel > i7-8650U with up-to-date BIOS running Debian Testing. > > Any help is highly appreciated. A similar report was done in SuSE https://bugzilla.suse.com/show_bug.cgi?id=1129258 Can you check if hte issue ist still present with a more recent kernel, ideally test up to 5.8.7-1 in unstable. If the issue is still present, it might be woth reporting it directly upstream to the linux-...@vger.kernel.org list. Regards, Salvatore
Bug#964839: Still happens on 5.7.17
Hi Felix, On Sat, Sep 05, 2020 at 10:53:59AM +0200, Felix Dörre wrote: > The behavior on: > Linux chinchilla 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23) x86_64 > GNU/Linux > is still the same: for the first suspend you need to enable the graphics > card manually. On any subsequent suspend the mechanic works. > > Could someone please look into this bug? It lies around since nearly a month > now with no reaction at all. There was an update for 5.8.7-1 yesterday to unstable (although the signed packages are not yet there). Could you test that one as well? Now if the issue is still present in 5.8.7 then if I understand you correctly then it is okay with 5.6.14-2, but is an issue first with 5.7.6-1. What you can try to do is, check if to bisect between the two stable upstream versions 5.6.14 and 5.7.6 and try to find the commit introducing the issue. If it is convicable enough that it introduced a bug we are probably on the lucky side (saying that because if you see the issue only with bbswitch, and a tainted kernel upstream might ask to reproduce the issue with an untainted kernel, or it is convicable a bug otherwise). Can you try those two things? So first check if 5.8.7 has the issue, if possible then confirm as well for the current mainline, and secondly if the issue is still present in 5.8.7, try to isolate the commit introducing the issue beween 5.6.14 and 5.7.6. Some help on how to do the bisect can be found in https://wiki.debian.org/DebianKernelReportingBugs https://wiki.debian.org/DebianKernel/GitBisect Regards, Salvatore
Processed: tagging 953545, severity of 953545 is important
Processing commands for cont...@bugs.debian.org: > tags 953545 - patch Bug #953545 [src:linux] linux-image-4.19: System unusably slow after Debian upgrade. Removed tag(s) patch. > severity 953545 important Bug #953545 [src:linux] linux-image-4.19: System unusably slow after Debian upgrade. Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 953545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953545 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 884622
Processing commands for cont...@bugs.debian.org: > close 884622 Bug #884622 [src:linux] Migrating VM with kernel 3.16 between xen hosts results in fs corruption / data loss Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 884622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 878216
Processing commands for cont...@bugs.debian.org: > close 878216 Bug #878216 [src:linux] Bug relating linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb and hyper-v gen2 vm Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 878216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 968335 968338
Processing commands for cont...@bugs.debian.org: > forcemerge 968335 968338 Bug #968335 [src:linux] kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120 Bug #968338 [src:linux] WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120 Merged 968335 968338 > thanks Stopping processing here. Please contact me if you need assistance. -- 968335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968335 968338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928526: linux-image-4.19.0-4-amd64: data corruption when swapping to encrypted SSD with LVM and TRIM enabled
Hi Simon, On Fri, Sep 20, 2019 at 10:42:17PM +0200, Salvatore Bonaccorso wrote: > Hi Simon, > > On Mon, May 06, 2019 at 10:28:09PM +0200, Simon Richter wrote: > > Hi, > > > > On 06.05.19 21:35, Simon Richter wrote: > > > > > I can probably test intermediate versions and/or changes in setup, but > > > this > > > is difficult to automate because "bad" runs require manual file system > > > repairs and every run requires LUKS setup to be repeated. > > > > FWIW, using a separate LV and swapon --discard=pages seems to work, so > > this is likely to be specific to swap files (which normally shouldn't be > > affected by discards, as their allocation doesn't change, but the kernel > > might have some default behaviour here that I'm not aware of). > > Possible for you to directly report that upstream, keeping the bug in > the loop? (is it still an issue with 5.2.x and 5.3)? Did you had a chance to check this? Regards, Salvatore
Bug#941712: hfs partitions corrupted when removing lots of files over network
Hi
I assume the issue might be fixed with 25efb2ffdf99 ("hfsplus: fix
crash and filesystem corruption when deleting files") which was
included upstream in 5.7-rc1 and was backported to 4.19.116 as well.
Can you please do check if the issue is still prsent in up to date
buster?
Regards,
Salvatore
Processed (with 5 errors): found 962003
Processing commands for cont...@bugs.debian.org: > found 962003 linux/5.8.7-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Marked as found in versions linux/5.8.7-1. > found 962003 linux-image-amd64/5.6.14-2 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-image-amd64 and version 5.6.14-2 do not appear to match any binary packages Marked as found in versions linux-image-amd64/5.6.14-2. > found 962003 linux-image-amd64/5.7.10-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-image-amd64 and version 5.7.10-1 do not appear to match any binary packages Marked as found in versions linux-image-amd64/5.7.10-1. > found 962003 linux-image-amd64/5.7.17-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-image-amd64 and version 5.7.17-1 do not appear to match any binary packages Marked as found in versions linux-image-amd64/5.7.17-1. > found 962003 linux-image-amd64/5.8.7-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-image-amd64 and version 5.8.7-1 do not appear to match any binary packages Marked as found in versions linux-image-amd64/5.8.7-1. > [p.s.: APPEARS that 'reportbug kernel' looks like finds bugs Unknown command or malformed arguments to command. > against linux-image-amd64 and so marking under those names Unknown command or malformed arguments to command. > too -- however, I note all this confusing versioning, Unknown command or malformed arguments to command. > unclear how to search for existing kernel bugs, many Unknown command or malformed arguments to command. > different metapackage names and so-on needs documenting on Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 962003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 942223 in 5.2.0-3, found 942223 in 5.2.17-1
Processing commands for cont...@bugs.debian.org: > notfound 942223 5.2.0-3 Bug #942223 [src:linux] SATA Hot Plug Seagate disks problem The source 'linux' and version '5.2.0-3' do not appear to match any binary packages No longer marked as found in versions linux/5.2.0-3. > found 942223 5.2.17-1 Bug #942223 [src:linux] SATA Hot Plug Seagate disks problem Marked as found in versions linux/5.2.17-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 942223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962003: Bug found still present In current debian Kernels
Hi, On Sun, Sep 06, 2020 at 06:53:56AM +0100, Simon Iremonger (debian) wrote: > Bug still present, affects for-example X201-Tablet, similar > hardware to T410 with Intel Graphics variant. > > > Affects at least debian kernels:- > > 5.6.0-2-amd64 5.6.14-2 > 5.7.0-2-amd64 5.7.10-1 > 5.7.0-3-amd64 5.7.17-1 Please do test as well the yesterday uploaded 5.8.7-1 but I suspect the bug is still present there. To isolate the issue it might be worth trying to bisect were the issue is introduced and ideally then reported upstream. Some hints are in https://wiki.debian.org/DebianKernelReportingBugs#Identifying_when_the_bug_was_introduced In particular if you found the introducing Debian revision, then do check the respective upstream stable versions, and then try to bisect to find the introducing commit. See https://wiki.debian.org/DebianKernel/GitBisect Hope this helps, Regards, Salvatore
Processed: notfound 962003 in linux-signed-amd64/5.6.14-2, notfound 962003 in linux-signed-amd64/5.7.10-1 ...
Processing commands for cont...@bugs.debian.org: > # not valid version for linux-signed-amd64 and issues tracked for source > package src:linux > notfound 962003 linux-signed-amd64/5.6.14-2 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-signed-amd64 and version 5.6.14-2 do not appear to match any binary packages No longer marked as found in versions linux-signed-amd64/5.6.14-2. > notfound 962003 linux-signed-amd64/5.7.10-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-signed-amd64 and version 5.7.10-1 do not appear to match any binary packages No longer marked as found in versions linux-signed-amd64/5.7.10-1. > notfound 962003 linux-signed-amd64/5.7.17-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-signed-amd64 and version 5.7.17-1 do not appear to match any binary packages No longer marked as found in versions linux-signed-amd64/5.7.17-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 962003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 962003
Processing commands for cont...@bugs.debian.org: > found 962003 linux/5.6.14-2 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Marked as found in versions linux/5.6.14-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 962003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 962003
Processing commands for cont...@bugs.debian.org: > found 962003 linux-signed-amd64/5.6.14-2 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-signed-amd64 and version 5.6.14-2 do not appear to match any binary packages Marked as found in versions linux-signed-amd64/5.6.14-2. > found 962003 linux-signed-amd64/5.7.10-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-signed-amd64 and version 5.7.10-1 do not appear to match any binary packages Marked as found in versions linux-signed-amd64/5.7.10-1. > found 962003 linux-signed-amd64/5.7.17-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang The source linux-signed-amd64 and version 5.7.17-1 do not appear to match any binary packages Marked as found in versions linux-signed-amd64/5.7.17-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 962003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 962003 in 5.6.14-1, found 962003 in 5.7.10-1
Processing commands for cont...@bugs.debian.org: > found 962003 5.6.14-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Marked as found in versions linux/5.6.14-1. > found 962003 5.7.10-1 Bug #962003 [src:linux] Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Marked as found in versions linux/5.7.10-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 962003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962003: Bug found still present In current debian Kernels
Bug still present, affects for-example X201-Tablet, similar hardware to T410 with Intel Graphics variant. Affects at least debian kernels:- 5.6.0-2-amd64 5.6.14-2 5.7.0-2-amd64 5.7.10-1 5.7.0-3-amd64 5.7.17-1 --Simon
